Red Hat Bugzilla – Bug 211981
LVS VIP unreachable when interfaces are restarted
Last modified: 2009-04-16 16:23:44 EDT
Description of problem:
A service network restart or ifdown/ifup on the interface to which the LVS VIP
is bound causes the VIP to become unreachable until the pulse service is also
The monitor_links option is enabled on both LVS routers.
This is related to bug 164576 and bug 160103 (in bug 160103 ifdown was suggested
as a means to test monitor_links but this does not work).
Steps to Reproduce:
1. Configure an LVS router with backup
2. Enable monitor_links on both LVSs
3. Run service network restart or ifdown/ifup
The VIP is not reinstated on the primary when the interface is brought back up
and does not fail over to the backup when the interface is brought down.
The VIP should be reinstated on the primary LVS router when the interface comes
back up. Failing over to the secondary LVS may also be an option but this does
not happen either.
Ping. Any news on this?
Stan, any update on this one. Support is asking. I put it on the requested
list for 4.5.
I've updated 160103 to note that you actually have to pull the cable, and linked
to the correct test procedure, which is listed in #164576:
I think restarting the interfaces is a "don't do that" case which can be release
noted (e.g. if you do this, you must restart pulse, too).
To fix it, I think what would need to be done is that piranha would have to be
able to detect this event (hard? probably stuff in netlink to figure this out)
and issue a gratuitous ARP for each VIP (not hard).
Reassigning to component owner