On Nov 15, 2007, at 12:19 PM, Scott Comboni wrote:
Hello all,
Well It seems the 10.4.11 release seems to have solved a few
issues. I can now take over my Primary machine in full failover
Great!! so that is working. Releasing is my new issue. When I
reboot the Primary the Seconday sees the machine up on the Firewire
IP, releases control but the Primary machines en0: IP is not
starting up.
I remote logged into the Primary servers FW IP and saw this in the
logs.
I noticed that primary server is trying to hit the backup servers
Public address and showing steady errors in /var/log/system.log
heartbeat[214]: Unable to send to 192.168.1.20: No route to host (65)
heartbeat[214]: Unable to send to 192.168.1.20: Host is down
Of course the reason being is my Public address en0: card is down
and not showing an IP
Then you have a routing problem. If an NI is down it shouldn't be
getting used as a primary route.
Is your subnet for heartbeat completely different from your other
subnets??? If so the above should not be occurring.
Any ideas why the primary machines en0 would not startup?
Because the IP is already in use?
What's your routing tables show and what does ifconfig say?
-dhan
------------------------------------------------------------------------
Dan Shoop
Computer Scientist
iWiring / U.S. Technical Services
email@hidden
AOL IM .................... iWiring
Nextel .................... 1-714-363-1174
Operations TOC (24/7) ..... 1-866-901-USTS
USTS Offices .............. 1-714-374-6300
For immediate response for urgent matters please speak to the Duty
Officer
at the USTS Tactical Operations Center (above) who can reach me by
radio.
