Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

What is the mean "%STP-2-DISPUTE_DETECTED" ?

Hi.

We test the Nexus as daisy chain.

but When we attach the port to port in the same module, We got the following log :

"%STP-2-DISPUTE_DETECTED"

I had searched the log on CCO, but I can't find exactly what mean is.

If you know the log, Please let me know as soon as possibly

Thanks in advance.

4 REPLIES
Hall of Fame Super Blue

Re: What is the mean "%STP-2-DISPUTE_DETECTED" ?

syjeon wrote:

Hi.

We test the Nexus as daisy chain.

but When we attach the port to port in the same module, We got the following log :

"%STP-2-DISPUTE_DETECTED"

I had searched the log on CCO, but I can't find exactly what mean is.

If you know the log, Please let me know as soon as possibly

Thanks in advance.

Error message -

1. %STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars]. 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 show spanning-tree inconsistentports command to review the list  of interfaces with Dispute. Dispute is caused if the peer in 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 can not transmit but you can receive)  it should be replaced with a proper cable.

Related documents- No specific documents apply to this error message.

Jon

New Member

Hello,I just wanter to

Hello,

I just wanter to refresh this issue. I understand the reason of dispute on a certain link, but recently I had a situation where dispute appeared on all links attached to N7K. There are two reasons I can think of. One is some kind of bug/instability on the N7K itself. Two, there was some STP inconsistency in the network, however all links are rather edge switches. This could point to some vPC issue, where one peer still sends superior BPDU, and the other does not (bug?).

Cheers,

Krzysztof

Cisco Employee

Re: What is the mean "%STP-2-DISPUTE_DETECTED" ?

Hi

This is related to new feature called Spanning tree dispute mechanism in NX-OS and 6500 starting 12.2(33)SXI. The following link has more details anout it in Nexus 7K running NX-OS 4.2.

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/layer2/configuration/guide/Cisco_Nexus_7000_Series_NX-OS_Layer_2_Switching_Configuration_Guide_Release_4.2_chapter6.html#con_1490082

Thanks

Hatim Badr

poz
New Member

Re: What is the mean "%STP-2-DISPUTE_DETECTED" ?

I had this issue recently and spent some time troubleshooting the fiber link only to find out the far end switch, a 3750 did not include the native VLAN command on the trunk interface. Normally when that command is missing you get a native VLAN mismatch syslog error but not in this case on either side.

 

Symptom: Nexus 7000 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet3/21 on VLAN0100

(config-if)# sh spanning-tree blockedports
Name                 Blocked Interfaces List
-------------------- ------------------------------------
VLAN0100             Eth3/21

 

Finally cleared - %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet3/21 on VLAN0100.

 

We had native VLAN configured on the 7K side but not the 3750, added switchport trunk native vlan 100.

 

I wanted to reply so if anyone has this issue they can look into the native VLAN as all the documentation I found mentions unidirectional link failure as cause. This is not always the case.

 

25664
Views
5
Helpful
4
Replies
CreatePlease to create content