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

P2P Dispute BLK


one of the ports of 6509 router to which MARUTA encryptor (Clear port) is connected is showing as " P2P Dispute"  and is put into BLK state.

What could be the reason?Can i get some valuable info/soltuion to this issue

New Member

P2P Dispute BLK

The reason for P2P Dispute can be that remote end (MARUTA encryptor) sent RSTP BPDU with Designated bit set (flag field in BPDU in RSTP encode the role and state of the port that originates the BPDU) but your 6509 think that he is root and sent best BPDU for segment. To solve this 6509 puts port in dispute/blk state to avoid situation when loop can occur due unidirectional connection or thmth else.

So in your case smth wrong with devices interpreting each other BPDU, or link from 6509 to MARUTA encryptor is unidirectional.

Cisco Employee

Re: P2P Dispute BLK

Hi Sonam,

The dispute mechanism was a very nice enhancement that was added into spanning-tree. I'll try to provide some information on it and then we'll move on to how we can find out what's wrong and fix it.

Every segment, as you are probably aware, should have only one designated port. This port (and bridge) is responsible for generating BPDUs for the segment. Now, RSTP onwards, the BPDU format changed a little bit. It now includes the port role as well among other things. The port role is simply the spanning-tree role of the port.

A spanning-tree dispute happens when a designated port receives a BPDU in which the port role is also designated. The bridge that receives and detects this moves it's port to a discarding state - note that the port role still remains designated. The BPDU being received should also have the learning bit set for the dispute to occur.

This entire mechanism is quite helpful in detecting unidirectional situations which can lead to loops.

Let's come back to your scenario now. Could you post the show spanning-tree vlan please? As you said, this port goes to a Maruta encryptor. I'm not familiar with this device but I am assuming that it does not participate in spanning-tree. Is that correct? Are there any other switches connected to this device?



New Member

P2P Dispute BLK

Hi ,

Yeah it is an encryptor and it is not supposed to participate in spanning-tree.

And there are 3560s connected to this 6509.

How can i prohibit this encryptor from participating in spanning-tree.?

CreatePlease to create content