Cisco Bug: CSCsz74831 - vPC failed commands are logged in "sh accounting log" as success
Aug 02, 2016
- Cisco Nexus 5000 Series Switches
- Cisco Nexus 5020 Switch
- Cisco Nexus 5010 Switch
Known Affected Releases
Symptom: DCNM and the N5K switch are out of sync related to vPC. Conditions: Consider, there is a port-channel interface x, configured with vPC domain-ID 10. Now, if you try to configure the same port-channel with vPC domain-ID 20, device will throw an error saying, "ERROR: Operation failed: [vPC already exists]". But, in the accounting log, the configuration command status will be saved as "SUCCESS". Since, DCNM rely on the accounting log for syncing itself with the switch on offline changes ( changes not done via DCNM ), when it reads the accounting log, it will think that the port-channel x is configured with vPC domain-ID 20, so it will replace the domain-ID 10 with 20. Same is the case when user configured two port-channels as peer-links.
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