Table Of Contents
debug ethernet-controller ram-access
debug spanning-tree backbonefast
debug spanning-tree uplinkfast
Debug Commands
This appendix describes only the Catalyst 3550-specific debug privileged EXEC commands. These commands are helpful in diagnosing and resolving internetworking problems and should be enabled only under the guidance of Cisco technical support staff.
CautionBecause 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 acltcam
Use the debug acltcam privileged EXEC command to debug the actions of the quality of service/access control list (QoS/ACL) ternary content addressable memory (TCAM) manager software module, which controls the allocation and updating of entries in the parts of the TCAM used for input security ACLs, output security ACLs, and QoS ACLs. Use the no form of this command to disable debugging output.
debug acltcam [verbose]
no debug acltcam [verbose]
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug acltcam command is the same as the no debug acltcam command.
Related Commands
debug autoqos
Use the debug autoqos privileged EXEC command to enable debugging of the automatic quality of service (auto-QoS) feature. Use the no form of this command to disable debugging.
debug autoqos
no debug autoqos
Syntax Description
This command has no keywords or arguments.
Defaults
Auto-QoS debugging is disabled.
Command Modes
Privileged EXEC
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 autoqos privileged EXEC command.
The undebug autoqos command is the same as the no debug autoqos command.
Examples
This example shows how to display the QoS configuration that is automatically generated when auto-QoS is enabled:
Switch# debug autoqosAutoQoS debugging is onSwitch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface fastethernet0/1Switch(config-if)# auto qos voip trustSwitch(config-if)#4d22h:mls qos map cos-dscp 0 8 16 26 32 46 48 564d22h:mls qos min-reserve 5 1704d22h:mls qos min-reserve 6 104d22h:mls qos min-reserve 7 654d22h:mls qos min-reserve 8 264d22h:mls qos4d22h:interface FastEthernet0/14d22h: mls qos trust cos4d22h: wrr-queue bandwidth 20 1 80 04d22h: wrr-queue min-reserve 1 54d22h: wrr-queue min-reserve 2 64d22h: wrr-queue min-reserve 3 74d22h: wrr-queue min-reserve 4 84d22h: no wrr-queue cos-map4d22h: wrr-queue cos-map 1 0 1 2 44d22h: wrr-queue cos-map 3 3 6 74d22h: wrr-queue cos-map 4 54d22h: priority-queue outSwitchconfig-if)# interface gigabitethernet0/1Switch(config-if)# auto qos voip cisco-phoneSwitch(config-if)#4d22h:interface GigabitEthernet0/14d22h: mls qos trust device cisco-phone4d22h: mls qos trust cos4d22h: wrr-queue bandwidth 20 1 80 04d22h: wrr-queue queue-limit 80 1 20 14d22h: no wrr-queue cos-map4d22h: wrr-queue cos-map 1 0 1 2 44d22h: wrr-queue cos-map 3 3 6 74d22h: wrr-queue cos-map 4 54d22h: priority-queue outSwitch(config-if)#Related Commands
debug cluster
Use the debug cluster privileged EXEC command to debug cluster-specific events. Use the no form of this command to disable debugging output.
debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat | neighbors | snmp | vqpxy}
no debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat | neighbors | snmp | vqpxy}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug cluster command is the same as the no debug cluster command.
Related Commands
debug cpu-interface
Use the debug cpu-interface privileged EXEC command to debug the driver for the application-specific integrated circuit (ASIC) that interfaces the CPU to the switch ASIC. Use the no form of this command to disable debugging output.
debug cpu-interface
no debug cpu-interface
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug cpu-interface command is the same as the no debug cpu-interface command.
Related Commands
debug dot1x
Use the debug dot1x privileged EXEC command to enable debugging of the 802.1X feature. Use the no form of this command to disable debugging output.
debug dot1x {all | authsm | backend | besm | core | reauthsm}
no debug dot1x {all | authsm | backend | besm | core | reauthsm}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug dot1x command is the same as the no debug dot1x command.
Related Commands
debug etherchannel
Use the debug etherchannel privileged EXEC command for EtherChannel/PAgP shim debugging. This shim is the software module that is the interface between the PAgP software module and the port manager software module. Use the no form of this command to disable debugging output.
debug etherchannel [all | detail | error | event | idb]
no debug etherchannel [all | detail | error | event | idb]
Syntax Description
Note
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify a keyword, all debug messages are displayed.
The undebug etherchannel command is the same as the no debug etherchannel command.
Related Commands
debug ethernet-controller ram-access
Use the debug ethernet-controller ram-access privileged EXEC command to debug the driver that controls reads from and writes to the private (not directly accessible by the CPU) RAM connected to the forwarding application-specific integrated circuits (ASICs). Use the no form of this command to disable debugging output.
debug ethernet-controller ram-access
no debug ethernet-controller ram-access
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug ethernet-controller ram-access command is the same as the no debug ethernet-controller ram-access command.
Related Commands
debug fallback-bridging
Use the debug fallback-bridging privileged EXEC command to enable debugging of the fallback bridging manager software module. This command debugs the platform-specific part of the process of learning MAC addresses on bridge groups and updating the hardware with the necessary information. Use the no form of this command to disable debugging output.
debug fallback-bridging
no debug fallback-bridging
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug fallback-bridging command is the same as the no debug fallback-bridging command.
Related Commands
debug gigastack
Use the debug gigastack privileged EXEC command to debug the actions of the driver for the GigaStack Gigabit Interface Converter (GBIC). Use the no form of this command to disable debugging output.
debug gigastack
no debug gigastack
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug gigastack command is the same as the no debug gigastack command.
Related Commands
debug ilpower controller
Use the debug ilpower controller privileged EXEC command to enable debugging of the platform-specific inline power software module in long message format. These messages include the Power Controller register reading. Use the no form of this command to disable debugging output.
debug ilpower controller
no debug ilpower controller
This command is available only on the Catalyst 3550-24PWR switch.
Syntax Description
This command has no keywords or arguments.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug ilpower controller command is the same as the no debug ilpower controller.
Related Commands
Enables debugging of the platform-specific inline power software module in a short message format.
debug ilpower event
Use the debug ilpower event privileged EXEC command to enable debugging of the platform-specific inline power software module in a short message format. These messages display the inline power state and events received. Use the no form of this command to disable debugging output.
debug ilpower event
no debug ilpower event
This command is available only on the Catalyst 3550-24PWR switch.
Syntax Description
This command has no keywords or arguments.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug ilpower event command is the same as the no debug ilpower event.
Related Commands
Enables debugging of the platform-specific inline power software module in long message format
debug ip igmp filter
Use the debug ip igmp filter privileged EXEC command to debug IGMP filter events. Use the no form of this command to disable debugging output.
debug ip igmp filter
no debug ip igmp filter
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug ip igmp filter command is the same as the no debug ip igmp filter command.
Related Commands
debug ip igmp max-groups
Use the debug ip igmp max-groups privileged EXEC command to debug IGMP maximum groups events. Use the no form of this command to disable debugging output.
debug ip igmp max-groups
no debug ip igmp max-groups
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug ip igmp max-groups command is the same as the no debug ip igmp max-groups command.
Related Commands
debug l3multicast
Use the debug l3multicast privileged EXEC command to debug the platform-specific Layer 3 IP multicast manager software module, which maintains platform-specific data describing IP multicast routes. Use the no form of this command to disable debugging output.
debug l3multicast
no debug l3multicast
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug l3multicast command is the same as the no debug l3multicast command.
Related Commands
debug l3tcam
Use the debug l3tcam privileged EXEC command to debug the Layer 3 ternary content addressable memory (TCAM) manager software module, which controls the allocation of the part of the TCAM used in IP unicast and multicast routing, including the allocation of both routes and adjacencies in the TCAM. Use the no form of this command to disable debugging output.
debug l3tcam
no debug l3tcam
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug l3tcam command is the same as the no debug l3tcam command.
Related Commands
debug l3unicast
Use the debug l3unicast privileged EXEC command to debug the Layer 3 IP unicast manager, which maintains platform-specific data describing the IP forwarding information base (FIB) entries (routes and adjacencies) and ARP table entries. Use the no form of this command to disable debugging output.
debug l3unicast
no debug l3unicast
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug l3unicast command is the same as the no debug l3unicast command.
Related Commands
debug mac-manager
Use the debug mac-manager privileged EXEC command to debug the platform-specific MAC address table manager software module. This command debugs the platform-specific part of learning MAC addresses on VLANs and updating the hardware with the necessary information. Use the no form of this command to disable debugging output.
debug mac-manager
no debug mac-manager
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug mac-manager command is the same as the no debug mac-manager command.
Related Commands
debug mac-notification
Use the debug mac-notification privileged EXEC command to debug MAC notification events. Use the no form of this command to disable debugging output.
debug mac-notification
no debug mac-notification
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug mac-notification command is the same as the no debug mac-notification command.
Related Commands
debug met
Use the debug met privileged EXEC command to debug the allocation, freeing, and updating of the multicast expansion table (MET) entries. These entries are used by the hardware when forwarding individual IP multicast and fallback-bridged packets to multiple output VLANs. Use the no form of this command to disable debugging output.
debug met
no debug met
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug met command is the same as the no debug met command.
Related Commands
debug mvrdbg
Use the debug mvrdbg privileged EXEC command to enable Multicast VLAN Registration (MVR) debugging. Use the no form of this command to disable debugging output.
debug mvrdbg {all | events | igmpsn | management | ports}
no debug mvrdbg {all | events | igmpsn | management | ports}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug mvrdbg command is the same as the no debug mvrdbg command.
Related Commands
debug pagp
Use the debug pagp privileged EXEC command to debug Port Aggregation Protocol (PAgP) activity. Use the no form of this command to disable debugging output.
debug pagp [all | event | fsm | misc | packet]
no debug pagp [all | event | fsm | misc | packet]
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command can be entered only from the switch console.
The undebug pagp command is the same as no debug pagp command.
Related Commands
debug pbr
Use the debug pbr privileged EXEC command to debug policy-based routing (PBR) events. Use the no form of this command to disable debugging output.
debug pbr [acl-merge]
no debug pbr [acl-merge]
Syntax Description
acl-merge
(Optional) Enable debugging of the merge of ACLs present in a route-map that is applied to an interface for PBR.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug pbr command is the same as the no debug pbr command.
Related Commands
debug pm
Use the debug pm privileged EXEC command to debug port manager (PM) activity. The port manager is a state machine that controls all the logical and physical interfaces. All features, such as VLANs, UniDirectional Link Detection (UDLD), and so forth, work with the port manager to provide switch functions. Use the no form of this command to disable debugging output.
debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split | vlan | vp}
no debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split | vlan | vp}
Syntax Description
Note
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug pm command is the same as the no debug pm command.
Related Commands
debug port-security
Use the debug port-security privileged EXEC command to debug the allocation and states of the port security subsystem. Use the no form of this command to disable debugging output.
debug port-security
no debug port-security
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug port-security command is the same as the no debug port-security command.
Related Commands
debug span-session
Use the debug span-session privileged EXEC command to debug events occurring in the platform-specific software that implements the Switched Port Analyzer (SPAN) feature. Use the no form of this command to disable debugging output.
debug span-session
no debug span-session
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug span-session command is the same as the no debug span-session command.
Related Commands
debug spanning-tree
Use the debug spanning-tree privileged EXEC command to debug spanning-tree activities. Use the no form of this command to disable debugging output.
debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | csuf | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | uplinkfast}
no debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | csuf | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | uplinkfast}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
12.1(4)EA1
This command was first introduced.
12.1(9)EA1
The mstp and csuf keywords were added.
Usage Guidelines
The undebug spanning-tree command is the same as the no debug spanning-tree command.
Related Commands
