10-28-2021 12:39 PM - edited 10-28-2021 12:40 PM
Hi guys,
After power outdage I begin to receive on one of my switch next logs:
Oct 28 14:44:23 EDT: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on GigabitEthernet1/0/52 VLAN138.
Oct 28 14:44:55 EDT: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on GigabitEthernet1/0/52 VLAN138.
Oct 28 14:45:25 EDT: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on GigabitEthernet1/0/52 VLAN138.
Any configuration changes since few months.
Switch with errors WS-C2960X-48FPS-L 15.2(7)E4:
interface GigabitEthernet1/0/52
description Transit
switchport trunk allowed vlan 134,135,138,139,881-883,885,888
switchport trunk native vlan 138
switchport mode trunk
ip arp inspection trust
ip dhcp snooping trust
end
======
Name: Gi1/0/52
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 138 (MGMT)
Administrative Native VLAN tagging: disabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 134,135,138,139,881-883,885,888
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
======
Another end WS-C3850-12XS 16.12.05b:
interface TenGigabitEthernet1/0/7
description Transit
switchport trunk native vlan 138
switchport trunk allowed vlan 134,135,138,139,881-883,885,888
switchport mode trunk
end
======
Name: Te1/0/7
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 138 (MGMT)
Administrative Native VLAN tagging: disabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 134,135,138,139,881-883,885,888
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Vepa Enabled: false
Appliance trust: none
Can you please advice me?
10-28-2021 01:05 PM
Hi,
Appears to be a bug in the IOS that was triggered by the power outage. A soft reboot may fix the issue, if not you may have to upgrade the IOS. Here is a bug id:
https://quickview.cloudapps.cisco.com/quickview/bug/CSCvu77162
HTH
10-28-2021 07:59 PM
09-11-2023 06:18 AM
Hi, thanks for the Bug id.
Do you guys know if this bug can prevent the uplink interfaces with custom native vlan from getting connected as before the restart ?
Regards,
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