Cisco 3845 Message Guide - Page 74
show spanning-tree, show spanning-tree inconsistentports, SSTP BPDU.
![]() |
UPC - 746320981420
View all Cisco 3845 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 74 highlights
SPANTREE Messages Chapter 2 Messages and Recovery Procedures Error Message SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars] [chars]. Explanation The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is discarded. The first [chars] is the interface, and the second [chars] is the VLAN that received the SSTP BPDU. Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 1-5. Error Message SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars]. Explanation The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID that received the BPDU. This occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN. Recommended Action Verify that the configurations of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces. Error Message SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars]. Explanation The listed interface received a BPDU that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) than that in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the output of the show spanning-tree privileged EXEC command. Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with root-guard inconsistencies. Find out why devices connected to the listed ports are sending BPDUs with a superior root bridge, and take action to prevent more occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface. Error Message SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars] on [chars]. Explanation The spanning-tree root guard configuration for the listed interface has changed. If enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put 2-60 Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide OL-23408-01
![](/manual_guide/products/cisco-3845-message-guide-8b81c11/74.png)