- Index
- Preface
- Using the Command-Line Interface
- Catalyst 3750-X and 3560-X Switch Cisco IOS Commands - aaa accounting through reserved-only
- Catalyst 3750-X and 3560-X Switch Cisco IOS Commands - rmon collection through show vtp
- Catalyst 3750-X and 3560-X Switch Cisco IOS Commands - shutdown through vtp
- Catalyst 3750-X and 3560-X Switch Bootloader Commands
- Catalyst 3750-X and 3560-X Switch Debug Commands
- Catalyst 3750-X and 3560-X Switch Show Platform Commands
- Acknowledgments for Open-Source Software
- debug authentication
- debug auto qos
- debug backup
- debug cisp
- debug cluster
- debug device-sensor
- debug dot1x
- debug dtp
- debug eap
- debug etherchannel
- debug fastethernet
- debug ilpower
- debug interface
- debug ip dhcp snooping
- debug ip verify source packet
- debug ip igmp filter
- debug ip igmp max-groups
- debug ip igmp snooping
- debug lacp
- debug lldp packets
- debug logging smartlog debug
- debug mac-notification
- debug macsec
- debug matm
- debug matm move update
- debug mka
- debug monitor
- debug mvrdbg
- debug nmsp
- debug nvram
- debug pagp
- debug platform acl
- debug platform backup interface
- debug platform cisp
- debug platform cli-redirection main
- debug platform configuration
- debug platform cpu-queues
- debug platform device-manager
- debug platform dot1x
- debug platform etherchannel
- debug platform fallback-bridging
- debug platform forw-tcam
- debug platform frontend-controller
- debug platform ip arp inspection
- debug platform ip dhcp
- debug platform ip igmp snooping
- debug platform ip multicast
- debug platform ip unicast
- debug platform ip wccp
- debug platform ipc
- debug platform led
- debug platform matm
- debug platform messaging application
- debug platform phy
- debug platform pm
- debug platform port-asic
- debug platform port-security
- debug platform qos-acl-tcam
- debug platform remote-commands
- debug platform resource-manager
- debug platform snmp
- debug platform span
- debug platform stack-manager
- debug platform supervisor-asic
- debug platform sw-bridge
- debug platform tcam
- debug platform udld
- debug platform vlan
- debug pm
- debug port-security
- debug qos-manager
- debug spanning-tree
- debug spanning-tree backbonefast
- debug spanning-tree bpdu
- debug spanning-tree bpdu-opt
- debug spanning-tree mstp
- debug spanning-tree switch
- debug spanning-tree uplinkfast
- debug sw-vlan
- debug sw-vlan ifs
- debug sw-vlan notification
- debug sw-vlan vtp
- debug udld
- debug vqpc
Catalyst 3750-X and 3560-X Switch Debug Commands
This appendix describes the debug privileged EXEC commands that have been created or changed for use with the Catalyst 3750-X and 3560-X switch. These commands are helpful in diagnosing and resolving internetworking problems and should be enabled only under the guidance of Cisco technical support staff.
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use the
debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. It is best to use the
debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased
debug command processing overhead will affect system use.
debug authentication
Use the debug authentication privileged EXEC command to enable debugging of the authentication settings on an interface. Use the no form of this command to disable debugging.
debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
no debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug authentication command is the same as the no debug authentication command.
On a 3750-E switch, when you enable debugging, it is enabled only on the stack master.
To enable debugging on a stack member, you can start a session from the stack master by using the session switch-number privileged EXEC command and then entering the debug authentication command at the command-line prompt of the stack member. You also can use the remote command stack-member-number line privileged EXEC command on the stack master switch to enable debugging on a stack member.
Related Commands
debug auto qos
Use the debug auto qos 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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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 auto qos privileged EXEC command.
The undebug auto qos command is the same as the no debug auto qos command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Examples
This example shows how to display the QoS configuration that is automatically generated when auto-QoS is enabled:
Related Commands
debug backup
Use the debug backup privileged EXEC command to enable debugging of the Flex Links backup interface. Use the no form of this command to disable debugging.
debug backup { all | errors | events | vlan-load-balancing }
no debug backup { all | errors | events | vlan-load-balancing }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug backup command is the same as the no debug backup command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug cisp
Use the debug cisp global configuration command to enable debugging message exchanges and events on a Client Information Signalling Protocol (CISP)-enabled interface.Use the no form of this command to disable debugging.
debug cisp [all | errors | events | packets | sync]
no debug cisp [initialization | interface-configuration | rpc]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Related Commands
|
|
|
|---|---|
debug cluster
Use the debug cluster privileged EXEC command to enable debugging of cluster-specific events. Use the no form of this command to disable debugging.
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 }
Syntax Description
Display the Hot Standby Router Protocol (HSRP) debug messages. |
|
Display Simple Network Management Protocol (SNMP) debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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 on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
debug device-sensor
To enable debugging for Device Sensor, use the debug device-sensor command in privileged EXEC mode.
debug device-sensor errors events
Syntax Description
Displays messages for events such as protocol packet arrivals, identity updates, and release events sent to the session manager. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the debug device-sensor command in conjunction with the debug authentication all command to troubleshoot scenarios where the Device Sensor cache entries are not being created for the connected devices.
Examples
The following is sample output from the debug device-sensor events command. The debug output shows how Cisco Discovery Protocol packets and TLVs are received from the device connected to the GigabitEthernet 2/1 interface.
Related Commands
debug dot1x
Use the debug dot1x privileged EXEC command to enable debugging of the IEEE 802.1x authentication feature. Use the no form of this command to disable debugging.
debug dot1x { all | errors | events | feature | packets | registry | state-machine }
no debug dot1x { all | errors | events | feature | packets | registry | state-machine }
Syntax Description
Note Though visible in the command-line help strings, the redundancy keyword is not supported.
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug dot1x command is the same as the no debug dot1x command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
debug dtp
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.
debug dtp { aggregation | all | decision | events | oserrs | packets | queue | states | timers }
no debug dtp { aggregation | all | decision | events | oserrs | packets | queue | states | timers }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug dtp command is the same as the no debug dtp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays DTP information for the switch or for a specified interface. |
debug eap
Use the debug eap privileged EXEC command to enable debugging of the Extensible Authentication Protocol (EAP) activity. Use the no form of this command to disable debugging.
debug dot1x { all | authenticator | errors | events | md5 | packets | peer | sm }
no debug dot1x { all | authenticator | errors | events | md5 | packets | peer | sm }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug dot1x command is the same as the no debug dot1x command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays EAP registration and session information for the switch or for the specified port. |
debug etherchannel
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.
debug etherchannel [ all | detail | error | event | idb ]
no debug etherchannel [ all | detail | error | event | idb ]
Syntax Description
(Optional) Display PAgP interface descriptor block debug messages. |
Note Though visible in the command-line help strings, the linecard keyword is not supported.
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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 on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug fastethernet
Use the debug fastethernet privileged EXEC command to enable debugging of the Ethernet management port. Use the no form of this command to disable debugging.
debug fastethernet { af | events | packets }
no debug fastethernet { af | events | packets }
Syntax Description
Display Ethernet management port software-address-filter debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug fastethernet { af | events | packets } command is the same as the no debug fastethernet { af | events | packets } command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug ilpower
Use the debug ilpower privileged EXEC command to enable debugging of the power controller and Power over Ethernet (PoE) system. Use the no form of this command to disable debugging.
debug ilpower { cdp | controller | event | ha | port | powerman | registries }
no debug ilpower { cdp | controller | event | ha | port | powerman | registries }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is supported only on PoE-capable switches.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
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. |
debug interface
Use the debug interface privileged EXEC command to enable debugging of interface-related activities. Use the no form of this command to disable debugging.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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 on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug ip dhcp snooping
Use the debug ip dhcp snooping privileged EXEC command to enable debugging of DHCP snooping. Use the no form of this command to disable debugging.
debug ip dhcp snooping { mac-address | agent | event | packet }
no debug ip dhcp snooping { mac-address | agent | event | packet }
Syntax Description
Display debug messages for a DHCP packet with the specified MAC address. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug ip dhcp snooping command is the same as the no debug ip dhcp snooping command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug ip verify source packet
Use the debug ip verify source packet privileged EXEC command to enable debugging of IP source guard. Use the no form of this command to disable debugging.
no debug ip verify source packet
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug ip verify source packet command is the same as the no debug ip verify source packet command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug ip igmp filter
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug ip igmp filter command is the same as the no debug ip igmp filter command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug ip igmp max-groups
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug ip igmp max-groups command is the same as the no debug ip igmp max-groups command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug ip igmp snooping
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.
debug ip igmp snooping [ group | management | querier | router | timer ]
no debug ip igmp snooping [ group | management | querier | router | timer ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug ip igmp snooping command is the same as the no debug ip igmp snooping command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about platform-dependent IGMP snooping activity. |
|
Displays information about the types of debugging that are enabled. |
debug lacp
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.
debug lacp [ all | event | fsm | misc | packet ]
no debug lacp [ all | event | fsm | misc | packet ]
Syntax Description
(Optional) Display LACP finite state-machine debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug lacp command is the same as the no debug lacp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug lldp packets
Use the debug lldp packets privileged EXEC command to enable debugging of Link Layer Discovery Protocol (LLDP) packets. Use the no form of this command to disable debugging.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug lldp packets command is the same as the no debug lldp packets command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug logging smartlog debug
To debug smart logging, use the debug logging smartlog debug command in privileged EXEC mode. To disable smart logging debugging, use the no form of this command.
no debug logging smartlog debug
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug logging smartlog debug command is the same as the no debug logging smartlog debug command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug mac-notification
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug mac-notification command is the same as the no debug mac-notification command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays the MAC address notification information for all interfaces or the specified interface. |
debug macsec
To enable debugging of 802.1ae Media Access Control Security (MACsec), use the debug macsec privileged EXEC command. To disable debugging, use the no form of this command.
debug macsec [ errors | events ]
no debug macsec [ errors | events ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Entering the debug macsec command with no keywords starts all MACsec debugging facilities.
The undebug macsec command is the same as the no debug macsec command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug matm
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug matm command is the same as the no debug matm command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about platform-dependent MAC address management. |
|
Displays information about the types of debugging that are enabled. |
debug matm move update
Use the debug matm move update privileged EXEC command to enable debugging of MAC address-table move update message processing.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug matm move update command is the same as the no debug matm move update command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
mac address-table move update { receive | transmit } |
Configures MAC address-table move update feature on the switch. |
Displays information about the types of debugging that are enabled. |
|
Displays the MAC address-table move update information on the switch. |
debug mka
To enable debugging of the MACsec Key Agreement (MKA) protocol sessions, use the debug mka privileged EXEC command. To disable debugging, use the no form of this command.
debug mka [ errors | events | lli | mli | packets | trace ]
no debug mka [ errors | events | lli | mli | packets | trace ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Entering the debug mka command with no keywords enables all MKA debugging facilities.
The undebug backup command is the same as the no debug backup command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without starting a session.
Related Commands
|
|
|
|---|---|
debug monitor
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.
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 }
Syntax Description
Display SPAN interface description block (IDB) update-trace debug messages. |
|
Display SPAN and Simple Network Management Protocol (SNMP) tracing debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug monitor command is the same as the no debug monitor command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays information about all SPAN and remote SPAN (RSPAN) sessions on the switch. |
debug mvrdbg
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.
debug mvrdbg { all | events | igmpsn | management | ports }
no debug mvrdbg { all | events | igmpsn | management | ports }
Syntax Description
Display MVR Internet Group Management Protocol (IGMP) snooping-activity debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug mvrdbg command is the same as the no debug mvrdbg command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug nmsp
Use the debug nmsp privileged EXEC command to the enable debugging of the Network Mobility Services Protocol (NMSP) on the switch. Use the no form of this command to disable debugging.
debug nmsp {all | connection | error | event | packet | rx | tx}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug nmsp command is the same as the no debug nmsp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug nvram
Use the debug nvram privileged EXEC command to enable debugging of NVRAM activity. Use the no form of this command to disable debugging.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug nvram command is the same as the no debug nvram command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug pagp
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.
debug pagp [ all | dual-active | event | fsm | misc | packet ]
no debug pagp [ all | dual-active | event | fsm | misc | packet ]
Syntax Description
(Optional) Display PAgP finite state-machine debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug pagp command is the same as the no debug pagp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug platform acl
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.
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 }
Syntax Description
Note Though visible in the command-line help strings, the stack keyword is not supported on Catalyst 3560-X switches.
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform acl command is the same as the no debug platform acl command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform backup interface
Use the debug platform backup interface privileged EXEC command to enable debugging of the Flex Links platform backup interface. Use the no form of this command to disable debugging.
debug platform backup interface
no debug platform backup interface
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform backup interface command is the same as the no platform debug backup interface command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform cisp
Use the debug platform cisp global configuration command to enable platform-level debugging of a switch that has one or more Client Information Signalling Protocol (CISP)-enabled interfaces. Use the no form of this command to disable debugging.
debug platform cisp [initialization | interface-configuration | rpc]
no debug platform cisp [initialization | interface-configuration | rpc]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, start a session from the stack master by using the session switch-number privileged EXEC command and enter the debug command at the command-line prompt of the stack member. You also can use the remote command stack-member-number <line> privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
debug platform cli-redirection main
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.
debug platform cli-redirection main
no debug platform cli-redirection main
Note This command is supported only on Catalyst 3750-X switches.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform cli-redirection main command is the same as the no debug platform cli-redirection main command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform configuration
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.
debug platform configuration { all | reception | transmission }
no debug platform configuration { all | reception | transmission }
Note This command is supported only on Catalyst 3750-X switches.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform configuration command is the same as the no debug platform configuration command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform cpu-queues
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform cpu-queues command is the same as the no debug platform cpu-queues command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform device-manager
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.
debug platform device-manager { all | device-info | poll | port-download | trace }
no debug platform device-manager { all | device-info | poll | port-download | trace }
Note This command is not supported on switches running the LAN base feature set.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform device-manager command is the same as the no debug platform device-manager command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform dot1x
Use the debug platform dot1x privileged EXEC command to enable debugging of IEEE 802.1x events. On switch stacks, this command enables debugging of stack-related IEEE 802.1x events. Use the no form of this command to disable debugging.
debug platform dot1x { initialization | interface-configuration | rpc }
no debug platform dot1x { initialization | interface-configuration | rpc }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform dot1x command is the same as the no debug platform dot1x command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform etherchannel
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.
debug platform etherchannel { init | link-up | rpc | warnings }
no debug platform etherchannel { init | link-up | rpc | warnings }
Syntax Description
Display EtherChannel link-up and link-down related debug messages. |
|
Display EtherChannel remote procedure call (RPC) debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform etherchannel command is the same as the no debug platform etherchannel command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform fallback-bridging
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.
debug platform fallback-bridging [ error | retry | rpc { events | messages }]
no debug platform fallback-bridging [ error | retry | rpc { events | messages }]
Note This command is not supported on switches running the LAN base feature set.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
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 on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform forw-tcam
Use the debug platform forw-tcam privileged EXEC command to enable debugging of the forwarding hardware memory manager. Use the no form of this command to disable debugging.
debug platform forw-tcam [ adjustment | allocate | audit | error | move | read | write ]
no debug platform forw-tcam [ adjustment | allocate | audit | error | move | read | write ]
Note This command is not supported on switches running the LAN base feature set.
Syntax Description
(Optional) Display hardware manager adjustment debug messages. |
|
(Optional) Display hardware manager allocation debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify a keyword, all forwarding hardware 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 on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform frontend-controller
Use the debug platform frontend-controller privileged EXEC command to enable debugging of front-end controller activity. Use the no form of this command to disable debugging.
debug platform frontend-controller { all | image | led | manager | poe | register | thermal }
no debug platform frontend-controller { all | image | led | manager | poe | register | thermal }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform frontend-controller command is the same as the no debug platform frontend-controller command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
debug platform ip arp inspection
Use the debug platform ip arp inspection privileged EXEC command to debug dynamic Address Resolution Protocol (ARP) inspection events. Use the no form of this command to disable debugging.
debug platform ip arp inspection { all | error | event | packet | rpc }
no debug platform ip arp inspection { all | error | event | packet | rpc }
Syntax Description
Display dynamic ARP inspection packet-related debug messages. |
|
Display dynamic ARP inspection remote procedure call (RPC) request debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip arp inspection command is the same as the no debug platform ip arp inspection command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays the dynamic ARP inspection configuration and operating state. |
|
Displays information about the types of debugging that are enabled. |
debug platform ip dhcp
Use the debug platform ip dhcp privileged EXEC command to debug DHCP events. Use the no form of this command to disable debugging.
debug platform ip dhcp [ all | error | event | packet | rpc ]
no debug platform ip dhcp [ all | error | event | packet | rpc ]
Syntax Description
(Optional) Display DHCP remote procedure call (RPC) request debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip dhcp command is the same as the no debug platform ip dhcp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform ip igmp snooping
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip igmp snooping command is the same as the no debug platform ip igmp snooping command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about platform-independent IGMP snooping activity. |
|
Displays information about the types of debugging that are enabled. |
debug platform ip multicast
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip multicast command is the same as the no debug platform ip multicast command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform ip unicast
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.
debug platform ip unicast { adjacency | all | arp | dhcp | errors | events | interface | mpath | registries | retry | route | rpc | rpf | standby | statistics }
no debug platform ip unicast { adjacency | all | arp | dhcp | errors | events | interface | mpath | registries | retry | route | rpc | rpf | standby | statistics }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip unicast command is the same as the no debug platform ip unicast command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform ip wccp
Use the debug platform ip wccp privileged EXEC command to enable debugging of Web Cache Communication Protocol (WCCP). Use the no form of this command to disable debugging.
debug platform ip wccp { acl | event | odm | trace }
no debug platform ip wccp { acl | event | odm | trace }
Note This command is available only if your switch is running the IP services feature set.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ip wccp command is the same as the no debug platform ip wccp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform ipc
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.
debug platform ipc { all | init | receive | send | trace }
no debug platform { all | init | receive | send | trace }
Note This command is supported only on Catalyst 3750-X switches.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform ipc command is the same as the no debug platform ipc.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform led
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.
debug platform led { generic | signal | stack }
no debug platform led { generic | signal | stack }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform led command is the same as the no debug platform led command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform matm
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform matm command is the same as the no debug platform matm command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about platform-independent MAC address management. |
|
Displays information about the types of debugging that are enabled. |
debug platform messaging application
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform messaging application command is the same as the no debug platform messaging application command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable e debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform phy
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.
debug platform phy { automdix | cablediag | dual-purpose | flcd { configure | ipc | iter | trace } | flowcontrol | forced | init-seq | link-status | read | sfp | show-controller | speed | write | xenpak }
no debug platform phy { automdix | cablediag | dual-purpose | flcd { configure | ipc | iter | trace } | flowcontrol | forced | init-seq | link-status | read | sfp | show-controller | speed | write | xenpak }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform phy command is the same as the no debug platform phy command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform pm
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.
debug platform pm { all | counters | errdisable | etherchnl | exceptions | hpm-events | idb-events | if-numbers | ios-events | link-status | platform | pm-events | pm-span | pm-vectors [ detail ] | rpc [ general | oper-info | state | vectors | vp-events ] | soutput-vectors | 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-span | pm-vectors [ detail ] | rpc [ general | oper-info | state | vectors | vp-events ] | soutput-vectors | stack-manager | sync | vlans }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform pm command is the same as the no debug platform pm command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform port-asic
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.
debug platform port-asic { interrupt | periodic | read | stack | write }
no debug platform port-asic { interrupt | periodic | read | stack | write }
Syntax Description
Display port-ASIC interrupt-related function debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform port-asic command is the same as the no debug platform port-asic command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform port-security
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.
debug platform port-security { add | aging | all | delete | errors | rpc | warnings }
no debug platform port-security { add | aging | all | delete | errors | rpc | warnings }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform port-security command is the same as the no debug platform port-security command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable e debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform qos-acl-tcam
Use the debug platform qos-acl-tcam privileged EXEC command to enable debugging of the quality of service (QoS) and access control list (ACL) hardware memory manager software. Use the no form of this command to disable debugging.
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 }
Syntax Description
Display all QoS and ACL ternary content addressable memory (QATM) manager debug messages. |
|
Display QATM remote procedure call (RPC) related-events debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform qos-acl-tcam command is the same as the no debug platform qos-acl-tcam command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform remote-commands
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.
debug platform remote-commands
no debug platform remote-commands
Note This command is not supported on switches running the LAN base feature set.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform remote-commands command is the same as the no debug platform remote-commands command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform resource-manager
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.
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 }
Syntax Description
Display the MAC address descriptor table and multi-expansion descriptor table debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform resource-manager command is the same as the no debug platform resource-manager command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform snmp
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform snmp command is the same as the no debug platform snmp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform span
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform span command is the same as the no debug platform span command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform stack-manager
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.
debug platform stack-manager { all | rpc | sdp | sim | ssm | trace }
no debug platform stack-manager { all | rpc | sdp | sim | ssm | trace }
Note This command is supported only on Catalyst 3750-X switches.
Syntax Description
Display stack manager remote procedure call (RPC) usage debug messages. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform stack-manager command is the same as the no debug platform stack-manager command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable e debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform supervisor-asic
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.
debug platform supervisor-asic { all | errors | receive | send }
no debug platform supervisor-asic { all | errors | receive | send }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform supervisor-asic command is the same as the no debug platform supervisor-asic command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform sw-bridge
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.
debug platform sw-bridge { broadcast | control | multicast | packet | unicast }
no debug platform sw-bridge { broadcast | control | multicast | packet | unicast }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform sw-bridge command is the same as the no debug platform sw-bridge command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform tcam
Use the debug platform tcam privileged EXEC command to enable debugging of hardware memory access and lookups. Use the no form of this command to disable debugging.
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 | s econdary } | local | qos | secondary }
debug platform tcam read { reg | ssram | tcam }
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 | s econdary } | local | qos | secondary }
no debug platform tcam read { reg | ssram | tcam }
no debug platform tcam write { forw-ram | reg | tcam }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform tcam command is the same as the no debug platform tcam command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform udld
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.
debug platform udld [ all | error | rpc { events | messages }]
no debug platform udld [ all | error | rpc { events | messages }]
Syntax Description
(Optional) Display UDLD remote procedure call (RPC) debug messages. The keywords have these meanings: |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform udld command is the same as the no debug platform udld command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug platform vlan
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.
debug platform vlan { errors | mvid | rpc }
no debug platform vlan { errors | mvid | rpc }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug platform vlan command is the same as the no debug platform vlan command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug pm
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.
debug pm { all | assert | card | etherchnl | hatable | messages | port | redundancy | registry | sm | span | split | vlan | vp }
no debug pm { all | assert | card | etherchnl | hatable | messages | port | redundancy | registry | sm | span | split | vlan | vp }
Syntax Description
Note Though visible in the command-line help strings, the scp and pvlan keywords are not supported.
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug pm command is the same as the no debug pm command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug port-security
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.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug port-security command is the same as the no debug port-security command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays port-security settings for an interface or for the switch. |
debug qos-manager
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.
debug qos-manager { all | event | verbose }
no debug qos-manager { all | event | verbose }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug qos-manager command is the same as the no debug qos-manager command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
debug spanning-tree
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree command is the same as the no debug spanning-tree command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree backbonefast
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.
debug spanning-tree backbonefast [ detail | exceptions ]
no debug spanning-tree backbonefast [ detail | exceptions ]
Syntax Description
(Optional) Display spanning-tree BackboneFast-exception debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree backbonefast command is the same as the no debug spanning-tree backbonefast command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree bpdu
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.
debug spanning-tree bpdu [ receive | transmit ]
no debug spanning-tree bpdu [ receive | transmit ]
Syntax Description
(Optional) Display the nonoptimized path for received BPDU debug messages. |
|
(Optional) Display the nonoptimized path for sent BPDU debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree bpdu command is the same as the no debug spanning-tree bpdu command .
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree bpdu-opt
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.
debug spanning-tree bpdu-opt [ detail | packet ]
no debug spanning-tree bpdu-opt [ detail | packet ]
Syntax Description
(Optional) Display detailed optimized BPDU-handling debug messages. |
|
(Optional) Display packet-level optimized BPDU-handling debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree bpdu-opt command is the same as the no debug spanning-tree bpdu-opt command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree mstp
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.
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 }
Syntax Description
Debug handshake messages between the designated switch and the root switch. |
|
Debug the region synchronization between the switch processor (SP) and the route processor (RP). |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree mstp command is the same as the no debug spanning-tree mstp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree switch
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.
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree switch command is the same as the no debug spanning-tree switch command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug spanning-tree uplinkfast
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.
debug spanning-tree uplinkfast [ exceptions ]
no debug spanning-tree uplinkfast [ exceptions ]
Syntax Description
(Optional) Display spanning-tree UplinkFast-exception debug messages. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug spanning-tree uplinkfast command is the same as the no debug spanning-tree uplinkfast command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
debug sw-vlan
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.
debug sw-vlan { badpmcookies | cfg-vlan { bootup | cli } | events | ifs | management | mapping | notification | packets | redundancy | registries | vtp }
no debug sw-vlan { badpmcookies | cfg-vlan { bootup | cli } | events | ifs | management | mapping | notification | packets | redundancy | registries | vtp }
Syntax Description
Display debug messages for VLAN manager incidents of bad port manager cookies. |
|
Display config-vlan debug messages. The keywords have these meanings: |
|
See the debug sw-vlan ifs command. |
|
Display debug messages for VLAN manager management of internal VLANs. |
|
See the debug sw-vlan notification command. |
|
Display debug messages for packet handling and encapsulation processes. |
|
See the debug sw-vlan vtp command. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug sw-vlan command is the same as the no debug sw-vlan command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
debug sw-vlan ifs
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.
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 }
Syntax Description
Display VLAN manager IFS file-open operation debug messages. The keywords have these meanings: |
|
Display file-read operation debug messages for the specified error test (1, 2, 3, or 4). |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug sw-vlan ifs command is the same as the no debug sw-vlan ifs command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
When selecting 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.
Related Commands
debug sw-vlan notification
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.
debug sw-vlan notification { accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange }
no debug sw-vlan notification { accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug sw-vlan notification command is the same as the no debug sw-vlan notification command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
debug sw-vlan vtp
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.
debug sw-vlan vtp { events | packets | pruning [ packets | xmit ] | redundancy | xmit }
no debug sw-vlan vtp { events | packets | pruning | redundancy | xmit }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug sw-vlan vtp command is the same as the no debug sw-vlan vtp command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
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.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays general information about VTP management domain, status, and counters. |
debug udld
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 }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug udld command is the same as the no debug udld command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
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:
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
|
Displays UDLD administrative and operational status for all ports or the specified port. |
debug vqpc
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.
debug vqpc [ all | cli | events | learn | packet ]
no debug vqpc [ all | cli | events | learn | packet ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The undebug vqpc command is the same as the no debug vqpc command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can 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. You also can use the remote command stack-member-number LINE privileged EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
Related Commands
|
|
|
|---|---|
Displays information about the types of debugging that are enabled. |
Feedback