|
|
2
Use the debug adjacency command to display information on the adjacency database. Use the no form of this command to disable debugging output.
debug adjacency [ipc]
Syntax Description
ipc (Optional) Keyword to display IPC entries in the adjacency database.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to display information on the adjacency database:
Router# debug adjacency 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00 <... output truncated ...> Router#
Related Commands
undebug adjacency (same as no debug adjacency)
Use the debug backup command to debug backup events. Use the no form of this command to disable debugging output.
debug backupSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug backup events:
Router# debug backup Backup events debugging is on Router#
Related Commands
undebug backup (same as no debug backup)
Use the debug callback command to debug PPP telephone callback activity. Use the no form of this command to disable debugging output.
debug callbackSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug callback activity:
Router# debug callback Callback activity debugging is on Router#
Related Commands
undebug callback (same as no debug callback)
Use the debug cca command to debug CCA register activity. Use the no form of this command to disable debugging output.
debug ccaSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug CCA register activity:
Router# debug cca CCA debugging is on Router#
Related Commands
undebug cca (same as no debug cca)
Use the debug condition interface command to limit output for debugging of interface-related activities. Use the no form of this command to disable debugging output.
debug condition interface {FastEthernet interface-num | GigabitEthernet interface-num | Null | vlan interface-num group-number} |
Note The vlan keyword for the debug condition interface command is only supported on the MSFC and can be entered only from the router console. |
Syntax Description
FastEthernet Keyword to limit debugging to Fast Ethernet interfaces. interface-num Fast Ethernet interface number; valid values are from 1 to 9. GigabitEthernet Keyword to limit debugging of a condition to Gigabit Ethernet interfaces. interface-num Gigabit Ethernet interface number; valid values are from 1 to 9. Null Keyword to limit debugging of a condition to a null interface. interface-num Port-channel interface number; valid values are from 1 to 1024. vlan Keyword to limit debugging of a condition on a VLAN interface. interface-num VLAN interface number; valid values are from 1 to 1000. See the "Usage Guidelines" section for information regarding VLAN selection. group-number VLAN group number; valid values are from 0 to 255.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
When defining vlan interface-num, VLANs 1 to 1005 are the complete range of VLANs, VLANs 2 to 1000 are the user-configurable range of VLANs, and VLANs 1 and 1001 to 1005 are default VLANs.
Examples
This example shows how to limit debugging output to VLAN interface 1:
Router# debug condition interface vlan 1 Condition 2 set Router#
Related Commands
debug interface
undebug condition interface (same as no debug condition interface)
Use the debug condition standby command to limit output for debugging of Hot Standby Protocol state changes. Use the no form of this command to disable debugging output.
debug condition standby {FastEthernet interface-num | GigabitEthernet interface-num
Syntax Description
FastEthernet Keyword to limit debugging output to Fast Ethernet interfaces. interface-num Fast Ethernet interface number; valid values are from 1 to 9. GigabitEthernet Keyword to limit debugging output to Gigabit Ethernet interfaces. interface-num Gigabit Ethernet interface number; valid values are from 1 to 9. Port-channel Keyword to turn limit debugging output to port-channel interfaces. interface-num Port-channel interface number; valid values are from 1 to 1024. vlan Keyword to limit debugging of a condition on a VLAN interface. interface-num VLAN interface number; valid values are from 1 to 1000. See the "Usage Guidelines" section for information regarding VLAN selection. group-number VLAN group number; valid values are from 0 to 255.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
When defining vlan interface-num, VLANs 1 to 1005 are the complete range of VLANs, VLANs 2 to 1000 are the user-configurable range of VLANs, and VLANs 1 and 1001 to 1005 are default VLANs.
If you attempt to remove the only condition set, you will be prompted with a message asking if you want to abort operation. You can press n to abort or y to proceed with removal. If you remove the only condition set, it may cause an excessive number of debugging messages to be output.
The no debug condition standby command is similar to the undebug condition standby command.
Examples
This example shows how to limit the debugging output to group 0 in VLAN 1:
Router# debug condition standby vlan 1 0 Condition 3 set Router#
This example shows the display if you try to turn off the last standby debug condition:
Router# no debug condition standby vlan 1 0 This condition is the last standby condition set. Removing all conditions may cause a flood of debugging messages to result, unless specific debugging flags are first removed. Proceed with removal? [yes/no]: n % Operation aborted Router#
Related Commands
undebug condition standby (same as no debug condition standby)
Use the debug condition vlan command to limit VLAN debugging output to a specified VLAN. Use the no form of this command to disable debugging output.
debug condition vlan {vlan-id}
Syntax Description
vlan-id Number of the VLAN; valid values are from 1 to 1005. See the "Usage Guideline" section for information regarding VLAN selection.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines Usage Guideline
When defining vlan id, VLANs 1 to 1005 are the complete range of VLANs, VLANs 2 to 1000 are the user-configurable range of VLANs, and VLANs 1 and 1001 to 1005 are default VLANs.
If you attempt to remove the only VLAN condition set, you will be prompted with a message asking if you want to abort operation. You can press n to abort or y to proceed with removal. If you remove the only condition set, it may cause an excessive number of debugging messages to be output.
The no debug condition vlan command is similar to the undebug condition vlan command.
Examples
This example shows how to limit debugging output to VLAN 1:
Router# debug condition vlan 1 Condition 4 set Router#
This example shows the display if you try to turn off the last VLAN debug condition:
Router# no debug condition vlan 1 This condition is the last vlan condition set. Removing all conditions may cause a flood of debugging messages to result, unless specific debugging flags are first removed. Proceed with removal? [yes/no]: n % Operation aborted Router#
Related Commands
undebug condition vlan (same as no debug condition vlan)
Use the debug earl command to enable debugging of EARL activity. Use the no form of this command to disable debugging output.
debug earl {L2 aging | L2 events | L3 aging | L3 control | L3 netflow}
Syntax Description
L2 aging Keyword to enable debugging of EARL Layer 2 aging. L2 events Keyword to enable debugging of EARL Layer 2 events. L3 aging Keyword to enable debugging of EARL Layer 3 aging. L3 control Keyword to enable debugging of EARL Layer 3 control events. L3 netflow Keyword to enable debugging of EARL Layer 3 NDE.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to enable debugging of EARL events:
Switch-sp# debug earl events
EARL5 events debugging is on
Router#
*Sep 29 13:31:04: SP: cafe_general_isr: EARL5 INT
*Sep 29 13:31:04: SP: cafe_general_isr: intr source 0x4 with mask 0x3FEC6
*Sep 29 13:31:04: SP: cafe_general_isr: NMI intr source 0x3
*Sep 29 13:31:04: SP: CAFE_DEBUG: cafe_se_process_data() : address found = 11342
*Sep 29 13:31:04: SP: CAFE_DEBUG: cafe_se_process_data() : address found = 21368
*Sep 29 13:31:04: SP: CAFE_DEBUG: cafe_se_process_data() : address found = 59626
*Sep 29 13:31:04: SP: CAFE_DEBUG: cafe_se_process_data() : address found = 72581
<... output truncated ...>
Switch-sp#
Related Commands
undebug earl (same as no debug earl )
remote login
Use the debug ehsa command to enable debugging of EHSA activity. Use the no form of this command to disable debugging output.
debug ehsa {all | config_sync | fsm | general}
Syntax Description
all Keyword to enable debugging of all EHSA events. config_sync Keyword to enable debugging of EHSA configuration synchronization. fsm Keyword to enable debugging of EHSA FSM. general Keyword to enable debugging of EHSA general events.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to enable debugging of general EHSA events:
Switch-sp# debug ehsa general EHSA general debugging is on Switch-sp#
Related Commands
undebug ehsa (same as no debug ehsa)
remote login
Use the debug entry command to debug incoming queue entries. Use the no form of this command to disable debugging output.
debug entrySyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of incoming queue entries:
Router# debug entry Incoming queue entry debugging is on Router#
Related Commands
undebug entry (same as no debug entry)
Use the debug etherchnl command for EtherChannel/PAgP shim debugging. Use the no form of this command to disable debugging output.
debug etherchnl [all | detail | error | event | idb | linecard]
Syntax Description
all (Optional) Keyword to display all EtherChannel debug messages. detail (Optional) Keyword to display detailed EtherChannel debug messages. error (Optional) Keyword to display EtherChannel error debug messages. event (Optional) Keyword to debug major EtherChannel event messages. idb (Optional) Keyword to debug PAgP IDB messages. linecard (Optional) Keyword to debug SCP messages to the line card.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
If you do not specify a keyword, all debug messages are displayed.
Examples
This example shows how to display all EtherChannel debug messages:
Router# debug etherchnl Sep 14 12:59:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8 , changed state to down Sep 14 12:59:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/9 , changed state to down Sep 14 13:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8 , changed state to up Sep 14 13:11:03: %SYS-5-CONFIG_I: Configured from console by vty2 (171.69.200.22 7) Sep 14 13:12:59: %SYS-5-CONFIG_I: Configured from console by vty2 (171.69.200.22 7) <... output truncated ...> Router#
This example shows how to display EtherChannel IDB debug messages:
Router# debug etherchnl idb Agport idb related debugging is on Router#
Related Commands
undebug etherchnl (same as no debug etherchnl)
Use the debug ethernet-interface command to debug Ethernet interface events. Use the no form of this command to disable debugging output.
debug ethernet-interfaceSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of Ethernet-interface events:
Router# debug ethernet-interface Ethernet network interface debugging is on Router# RX:(D)b000.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.0.80 (TL)6 RX:(D)b800.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.255.255 (TL)57344 RX:(D)c800.0008.0000 (S)0000.0000.0000 (T)0x6000 (L)124 (IP)0.0.255.255 (TL)3225 <... output truncated ...> Router#
Related Commands
undebug ethernet-interface (same as no debug ethernet-interface)
Use the debug fastethernet command to debug Fast Ethernet interface events or packets. Use the no form of this command to disable debugging output.
debug fastethernet {events | packets}
Syntax Description
events Keyword to debug Fast Ethernet events. packets Keyword to debug Fast Ethernet packets.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
These examples show how to debug Fast Ethernet events and packets:
Router# debug fastethernet events Fast Ethernet events debugging is on Router# Router# debug fastethernet packets Fast Ethernet packets debugging is on Router#
Related Commands
undebug fastethernet (same as no debug fastethernet)
Use the debug fm command to debug feature manager events and activities. Use the no form of this command to disable debugging output.
debug fm {all | event | queue-event | unusual | verbose}
Syntax Description
all Keyword to debug all FM activity. event Keyword to debug FM events. queue-event Keyword to debug only FM queue-events. unusual Keyword to debug only unusual FM events. verbose Keyword to display verbose debug output for FM.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable verbose debugging output of feature manager events and activities:
Router# debug fm verbose FM verbose debugging is on Router#
Related Commands
undebug fm (same as no debug fm)
Use the debug gssapi command to debug GSSAPI events. Use the no form of this command to disable debugging output.
debug gssapiSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of GSSAPI events:
Router# debug gssapi GSSAPI debugging is on Router#
Related Commands
undebug gssapi (same as no debug gssapi)
Use the debug icc command to debug ICC events. Use the no form of this command to disable debugging output.
debug icc [all | async-requests | events | exceptions | requests]
Syntax Description
all (Optional) Keyword to debug all ICC events. async-requests (Optional) Keyword to debug ICC async-requests. events (Optional) Keyword to debug only ICC events. exceptions (Optional) Keyword to debug ICC exceptions. requests (Optional) Keyword to debug ICC requests.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of ICC asynchronous requests:
Router# debug icc async-requests
ICC Asynchronous Requests debugging is on
Router# #icc_append_async_request: msg 0x617E2058, id 0x62595448, cb 0x603E9CB8
icc_append_async_request: ar 0x618438E0
icc_append_async_request: head 0x0, tail 0x61479B50
icc_async_callback: msg=0x617E2058, err=0
icc_unlink_async_request: msg 0x617E2058
icc_unlink_async_request: head matches
icc_unlink_async_request: took tail
icc_unlink_async_request: head 0x0, tail 0x61479B50, p 0x618438E0
icc_async_callback: ar 0x618438E0, cb 0x603E9CB8, id 0x62595448
icc_async_callback: got rpc respsonse, msg=0x617E25AC
icc_async_callback: calling callback
icc_async_callback: callback complete
<... output truncated ...>
Router#
Related Commands
undebug icc (same as no debug icc)
Use the debug iccshim command to debug ICC shim events. Use the no form of this command to disable debugging output.
debug iccshim [all | event | packet]
Syntax Description
all (Optional) Keyword to debug all ICC shim events. event (Optional) Keyword to debug only ICC shim events. packet (Optional) Keyword to debug ICC shim packets.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of ICC shim packets:
Router# debug iccshim packet ICCSHIM packets debugging is on Router# icc_append_async_request: msg 0x617E25AC, id 0x62595448, cb 0x603E9CB8 icc_append_async_request: ar 0x618438E0 icc_append_async_request: head 0x0, tail 0x61479B50 icc_async_callback: msg=0x617E25AC, err=0 icc_unlink_async_request: msg 0x617E25AC icc_unlink_async_request: head matches icc_unlink_async_request: took tail icc_unlink_async_request: head 0x0, tail 0x61479B50, p 0x618438E0 icc_async_callback: ar 0x618438E0, cb 0x603E9CB8, id 0x62595448 icc_async_callback: got rpc respsonse, msg=0x617E2058 icc_async_callback: got rpc respsonse, pak=0x6176B770 icc_async_callback: calling callback icc_async_callback: callback complete <... output truncated ...> Router#
Related Commands
undebug iccshim (same as no debug iccshim)
Use the debug interface command as a shortcut for the debug condition interface command. Use the no form of this command to disable debugging output.
debug interface {FastEthernet interface-num | GigabitEthernet interface-num | Null | Port-channel interface-num | vlan vlan} |
Note The vlan parameter for the debug interface command only applies to the MSFC and can be entered only from the router console. |
Syntax Description
FastEthernet Keyword to limit debugging to Fast Ethernet interfaces. interface-num Fast Ethernet interface number; valid values are from 1 to 9. GigabitEthernet Keyword to limit debugging to Gigabit Ethernet interfaces. interface-num Gigabit Ethernet interface number; valid values are from 1 to 9. Null Keyword to limit debugging to null interfaces. Port-channel Keyword to limit debugging to port-channel interfaces. interface-num Port-channel interface number; valid values are from 1 to 1024. vlan interface-num Keyword and variable to limit debugging to a specific VLAN; valid values are from 1 to 1000. See the "Usage Guidelines" section for information regarding VLAN selection.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
When defining vlan vlan, VLANs 1 to 1005 are the complete range of VLANs, VLANs 2 to 1000 are the user-configurable range of VLANs, and VLANs 1 and 1001 to 1005 are default VLANs.
Examples
This example shows how to limit debugging to interface vlan 1:
Router# debug interface vlan 1 Condition 1 set Router#
Related Commands
debug condition interface
undebug interface (same as no debug interface)
Use the debug ipc command to debug IPC activity. Use the no form of this command to disable debugging output.
debug ipc {all | errors | events | headers | packets | ports | seats}
Syntax Description
all Keyword to turn on all IPC debugging. errors Keyword to turn on IPC error debugging. events Keyword to turn on IPC event debugging. headers Keyword to turn on IPC header debugging. packets Keyword to turn on IPC packet debugging. ports Keyword to turn on debugging of creation and deletion of ports. seats Keyword to turn on debugging of creation and deletion of nodes.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of IPC events:
Router# debug ipc events Special Events debugging is on Router#
Related Commands
undebug ipc (same as no debug ipc)
Use the debug l2-mgr events command to debug Layer 2 manager events. Use the no form of this command to disable debugging output.
debug l2-mgr eventsSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered from the switch console (see the remote login command) only.
Examples
This example shows how to enable debugging of Layer 2 manager events:
Switch-sp# debug l2-mgr events L2 mgr events debugging is on Switch-sp#
Related Commands
undebugl2-mgr events (same as no debug l2-mgr events)
remote login
Use the debug l3-mgr command to debug Layer 3 manager activity. Use the no form of this command to disable debugging output.
debug l3-mgr {all | events | global | packets}
Syntax Description
all Keyword to display all Layer 3 manager debug messages. events Keyword to display Layer 3 manager-related events. global Keyword to display bug trace of IP global purge events. packets Keyword to display Layer 3 manager packets.
Defaults
This command has no default stting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable global Layer 3 manager debugging:
Router# debug l3-mgr global L3 mgr ip global purge debugging is on Router#
Related Commands
undebugl3-mgr (same as no debug l3-mgr)
Use the debug local-ack command to debug local acknowledgment activity. Use the no form of this command to disable debugging output.
debug local-ack {errors | packets | state}
Syntax Description
errors Keyword to display all local acknowledgement errors. packets Keyword to display local acknowledgment packets. state Keyword to display local acknowledgment state changes.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of local acknowledgement state changes:
Router# debug local-ack state Local Acknowledgement states debugging is on Router#
Related Commands
undebug local-ack (same as no debug local-ack)
Use the debug ltl command to enable debugging of LTL manager activity. Use the no form of this command to disable debugging output.
debug ltlSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered from the switch console only (see the remote login command).
Examples
This example shows how to enable LTL manager debugging:
Switch-sp# debug ltl ltl mgr debugging is on Switch-sp#
Related Commands
undebug ltl (same as no debug ltl)
remote login
Use the debug mergeapi command to debug ACL merge activity. Use the no form of this command to disable debugging output.
debug mergeapi {all | normal | profile | verbose}
Syntax Description
all Keyword to display all ACL merge activity. normal Keyword to display main steps traversed by the ACL merge program. profile Keyword to display a profile of the CUDD library's internal cache. verbose Keyword to display detailed information on ACL merge events.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug the CUDD library's internal cache:
Router# debug mergeapi profile ACLMERGE debug time profile debugging is on Router#
Related Commands
undebug mergeapi (same as no debug mergeapi)
Use the debug mls ip multicast command to debug MLS IP multicast activity. Use the no form of this command to disable debugging output.
debug mls ip multicast {all | error | events | group | messages}
Syntax Description
all Keyword to enable debugging of all MLS IP multicast activity. error Keyword to enable MLS IP multicast error debugging. events Keyword to enable MLS IP multicast event debugging. group Keyword to enable MLS IP multicast group-based debugging. messages Keyword to enable MLS IP multicast message debugging.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable debugging of MLS IP multicast errors:
Router# debug mls ip multicast error mcast error debugging is on Router#
Related Commands
undebug mls ip multicast (same as no debug mls ip multicast)
Use the debug mls rp command to debug MLS RP activity. Use the no form of this command to disable debugging output.
debug mls rp {all | error | events | ip | ipx | locator | packets | verbose packets}
Syntax Description
all Keyword to enable debugging of all MLS RP activities. error Keyword to enable debugging of MLS RP errors. events Keyword to enable debugging of MLS RP events. ip Keyword to enable debugging of MLS IP events. ipx Keyword to enable debugging of MLS IPX events. locator Keyword to enable debugging of the MLS RP locator. packets Keyword to enable debugging of MLS RP packets without keepalives. verbose packets Keyword to enable debugging of MLS RP packets with keepalives.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can only be entered from the switch console (see the remote login command).
Examples
This example shows how to enable debugging of MLS RP IGMP events:
Switch-sp# debug mls rp events mls events debugging is on Switch-sp#
Related Commands
undebug mls rp (same as no debug mls rp)
remote login
Use the debug monitor command to display monitoring activity. Use the no form of this command to disable debugging output.
debug monitor {all | errors | idb-update | list | notifications | platform | requests}
Syntax Description
all Keyword to display all SPAN debugging messages. errors Keyword to display SPAN error details. idb-update Keyword to display SPAN IDB update traces. list Keyword to display SPAN and VLAN list tracing. notifications Keyword to display SPAN notifications. platform Keyword to display SPAN platform tracing. requests Keyword to display SPAN requests.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug monitoring errors:
Router# debug monitor errors SPAN error detail debugging is on Router#
Related Commands
undebug monitor (same as no debug monitor)
Use the debug msc command to debug MSC activity. Use the no form of this command to disable debugging output.
debug msc {all | events | pak}
Syntax Description
all Keyword to debug all MSC activity. events Keyword to enable MSC event debugging. pak Keyword to enable MSC packet debugging.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug MSC packets:
Router# debug msc pak Router#
Related Commands
undebug msc (same as no debug msc)
Use the debug netdr command to debug NetDriver activity. Use the no form of this command to disable debugging output.
debug netdr {all | data}
Syntax Description
all Keyword to debug all NetDriver activity. data Keyword to debug NetDriver data flow.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug the NetDriver data flow:
Router# debug netdr data NetDriver Receive Data on interrupt debugging is on NetDriver Receive Data debugging is on NetDriver Transmit Data debugging is on NetDriver Relay Data debugging is on Router# 2d21h: const_ether_vlan_vencap() Vlan1: 2d21h: src_vlan=0x1 src_indx=0x3 len=0xE9 bpdu=0 2d21h: index_dir=0 dest_indx=0x0 dont_lrn=0 2d21h: Dbus hdr: 00000000 00010000 00030000 E9000000 2d21h: 00000000 00000000 00000000 00000000 2d21h: MAC hdr: dmac=00801C.938040, smac=00503E.8D6400, typelen=0800 2d21h: IP hdr: 45C000DB 02F30000 FF066331 AC143412 AB45C8CC 2d21h: fx1000_process_receive_packet() Vlan1: 2d21h: src_vlan=0x1 src_indx=0x108 len=0x40 bpdu=0 2d21h: index_dir=0 dest_indx=0x3 dont_lrn=0 2d21h: Dbus hdr: 60000000 00010000 01080000 40100000 2d21h: 0006AC14 3412AB45 C8CC0000 00030000 2d21h: MAC hdr: dmac=00503E.8D6400, smac=00605C.865B28, typelen=0800 2d21h: IP hdr: 45000028 B5254000 7D06F471 AB45C8CC AC143412 <... output truncated ...> Router#
Related Commands
undebug netdr (same as no debug netdr)
Use the debug nvram command to debug NVRAM activity. Use the no form of this command to disable debugging output.
debug nvramSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug NVRAM:
Router# debug nvram NVRAM behaviour debugging is on Router#
Related Commands
undebug nvram (same as no debug nvram)
Use the debug pagp command to debug PAgP activity. Use the no form of this command to disable debugging output.
debug pagp [all | event | fsm | misc | packet]
Syntax Description
all (Optional) Keyword to enable all PAgP debugging. event (Optional) Keyword to enable debugging of PAgP events. fsm (Optional) Keyword to enable debugging of the PAgP finite state machine. misc (Optional) Keyword to enable miscellaneous PAgP debugging. packet (Optional) Keyword to enable PAgP packet debugging.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to enable PAgP miscellaneous debugging:
Switch-sp# debug pagp misc Port Aggregation Protocol Miscellaneous debugging is on Router# *Sep 30 10:13:03: SP: PAgP: pagp_h(Fa5/6) expired *Sep 30 10:13:03: SP: PAgP: 135 bytes out Fa5/6 *Sep 30 10:13:03: SP: PAgP: Fa5/6 Transmitting information packet *Sep 30 10:13:03: SP: PAgP: timer pagp_h(Fa5/6) started with interval 30000 <... output truncated ...> Switch-sp#
Related Commands
undebug pagp (same as no debug pagp)
remote login
Use the debug pf command to debug PF activity. Use the no form of this command to disable debugging output.
debug pf {all | errors | events | learns | sm}
Syntax Description
all Keyword to enable all PF debugging. errors Keyword to enable PF error debugging. events Keyword to enable PF event debugging. learns Keyword to debug PF address learning. sm Keyword to debug the state machine.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug the PF learned addresses:
Router# debug pf learns Address learning debugging is on Router#
Related Commands
undebug pf (same as no debug pf)
Use the debug pm command to debug PM activity. Use the no form of this command to disable debugging output.
debug pm {all | card | cookies | etherchnl | messages | port | registry | scp | sm | span | split |
Syntax Description
all Keyword to display all PM debugging messages. card Keyword to debug line card-related events. cookies Keyword to enable internal PM cookie validation. etherchnl Keyword to debug EtherChannel-related events. messages Keyword to debug PM messages. port Keyword to debug port-related events. registry Keyword to debug PM registry invocations. scp Keyword to debug SCP line card messaging. sm Keyword to debug state machine-related events. span Keyword to debug spanning tree-related events. split Keyword to debug split-processor. vlan Keyword to debug VLAN-related events. vp Keyword to debug virtual port-related events.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to enable all PM debugging:
Router# debug pm all Router#
Examples
undebug pm (same as no debug pm)
Use the debug priority command to debug priority output queueing. Use the no form of this command to disable debugging output.
debug prioritySyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug priority output queueing:
Router# debug priority Priority output queueing debugging is on Router#
Related Commands
undebug priority (same as no debug priority)
Use the debug rpc command to debug RPC activity. Use the no form of this command to disable debugging output.
debug rpc {all | errors | events | packets | requests}
Syntax Description
all Keyword to debug all RPC activity. errors Keyword to enable debugging of RPC errors. events Keyword to enable RPC event debugging. packets Keyword to enable RPC packet debugging. requests Keyword to enable debugging of RPC requests.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug RPC packets:
Router#debug rpc packetsRPC packet debugging is onRouter#2d20h: rpc-tx-req: 123790 cygnus-oir: req 6: size 122d20h: 00 01 E3 8D 0E C3 EB 5C 00 00 00 002d20h: rpc-rx-req: 123791 draco-oir: req 4: size 122d20h: 00 01 E3 8D 0E C3 EC A0 00 00 00 002d20h: rpc-tx-res: 123791 draco-oir: req 4(okay)o debug2d20h: rpc-tx-req: 123791 cygnus-oir: req 6: size 122d20h: 00 01 E3 8E 0E C3 F3 2C 00 00 00 002d20h: rpc-rx-req: 123792 draco-oir: req 4: size 122d20h: 00 01 E3 8E 0E C3 F4 70 00 00 00 002d20h: rpc-tx-res: 123792 draco-oir: req 4(okay)2d20h: rpc-tx-req: 123792 cygnus-oir: req 6: size 122d20h: 00 01 E3 8F 0E C3 FA FC 00 00 00 002d20h: rpc-rx-req: 123793 draco-oir: req 4: size 122d20h: 00 01 E3 8F 0E C3 FC 40 00 00 00 002d20h: rpc-tx-res: 123793 draco-oir: req 4(okay)<... output truncated ...>Router#
Related Commands
undebug rpc (same as no debug rpc)
Use the debug scp command to debug SCP activity. Use the no form of this command to disable debugging output.
debug scp {all | async | data | errors | packets | timeouts}
Syntax Description
all Keyword to debug all SCP activity. async Keyword to debug asynchronous data in and out of the SCP system. data Keyword to enable a data packet trace. errors Keyword to enable debugging of SCP errors. packets Keyword to enable SCP packet debugging. timeouts Keyword to report SCP timeouts.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug SCP packets:
Router# debug scp packets SCP packets debugging is on Router#
Related Commands
undebug scp (same as no debug scp)
Use the debug smf command to debug SMF address insertions and deletions. Use the no form of this command to disable debugging output.
debug smf updatesSyntax Description
This command has no arguments or keywords.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug SMF updates:
Router# debug smf updates Software MAC filter address insertions and deletions debugging is on Router
Related Commands
undebug smf (same as no debug smf)
Use the debug spanning-tree command to debug spanning tree activities. Use the no form of this command to disable debugging output.
debug spanning-tree {all | bpdu | bpdu-opt | ethernchannel | config | events | exceptions | general | pvst+ | root}
Syntax Description
all Keyword to display all spanning tree debugging messages. bpdu Keyword to debug spanning tree bridge protocol data units. bpdu-opt Keyword to debug optimized BPDU handling. config Keyword to debug spanning tree configuration changes. etherchannel Keyword to debug spanning tree EtherChannel support. events Keyword to enable TCAM event debugging. exceptions Keyword to debug spanning tree exceptions. general Keyword to debug general spanning tree activity. pvst+ Keyword to debug PVST+ events. root Keyword to debug spanning tree root events.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug spanning tree PVST+:
Router# debug spanning-tree pvst+ Spanning Tree PVST+ debugging is on Router
Related Commands
undebug spanning-tree (same as no debug spanning-tree)
Use the debug spanning-tree backbonefast command to enable debugging of spanning tree BackboneFast events. Use the no form of this command to disable debugging output.
debug spanning-tree backbonefast [detail | exceptions]
Syntax Description
detail (Optional) Keyword to display detailed BackboneFast debugging messages. exceptions (Optional) Keyword to enable debugging of spanning tree BackboneFast exceptions.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to display detailed spanning tree BackboneFast debugging information:
Switch-sp# debug spanning-tree backbonefast detail Spanning Tree backbonefast detail debugging is on Switch-sp#
Related Commands
undebug spanning-tree backbonefast (same as no debug spanning-tree backbonefast)
remote login
Use the debug spanning-tree switch command to enable switch shim debugging. Use the no form of this command to disable debugging output.
debug spanning-tree switch {all | errors | general | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
Syntax Description
all Keyword to display all STP switch shim debugging messages. errors Keyword to enable debugging of switch shim errors or exceptions. general Keyword to enable debugging of general events. pm Keyword to enable debugging of port manager events. rx Keyword to display received BPDU handling debugging messages. decode Keyword to enable debugging of spanning-tree switch shim decode received packets. errors Keyword to enable debugging of spanning-tree switch shim receive errors. interrupt Keyword to enable spanning tree switch shim ISR receive BPDU debugging. process Keyword to enable spanning tree switch shim process receive BPDU debugging. state Keyword to enable debugging of spanning tree port state changes. tx Keyword to enable spanning tree switch shim transmit BPDU debugging. decode (Optional) Keyword to enable spanning tree switch shim decode transmitted packets debugging.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to enable spanning tree switch shim transmit BPDU debugging:
Switch-sp# debug spanning-tree switch tx Spanning Tree Switch Shim transmit bpdu debugging is on Router# *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 303 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 304 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 305 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 349 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 350 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 351 *Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/ 9 801 <... output truncated ...> Switch-sp#
Related Commands
undebug spanning-tree switch (same as no debug spanning-tree switch)
remote login
Use the debug spanning-tree uplinkfast command to enable debugging of spanning tree UplinkFast events. Use the no form of this command to disable debugging output.
debug spanning-tree uplinkfast [exceptions]
Syntax Description
exceptions (Optional) Keyword to enable debugging of spanning tree UplinkFast exceptions.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Step 1
This command is only supported by the supervisor engine and can be entered only from the switch console (see the remote login command).
Examples
This example shows how to debug spanning tree UplinkFast exceptions:
Switch-sp# debug spanning-tree uplinkfast exceptions Spanning Tree uplinkfast exceptions debugging is on Switch-sp#
Related Commands
undebug spanning-tree uplinkfast (same as no debug spanning-tree uplinkfast)
remote login
Use the debug sw-vlan command to debug VLAN manager activities. Use the no form of this command to disable debugging output.
debug sw-vlan {badpmcookies | events | management | packets | registries}
Syntax Description
badpmcookies Keyword to display VLAN manager incidents of bad port manager cookies. events Keyword to debug VLAN manager events. management Keyword to debug VLAN manager management of internal VLANs. packets Keyword to debug packet handling and encapsulation processes. registries Keyword to debug VLAN manager registries.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug sw-vlan events:
Router# debug sw-vlan events vlan manager events debugging is on Router#
Related Commands
undebug sw-vlan (same as no debug sw-vlan)
Use the debug sw-vlan ifs command to enable VLAN manager IOS file system error tests. Use the no form of this command to disable debugging output.
debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
Syntax Description
open Keyword to enable VLAN manager IFS debugging of errors in an IFS file open operation. read Keyword to enable debugging of errors that occurred when opening the IFS VLAN configuration file in order to read it. write Keyword to enable debugging of errors that occurred when opening the IFS VLAN configuration file in order to write to it. read Keyword to enable debugging of errors that occurred when performing an IFS file read operation. {1 | 2 | 3 | 4} Keywords to determine the file read operation. See thethe "Usage Guidelines" section for information about operation levels. write Keyword to enable debugging of errors that occurred when performing an IFS file write operation.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
When determining the file read operation, Operation 1 reads the file header, which contains the header verification word and the file version number. Operation 2 reads the main body of the file, which contains most of the domain and VLAN information. Operation 3 reads TLV descriptor structures. Operation 4 reads TLV data.
Examples
This example shows how to enable debugging of TLV data errors during a file read operation:
Router# debug sw-vlan ifs read 4 vlan manager ifs read #4 errors debugging is on Router#
Related Commands
undebug sw-vlan ifs (same as no debug sw-vlan ifs)
Use the debug sw-vlan notification command to enable debugging messages that trace the activation and deactivation of ISL VLAN IDs.
debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange linkchange | modechange | pruningcfgchange | statechange}
Syntax Description
accfwdchange Keyword to enable VLAN manager notification of aggregated access interface STP forward changes. allowedvlancfgchange Keyword to enable VLAN manager notification of change to allowed VLAN configuration. fwdchange Keyword to enable VLAN manager notification of STP forwarding changes. linkchange Keyword to enable VLAN manager notification of interface link state changes. modechange Keyword to enable VLAN manager notification of interface mode changes. pruningcfgchange Keyword to enable VLAN manager notification of change to pruning configuration. statechange Keyword to enable VLAN manager notification of interface state changes.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example shows how to debug sw-vlan interface mode change notifications:
Router# debug sw-vlan notification modechange vlan manager port mode change notification debugging is on Router#
Related Commands
undebug sw-vlan notification (same as no debug sw-vlan notification)
Use the debug sw-vlan vtp command to enable debugging messages to be generated by the VTP protocol code. Use the no form of this command to disable debugging output.
debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
Syntax Description
events Keyword to display general-purpose logic flow and detailed VTP debugging messages generated by the VTP_LOG_RUNTIME macro in the VTP code. packets Keyword to display the contents of all incoming VTP packets that have been passed into the VTP code from the IOS VTP platform-dependent layer, except for pruning packets. pruning Keyword to enable debugging message to be generated by the pruning segment of the VTP protocol code. packets (Optional) Keyword to display the contents of all incoming VTP pruning packets that have been passed into the VTP code from the IOS VTP platform-dependent layer. xmit (Optional) Keyword to display the contents of all outgoing VTP packets that the VTP code will request the IOS VTP platform-dependent layer to send. xmit Keyword to display the contents of all outgoing VTP packets that the VTP code will request the IOS VTP platform-dependent layer to send, except for pruning packets.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Usage Guidelines
If no further parameters are entered after pruning, VTP pruning debugging messages are displayed 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.
Examples
This example shows how to debug sw-vlan outgoing VTP packets:
Router# debug sw-vlan vtp xmit vtp xmit debugging is on Router#
Related Commands
undebug sw-vlan vtp (same as no debug sw-vlan vtp)
Use the debug tcam command to debug TCAM activity. Use the no form of this command to disable debugging output.
debug tcam {all | events | messages | verbose}
Syntax Description
all Keyword to enable full TCAM debugging. events Keyword to enable TCAM event debugging. messages Keyword to enable debugging of messages sent to the TCAM. verbose Keyword to display detailed TCAM debugging information.
Defaults
This command has no default setting.
Command Modes
Privileged EXEC mode.
Examples
This example show how to display detailed TCAM debugging information:
Router# debug tcam verbose TCAM verbose debugging is on Router#
Related Commands
undebug tcam (same as no debug tcam)
Use the define interface-range command to create an interface-range macro.
define interface-range macro-name interface-range
Syntax Description
macro-name Name of the interface-range macro; up to 32 characters. interface-range Interface range; for a list of valid values for interface ranges, see the "Usage Guidelines" section.
Defaults
This command has no default setting.
Command Modes
Global configuration mode.
Usage Guidelines
The macro name is a 32-character maximum character string.
A macro can contain up to five ranges. An interface range cannot span slots.
When entering the interface-range, these formats can be used:
Valid values for card-type are:
Examples
The example shows how to create a multiple-interface macro:
Router(config)#defineinterface-range macro1 ethernet 1/2 - 5, fastethernet 5/5 - 10Router(config)#
Related Commands
Use the duplex command to configure the duplex operation on an interface. Use the no form of this command to return the system to half-duplex mode.
duplex {full | half}
Syntax Description
full Keyword to specify full-duplex operation. half Keyword to specify half-duplex operation.
Defaults
The default is half-duplex mode.
Command Modes
Interface configuration mode.
Usage Guidelines
Table 2-5 lists the supported command options by interface.
| Interface Type | Supported Syntax | Default Setting | Usage Guidelines |
|---|---|---|---|
10/100-Mbps module (WS-X6248-RJ-45) | duplex [half | full] | See the Usage Guidelines. | If the speed is set to auto, you will not be able to set duplex. If the speed is set to 10 or 100, and you do not configure the duplex setting, the duplex is set to half. |
100-Mbps fiber modules (WS-X6224- 100FX-MT) | duplex [half | full] | half |
|
Gigabit Ethernet Interface (WS-X6408-GBIC) | Not supported. | Not supported. |
|
10-Mbps ports | duplex [half | full] | half |
|
When manually configuring interface speed to either 10 or 100 Mbps, the switch prompts you to also configure duplex mode on the interface.
|
Note Catalyst 6000 family switches cannot automatically negotiate interface speed and duplex mode if either connecting interface is configured to a value other than auto. |
 |
Caution Changing the interface speed and duplex mode configuration might shut down and reenable the interface during the reconfiguration. |
Table 2-6 describes the system's performance for different combinations of the duplex and speed modes. The specified duplex command configured with the specified speed command produces the resulting system action shown in the table.
| duplex Command | speed Command | Resulting System Action |
|---|---|---|
duplex half or duplex full | speed auto | Autonegotiates both speed and duplex modes |
duplex half | speed 10 | Forces 10 Mbps and half duplex |
duplex full | speed 10 | Forces 10 Mbps and full duplex |
duplex half | speed 100 | Forces 100 Mbps and half duplex |
duplex full | speed 100 | Forces 100 Mbps and full duplex |
Examples
This example shows how to configure the interface for full-duplex operation:
Router(config-if)#duplex fullRouter(config-if)#
Related Commands
speed
interface (refer to Cisco IOS documentation)
show controllers (refer to Cisco IOS documentation)
show interfaces (refer to Cisco IOS documentation)
Use the errdisable recovery command to configure the recover mechanism variables. Use the no form of this command to return to the default state.
errdisable recovery cause {all | bpduguard | dtp-flap | link-flap | pagp-flap | rootguard | udld}
Syntax Description
cause Keyword to enable error disable recovery to recover from a specific cause. all Keyword to enable the recover timers for all error disable causes. bpduguard Keyword to enable the recovery timer for the BPDU guard error disable cause. dtp-flap Keyword to enable the recovery timer for the DTP flap error disable cause. link-flap Keyword to enable the recovery timer for the link flap error disable cause. pagp-flap Keyword to enable the recovery timer for the PAgP flap error disable cause. rootguard Keyword to enable the recovery timer for the root guard error disable cause. udld Keyword to enable the recovery timer for the UDLD error disable cause. interval interval Keyword and variable to specify the time to recover from specified error disable cause; valid values are from 30 to 86400 seconds.
Defaults
The default is recovery is disabled for all causes.
Command Modes
Global configuration mode.
Usage Guidelines
A cause (bpduguard, dtp-flap, link-flap, pagp-flap, root-guard, udld) is defined as the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in error-disabled state (an operational state similiar to link down state). If you do not enable errdisable recovery for the cause, the interface stays in error-disabled state until a shut and no shut occurs. If you enable recovery for a cause, the interface is brought out of error-disabled state and allowed to retry operation again once all the causes have timed out.
You must enter the shutdown then no shutdown commands to recover an interface manually from errdisable.
Examples
This example shows how to enable the recovery timer for the BPDU guard error disable cause:
Router(config)#errdisable recovery cause bpduguardRouter(config)#
This example shows how to set the timer to 300 seconds:
Router(config)#errdisable recovery interval 300Router(config)#
Related Commands
show errdisable recovery
show interfaces status
Posted: Fri Jul 21 13:03:29 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.