|
I've seen a similar delay in failover when using cisco routers. They
don't update the internal MAC address table after receiving gratuitous
arp packets during an LVS director failover event. I don't know if the
heartbeat package uses arps to fail over, but keepalived does. Cisco
routers seem to need icmp packets before they'll update the MAC address
table. For LVS, the problem here is that the router continues to send
traffic to the VIP at the master's hw address instead of shifting to the
backup's hw address.
However, this wouldn't explain why your real servers route to the wrong
address. The real servers and the LVS directors are on the same network
segment, right? And are the LVS directors configured with dual network
adapters?
Thanks,
-jrr
On Tue, 2004-04-20 at 12:52, Sean Roe wrote:
> I am having an issue with my LVS setup. I have 12 web servers behind 2
> LVSes (setup for redundancy and fall over) they are set up for LV-NAT
> and they work fine. My issue is when the primary fails over to the
> secondary. It seems to take several minutes (~5) for the fallover to
> complete. Any ideas why?
>
> Here is the real weirdness: The http servers are set to route to
> 10.4.2.46 but when I do a traceroute it hits 10.4.2.43 as its first hop.
|
