-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EVPN] When VRF to VNI map gets processed before VLAN to VNI mapping, it results in fails to create VLAN to VNI mapping #11428
Comments
orchagent/vxlanorch.cpp#L2218 As part of Vlan to VNI mapping, createTunnelHw() will be called and isActive() will be set. |
Thanks. Can you please fix this flow and raise PR? |
…map creation flow (#2404) Same as PR #2387 - What I did To fix issue sonic-net/sonic-buildimage#11428 Modified the logic of tunnel map creation to create tunnel with tunnel map for vlan-vni map in addition to vrf-vni map when tunnel is created first time in the VRF-VNI map processing flow. Modified the tunnel stats interval to 10 sec Modified the logic to create bridge port for p2mp tunnel only when p2p tunnel is not supported - Why I did it During the configuration phase when VRF-VNI map arrives before VLAN-VNI map, the tunnel is created without a tunnel map for vlan-vni membership. This is problematic when VLAN to VNI map arrives later, tunnel map entry cannot be created since the tunnel map doesn't exist and its a create only attribute in SAI. - How I verified it Modified UT to add VRF-VNI map first and VLAN-VLAN map later
…map creation flow (#2404) Same as PR #2387 - What I did To fix issue sonic-net/sonic-buildimage#11428 Modified the logic of tunnel map creation to create tunnel with tunnel map for vlan-vni map in addition to vrf-vni map when tunnel is created first time in the VRF-VNI map processing flow. Modified the tunnel stats interval to 10 sec Modified the logic to create bridge port for p2mp tunnel only when p2p tunnel is not supported - Why I did it During the configuration phase when VRF-VNI map arrives before VLAN-VNI map, the tunnel is created without a tunnel map for vlan-vni membership. This is problematic when VLAN to VNI map arrives later, tunnel map entry cannot be created since the tunnel map doesn't exist and its a create only attribute in SAI. - How I verified it Modified UT to add VRF-VNI map first and VLAN-VLAN map later
…map creation flow (sonic-net#2404) Same as PR sonic-net#2387 - What I did To fix issue sonic-net/sonic-buildimage#11428 Modified the logic of tunnel map creation to create tunnel with tunnel map for vlan-vni map in addition to vrf-vni map when tunnel is created first time in the VRF-VNI map processing flow. Modified the tunnel stats interval to 10 sec Modified the logic to create bridge port for p2mp tunnel only when p2p tunnel is not supported - Why I did it During the configuration phase when VRF-VNI map arrives before VLAN-VNI map, the tunnel is created without a tunnel map for vlan-vni membership. This is problematic when VLAN to VNI map arrives later, tunnel map entry cannot be created since the tunnel map doesn't exist and its a create only attribute in SAI. - How I verified it Modified UT to add VRF-VNI map first and VLAN-VLAN map later
Description
When VRF – VNI mapping arrives before VLAN – VNI mapping (It happens all the time during config reload), the VxLAN tunnel gets created with just VRF to VNI mapper. This is an issue because the encap mappers and decap mappers are create only attributes in tunnel and cannot be added when vlan to vni mapping arrives later. In all other places VLAN to VNI and VRF to VNI are created together and set in tunnel. Is the below case intentional or should be fixed? I also see the createTunnel is used only in this place and all other places use createTunnelHw which almost has same functionality. Should createTunnel be removed?
https://github.com/Azure/sonic-swss/blob/93af69c5cb9a78465604974b59d1b1ed709d2b10/orchagent/vxlanorch.cpp#L2220
Steps to reproduce the issue:
Describe the results you received:
VLAN to VNI mapping creation fails
Describe the results you expected:
VLAN to VNI mapping should succeed
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: