S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - f e e d b a c k - d o c @ c i s c o . c o m
2-620
Cisco NX-OS System Messages Reference
OL-15994-03
Chapter 2 System Messages and Recovery Procedures
STP Messages
Error Message
STP-2-DISPUTE_CLEARED: Dispute resolved for port [chars] on [chars].
Explanation
The listed interface has stopped receiving Inferior BPDUs with designated role and
state as learning and/or forwarding. The Dispute has been resolved and if the port is still designated,
it will be taken out of the blocking state as and when appropriate.
Recommended Action
No user action is required.
Error Message
STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars].
Explanation
The spanning tree has detected a Dispute on this interface. The BPDU received from
the peer is Inferior with designated role and state as learning and/or forwarding. Since this condition
could be caused by an unidirectional link failure, the interface is put into blocking state and marked
as disputed in order to prevent possible loops from being created.
Recommended Action
Issue the <CmdBold>show spanning-tree inconsistentports<noCmdBold>
command to review the list of interfaces with Dispute. Dispute is caused if the peer is not receiving
the Superior BPDUs sent by this interface. That is why the peer continues to send its own Inferior
BPDUs. Determine why devices connected to the listed ports are not receiving BPDUs. One reason
could be a failure in the cable: if the link has a failure that makes it unidirectional (you cannot
transmit but you can receive) it should be replaced with a proper cable.
Error Message
STP-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode =
[dec], Error code = [hex]
Explanation
STP has detected an error in processing an MTS message. The error and message are
specified in the error message.
Recommended Action
No action is required.
Error Message
STP-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on [chars].
Explanation
The spanning tree message age timer has expired because no BPDUs were received
from the designated bridge. Since this condition could be caused by an unidirectional link failure,
the interface is put into blocking state and marked as loop guard inconsistent in order to prevent
possible loops from being created.
Recommended Action
Issue the <CmdBold>show spanning-tree inconsistentports<noCmdBold>
command to review the list of interfaces with loop guard inconsistencies. Determine why devices
connected to the listed ports are not sending BPDUs. One reason could be that they do not run the
spanning tree protocol; in this case you should disable loopguard in the inconsistent interface/s or
start the spanning tree protocol on the other side of the links depending on the context. Another
reason could be a failure in the cable: if the link has a failure that makes it unidirectional (you can
transmit but you cannot receive) it should be replaced with a proper cable.
