The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This appendix describes the debug privileged EXEC commands that have been created or changed for use with the Catalyst 3750 switch. These commands are helpful in diagnosing and resolving internetworking problems and should be enabled only under the guidance of Cisco technical support staff.
Use the debug autoqos privileged EXEC command to enable debugging of the automatic quality of service (auto-QoS) feature. Use the no form of this command to disable debugging output.
debug autoqos
no debug autoqos
This command has no keywords or arguments.
Auto-QoS debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(14)EA1 |
This command was introduced. |
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. You enable debugging by entering the debug autoqos privileged EXEC command.
The undebug autoqos command is the same as the no debug autoqos command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
This example shows how to display the QoS configuration that is automatically generated when auto-QoS is enabled:
Switch# debug autoqos
AutoQoS debugging is on
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# auto qos voip cisco-phone
21:29:41: mls qos map cos-dscp 0 8 16 26 32 46 48 56
21:29:41: mls qos
21:29:42: no mls qos srr-queue input cos-map
21:29:42: no mls qos srr-queue output cos-map
21:29:42: mls qos srr-queue input cos-map queue 1 threshold 3 0
21:29:42: mls qos srr-queue input cos-map queue 1 threshold 2 1
21:29:42: mls qos srr-queue input cos-map queue 2 threshold 1 2
21:29:42: mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
21:29:43: mls qos srr-queue input cos-map queue 2 threshold 3 3 5
21:29:43: mls qos srr-queue output cos-map queue 1 threshold 3 5
21:29:43: mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
21:29:44: mls qos srr-queue output cos-map queue 3 threshold 3 2 4
21:29:44: mls qos srr-queue output cos-map queue 4 threshold 2 1
21:29:44: mls qos srr-queue output cos-map queue 4 threshold 3 0
21:29:44: no mls qos srr-queue input dscp-map
21:29:44: no mls qos srr-queue output dscp-map
21:29:44: mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
21:29:45: mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
21:29:45: mls qos srr-queue input dscp-map queue 1 threshold 3 32
21:29:45: mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
21:29:45: mls qos srr-queue input dscp-map queue 2 threshold 2 26 33 34 35 36 37 38 39
21:29:46: mls qos srr-queue input dscp-map queue 2 threshold 2 48 49 50 51 52 53 54 55
21:29:46: mls qos srr-queue input dscp-map queue 2 threshold 2 56 57 58 59 60 61 62 63
21:29:46: mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 27 28 29 30 31 40
21:29:47: mls qos srr-queue input dscp-map queue 2 threshold 3 41 42 43 44 45 46 47
21:29:47: mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
21:29:47: mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 27 28 29 30 31 48
21:29:47: mls qos srr-queue output dscp-map queue 2 threshold 3 49 50 51 52 53 54 55 56
21:29:48: mls qos srr-queue output dscp-map queue 2 threshold 3 57 58 59 60 61 62 63
21:29:48: mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
21:29:48: mls qos srr-queue output dscp-map queue 3 threshold 3 26 32 33 34 35 36 37 38
21:29:48: mls qos srr-queue output dscp-map queue 3 threshold 3 39
21:29:49: mls qos srr-queue output dscp-map queue 4 threshold 1 8
21:29:49: mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
trs(config-if)#
21:29:49: mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
21:29:49: no mls qos srr-queue input priority-queue 1
21:29:49: no mls qos srr-queue input priority-queue 2
21:29:50: mls qos srr-queue input bandwidth 90 10
21:29:50: no mls qos srr-queue input buffers
21:29:50: mls qos queue-set output 1 buffers 20 20 20 40
21:29:50: interface GigabitEthernet2/0/1
21:29:50: mls qos trust device cisco-phone
21:29:50: mls qos trust cos
21:29:50: no queue-set 1
21:29:50: srr-queue bandwidth shape 10 0 0 0
21:29:50: srr-queue bandwidth share 10 10 60 20
Use the debug cluster privileged EXEC command to enable debugging of cluster-specific events. Use the no form of this command to disable debugging output.
debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat | neighbors | platform | snmp | vqpxy}
no debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat | neighbors | platform | snmp | vqpxy}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
This command is available only on the cluster command switch stack or cluster command switch.
The undebug cluster command is the same as the no debug cluster command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug dot1x privileged EXEC command to enable debugging of the 802.1X feature. Use the no form of this command to disable debugging output.
debug dot1x {all | errors | events | packets | registry | state-machine}
no debug dot1x {all | errors | events | packets | registry | state-machine}
Debugging is disabled.
Privileged EXEC
The undebug dot1x command is the same as the no debug dot1x command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug dtp privileged EXEC command to enable debugging of the Dynamic Trunking Protocol (DTP) activity. Use the no form of this command to disable debugging output.
debug dtp {aggregation | all | decision | events | oserrs | packets | queue | states | timers}
no debug dtp {aggregation | all | decision | events | oserrs | packets | queue | states | timers}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug dtp command is the same as the no debug dtp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug etherchannel privileged EXEC command to enable debugging of the EtherChannel/PAgP shim. This shim is the software module that is the interface between the Port Aggregation Protocol (PAgP) software module and the port manager software module. Use the no form of this command to disable debugging output.
debug etherchannel [all | detail | error | event | idb]
no debug etherchannel [all | detail | error | event | idb]
Note Though visible in the command-line help strings, the linecard keyword is not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
If you do not specify a keyword, all debug messages appear.
The undebug etherchannel command is the same as the no debug etherchannel command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug ilpower priviledged EXEC command to enable debugging of the power controller and Power over Ethernet (PoE) system.
debug ilpower {controller | event | port | registries}
no debug ilpower {controller | event | port | registries}
Note This command is supported only on PoE-capable switches.
controller |
Display PoE controller debug messages. |
event |
Display PoE event debug messages. |
port |
Display PoE port manager debug messages. |
registries |
Display PoE registries debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(19)EA1 |
This command was introduced. |
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
|
|
Displays the values in the registers of the specified PoE controller. |
|
Displays the power status for the specified PoE port or for all PoE ports. |
Use the debug interface privileged EXEC command to enable debugging of interface-related activities. Use the no form of this command to disable debugging output.
debug interface {interface-id | null interface-number | port-channel port-channel-number | vlan vlan-id}
no debug interface {interface-id | null interface-number | port-channel port-channel-number | vlan vlan-id}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
If you do not specify a keyword, all debug messages appear.
The undebug interface command is the same as the no debug interface command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug ip igmp filter privileged EXEC command to enable debugging of Internet Group Management Protocol (IGMP) filter events. Use the no form of this command to disable debugging output.
debug ip igmp filter
no debug ip igmp filter
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug ip igmp filter command is the same as the no debug ip igmp filter command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug ip igmp max-groups privileged EXEC command to enable debugging of Internet Group Management Protocol (IGMP) maximum groups events. Use the no form of this command to disable debugging output.
debug ip igmp max-groups
no debug ip igmp max-groups
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug ip igmp max-groups command is the same as the no debug ip igmp max-groups command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug igmp snooping privileged EXEC command to enable debugging of Internet Group Management Protocol (IGMP) snooping activity. Use the no form of this command to disable debugging output.
debug ip igmp snooping [group | management | router | timer]
no debug ip igmp snooping [group | management | router | timer]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug ip igmp snooping command is the same as the no debug ip igmp snooping command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug lacp privileged EXEC command to enable debugging of Link Aggregation Control Protocol (LACP) activity. Use the no form of this command to disable debugging output.
debug lacp [all | event | fsm | misc | packet]
no debug lacp [all | event | fsm | misc | packet]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(14)EA1 |
This command was introduced. |
The undebug lacp command is the same as the no debug lacp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug mac-notification privileged EXEC command to enable debugging of MAC notification events. Use the no form of this command to disable debugging output.
debug mac-notification
no debug mac-notification
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug mac-notification command is the same as the no debug mac-notification command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug matm privileged EXEC command to enable debugging of platform-independent MAC address management. Use the no form of this command to disable debugging output.
debug matm
no debug matm
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug matm command is the same as the no debug matm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug monitor privileged EXEC command to enable debugging of the Switched Port Analyzer (SPAN) feature. Use the no form of this command to disable debugging output.
debug monitor {all | errors | idb-update | info | list | notifications | platform | requests | snmp}
no debug monitor {all | errors | idb-update | info | list | notifications | platform | requests | snmp}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug monitor command is the same as the no debug monitor command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug mvrdbg privileged EXEC command to enable debugging of Multicast VLAN Registration (MVR). Use the no form of this command to disable debugging output.
debug mvrdbg {all | events | igmpsn | management | ports}
no debug mvrdbg {all | events | igmpsn | management | ports}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug mvrdbg command is the same as the no debug mvrdbg command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug nvram privileged EXEC command to enable debugging of nonvolatile random-access memory (NVRAM) activity. Use the no form of this command to disable debugging output.
debug nvram
no debug nvram
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug nvram command is the same as the no debug nvram command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug pagp privileged EXEC command to enable debugging of Port Aggregation Protocol (PAgP) activity. Use the no form of this command to disable debugging output.
debug pagp [all | event | fsm | misc | packet]
no debug pagp [all | event | fsm | misc | packet]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug pagp command is the same as the no debug pagp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform acl privileged EXEC command to enable debugging of the access control list (ACL) manager. Use the no form of this command to disable debugging output.
debug platform acl {all | exit | label | main | racl | stack | vacl | vlmap | warn}
no debug platform acl {all | exit | label | main | racl | stack | vacl | vlmap | warn}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform acl command is the same as the no debug platform acl command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform cli-redirection main privileged EXEC command to enable debugging of the main (important) command-line interface (CLI) redirection events. Use the no form of this command to disable debugging output.
debug platform cli-redirection main
no debug platform cli-redirection main
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform cli-redirection main command is the same as the no debug platform cli-redirection main command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform configuration privileged EXEC command to enable debugging of configuration file activity across the stack. Use the no form of this command to disable debugging output.
debug platform configuration {all | reception | transmission}
no debug platform configuration {all | reception | transmission}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform configuration command is the same as the no debug platform configuration command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform cpu-queues privileged EXEC command to enable debugging of platform central processing unit (CPU) receive queues. Use the no form of this command to disable debugging output.
debug platform cpu-queues {broadcast-q | cbt-to-spt-q | cpuhub-q | host-q | icmp-q | igmp-snooping-q | layer2-protocol-q | logging-q | remote-console-q | routing-protocol-q | rpffail-q | software-fwd-q | stp-q}
no debug platform cpu-queues {broadcast-q | cbt-to-spt-q | cpuhub-q | host-q | icmp-q | igmp-snooping-q | layer2-protocol-q | logging-q | remote-console-q | routing-protocol-q | rpffail-q | software-fwd-q | stp-q}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform cpu-queues command is the same as the no debug platform cpu-queues command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform device-manager privileged EXEC command to enable debugging of the platform-dependent device manager. Use the no form of this command to disable debugging output.
debug platform device-manager {all | device-info | poll | port-download | trace}
no debug platform device-manager {all | device-info | poll | port-download | trace}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform device-manager command is the same as the no debug platform device-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform dot1x privileged EXEC command to enable debugging of stack-related 802.1X events. Use the no form of this command to disable debugging output.
debug platform dot1x {initialization | interface-configuration | rpc}
no debug platform dot1x {initialization | interface-configuration | rpc}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform dot1x command is the same as the no debug platform dot1x command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform etherchannel privileged EXEC command to enable debugging of platform-dependent EtherChannel events. Use the no form of this command to disable debugging output.
debug platform etherchannel {init | link-up | rpc-detailed | rpc-generic | warnings}
no debug platform etherchannel {init | link-up | rpc-detailed | rpc-generic | warnings}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform etherchannel command is the same as the no debug platform etherchannel command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform fallback-bridging privileged EXEC command to enable debugging of the platform-dependent fallback bridging manager. Use the no form of this command to disable debugging output.
debug platform fallback-bridging [error | retry | rpc {events | messages}]
no debug platform fallback-bridging [error | retry | rpc {events | messages}]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
If you do not specify a keyword, all fallback bridging manager debug messages appear.
The undebug platform fallback-bridging command is the same as the no debug platform fallback-bridging command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform forw-tcam privileged EXEC command to enable debugging of the forwarding ternary content addressable memory (TCAM) manager. Use the no form of this command to disable debugging output.
debug platform forw-tcam [adjustment | allocate | audit | error | move | read | write]
no debug platform forw-tcam [adjustment | allocate | audit | error | move | read | write]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
If you do not specify a keyword, all forwarding TCAM manager debug messages appear.
The undebug platform forw-tcam command is the same as the no debug platform forw-tcam command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform ip dhcp privileged EXEC command to debug Dynamic Host Configuration Protocol (DHCP) events. Use the no form of this command to disable debugging output.
debug platform ip dhcp [all | error | event | packet | rpc]
no debug platform ip dhcp [all | error | event | packet | rpc]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(19)EA1 |
This command was introduced. |
The undebug platform ip dhcp command is the same as the no debug platform ip dhcp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform ip igmp snooping privileged EXEC command to enable debugging of platform-dependent Internet Group Management Protocol (IGMP) snooping. Use the no form of this command to disable debugging output.
debug platform ip igmp snooping {all | di | error | event | group | mgmt | pak | retry | rpc | warn}
debug platform ip igmp snooping pak {ip-address | error | ipopt | leave| query | report | rx | svi | tx}
debug platform ip igmp snooping rpc [cfg | l3mm | misc | vlan]
no debug platform ip igmp snooping {all | di | error | event | group | mgmt | pak | retry | rpc | warn}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform ip igmp snooping command is the same as the no debug platform ip igmp snooping command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform ip multicast privileged EXEC command to enable debugging of IP multicast routing. Use the no form of this command to disable debugging output.
debug platform ip multicast {all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry | rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
no debug platform ip multicast {all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry | rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform ip multicast command is the same as the no debug platform ip multicast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform ip unicast privileged EXEC command to enable debugging of platform-dependent IP unicast routing. Use the no form of this command to disable debugging output.
debug platform ip unicast {adjacency | all | arp | dhcp | errors | events | interface | mpath | registries | retry | route | rpc | standby | statistics}
no debug platform ip unicast {adjacency | all | arp | dhcp | errors | events | interface | mpath | registries | retry | route | rpc | standby | statistics}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform ip unicast command is the same as the no debug platform ip unicast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform ipc privileged EXEC command to enable debugging of the platform-dependent Interprocess Communication (IPC) Protocol. Use the no form of this command to disable debugging output.
debug platform ipc {all | init | receive | send | trace}
no debug platform {all | init | receive | send | trace}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform ipc command is the same as the no debug platform ipc.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform led privileged EXEC command to enable debugging of light-emitting diode (LED) actions. Use the no form of this command to disable debugging output.
debug platform led {generic | signal | stack}
no debug platform led {generic | signal | stack}
generic |
Display LED generic action debug messages. |
signal |
Display LED signal bit map debug messages. |
stack |
Display LED stack action debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform led command is the same as the no debug platform led command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform matm privileged EXEC command to enable debugging of platform-dependent MAC address management. Use the no form of this command to disable debugging output.
debug platform matm {aging | all | ec-aging | errors | learning | rpc | secure-address | warnings}
no debug platform matm {aging | all | ec-aging | errors | learning | rpc | secure-address | warnings}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform matm command is the same as the no debug platform matm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform messaging application privileged EXEC command to enable debugging of application messaging activity. Use the no form of this command to disable debugging output.
debug platform messaging application {all | badpak | cleanup | events | memerr | messages | stackchg | usererr}
no debug platform messaging application {all | badpak | cleanup | events | memerr | messages | stackchg | usererr}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform messaging application command is the same as the no debug platform messaging application command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform phy privileged EXEC command to enable debugging of PHY driver information. Use the no form of this command to disable debugging output.
debug platform phy {automdix | flowcontrol | forced | init-seq | link-status | read | sfp | show-controller | speed | write}
no debug platform phy {automdix | flowcontrol | forced | init-seq | link-status | read | sfp | show-controller | speed | write}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
12.1(14)EA1 |
The automdix keyword was added. |
The undebug platform phy command is the same as the no debug platform phy command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform pm privileged EXEC command to enable debugging of the platform-dependent port manager software module. Use the no form of this command to disable debugging output.
debug platform pm {all | counters | errdisable | etherchnl | exceptions | hpm-events | idb-events | if-numbers | ios-events | link-status | platform | pm-events | pm-vectors [detail] | rpc [general | oper-info | state | vectors | vp-events] | soutput | stack-manager | sync | vlans}
no debug platform pm {all | counters | errdisable | etherchnl | exceptions | hpm-events | idb-events | if-numbers | ios-events | link-status | platform | pm-events | pm-vectors [detail] | rpc [general | oper-info | state | vectors | vp-events] | soutput | stack-manager | sync | vlans}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform pm command is the same as the no debug platform pm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform port-asic privileged EXEC command to enable debugging of the port application-specific integrated circuit (ASIC) driver. Use the no form of this command to disable debugging output.
debug platform port-asic {interrupt | periodic | read | stack | write}
no debug platform port-asic {interrupt | periodic | read | stack | write}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform port-asic command is the same as the no debug platform port-asic command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform port-security privileged EXEC command to enable debugging of platform-dependent port-security information. Use the no form of this command to disable debugging output.
debug platform port-security {add | aging | all | delete | errors | rpc | warnings}
no debug platform port-security {add | aging | all | delete | errors | rpc | warnings}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform port-security command is the same as the no debug platform port-security command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform qos-acl-tcam privileged EXEC command to enable debugging of the quality of service (QoS) and access control list (ACL) ternary content addressable memory (TCAM) manager software. Use the no form of this command to disable debugging output.
debug platform qos-acl-tcam {all | ctcam | errors | labels | mask | rpc | tcam}
no debug platform qos-acl-tcam {all | ctcam | errors | labels | mask | rpc | tcam}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform qos-acl-tcam command is the same as the no debug platform qos-acl-tcam command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform remote-commands privileged EXEC command to enable debugging of remote commands. Use the no form of this command to disable debugging output.
debug platform remote-commands
no debug platform remote-commands
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform remote-commands command is the same as the no debug platform remote-commands command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform resource-manager privileged EXEC command to enable debugging of the resource manager software. Use the no form of this command to disable debugging output.
debug platform resource-manager {all | dm | erd | errors | madmed | sd | stats | vld}
no debug platform resource-manager {all | dm | erd | errors | madmed | sd | stats | vld}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform resource-manager command is the same as the no debug platform resource-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform snmp privileged EXEC command to enable debugging of the platform-dependent Simple Network Management Protocol (SNMP) software. Use the no form of this command to disable debugging output.
debug platform snmp
no debug platform snmp
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform snmp command is the same as the no debug platform snmp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform span privileged EXEC command to enable debugging of the platform-dependent Switched Port Analyzer (SPAN) software. Use the no form of this command to disable debugging output.
debug platform span
no debug platform span
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform span command is the same as the no debug platform span command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform stack-manager privileged EXEC command to enable debugging of the stack manager software. Use the no form of this command to disable debugging output.
debug platform stack-manager {all | rpc | sdp | sim | ssm | trace}
no debug platform stack-manager {all | rpc | sdp | sim | ssm | trace}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform stack-manager command is the same as the no debug platform stack-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform supervisor-asic privileged EXEC command to enable debugging of the supervisor application-specific integrated circuit (ASIC). Use the no form of this command to disable debugging output.
debug platform supervisor-asic {all | errors | receive | send}
no debug platform supervisor-asic {all | errors | receive | send}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform supervisor-asic command is the same as the no debug platform supervisor-asic command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform sw-bridge privileged EXEC command to enable debugging of the software bridging function. Use the no form of this command to disable debugging output.
debug platform sw-bridge {broadcast | control | multicast | packet | unicast}
no debug platform sw-bridge {broadcast | control | multicast | packet | unicast}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform sw-bridge command is the same as the no debug platform sw-bridge command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform tcam privileged EXEC command to enable debugging of ternary content addressable memory (TCAM) access and lookups. Use the no form of this command to disable debugging output.
debug platform tcam {log | read | search | write}
debug platform tcam log l2 {acl {input | output} | local | qos}
debug platform tcam log l3 {acl {input | output} | ipv6 {acl {input | output} | local | qos | secondary} | local | qos | secondary}
debug platform tcam read {reg | ssram | tcam}
debug platform tcam search
debug platform tcam write {forw-ram | reg | tcam}
no debug platform tcam {log | read | search | write}
no debug platform tcam log l2 {acl {input | output} | local | qos}
no debug platform tcam log l3 {acl {input | output} | ipv6 {acl {input | output} | local | qos | secondary} | local | qos | secondary}
no debug platform tcam read {reg | ssram | tcam}
no debug platform tcam search
no debug platform tcam write {forw-ram | reg | tcam}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform tcam command is the same as the no debug platform tcam command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform udld privileged EXEC command to enable debugging of the platform-dependent UniDirectional Link Detection (UDLD) software. Use the no form of this command to disable debugging output.
debug platform udld [all | error | rpc {events | messages}]
no debug platform udld [all | error | rpc {events | messages}]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform udld command is the same as the no debug platform udld command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug platform vlan privileged EXEC command to enable debugging of the VLAN manager software. Use the no form of this command to disable debugging output.
debug platform vlan {errors | mvid | rpc}
no debug platform vlan {errors | mvid | rpc}
errors |
Display VLAN error debug messages. |
mvid |
Display mapped VLAN ID allocations and free debug messages. |
rpc |
Display remote procedure call (RPC) debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug platform vlan command is the same as the no debug platform vlan command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug pm privileged EXEC command to enable debugging of port manager (PM) activity. The port manager is a state machine that controls all the logical and physical interfaces. All features, such as VLANs, UniDirectional Link Detection (UDLD), and so forth, work with the port manager to provide switch functions. Use the no form of this command to disable debugging output.
debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split | vlan | vp}
no debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split | vlan | vp}
Note Though visible in the command-line help strings, the scp and pvlan keywords are not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
12.1(14)EA1 |
The hatable keyword was added. |
The undebug pm command is the same as the no debug pm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug port-security privileged EXEC command to enable debugging of the allocation and states of the port security subsystem. Use the no form of this command to disable debugging output.
debug port-security
no debug port-security
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug port-security command is the same as the no debug port-security command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug qos-manager privileged EXEC command to enable debugging of the quality of service (QoS) manager software. Use the no form of this command to disable debugging output.
debug qos-manager {all | event | verbose}
no debug qos-manager {all | event | verbose}
all |
Display all QoS-manager debug messages. |
event |
Display QoS-manager related-event debug messages. |
verbose |
Display QoS-manager detailed debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug qos-manager command is the same as the no debug qos-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree privileged EXEC command to enable debugging of spanning-tree activities. Use the no form of this command to disable debugging output.
debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | csuf/csrt | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | synchronization | uplinkfast}
no debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | csuf/csrt | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | synchronization | uplinkfast}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
12.1(14)EA1 |
The mstp and csuf/csrt keywords were added. |
The undebug spanning-tree command is the same as the no debug spanning-tree command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree backbonefast privileged EXEC command to enable debugging of spanning-tree BackboneFast events. Use the no form of this command to disable debugging output.
debug spanning-tree backbonefast [detail | exceptions]
no debug spanning-tree backbonefast [detail | exceptions]
detail |
(Optional) Display detailed BackboneFast debug messages. |
exceptions |
(Optional) Display spanning-tree BackboneFast-exception debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug spanning-tree backbonefast command is the same as the no debug spanning-tree backbonefast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree bpdu privileged EXEC command to enable debugging of sent and received spanning-tree bridge protocol data units (BPDUs). Use the no form of this command to disable debugging output.
debug spanning-tree bpdu [receive | transmit]
no debug spanning-tree bpdu [receive | transmit]
receive |
(Optional) Display the nonoptimized path for received BPDU debug messages. |
transmit |
(Optional) Display the nonoptimized path for sent BPDU debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug spanning-tree bpdu command is the same as the no debug spanning-tree bpdu command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree bpdu-opt privileged EXEC command to enable debugging of optimized spanning-tree bridge protocol data units (BPDUs) handling. Use the no form of this command to disable debugging output.
debug spanning-tree bpdu-opt [detail | packet]
no debug spanning-tree bpdu-opt [detail | packet]
detail |
(Optional) Display detailed optimized BPDU-handling debug messages. |
packet |
(Optional) Display packet-level optimized BPDU-handling debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug spanning-tree bpdu-opt command is the same as the no debug spanning-tree bpdu-opt command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree mstp privileged EXEC command to enable debugging of the Multiple Spanning Tree Protocol (MSTP) software. Use the no form of this command to disable debugging output.
debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration | pm | proposals | region | roles | sanity_check | sync | tc | timers}
no debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration | pm | proposals | region | roles | sanity_check | sync | tc | timers}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(14)EA1 |
This command was introduced. |
The undebug spanning-tree mstp command is the same as the no debug spanning-tree mstp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree switch privileged EXEC command to enable debugging of the software interface between the Spanning Tree Protocol (STP) software module and the port manager software module. Use the no form of this command to disable debugging output.
debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode] | uplinkfast}
no debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode] | uplinkfast}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
12.1(14)EA1 |
The flush and uplinkfast keywords were added. |
The undebug spanning-tree switch command is the same as the no debug spanning-tree switch command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug spanning-tree uplinkfast privileged EXEC command to enable debugging of spanning-tree UplinkFast events. Use the no form of this command to disable debugging output.
debug spanning-tree uplinkfast [exceptions]
no debug spanning-tree uplinkfast [exceptions]
exceptions |
(Optional) Display spanning-tree UplinkFast-exception debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug spanning-tree uplinkfast command is the same as the no debug spanning-tree uplinkfast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug sw-vlan privileged EXEC command to enable debugging of VLAN manager activities. Use the no form of this command to disable debugging output.
debug sw-vlan {badpmcookies | cfg-vlan {bootup | cli} | events | ifs | management | notification | packets | registries | vtp}
no debug sw-vlan {badpmcookies | cfg-vlan {bootup | cli} | events | ifs | management | notification | packets | registries | vtp}
badpmcookies |
Display debug messages for VLAN manager incidents of bad port manager cookies. |
cfg-vlan {bootup | cli} |
Display config-vlan debug messages. The keywords have these meanings: •bootup—Display messages when the switch is booting up. •cli—Display messages when the command-line interface (CLI) is in config-vlan mode. |
events |
Display debug messages for VLAN manager events. |
ifs |
See the debug sw-vlan ifs command. |
management |
Display debug messages for VLAN manager management of internal VLANs. |
notification |
See the debug sw-vlan notification command. |
packets |
Display debug messages for packet handling and encapsulation processes. |
registries |
Display debug messages for VLAN manager registries. |
vtp |
See the debug sw-vlan vtp command. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug sw-vlan command is the same as the no debug sw-vlan command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug sw-vlan ifs privileged EXEC command to enable debugging of the VLAN manager IOS file system (IFS) error tests. Use the no form of this command to disable debugging output.
debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
no debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug sw-vlan ifs command is the same as the no debug sw-vlan ifs command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
When determining the file read operation, Operation 1 reads the file header, which contains the header verification word and the file version number. Operation 2 reads the main body of the file, which contains most of the domain and VLAN information. Operation 3 reads type length version (TLV) descriptor structures. Operation 4 reads TLV data.
Use the debug sw-vlan notification privileged EXEC command to enable debugging of the activation and deactivation of Inter-Link Switch (ISL) VLAN IDs. Use the no form of this command to disable debugging output.
debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange}
no debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug sw-vlan notification command is the same as the no debug sw-vlan notification command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Use the debug sw-vlan vtp privileged EXEC command to enable debugging of the VLAN Trunking Protocol (VTP) code. Use the no form of this command to disable debugging output.
debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
no debug sw-vlan vtp {events | packets | pruning | xmit}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug sw-vlan vtp command is the same as the no debug sw-vlan vtp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
If no further parameters are entered after the pruning keyword, VTP pruning debugging messages appear. They are generated by the VTP_PRUNING_LOG_NOTICE, VTP_PRUNING_LOG_INFO, VTP_PRUNING_LOG_DEBUG, VTP_PRUNING_LOG_ALERT, and VTP_PRUNING_LOG_WARNING macros in the VTP pruning code.
Use the debug udld privileged EXEC command to enable debugging of the UniDirectional Link Detection (UDLD) feature. Use the no form of this command to disable UDLD debugging.
debug udld {events | packets | registries}
no debug udld {events | packets | registries}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug udld command is the same as the no debug udld command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.
For debug udld events, these debugging messages appear:
•General UDLD program logic flow
•State machine state changes
•Program actions for the set and clear ErrDisable state
•Neighbor cache additions and deletions
•Processing of configuration commands
•Processing of link-up and link-down indications
For debug udld packets, these debugging messages appear:
•General packet processing program flow on receipt of an incoming packet
•Indications of the contents of the various pieces of packets received (such as type length versions [TLVs]) as they are examined by the packet reception code
•Packet transmission attempts and the outcome
For debug udld registries, these categories of debugging messages appear:
•Sub-block creation
•Fiber-port status changes
•State change indications from the port manager software
•MAC address registry calls
Use the debug vqpc privileged EXEC command to enable debugging of the VLAN Query Protocol (VQP) client. Use the no form of this command to disable debugging output.
debug vqpc [all | cli | events | learn | packet]
no debug vqpc [all | cli | events | learn | packet]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.1(11)AX |
This command was introduced. |
The undebug vqpc command is the same as the no debug vqpc command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then enter the debug command at the command-line prompt of the stack member.