Unable to ping to Virtual IP address outside the subnet after failover to second node.
Article ID: 100004189
Updated On:
Cause
Gateway / router at customer configuration does not support “ARP Reply”.
This issue is tracked via Symantec etrack incident # e2220533 to support both ARP REQUEST and ARP REPLY in future releases.
Resolution
Workaround:
Modify /opt/VRTSvcs/bin/IP/online file for IP agent to allow router/gateway ARP REQUEST.
from:
`$arping -A -c 5 -I $Device $Address`;
to:
`$arping -U -c 5 -I $Device $Address`;
Applies To
RHEL 5
VCS 5.1 SP1 and below
Issue/Introduction
On a two node Linux cluster, an IP resource is configured as a virtual IP over a bonded network interface. The IP address could be pinged from outside the subnet when the resource is online on the first node. However, when the IP resource is failed over to the second node, the IP address could not be pinged from outside the subnet. Ping requests to IP address (VIP) starts responding after waiting for over five minutes. Ping requests to VIP also responds if a manual gratutious ARP request is sent.
Additional Information
ETrack: 2220533
Was this article helpful?
Yes
No
Powered by
