After restart NIC, keepalived can not become master state about keepalived HOT 6 CLOSED

After you restart the NIC can you please run tcpdump with filter "proto 112" (i.e. the VRRP protocol) on the system on which you restarted the NIC?

What happens if you do:

ip link set <src-nic> down
sleep 10
ip link set <src-nic> up

Does that work for you or not?

I don't experience a problem when doing the above, so it will be interesting to know what happens for you.

Also, after you have done the ifdown/ifup, can you ping the unicast-peer address from the master, and vice versa?

from keepalived.

After you restart the NIC can you please run tcpdump with filter "proto 112" (i.e. the VRRP protocol) on the system on which you restarted the NIC?

After I restart the NIC, tcpdump can capture the incoming "proto 112" package. But when I stop keepalived on another host, it will not send VRRP package, there is noting happend.

ip link set <src-nic> down
sleep 10
ip link set <src-nic> up

Does that work for you or not?

Yes, it works for me, host can become master.

Also, after you have done the ifdown/ifup, can you ping the unicast-peer address from the master, and vice versa?

Yes, I can ping the unicast-peer address from the master, and vice versa.

from keepalived.

Are you using the NetworkManager ifup/down, or the network-scripts ifup (in other words is /usr/sbin/ipup a link to /usr/libexec/nm-ifup or to /etc/sysconfig/network-scripts/ifup?

If you are using the NetworkManager version, can you try executing

nmcli connection load /etc/sysconfig/network-scripts/ifcfg-<src-nic>
nmcli connection down filename /etc/sysconfig/network-scripts/ifcfg-<src-nic>
sleep 10
nmcli connection up filename /etc/sysconfig/network-scripts/ifcfg-<src-nic>

and see if keepalived works properly after that.

from keepalived.

Are you using the NetworkManager ifup/down, or the network-scripts ifup (in other words is /usr/sbin/ipup a link to /usr/libexec/nm-ifup or to /etc/sysconfig/network-scripts/ifup?

It is link to /etc/sysconfig/network-scripts/ifup, not NetworkManager ifup/down

from keepalived.

Since you are using the NetworkManager versions of ifup/down, can you please try executing the following are advise what happens:

nmcli connection load /etc/sysconfig/network-scripts/ifcfg-<src-nic>
nmcli connection down filename /etc/sysconfig/network-scripts/ifcfg-<src-nic>
sleep 10
nmcli connection up filename /etc/sysconfig/network-scripts/ifcfg-<src-nic>

from keepalived.

Apologizes for the inconvenience, but I'm unable to provide further testing information at this time due to the removal of the testing environment. I will be closing this issue.

from keepalived.