Re: VRRP behavior on network restart

Can anyone please answer?

-----Original Message-----
From: Amir Dafny-Man 
Sent: Thursday, May 05, 2016 08:32
To: [email protected]
Subject: VRRP behavior on network restart

Hi,

I am using Keepalived on RHEL6, using Redhat's latest version (1.2.13).
I noticed that after the network is restarted (service network restart), multiple errors appear in the log:
May  2 12:55:30 sdclab006-09 Keepalived_vrrp[14885]: Netlink: filter function error After that Keepalived does not bring the VIP up anymore.
I have seen in an old email from this list that Keepalived does not handle well interfaces taken down and a configuration reload (kill -HUP) is required to correct this situation.

>From 1.2.20 changelog:
* vrrp: Dynamic addition of interfaces from netlink msg.
  When a tracked interface is deleted then recreated with the same config
  VRRP groups tracking this interface will remain down. This is due to
  tracking of stale information.
  This patch listens for netlink messages for the creation of interfaces
  and does one of two things.
  i) If the interface doesn't exist in the vrrp interface list a new
  interface structure is created and the information from the message is
  used to fill the structure. This new interface is then added to the
  interface queue.
  ii) If the interface already exists in the queue we zero it and then
  use the information in the message to fill the structure.

Does this change the behavior experienced above or do I still need to reload configuration after network restart?

Thanks,
Amir
------------------------------------------------------------------------------
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