Cisco IE-3000-8TC Message Manual page 70

Switch system
Hide thumbs Also See for IE-3000-8TC:
Table of Contents

Advertisement

SPANTREE Messages
Error Message SPANTREE-2-RECV_1Q_NON_1QTRUNK: Received 802.1Q BPDU on non 802.1Q
trunk [chars] [chars].
Explanation
received was in trunk mode but was not using IEEE 802.1Q encapsulation. The first [chars] is the
port, and the second [chars] is the VLAN.
Recommended Action
that of the interface to which it is connected are in the same mode (access or trunk). If the mode is
trunk, verify that both interfaces have the same encapsulation (ISL or IEEE 802.1Q). If the
encapsulation types are different, use the switchport trunk encapsulation interface configuration
command to make them consistent. When the encapsulation is consistent, spanning tree
automatically unblocks the interface.
Error Message SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].
Explanation
discarded. The first [chars] is the port, and the second [chars] is the VLAN that received the SSTP
BPDU.
Recommended Action
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 require assistance, open a case
with the TAC, or contact your Cisco technical support representative, and provide the representative
with the gathered information. For more information about these online tools and about contacting
Cisco, see the
Error Message SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id
[dec] on [chars] [chars].
Explanation
not match the VLAN ID on which the BPDU was received. This occurs when the native VLAN is
not consistently configured on both ends of an IEEE 802.1Q trunk. [dec] is the VLAN ID, the first
[chars] is the port, and the second [chars] is the VLAN.
Recommended Action
interfaces on each end of the IEEE 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
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
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
Cisco IE 3000 Switch System Message Guide
2-56
The listed interface on which a Shared Spanning Tree Protocol (SSTP) BPDU was
Verify that the configuration and operational state of the listed interface and
The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is
If this message recurs, copy the message exactly as it appears on the console
"Error Message Traceback Reports" section on page
The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does
Verify that the configurations of the native VLAN ID is consistent on the
On the listed interface, a BPDU was received that advertises a superior spanning-tree
Enter the show spanning-tree inconsistentports privileged EXEC command
Chapter 2
Message and Recovery Procedures
1-4.
OL-13020-01

Advertisement

Table of Contents
loading

This manual is also suitable for:

Ie 3000

Table of Contents