To enable tracing and generates debug statements for customer spanning tree debugging support, use the command debug customer spanning-tree in Privileged EXEC Mode. The no form of this command disables tracing for customer spanning tree debugging support.
Parameter | Type | Description |
---|---|---|
cep interface |
Enter to display the customer spanning tree information for the specified customer edge port (CEP). | |
interface |
Enter to display the interface-specific information of
active ports. Note:
This command does not support virtual interfaces, tunnels, or interface VLANs type of interfaces. |
|
Gigabitethernet |
Enter to display gigabitetethernet type of interface. Gigabitethernet is a version of LAN standard architecture that supports data transfer up to 1 Gigabit per second. | |
<interface-id> |
Enter to display a specific slot number / port number. The format is <0>/<1-28> without spaces between Slot Number/Port Number. For example, 0/1. | |
Extreme-Ethernet |
Enter to display the Extreme-Ethernet type of interface. Extreme Ethernet is a version of Ethernet that supports data transfer up to 10 Gigabits per second and only full duplex links | |
<interface-id> |
Enter to display a specific slot number / port number. The format is <0>/<1-28> without spaces between Slot Number/Port Number. For example, 0/1. | |
all |
Enter to generate debug statements for all RSTP / MSTP | |
bpdu |
Enter to generate debug statements for BPDU-related traces. | |
bridge-detection-state-machine |
Enter to generate debug statements for bridge detection SEM. | |
errors |
Enter to generate debug statements for all failure traces. | |
events |
Enter to generate debug statements for event handling traces. This trace is generated to denote events that are posted to STP configuration queue whenever you configure any of the STP features. | |
global |
Enter to generate debug statements for | |
init-shut |
Enter to generate debug statements for init and shutdown traces. This trace is generated on failed and successful initialization and shutting down of STP related module and memory. | |
management |
Enter to generate debug statements for management traces. This trace is generated whenever you configure any of the STP features. | |
memory |
Enter to generate debug statements for memory related traces. This trace is generated on failed and successful allocation of memory for STP process. | |
port-info-state-machine |
Enter to generate debug statements for port information SEM. | |
port-receive-state-machine |
Enter to generate debug statements for port receive SEM. | |
port-role-selection-state-machine |
Enter to generate debug statements for role selection SEM. | |
port-transmit-state-machine |
Enter to generate debug statements for port transmit SEM | |
protocol-migration-state-machine |
Enter to generate debug statements for protocol migration SEM. | |
pseudoInfo-state-machine |
Enter to generate debug statements for port receive pseudo information SEM. | |
redundancy |
Enter to generate debug statements for redundancy code flow traces. This trace is generated in standby node STP while taking backup of configuration information from active node. | |
role-transition-state-machine |
Enter to generate debug statements for role transition SEM | |
sem-variables |
Enter to generate debug statements for state machine variable changes traces. This trace is generated on failed and successful creation and deletion of semaphore. | |
state-transition-state-machine |
Enter to generate debug statements for state transition SEM. | |
timer |
Enter to generate debug statements for timer module traces. Tis generated on failed and successful start, stop and restart of STP timers. | |
topology-change-state-machine |
Enter to generate debug statements for topology change SEM. | |
<level (0-7)> |
Integer | Enter to generate debug statements for or the specified severity level value.This value ranges from 0 to 7. |
alerts |
Enter to generate debug statements for immediate action. | |
critical |
Enter to generate debug statements for critical conditions. | |
debugging |
Enter to generate debug statements for debugging messages. | |
emergencies |
Enter to generate debug statements when system cannot be used. | |
errors |
Enter to generate debug statements for for error conditions. | |
informational |
Enter to generate debug statements for information messages. | |
notification |
Enter to generate debug statements for significant messages. | |
warnings |
Enter to generate debug statements for warning conditions. |
Privileged EXEC Mode
Debug customer spanning-tree can be executed only on customer edge ports. To set port type as customer edge ports, bridge mode is set as provider-edge bridge mode.
iS5Comm# debug spanning-tree errors 1