Cisco Bug: CSCvu53702 - Add support for secondary IPs on L3out on different subnets
Aug 25, 2020
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: Depending on hashing of traffic withing the ACI fabric, at least 1/2 of traffic will drop because it reaches a leaf that does not have an adjacency for the next-hop on the L3out and is unable to forward the traffic. All but one leaf will not have this adjacency because the ARP requests are dropped when they are forwarded between the leaf switches in the ACI fabric before being flooded out the other leaf's interfaces. When the problem happens you will see ARP entries are not learned for next-hop IPs on the L3out BD for all but one leaf that have this L3out configured. Conditions: One or more Secondary IPs have been configured on an L3out. These Secondary IPs are for a different subnet from the side-a and side-b IPs configured on the L3out. Currently this behavior has only been seen when more than 1 leaf has the L3out BD.
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