Cisco Bug: CSCun58850 - FEX/vPC resources not synced to standby when standby reload
Aug 03, 2016
- Cisco Nexus 7000 Series Switches
Known Affected Releases
Symptom: This bug happens for switch with FEX or VPC+ configuration on non-default vdc. Issue for FEX: A non-default VDC's FEX with an erroneously configured duplicate FEX id will keep trying to come online but will not succeed. The user should get an error message indicating a fex id is already in use but they don't receive a message. issue for vPC: Traffic destined to CPU, ingressing a vPC leg in vPC+ setup is blackholed. For example ARP will be incomplete Conditions: There are two ways to trigger this: 1. configure fex id or vpc in a non-default vdc in a dual sup setup in pre 6.2.8 version, reload standby sup or both active and standby sups, and switchover after system is in full redundancy. 2. ISSU from older version to version up to 6.2.8(including 6.2.8). note: fex id or vpc configured in default vdc doesn't have this issue. After ISSU or switchover, if user configure new fex id which already be configured in default vdc, the configuration will be denied and will show error msg "chassis id: xxx, already taken". The issue only happens for non-default vdc. vPC configuration in default vdc will work fine. note: for vpc this issue only happens when the vdc type include "f1" and only happens if vpc+ is configured on f1 cards. note: Already have fix in 6.2.8 for the switchover case. So reload standby and switchover won't trigger the issue in 6.2.8. But ISSU from older version to 6.2.8 will still trigger this. The fix for ISSU issue is in 6.2.10, so ISSU from older version to 6.2.10 should work fine.
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