OPERATIONAL DEFECT DATABASE
...
...
When a Nexus switch generates a syslog indicating that a Spanning Tree Protocol Dispute has been detected, the syslog looks like this: 2022 Jan 28 15:25:03 switch %STP-2-DISPUTE_DETECTED: Dispute detected on port port-channel1 on VLAN0010. Identifying the source of the Spanning Tree Protocol BPDUs causing this Dispute scenario can be difficult if the Dispute scenario intermittently occurs.
This issue is observed when a Nexus switch encounters a Spanning Tree Protocol Dispute scenario.
At present, identifying the Bridge ID and source MAC address of the offending Spanning Tree BPDU must be done through an Ethanalyzer control plane packet capture during the time of the issue.
This software defect enhances the Spanning Tree Protocol Dispute such that the Bridge ID and source MAC address of the offending BPDU is displayed, which allows operators to easily trace the bridge causing the issue.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
