Inconsistent Peer VLAN ID

[Fenderbridge]

I'm having some trouble trying to figure out why I'm getting the following errors in my logs.  This morning, for the first time in over a year, my switch stopped communicating with my core switch,  so I checked the log.

Feb 27 16:25:15.364 UTC: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 1 on GigabitEthernet5/13 VLAN100.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0001. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet5/13 on VLAN0100. Inconsistent local vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0111. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0161. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0325. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0401. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0441. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0471. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0472. Inconsistent peer vlan.
Feb 27 16:25:15.364 UTC: %SPANTREE-2-BLOCK_PVID_PEER: Blocking GigabitEthernet5/13 on VLAN0775. Inconsistent peer vlan.
Feb 27 16:25:15.632 UTC: %DTP-5-TRUNKPORTON: Port Gi5/13 has become dot1q trunk
Feb 27 16:25:17.131 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet5/13, changed state to up
Feb 27 16:25:18.131 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet5/13, changed state to up
Feb 27 16:25:31.139 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0472. Port consistency restored.
Feb 27 16:25:31.379 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0775. Port consistency restored.
Feb 27 16:25:31.680 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0471. Port consistency restored.
Feb 27 16:25:31.888 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0161. Port consistency restored.
Feb 27 16:25:31.888 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0401. Port consistency restored.
Feb 27 16:25:32.023 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0111. Port consistency restored.
Feb 27 16:25:32.360 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0325. Port consistency restored.
Feb 27 16:25:32.361 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0441. Port consistency restored.
Feb 27 16:25:33.010 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0001. Port consistency restored.
Feb 27 16:25:33.010 UTC: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking GigabitEthernet5/13 on VLAN0100. Port consistency restored.
Feb 27 17:19:22.515 UTC: %DTP-5-NONTRUNKPORTON: Port Gi5/13 has become non-trunk
Feb 27 17:19:22.998 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet5/13, changed state to down
Feb 27 17:19:24.012 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet5/13, changed state to down

I checked the configurations on both sides, and they appear to be the same.

Sw1#src int g1/1/1
Building configuration...

Current configuration : 241 bytes
!
interface GigabitEthernet1/1/1
description Core-Switch-1
switchport trunk native vlan 100
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event spanning-tree
spanning-tree link-type point-to-point
end

Sw1#src int g1/1/2
Building configuration...

Current configuration : 238 bytes
!
interface GigabitEthernet1/1/2
description Core-Switch-2
switchport trunk native vlan 100
switchport mode trunk
switchport nonegotiate
logging event trunk-status
logging event spanning-tree
spanning-tree link-type point-to-point
end

Core-Switch1#src int g5/13
Building configuration...

Current configuration : 239 bytes
!
interface GigabitEthernet5/13
description Sw1 g1/1/1
switchport trunk native vlan 100
switchport mode trunk
switchport nonegotiate
logging event link-status
logging event trunk-status
spanning-tree link-type point-to-point
end

Core-Switch-2#src int g5/13
Building configuration...

Current configuration : 239 bytes
!
interface GigabitEthernet5/13
description Sw1 g1/1/2
switchport trunk native vlan 100
switchport mode trunk
switchport nonegotiate
logging event link-status
logging event trunk-status
spanning-tree link-type point-to-point
end

Anyone have any ideas on why this may be happening?  And why it happened randomly overnight, and again at noon?

src=sho run alias.

Thank you very much in advance!

[balaji.bandi]

we do not know the whole topology of your network and  full spanning tree config, so i would suggest to refer below document  :

https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24063-pvid-inconsistency-24063.html

More advise post the full configruation of all the devices

[Jaderson Pessoa · Accepted solution]

Sometime ago i had this same issue, but my problem were different versions of spanning-tree. I suggest to you check the whole configuration about your STP topology.

[Fenderbridge]

That's the one!  sho span sum showed the following:

Sw1#sho span summ
Switch is in rapid-pvst mode
Root bridge for: VLAN0001

Looking at all of the other switches on the topology, none of them were root bridges except for the core switches.

Thank you for the pointer! 

[Jaderson Pessoa]

Thanks for the positive feedback.

Best regards.

[omarmontes]

Hi! sorry for reviving this post.

What was the problem exactly? were the switches using different stp versions?