SPANTREE-2-RECV_PVID_ERR

[BhargavHingu]

Kindly help to resolve below mentioned issue.

SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 229 on GigabitEthernet0/1 VLAN1.

SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet0/1 on VLAN0229. Inconsistent peer vlan.

SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet0/1 on VLAN0001. Inconsistent local vlan.

[johnd2310]

Hi.

What is the configuration on both sides of that link? There is a mismatch  in the port configuration of the switches connected by that link.

Thanks

John

[BhargavHingu]

SW:1 interface GigabitEthernet0/1 switchport mode trunk SW 2: interface GigabitEthernet1/0/2 switchport mode trunk Gi1/0/2 on 802.1q trunking 1 Port Vlans allowed and active in management domain Gi1/0/2 1,224,226,229 Port Vlans in spanning tree forwarding state and not pruned Gi1/0/2 1,224,226,229

[Rolf Fischer]

Hi,

in addition to the portconfigs, what is the platform and what IOS are you running?

Could be a well-known misbehaviour, documented in several bugs for many years: When you add new VLANs or enable new uplinks, sometimes the spanning-tree (software) process begins sending BPDUs for this VLAN(s) before the ASIC got knowledge about the new VLAN(s). The ASIC then sends those BPDUs untagged (!), so the neighbor switch receives them in the trunk's native VLAN. After recovering from the err-disabled or stp-inconsistent state, the link should work as desired.

We see this every now and then in our networks. If it occurs only once after a link- or VLAN-change, normally no further actions are required.   

HTH

Rolf

[BhargavHingu]

Here is the IOS version currently running on the switch

flash:c2960-lanbasek9-mz.122-55.SE9/c2960-lanbasek9-mz.122-55.SE9.bin

Regards ,

Bhargav