Spanning Tree Error

[BhavMistry]

Hi All,

i am getting the following error when connecting a trunk link back to core switch:

Topology:

Core > SW1 > SW4 > Core

Core: VTP Server

Edge Switches : Client

VTP Version 1

Domain has been set

VTP password has been set

all interfaces have the same configuration as follows:
switchport trunk native vlan 10

switchport mode trunk

All VLANS are allowed to pass on trunk

SW is getting the following error message:
MD5 digest checksum mismatch on receipt of equal revision summary on trunk: Te1/0/1

I have checked the MD5 Checksum and they are all identical as is the revision.

when the link between Core and SW4 is shut down the error is no longer there.

Logs:
Feb 23 20:13:52.748: %SW_MATM-4-MACFLAP_NOTIF: Host xxxx.xxxx.xxxx in vlan 10 is flapping between port Te1/0/2 and port Te1/0/1
Feb 23 20:13:53.027: %SW_MATM-4-MACFLAP_NOTIF: Host xxxx.xxxx.xxxx in vlan 10 is flapping between port Te1/0/1 and port Te1/0/2
Feb 23 20:13:56.736: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 11 on TenGigabitEthernet1/0/1 VLAN10.
Feb 23 20:13:56.736: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/0 /1 on VLAN0011. Inconsistent peer vlan.
Feb 23 20:13:56.736: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking TenGigabitEthernet1/ 0/1 on VLAN0010. Inconsistent local vlan.
Feb 23 20:13:58.735: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 11 on TenGigabitEthernet1/0/1 VLAN1.
Feb 23 20:13:58.735: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking TenGigabitEthernet1/ 0/1 on VLAN0001. Inconsistent local vlan.
Feb 23 20:13:58.753: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/0 /1 on VLAN0070. Inconsistent peer vlan.
Feb 23 20:14:06.590: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthe rnet1/0/1 on VLAN0720. Port consistency restored.
Feb 23 20:14:09.211: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/0 /1 on VLAN0060. Inconsistent peer vlan.
Feb 23 20:14:12.064: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/0 /1 on VLAN0720. Inconsistent peer vlan.
Feb 23 20:14:13.755: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthe rnet1/0/1 on VLAN0070. Port consistency restored.
Feb 23 20:14:16.597: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthe rnet1/0/1 on VLAN0710. Port consistency restored.
Feb 23 20:14:21.211: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/0 /1 on VLAN0070. Inconsistent peer vlan.
Feb 23 20:14:24.140: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 40 on TenGigabitEthernet1/0/1 VLAN710.
Feb 23 20:14:24.140: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking TenGigabitEthernet1/ 0/1 on VLAN0710. Inconsistent local vlan.
Feb 23 20:14:25.210: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV o n TenGigabitEthernet1/0/1 VLAN10.
Feb 23 20:14:55.959: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV o n TenGigabitEthernet1/0/1 VLAN10.
Feb 23 20:15:11.384: %LINK-5-CHANGED: Interface TenGigabitEthernet1/0/1, changed state to administratively down
Feb 23 20:15:12.384: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitE thernet1/0/1, changed state to down

any help and advise would be appriciated

Thanks

[balaji.bandi]

as per the topology you mentioned looks simple, but we are not sure you have 2 VTP servers on Core switches? post all the switch config and output as below :

show run

show vtp status

show int trunk

suggest moving to VTP version 2

suggested to look below link :

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

From cisco documentation :

Error Message

%SPANTREE-2-RECV_PVID_ERR : Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].

Explanation : The specified interface has received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This condition occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.

Recommended Action : Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once this inconsistency is corrected, spanning tree will automatically unblock the interfaces as appropriate.

[Martin L]

Do not use VTP version 1; use 2 or even 3 if supported on all switches;

Native vlan does not need to be the same on all trunks in all switches but must be same on a single trunk link between 2 switches; So, Check your Native vlan 10 set up; I would make it the same through out your L2 domain for clarity sake. Make sure vlan 10 is present on all switches in vlan databases.  Or move back to native vlan 1 on all trunks;

Regards, ML
**Please Rate All Helpful Responses **

[Georg Pauwen]

Hello,

I somewhere recall a bug that caused this. Can you try to create a new Vlan on the VTP server (the core switch), a Vlan that is not assigned to any specific access port (so basically an empty Vlan) ?