Cisco Bug: CSCur47356 - Incorrect endpoints(over 3000EPs) convergence
Sep 11, 2019
- Cisco Nexus 9000 Series Switches
Known Affected Releases
Symptom: 1. After node mobility, all EPs on Border-Leaf4 should point to Leaf2. But some of EPs entries still pointed to Leaf1. <Leaf4 endpoints> 53/cisco:nw1 vxlan-14909417 0011.9400.0a04 tunnel9 (to leaf2) 53/cisco:nw1 vxlan-14909417 0011.9400.0d81 tunnel9 (to leaf2) 53/cisco:nw1 vxlan-14909417 0011.9400.0dd7 tunnel8 (to leaf1) wrong 53/cisco:nw1 vxlan-14909417 0011.9400.0dd8 tunnel8 (to leaf1) wrong 2. Some entries on Leaf1 didn't bounce.(Not flagged as bounce) <Leaf1 endpoints> 79/cisco:nw1 vxlan-14909417 0011.9400.09b6 B tunnel3 79/cisco:nw1 vxlan-14909417 0011.9400.0a86 B tunnel3 79/cisco:nw1 vxlan-14909417 0011.9400.141a tunnel3 wrong 79/cisco:nw1 vxlan-14909417 0011.9400.0c13 tunnel3 wrong 3. It takes several minutes until all 6K EP flows are normal. Conditions: [Test Condition] -6K endpoints(Only MAC address /EP) made by tester. Half of FCS ACI capacity. -Bidirectional L2 6K flows, 100fps/flow -Use Flexlink to virtualize node mobility. Shut one of flexlinks on L2SW at the bottom of topology. Then 6K EPs move from Leaf1 to Leaf2(We call it node mobility). I confirmed the issue when EPs were 3K or 6K. In case of 1K EPs, it doesn't happen.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases