Cisco Systems Intelligent Gigabit Ethernet Switch Module manual

Page 36

SPANTREE-2-PVSTSIM_FAIL: Superior PVST BPDU received on VLAN [dec] port [chars], claiming root [dec]:[enet].

Invoking root guard to block the port.

Explanation This message means that when a per-VLAN spanning-tree plus (PVST+) switch is connected to a Multiple Spanning Tree Protocol (MSTP) switch, the internal spanning-tree (IST) root (MST00) becomes the root for all PVST+ spanning trees. A loop might be created if any of the PVST+ spanning trees have a better root than the IST. To prevent the loop, the port on the MSTP switch that receives the superior message from the PVST+ side is blocked by root guard. The first [dec] is the VLAN number, [chars] is the port name, and [dec]:[enet] is the priority and MAC address.

Response When STP is converging after a new switch or switch port is added to the topology, this condition might happen transiently, and the port automatically unblocks in these cases. If the port remains blocked, identify the root bridge as reported in the message, and configure a priority for the VLAN spanning tree so that it is not selected as the root. There could be other superior PVST+ roots (lower bridge ID, lower path cost, and so forth) than the message shows, and the port does not recover until all such roots are cleared. If you are unsure, disable and re-enable the port.

SPANTREE-2-RECV-1Q-NON-1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].

Explanation This message means that the listed interface on which a Shared Spanning Tree Protocol (SSTP) BPDU was received was in trunk mode but was not using 802.1Q encapsulation. The first [chars] is the port, and the second [chars] is the VLAN.

Response Verify that the configuration and operational state of the listed interface and 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 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.

SPANTREE-2-RECV-BAD-TLV: Received SSTP BPDU with bad TLV on [chars] [chars].

Explanation This message means that the listed interface received a Shared Spanning Tree Protocol (SSTP) bridge protocol data unit (BPDU) without the VLAN ID tag. The BPDU is discarded. The first [chars] is the port, and the second [chars] is the VLAN that received the SSTP BPDU.

Response If the message recurs, find out more about the error by using the show tech-supportprivileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools , see the “Error Message Traceback Reports” section on page .9

SPANTREE-2-RECV-PVID-ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].

Explanation This message means that the listed interface received an SSTP BPDU that is tagged with a VLAN ID that does 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 802.1Q trunk. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN.

Response Verify that the configurations of the native VLAN ID are consistent on the interfaces on each end of the 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces.

34Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

Image 36
Contents IBM First Edition June Contents BookTitle change in special and import Preface AudiencePurpose ConventionsEServer BladeCenter Type 8677 Installation and User’s Guide Preface Page How to Read System Messages System Message OverviewSeverity Level Description Error Message Traceback Reports Output InterpreterPage Message and Recovery Procedures Cigesm Messages Message and Recovery Procedures Page CMP Messages DOT1X Messages DTP Messages EC Messages Message and Recovery Procedures EC-5-NOLACP Invalid EC mode. Lacp not enabled Ethcntr Messages Hwmatmmod Messages PLATFORMCAT2950 MessagesMessage and Recovery Procedures Page Message and Recovery Procedures PLATFORMCATALYST2950 Messages PM MessagesPM-4-BADAPPID An invalid application id dec was detected PM-4-BADCOOKIE chars was detected PM-4-BADVLANID An invalid vlan id dec was detected PM-4-NOSUBBLOCK No PM subblock found for chars Port Security Messages Span MessagesSpantree Messages This section contains the spanning-tree messagesMessage and Recovery Procedures Page Message and Recovery Procedures SPANTREE-4-PORTNOTFORWARDING chars chars chars Chars port chars Spantreevlanswitch Messages Spantreefast MessagesStormcontrol Messages Swvlan Messages Page Chars chars Charschars Udld Messages Ufastmcastsw Messages Message and Recovery Procedures Page Appendix A. Security and QoS Configuration Messages Error Message Explanation and Suggested SolutionMessage Traceback Reports section on Tools , see the Error Message Traceback Reports section This error message means that there are no free masks This error message means that a hardware failure has This error message means that the granularity of the policer Appendix B. Getting help and technical assistance Before you callSoftware service and support Hardware service and support Appendix C. Notices Edition noticeTrademarks IBMIndex Numerics Udld Ufast Page IBM@