Cisco Bug: CSCvh96960 - Routed traffic gets dropped when "no port-channel limit" is configured and local vpc+ member is down
Sep 09, 2019
- Cisco Nexus 7000 Series Switches
Known Affected Releases
Symptom: Traffic incoming on layer 3 interface on either of the vPC peer , getting routed and sent across vpc+ peer-link (because local vPC member port is down) will be dropped upon reaching the peer. Conditions: 1. We need to have fabric-path with VPC. 2. The pkts have to hit the vpc switch from a CE intf (not a core intf). Hence, it is either from an orphan port or from one of the hosts hanging off of the vpc leg. 3. It has be an L3 routing case. Bridging cases are all fine. The pkt is destined to one of the hosts hanging off the vpc-leg. 4. We need to have the feature "no port-channel limit" configured. 5. We need to have a case where the vpc-leg is down forcing the pkt to go over the peer link. 6. The egress card has to be an M3 card (through which this pkt goes over the peer link).
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