Re: Keepalived on vmware
"M. Piscaer" <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
On 25-05-16 11:02, Patrick Schaaf wrote: > Hello Michiel, > > On Wednesday 25 May 2016 10:22:30 M. Piscaer wrote: >> >> We are running keepalived within an vmware guests. >> ... >> This means that the arp entry in the router still points to lb02 instead >> lb01. >> >> What can we do to solve this issue? > > In your vrrp_instance, use > garp_master_refresh 5 > garp_master_refresh_repeat 1 > > or something similar. garp_master_refresh_repeat is the crucial thing: it > makes the GARP (of the master instance) repeat regularly for as long as the > master stays master. > Thanks for your response, I don't think this will solve my problem. The problem is that lb01 never saw that it was offline. So it thinks it was the master all the time. lb02 sees that lb01 is back online and it stops sending vrrp messages. So lb01 never got any vrrp messages from lb02, - so I don't see any log messages like "VRRP_Instance(internet_interface4) Received lower prio advert, forcing new election" in lb01. - so it never send any garp messages - so the router has an incorrect arp entry. I can repredus it with: 1. On lb01 run: iptables -I OUTPUT 1 -d 224.0.0.18 -j DROP; iptables -I INPUT 1 -d 224.0.0.18 -j DROP This will set the lb02 in master state 2. after lb02 is in master state run on lb01: iptables -D OUTPUT 1; sleep 1; iptables -D INPUT 1; Kinds regards, Michiel Piscaer ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j