The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This appendix describes the debug privileged EXEC commands that have been created or changed for use with the Cisco ME 3800X and ME 3600X switch. These commands are helpful in diagnosing and resolving internetworking problems and should be enabled only under the guidance of Cisco technical support staff.
Although visible in the command-line help, the switch does not support the debug platform commands.
To enable debugging of bridge domains, use the debug bridge-domain command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug bridge-domain {number mac {security | table} {errors | events} | configuration | errors | ipc}
no debug bridge-domain {number mac {security | table} {errors | events} | configuration | errors | ipc}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug bridge-domain command is the same as the no debug bridge-domain command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of the EtherChannel/PAgP shim, use the debug etherchannel command in privileged EXEC mode. This shim is the software module that is the interface between the Port Aggregation Protocol (PAgP) software module and the port manager software module. To disable debugging, use the no form of this command.
debug etherchannel [all | detail | error | event | idb]
no debug etherchannel [all | detail | error | event | idb]
Note Though visible in the command-line help strings, the linecard keyword is not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
If you do not specify a keyword, all debug messages appear.
The undebug etherchannel command is the same as the no debug etherchannel command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show etherchannel |
Displays EtherChannel information for the channel. |
To enable debugging of Ethernet customer service instances, use the debug ethernet service command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ethernet service {all | api | error | evc [id evc-id] | instance [id id interface-id | interface interface-id] | interface [interface-id] | oam-mgr}
no debug ethernet service {all | api | error | evc [id evc-id] | instance [id id interface-id | interface interface-id] | interface [interface-id] | oam-mgr}
Ethernet service debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug ethernet service command is the same as the no debug ethernet service command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of interface-related activities, use the debug interface command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug interface {interface-id | null interface-number | port-channel port-channel-number | vlan vlan-id}
no debug interface {interface-id | null interface-number | port-channel port-channel-number | vlan vlan-id}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
If you do not specify a keyword, all debug messages appear.
The undebug interface command is the same as the no debug interface command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show interface |
Displays interface status and configuration information. |
To enable debugging of Internet Group Management Protocol (IGMP) filter events, use the debug ip igmp filter command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ip igmp filter
no debug ip igmp filter
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug ip igmp filter command is the same as the no debug ip igmp filter command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of Internet Group Management Protocol (IGMP) maximum groups events, use the debug ip igmp max-groups command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ip igmp max-groups
no debug ip igmp max-groups
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug ip igmp max-groups command is the same as the no debug ip igmp max-groups command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of Internet Group Management Protocol (IGMP) snooping activity, use the debug igmp snooping command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ip igmp snooping [ip_address | group | management | querier | redundancy | router | timer]
no debug ip igmp snooping [ip_address | group | management | querier | redundancy | router | timer]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug ip igmp snooping command is the same as the no debug ip igmp snooping command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of Link Aggregation Control Protocol (LACP) activity, use the debug lacp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug lacp [all | event | fsm | misc | packet]
no debug lacp [all | event | fsm | misc | packet]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug lacp command is the same as the no debug lacp command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show lacp |
Displays LACP channel-group information. |
To enable debugging of MAC notification events, use the debug mac-notification command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug mac-notification
no debug mac-notification
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug mac-notification command is the same as the no debug mac-notification command.
To enable debugging of platform-independent MAC address management events, use the debug matm command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug matm {add | age | all | bulkdelete | create | delete | error | move | pm | remove | traceback}
no debug matm {add | age | all | bulkdelete | create | delete | error | move | pm | remove | traceback}
Note Although visible in the command-line help, the pvlan keyword is not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug matm command is the same as the no debug matm command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of MAC address-table move message processing, use the debug matm move command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug matm move [address | update]
no debug matm move [address | update]
address |
Displays MAC address table move address debug messages. |
move |
Displays MAC address table move update debug messages. |
Debugging is disabled. update
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug matm move command is the same as the no debug matm move command.
To enable debugging of NVRAM activity, use the debug nvram command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug nvram
no debug nvram
This command has no arguments or keywords.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug nvram command is the same as the no debug nvram command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of Port Aggregation Protocol (PAgP) activity, use the debug pagp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug pagp [all | dual-active | event | fsm | misc | packet]
no debug pagp [all | dual-active | event | fsm | misc | packet]
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug pagp command is the same as the no debug pagp command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show pagp |
Displays PAgP channel-group information. |
To enable debugging of port manager (PM) activity, use the debug pm command in privileged EXEC mode. 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. To disable debugging, use the no form of this command.
debug pm {all | assert | card | cookies | etherchnl | hatable | messages | port | redundancy | registry | sm | span | split | statistics| vlan | vp}
no debug pm {all | assert | card | cookies | etherchnl | hatable | messages | port | redundancy | registry | sm | span | split | statistics| vlan | vp}
Note Though visible in the command-line help strings, the pvlan and scp keywords are not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug pm command is the same as the no debug pm command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of Resilient Ethernet Protocol (REP) functions, use the debug rep command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug rep {all | bpa-event | bpasm | database | epa-pkt | epasm | error | failure-recovery | lslsm | misc | packet | prsm |show cli}
no debug rep {all | bpa-event | bpasm | database | epa-pkt | epasm | error | failure-recovery | lslsm | misc | packet | prsm |show cli}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug rep command is the same as the no debug rep command.
To enable debugging of the quality of service (QoS) feature, use the debug qos command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug qos {capability | events | service-policy {global-lock | iteration | lifecycle | polling | stats trace} | set}
no debug qos {capability | events | service-policy {global-lock | iteration | lifecycle | polling | stats trace} | set}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug qos command is the same as the no debug qos command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
To enable debugging of spanning-tree activities, use the debug spanning-tree command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree {all | bpdu | bpdu-opt | config | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | synchronization | vlan-shim}
no debug spanning-tree {all | bpdu | bpdu-opt | config | etherchannel | events | exceptions | general | mstp | pvst+ | root | snmp | switch | synchronization | vlan-shim}
all |
Displays all spanning-tree debug messages. |
bpdu |
Displays spanning-tree bridge protocol data unit (BPDU) debug messages. See the debug spanning-tree bpdu command. |
bpdu-opt |
Displays optimized BPDU handling debug messages. See the debug spanning-tree bpdu-opt command. |
config |
Displays spanning-tree configuration change debug messages. |
etherchannel |
Displays EtherChannel-support debug messages. |
events |
Displays spanning-tree topology event debug messages. |
exceptions |
Displays spanning-tree exception debug messages. |
general |
Displays general spanning-tree activity debug messages. |
mstp |
Debug Multiple Spanning Tree Protocol events. See the debug spanning-tree mstp command. |
pvst+ |
Displays per-VLAN spanning-tree plus (PVST+) event debug messages. |
root |
Displays spanning-tree root-event debug messages. |
snmp |
Displays spanning-tree Simple Network Management Protocol (SNMP) handling debug messages. |
switch |
Displays switch shim command debug messages. This shim is the software module that is the interface between the generic Spanning Tree Protocol (STP) code and the platform-specific code of various switch platforms. See the debug spanning-tree switch command. |
synchronization |
Displays the spanning-tree synchronization event debug messages. |
vlan-shim |
Displays spanning-tree VLAN shim debug messages. See the debug spanning-tree vlan-shim command |
Note Though visible in the command-line help strings, the csuf/csrt keyword is not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree command is the same as the no debug spanning-tree command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of sent and received spanning-tree bridge protocol data units (BPDUs), use the debug spanning-tree bpdu command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree bpdu [receive | transmit]
no debug spanning-tree bpdu [receive | transmit]
receive |
(Optional) Displays the nonoptimized path for received BPDU debug messages. |
transmit |
(Optional) Displays the nonoptimized path for sent BPDU debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree bpdu command is the same as the no debug spanning-tree bpdu command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of optimized spanning-tree bridge protocol data units (BPDUs) handling, use the debug spanning-tree bpdu-opt command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree bpdu-opt [detail | packet]
no debug spanning-tree bpdu-opt [detail | packet]
detail |
(Optional) Displays detailed optimized BPDU-handling debug messages. |
packet |
(Optional) Displays packet-level optimized BPDU-handling debug messages. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree bpdu-opt command is the same as the no debug spanning-tree bpdu-opt command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of the Multiple Spanning Tree Protocol (MSTP) feature, use the debug spanning-tree mstp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration | pm | proposals | region | roles | sanity_check | sync | tc | timers}
no debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration | pm | proposals | region | roles | sanity_check | sync | tc | timers}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree mstp command is the same as the no debug spanning-tree mstp command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of the software interface between the Spanning Tree Protocol (STP) and the port manager, use the debug spanning-tree switch command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
no debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree switch command is the same as the no debug spanning-tree switch command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of the Spanning Tree Protocol (STP) VLAN shim, use the debug spanning-tree switch command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug spanning-tree vlan-shim {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
no debug spanning-tree vlan-shim {all | errors | flush | general | helper | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug spanning-tree vlan-shim command is the same as the no debug spanning-tree vlan-shim command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show spanning-tree |
Displays spanning-tree state information. |
To enable debugging of VLAN manager activities, use the debug sw-vlan command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug sw-vlan {badpmcookies | cfg-vlan {bootup | cli} | events | ifs | management | notification | packets | registries}
no debug sw-vlan {badpmcookies | cfg-vlan {bootup | cli} | events | ifs | management | notification | packets | registries}
badpmcookies |
Displays debug messages for VLAN manager incidents of bad port manager cookies. |
cfg-vlan {bootup | cli} |
Displays config-vlan debug messages. The keywords have these meanings: • • |
events |
Displays debug messages for VLAN manager events. |
ifs |
See the debug sw-vlan ifs command. |
management |
Displays debug messages for VLAN manager management of internal VLANs. |
notification |
See the debug sw-vlan notification command. |
packets |
Displays debug messages for packet handling and encapsulation processes. |
registries |
Displays debug messages for VLAN manager registries. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug sw-vlan command is the same as the no debug sw-vlan command.
To enable debugging of the VLAN manager IOS file system (IFS) error tests, use the debug sw-vlan ifs command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
no debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug sw-vlan ifs command is the same as the no debug sw-vlan ifs command.
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.
To enable debugging of the activation and deactivation of VLAN IDs, use the debug sw-vlan notification command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | statechange}
no debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | statechange}
Note Though visible in the command-line help strings, the pruningcfgchange keyword is not supported.
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug sw-vlan notification command is the same as the no debug sw-vlan notification command.
To enable debugging of the UniDirectional Link Detection (UDLD) feature, use the debug udld command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug udld {events | packets | registries}
no debug udld {events | packets | registries}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug udld command is the same as the no debug udld command.
For debug udld events, these debugging messages appear:
•General UDLD program logic flow
•State machine state changes
•Program actions for the set and clear ErrDisable state
•Neighbor cache additions and deletions
•Processing of configuration commands
•Processing of link-up and link-down indications
For debug udld packets, these debugging messages appear:
•General packet processing program flow on receipt of an incoming packet
•Indications of the contents of the various pieces of packets received (such as type length versions [TLVs]) as they are examined by the packet reception code
•Packet transmission attempts and the outcome
For debug udld registries, these categories of debugging messages appear:
•Sub-block creation
•Fiber-port status changes
•State change indications from the port manager software
•MAC address registry calls
To enable debugging of the virtual forwarding infrastructure (VFI) feature, use the debug vfi command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug vfi [fsm] {error | event}
no debug vfi [fsm] {error | event}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug vfi command is the same as the no debug vfi command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
show vfi |
Displays VFI status for the switch. |
To enable debugging of the Virtual Router Redundancy Protocol (VRRP), use the debug vrrp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug vrrp {all | errors | events | packets | process | registry | state | timer | track}
no debug vrrp {all | errors | events | packets | process | registry | state | timer | track}
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug vrrp command is the same as the no debug vrrp command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
to enable debugging of the xconnect virtual connection or virtual connection infrastructure (VFI), use the debug xconnect command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug xconnect {error | event}
no debug xconnect {error | event}
error |
Displays debug messages for xconnect authorization errors. |
events |
Displays debug messages for xconnect authorization events. |
Debugging is disabled.
Privileged EXEC
|
|
---|---|
12.2(52)EY |
This command was introduced. |
The undebug xconnect command is the same as the no debug xconnect command.
|
|
---|---|
show debugging |
Displays information about the types of debugging that are enabled. |
xconnect |
Enable xconnect on an interface. |