10-21-2020 11:53 AM
hi everyone
this topic is been posted few time and there were some solutions but its not working. Below are the logs from a access layer switch(c3650) which blocks the trunk port. this switch is connected to a layer 3 switch(c3850) in that switch its not happening i see inconsistent peer and local vlan . the native vlan on both sides are same. the weird thing is automatically comes back after seconds and sometimes hours to come back up ..any advise on how to resolve this ?
000150: *Oct 21 11:08:38.412: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0405. Inconsistent peer vlan.
000151: *Oct 21 11:08:38.414: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking TenGigabitEthernet1/1/2 on VLAN0001. Inconsistent local vlan.
000152: *Oct 21 11:08:38.415: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0406. Inconsistent peer vlan.
000153: *Oct 21 11:08:38.416: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0407. Inconsistent peer vlan.
000154: *Oct 21 11:08:38.417: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0408. Inconsistent peer vlan.
000155: *Oct 21 11:08:38.417: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0409. Inconsistent peer vlan.
000156: *Oct 21 11:08:38.418: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0410. Inconsistent peer vlan.
000157: *Oct 21 11:08:38.419: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0411. Inconsistent peer vlan.
000158: *Oct 21 11:08:38.420: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0412. Inconsistent peer vlan.
000159: *Oct 21 11:08:38.421: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0413. Inconsistent peer vlan.
000160: *Oct 21 11:08:38.421: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0500. Inconsistent peer vlan.
000161: *Oct 21 11:08:38.422: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0501. Inconsistent peer vlan.
000162: *Oct 21 11:08:38.423: %SPANTREE-2-BLOCK_PVID_PEER: Blocking TenGigabitEthernet1/1/2 on VLAN0504. Inconsistent peer vlan.
Oct 21 11:08:53.414: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0405. Port consistency restored.
000193: *Oct 21 11:08:53.414: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0406. Port consistency restored.
000194: *Oct 21 11:08:53.416: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0407. Port consistency restored.
000195: *Oct 21 11:08:53.417: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0408. Port consistency restored.
000196: *Oct 21 11:08:53.418: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0409. Port consistency restored.
000197: *Oct 21 11:08:53.418: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0410. Port consistency restored.
000198: *Oct 21 11:08:53.418: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0411. Port consistency restored.
000199: *Oct 21 11:08:53.421: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0412. Port consistency restored.
000200: *Oct 21 11:08:53.422: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0413. Port consistency restored.
000201: *Oct 21 11:08:53.422: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0500. Port consistency restored.
000202: *Oct 21 11:08:53.422: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0501. Port consistency restored.
000203: *Oct 21 11:08:53.423: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0504. Port consistency restored.
000204: *Oct 21 11:08:53.426: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet1/1/2 on VLAN0001. Port consistency restored.
10-21-2020 02:57 PM - edited 10-21-2020 02:58 PM
Hello
The port is receiving a stp BPDU that is tagged with the same vlan id of the specified native vlan id which is untagged
example:
sw1
int x/x
switchport mode trunk
switchport trunk native vlan 10 < --- vlan 10 is untagged
sw2
int x/x
switchport mode trunk <--- here all vlan area allowed and tagged including vlan 10
06-15-2023 12:08 AM
We had the same problem.
Our solution:
check the error counters on your uplink ports. One port from our port-channel got fcs errors:
#sh int e 1/49 count err
--------------------------------------------------------------------------------
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
--------------------------------------------------------------------------------
Eth1/49 2957 92460441 0 92463398 0 0
Then check your transiever values:
#sh int e 1/49 transceiver de
SFP Detail Diagnostics Information (internal calibration)
----------------------------------------------------------------------------
Current Alarms Warnings
Measurement High Low High Low
----------------------------------------------------------------------------
Temperature 33.39 C 65.00 C 5.00 C 60.00 C 10.00 C
Voltage 3.26 V 3.63 V 2.97 V 3.46 V 3.09 V
Current 42.05 mA 105.00 mA 8.00 mA 98.00 mA 9.00 mA
Tx Power 1.47 dBm 5.29 dBm -14.08 dBm 2.29 dBm -10.00 dBm
Rx Power -20.00 dBm -- 3.30 dBm -17.69 dBm 2.29 dBm -13.76 dBm
Transmit Fault Count = 0
After cable replacement our error counter and log is clear.
11-20-2023 08:32 AM
I finally figured this out. I had the exact same problem. SPANTREE-2-BLOCK constantly shutting down my uplink ports with all kinds of vlan erros. Here is why:
If you are connecting a switch to a switch do NOT add native vlan. Leave the trunk ports just as a trunk on both ends and just enable the vlans as "allowed vlans" See below.
This INCORRECT:
SW1
interface FastEthernet0/16
switchport trunk native vlan 300 <-- wrong don't do this
switchport trunk allowed vlan 105,300 <-- correct
switchport trunk encapsulation dot1q<-- wrong don't do this
switchport mode trunk <-- correct
The correct way you should setup your trunks is like this:
SW1
interface FastEthernet0/16
switchport trunk allowed vlan 105,300
switchport mode trunk
Do that on both ends and your SPANTREE errors will go away and stop shutting down your uplink ports.
I have tested this in every single way possible and the only way this works is to setup the trunks like I mentioned above. Just add the any additional vlans you setup on the trunk as "allowed"
I added additional vlans down the line on member switches and connected PC's and all works fine this way.
The image below is of another port Fa0/12 with the same issue
The setup is a 3560 switch with routing on acting as a Multilayer Switch connected to many edge switches (3560's and 2960's)
The problem the whole time was adding the Native Vlan to the trunk.
03-26-2024 08:51 AM
Check the Gateway ip for the new switch.
thanks me later.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide