Hi Team, Dear VPP Community,
We are currently using *VPP version 24.02* and have encountered an issue related to VRRP configuration. We would appreciate your guidance on this behavior. Setup Details - Two VMs configured in an active/backup redundancy model. - A VRRP instance (VR ID 101) is configured on interface eth0.1. - eth0.1 is associated with *FIB table 1*. - Both VMs participate in this VRRP instance, with one acting as *Master* and the other as *Backup*. - In this setup, the Backup VM is able to successfully ping the VRRP VIP. Issue Observed When we configure a second VRRP instance with the *same VR ID (101)* on a different interface (eth0.2), where: - eth0.2 belongs to a separate FIB table (FIB table 2), we observe the following behavior: - The Backup VM is no longer able to ping the VRRP VIP of the first VRRP instance. - This functionality was working correctly prior to configuring the second VRRP instance. Additional Observation - After restarting the VPP service, the ping to the first VRRP VIP from the Backup VM starts working again. - We understand that using the same VR ID results in the same Virtual MAC address. - However, we are unsure why restarting VPP restores correct behavior. Query 1. Is this an expected behavior when using the same VR ID across different interfaces and FIB tables? 2. Could this be a known issue or limitation in VPP 24.02? 3. Are there any recommended best practices for handling VRRP instances across multiple FIB tables? Please let us know if additional logs, configuration snippets, or packet captures would help in analyzing the issue further. Thank you in advance for your support. regards Inder
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26849): https://lists.fd.io/g/vpp-dev/message/26849 Mute This Topic: https://lists.fd.io/mt/118013037/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
