Cisco 3110 Message Manual page 98

Catalyst switch module for ibm bladecenter system
Hide thumbs Also See for 3110:
Table of Contents

Advertisement

SPANTREE Messages
Error Message SPANTREE-2-PVSTSIM_FAIL: Blocking [chars] port [chars]: Inconsistent
[chars] PVST BPDU received on VLAN [dec], claiming root [dec]:[enet]
Explanation
switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST
switch must be consistently superior (lower bridge ID, lower path cost, and so forth) to the
information in all the PVST+ messages. If the port is the root, the CIST (MST00) information on
the MST switch must be consistently inferior to all the PVST+ messages. If this constraint is
violated, the port on the MST switch is blocked to prevent a potential bridging loop.
Recommended Action
topology, this condition might happen briefly. In such cases, the port unblocks automatically. If the
port remains blocked, identify the root bridge as reported in the message, and configure the
appropriate priority for the VLAN spanning tree, consistent with the CIST role on the port of the
MST switch. The first [chars] is the MST switch, the second [chars] is the port, and the third [chars]
is the PVST+ switch. The first [dec] is the VLAN ID, the second [dec] is the MST switch, and [enet]
is the MST-switch MAC address.
There could be additional inconsistencies not shown in the message, and the port does not recover
until all these are cleared. To determine which other VL4ANs have inconsistencies, disable and
re-enable the port. This message appears again and specifies another VLAN with inconsistencies to
be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.
Error Message SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port
[chars].
Explanation
that is inconsistent with the CIST port information. The PVST simulation inconsistency is cleared,
and the interface returns to normal operation. [chars] is the port.
Recommended Action
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.
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide
2-82
The specified port on the MST switch is blocked. When a designated port on an MST
When STP is converging after a new switch or switch port is added to the
The specified interface is no longer receiving PVST BPDUs advertising information
No action is required.
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
Chapter 2
Message and Recovery Procedures
OL-12191-01

Advertisement

Table of Contents
loading

This manual is also suitable for:

3112

Table of Contents