cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2648
Views
0
Helpful
3
Replies

Received SSTP BPDU with bad TLV

4uba
Level 1
Level 1

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?

3 Replies 3

Reza Sharifi
Hall of Fame
Hall of Fame

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

Hi. Thanks for reply.

Recommended fix from bug tool doesn’t work for me.
Reload command was already issued with no success.
What version of IOS will solve this issue?

Thanks.

Max_m
Level 1
Level 1

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,

Review Cisco Networking for a $25 gift card