I came across a situation where a virtual ip address is configured to two linux box sharing a virtual ip address
(each physical linux machines have their own ip address, however, for high availability a virtual IP address was
configured).
Above output shows arp entry for virtual address is binded to Server A. If Server A goes down, it takes a while
for arp entry to clear and this may cause an outage while new mac is binded to Server B.
My ideas were:
1. Create ip sla to ping to the ip address to primary server, if no response action is to clear ip arp for the virtual
ip address
2. reduce arp aging time
Any ideas?
2015 Cisco and/or its affiliates. All Rights Reserved. Generated on 2015-05-24-07:00
This document is Cisco Public Information.
1
ARP and Virtual IP address for servers
Did someone just go and run something like "ifconfig eth0:1 192.168.14.233 netmask 255.255.255.0" ? What
happens when the primary fails? Does someone go and manually add the IP to the secondary system?
Or is something like keepalived used to provide VRRP, and handle failure detection and failover?
Tools like keepalived will handle the GARP, and are overall a much better solution than trying to do something
with EEM. Remember that clustering is widely configured these days, and reasonably well understood. Better
to leverage off those solutions at a server level than try a "Stupid Router Trick". It will give you a more scalable,
easier to understand solution.
2015 Cisco and/or its affiliates. All Rights Reserved. Generated on 2015-05-24-07:00
This document is Cisco Public Information.
2