You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know the FRR VRRP needs 5.1 kernel and above so that is why I am using RHEL9 because it has the latest 5.24 kernel. I also tried a RHEL8 with a newly compiled 6.3.9 kernel but it is pretty much the same behavior below. I also tried RHEL8 with 5.4.249 kernel from the ELREPO.
FRRv8.5.2
ISSUE: Using RHEL9.2 kernel 5.24 as base os for FRR with VRRP feature does not show correct behavior.
First: The vrrp failover from backup to master takes anywhere from 10-20seconds. On Ubuntu the failover is sub-second.
Second: The "OSPF redistribute connected" advertises the interface subnet that is configured with VRRP even when it is on "VRRP backup" state. I don't think that is the correct behavior. On Ubuntu FRR it only advertise the "OSPF redistribute connected" when VRRP takes over as "VRRP Master".
Third: I am not getting the correct mac address for the VRRP vip. Ultimately, I think this is the reason why the VRRP convergence is taking a long time since the mac address change. As I ping through the VRRP vip and when I list the arp cache using "ip neighbor" the mac address is not what I defined using the nmcli command below. The "ip add" and "nmcli" shows the correct mac-address. Ubuntu FRR works just fine..
The parent eth2 mac (IP 192.168.22.27) and the the vrrp vip mac (IP 192.168.22.1) is the same.
FRR striped down config
RHEL details
I used Network Manager to configure interfaces. I used the same commands on both RHEL and Ubuntu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Does anybody uses FRR with VRRP on RHEL?
I know the FRR VRRP needs 5.1 kernel and above so that is why I am using RHEL9 because it has the latest 5.24 kernel. I also tried a RHEL8 with a newly compiled 6.3.9 kernel but it is pretty much the same behavior below. I also tried RHEL8 with 5.4.249 kernel from the ELREPO.
FRRv8.5.2
ISSUE: Using RHEL9.2 kernel 5.24 as base os for FRR with VRRP feature does not show correct behavior.
First: The vrrp failover from backup to master takes anywhere from 10-20seconds. On Ubuntu the failover is sub-second.
Second: The "OSPF redistribute connected" advertises the interface subnet that is configured with VRRP even when it is on "VRRP backup" state. I don't think that is the correct behavior. On Ubuntu FRR it only advertise the "OSPF redistribute connected" when VRRP takes over as "VRRP Master".
Third: I am not getting the correct mac address for the VRRP vip. Ultimately, I think this is the reason why the VRRP convergence is taking a long time since the mac address change. As I ping through the VRRP vip and when I list the arp cache using "ip neighbor" the mac address is not what I defined using the nmcli command below. The "ip add" and "nmcli" shows the correct mac-address. Ubuntu FRR works just fine..
The parent eth2 mac (IP 192.168.22.27) and the the vrrp vip mac (IP 192.168.22.1) is the same.
FRR striped down config
RHEL details
I used Network Manager to configure interfaces. I used the same commands on both RHEL and Ubuntu
Beta Was this translation helpful? Give feedback.
All reactions