I had tested quite a bit in 3.7 in a lab environment, never found an
issue. Now this is 3.8 in production for my business network. I
just pulled the patch cable from the switch for the WAN NIC on the
master node. Poof the FW service switched to the backup node. I
then plugged the patch cable back into the switch and the FW service
switched back to the master node. All expected.
I pulled the LAN patch cable on the master node, FW switched over
again. When I plugged the LAN patch cable back in the FW service did
_not_ switch back to the master node. :( Though the 'backup' node
continued providing the FW service. I tried unplugging the LAN cable
again, no change. FW stayed on the 'backup' node.
I checked both the WAN and LAN physical interfaces and both were
active and had link. I tried 'ifconfig rl0 down' and then up but
still the FW services remained on the backup node.
I rebooted the master node and when it came back up the FW service
moved from the backup node to the master node.
I also discovered that since I'm also running squid and privoxy on
these machines and via a transparent proxy setup I need to adjust the
startup sequence so that squid/privoxy get time to startup before the
CARP interfaces are brought up.
-Chad
On Nov 22, 2005, at 3:46 PM, Eli K. Breen wrote:
Have you tried simply unplugging one's network cable? (to more
closely replicate what would happen during a hard lock or panic?) I
should think things won't be as smooth. Additionally, what happens
if you shut the master down in to Single-User mode?
I'm seeing a bug where if the MASTER is shutdown to single user
mode it stops the BACKUP from becoming MASTER. ...which is somewhat
disturbing as the original MASTER no longer actually performs any
useful network functions, but it does prevent takeover of the ARP
address.
Has anyone else tested/run in to this?
-Eli
