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
We observe an VRRP issue with Interl E810-C/E823-L of ice driver on VPP 23.10, 24.10 and the latest codes from git.
Here are my test configurations and steps:
• 2 nodes with VPP on each node and one DPDK interface connected to each VPP
• The 2 test ports are connected directly by a fiber link.
Node1(82599 10G port, priority=200, vpp) <-> Node2(E823-L 10G port, priority=150, vpp)
Node1 VRRP config:
set interface state eth4 up
set interface ip address eth4 192.168.61.51/25
vrrp vr add eth4 vr_id 61 priority 200 accept_mode 192.168.61.50
vrrp proto start eth4 vr_id 61
Node2 VRRP config:
set interface state eth4 up
set interface ip address eth4 192.168.61.52/25
vrrp vr add eth4 vr_id 61 priority 150 accept_mode 192.168.61.50
vrrp proto start eth4 vr_id 61
At startup, node1 is master and node2 is backup.
Change node1 priority=100, node1 becomes backup and node2 becomes master.
Change node1 priority=200, node1 becomes master but node2 still remains master.
From “show interface” and “show error”, no VRRP packet is counted on node2 VPP.
It seems that when VRRP takes over as master, VPP no longer receives the VRRP advertisements from the other routers via E823-L port.
The same setup can work if we change VPP to keealived or just use another 82599 10G port on node2.
The text was updated successfully, but these errors were encountered:
We found that when node2 is switched to master, DPDK will call ice_macaddr_set. We conducted a test by commenting out this call and found that the issue disappeared, allowing VPP to normally receive 01:00:5e:00:00:12 VRRP packets. Could you please provide us with the contact information for DPDK ICE drvier maintenance?
We observe an VRRP issue with Interl E810-C/E823-L of ice driver on VPP 23.10, 24.10 and the latest codes from git.
Here are my test configurations and steps:
• 2 nodes with VPP on each node and one DPDK interface connected to each VPP
• The 2 test ports are connected directly by a fiber link.
Node1(82599 10G port, priority=200, vpp) <-> Node2(E823-L 10G port, priority=150, vpp)
Node1 VRRP config:
set interface state eth4 up
set interface ip address eth4 192.168.61.51/25
vrrp vr add eth4 vr_id 61 priority 200 accept_mode 192.168.61.50
vrrp proto start eth4 vr_id 61
Node2 VRRP config:
set interface state eth4 up
set interface ip address eth4 192.168.61.52/25
vrrp vr add eth4 vr_id 61 priority 150 accept_mode 192.168.61.50
vrrp proto start eth4 vr_id 61
From “show interface” and “show error”, no VRRP packet is counted on node2 VPP.
It seems that when VRRP takes over as master, VPP no longer receives the VRRP advertisements from the other routers via E823-L port.
The same setup can work if we change VPP to keealived or just use another 82599 10G port on node2.
The text was updated successfully, but these errors were encountered: