-
Cisco 7600 Series Router Cisco IOS Command Reference, 12.1E
-
Index
-
Preface
-
Command-Line Interface
-
action to cd
-
Cisco 7600 Series Router Cisco IOS Commands
-
BRC
-
channel-group to clear catalyst6000
-
clear counters to debug callback
-
debug cca to duplex
-
erase to mls aging
-
mls exclude to pagp port-priority
-
policy-map to protocol filtering
-
rcv-queue to show bootflash
-
shutdown vlan to time-range
-
show bootvar to show ip cache
-
show ip cef to show mls asic
-
show mls cef to show qm-sp
-
show queueing to show vtp
-
title
-
udld to username
-
verify to wrr-queue bandwidth
-
wrr-queue cos-map to wrr-queue threshold
-
Acronyms
-
Acknowledgments for Open-Source Software
-
Table Of Contents
debug spanning-tree backbonefast
debug spanning-tree uplinkfast
22debug cca
To debug CCA register activity, use the debug cca command. Use the no form of this command to disable debugging output.
debug cca
no debug cca
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug CCA register activity:
Router# debug ccaCCA debugging is onRouter#Related Commands
undebug cca (same as no debug cca)
debug condition interface
To limit the debugging output of interface-related activities, use the debug condition interface command. Use the no form of this command to disable debugging output.
debug condition interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id group-number}}
no debug condition interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id 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
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
12.1(11b)E
This command was changed to include the pos, atm, and ge-wan keywords.
Usage Guidelines
The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.
The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.
If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to limit debugging output to VLAN interface 1:
Router# debug condition interface vlan 1Condition 2 setRouter#Related Commands
debug interface
undebug condition interface (same as no debug condition interface)debug condition standby
To limit the debugging output of Hot Standby Router Protocol state changes, use the debug condition standby command. Use the no form of this command to disable debugging output.
debug condition standby {{interface interface-number} | {port-channel number} | {vlan vlan-id group-number}}
no debug condition standby {{interface interface-number} | {port-channel number} | {vlan vlan-id group-number}}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
12.1(11b)E
This command was changed to include the pos, atm, and ge-wan keywords.
Usage Guidelines
The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.
The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.
If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.
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. Removing the only condition set may cause an excessive number of debugging messages.
Examples
This example shows how to limit the debugging output to group 0 in VLAN 1:
Router# debug condition standby vlan 1 0Condition 3 setRouter#This example shows the display if you try to turn off the last standby debug condition:
Router# no debug condition standby vlan 1 0This condition is the last standby condition set.Removing all conditions may cause a flood of debuggingmessages to result, unless specific debugging flagsare first removed.Proceed with removal? [yes/no]: n% Operation abortedRouter#Related Commands
undebug condition standby (same as no debug condition standby)
debug condition vlan
To limit the VLAN debugging output to a specified VLAN, use the debug condition vlan command. Use the no form of this command to disable debugging output.
debug condition vlan {vlan-id}
no debug condition vlan {vlan-id}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
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. Removing the only condition set may cause an excessive number of debugging messages.
If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to limit debugging output to VLAN 1:
Router# debug condition vlan 1Condition 4 setRouter#This example shows the display if you try to turn off the last VLAN debug condition:
Router# no debug condition vlan 1This condition is the last vlan condition set.Removing all conditions may cause a flood of debuggingmessages to result, unless specific debugging flagsare first removed.Proceed with removal? [yes/no]: n% Operation abortedRouter#Related Commands
undebug condition vlan (same as no debug condition vlan)
debug earl
To enable debugging of EARL activity, use the debug earl command. Use the no form of this command to disable debugging output.
debug earl {L2 aging | L2 events | L3 aging | L3 control | L3 netflow}
no debug earl {L2 aging | L2 events | L3 aging | L3 control | L3 netflow}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable debugging of EARL events and provides a sample of the output:
Switch-sp# debug earl L2 eventsEARL5 events debugging is onRouter#*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...Switch-sp#Related Commands
undebug earl (same as no debug earl)
remote logindebug ehsa
To enable debugging of EHSA activity, use the debug ehsa command. Use the no form of this command to disable debugging output.
debug ehsa {all | config_sync | fsm | general}
no debug ehsa {all | config_sync | fsm | general}
Syntax Description
all
Enables debugging of all EHSA events.
config_sync
Enables debugging of EHSA configuration synchronization.
fsm
Enables debugging of EHSA FSM.
general
Enables debugging of EHSA general events.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable debugging of general EHSA events:
Switch-sp# debug ehsa generalEHSA general debugging is onSwitch-sp#Related Commands
undebug ehsa (same as no debug ehsa)
remote logindebug entry
To debug incoming queue entries, use the debug entry command. Use the no form of this command to disable debugging output.
debug entry
no debug entry
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of incoming queue entries:
Router# debug entryIncoming queue entry debugging is onRouter#Related Commands
undebug entry (same as no debug entry)
debug etherchnl
To enable EtherChannel/PAgP shim debugging, use the debug etherchnl command. Use the no form of this command to disable debugging output.
debug etherchnl [all | detail | error | event | idb | linecard]
no debug etherchnl
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
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 etherchnlSep 14 12:59:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8, changed state to downSep 14 12:59:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/9, changed state to downSep 14 13:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8, changed state to upSep 14 13:11:03: %SYS-5-CONFIG_I: Configured from console by vty2 (171.69.200.227)...Router#This example shows how to display EtherChannel IDB debug messages:
Router# debug etherchnl idbAgport idb related debugging is onRouter#Related Commands
undebug etherchnl (same as no debug etherchnl)
debug ethernet-interface
To debug Ethernet interface events, use the debug ethernet-interface command. Use the no form of this command to disable debugging output.
debug ethernet-interface
no debug ethernet-interface
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of Ethernet interface events and provides a sample of the output:
Router# debug ethernet-interfaceEthernet network interface debugging is onRouter# RX:(D)b000.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.0.80 (TL)6RX:(D)b800.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.255.255 (TL)57344RX:(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)
debug fastethernet
To debug Fast Ethernet interface events or packets, use the debug fastethernet command. Use the no form of this command to disable debugging output.
debug fastethernet {events | packets}
no debug fastethernet {events | packets}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
These examples show how to debug Fast Ethernet events and packets:
Router# debug fastethernet eventsFast Ethernet events debugging is onRouter#Router# debug fastethernet packetsFast Ethernet packets debugging is onRouter#Related Commands
undebug fastethernet (same as no debug fastethernet)
debug fm
To debug feature manager (fm) events and activities, use the debug fm command. Use the no form of this command to disable debugging output.
debug fm {all | event | queue-event | unusual | verbose}
no debug fm {all | event | queue-event | unusual | verbose}
Syntax Description
all
Debugs all FM activity.
event
Debugs FM events.
queue-event
Debugs only FM queue events.
unusual
Debugs only unusual FM events.
verbose
Displays verbose debug output for FM.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable verbose debugging output of feature manager events and activities:
Router# debug fm verboseFM verbose debugging is onRouter#Related Commands
undebug fm (same as no debug fm)
debug gssapi
To debug GSSAPI events, use the debug gssapi command. Use the no form of this command to disable debugging output.
debug gssapi
no debug gssapi
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of GSSAPI events:
Router# debug gssapiGSSAPI debugging is onRouter#Related Commands
undebug gssapi (same as no debug gssapi)
debug icc
To debug ICC events, use the debug icc command. Use the no form of this command to disable debugging output.
debug icc [all | async-requests | events | exceptions | requests]
no debug icc [all | async-requests | events | exceptions | requests]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of ICC asynchronous requests and provides a sample of the output:
Router# debug icc async-requestsICC Asynchronous Requests debugging is onRouter# #icc_append_async_request: msg 0x617E2058, id 0x62595448, cb 0x603E9CB8icc_append_async_request: ar 0x618438E0icc_append_async_request: head 0x0, tail 0x61479B50icc_async_callback: msg=0x617E2058, err=0icc_unlink_async_request: msg 0x617E2058icc_unlink_async_request: head matches<... output truncated ...>Router#Related Commands
undebug icc (same as no debug icc)
debug iccshim
To debug ICC shim events, use the debug iccshim command. Use the no form of this command to disable debugging output.
debug iccshim [all | event | packet]
no debug iccshim [all | event | packet]
Syntax Description
all
(Optional) Debugs all ICC shim events.
event
(Optional) Debugs only ICC shim events.
packet
(Optional) Debugs ICC shim packets.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of ICC shim packets and provides a sample of the output:
Router# debug iccshim packetICCSHIM packets debugging is onRouter# icc_append_async_request: msg 0x617E25AC, id 0x62595448, cb 0x603E9CB8icc_append_async_request: ar 0x618438E0icc_append_async_request: head 0x0, tail 0x61479B50icc_async_callback: msg=0x617E25AC, err=0icc_unlink_async_request: msg 0x617E25ACicc_unlink_async_request: head matchesicc_unlink_async_request: took tailicc_unlink_async_request: head 0x0, tail 0x61479B50, p 0x618438E0icc_async_callback: ar 0x618438E0, cb 0x603E9CB8, id 0x62595448icc_async_callback: got rpc respsonse, msg=0x617E2058icc_async_callback: got rpc respsonse, pak=0x6176B770icc_async_callback: calling callbackicc_async_callback: callback complete<... output truncated ...>Router#Related Commands
undebug iccshim (same as no debug iccshim)
debug interface
To create a shortcut for the debug condition interface command, use the debug interface command. Use the no form of this command to disable debugging output.
debug interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id}}
no debug interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id}}
Note
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
12.1(11b)E
This command was changed to include the pos, ge-wan, and atm keywords.
Usage Guidelines
The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.
The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.
If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.
Examples
This example shows how to limit debugging to interface VLAN 1:
Router# debug interface vlan 1Condition 1 setRouter#Related Commands
debug condition interface
undebug interface (same as no debug interface)debug ipc
To debug IPC activity, use the debug ipc command. Use the no form of this command to disable debugging output.
debug ipc {all | errors | events | headers | packets | ports | seats}
no debug ipc {all | errors | events | headers | packets | ports | seats}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of IPC events:
Router# debug ipc eventsSpecial Events debugging is onRouter#Related Commands
undebug ipc (same as no debug ipc)
debug ip rgmp
To debug RGMP activity, use the debug ip rgmp command. Use the no form of this command to disable debugging output.
debug ip rgmp [name | group-address]
no debug ip rgmp [name | group-address]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable RGMP debugging:
Router# debug ip rgmpRGMP debugging is onRouter#This example shows how to disable RGMP debugging:
Router# no debug ip rgmpRGMP debugging is offRouter#Related Commands
debug l2-mgr events
To debug Layer 2 manager events, use the debug l2-mgr events command. Use the no form of this command to disable debugging output.
debug l2-mgr events
no debug l2-mgr events
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable debugging of Layer 2 manager events:
Switch-sp# debug l2-mgr eventsL2 mgr events debugging is onSwitch-sp#Related Commands
remote login
undebugl2-mgr events (same as no debug l2-mgr events)
debug l3-mgr
To debug Layer 3 manager activity, use the debug l3-mgr command. Use the no form of this command to disable debugging output.
debug l3-mgr {all | events | global | packets}
no debug l3-mgr {all | events | global | packets}
Syntax Description
all
Displays all Layer 3 manager debug messages.
events
Displays Layer 3 manager-related events.
global
Displays a bug trace of IP global purge events.
packets
Displays Layer 3 manager packets.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable global Layer 3 manager debugging:
Router# debug l3-mgr globalL3 mgr ip global purge debugging is onRouter#Related Commands
undebugl3-mgr (same as no debug l3-mgr)
debug local-ack
To debug local acknowledgment activity, use the debug local-ack command. Use the no form of this command to disable debugging output.
debug local-ack {errors | packets | state}
no debug local-ack {errors | packets | state}
Syntax Description
errors
Displays all local acknowledgement errors.
packets
Displays local acknowledgment packets.
state
Displays local acknowledgment state changes.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of local acknowledgement state changes:
Router# debug local-ack stateLocal Acknowledgement states debugging is onRouter#Related Commands
undebug local-ack (same as no debug local-ack)
debug ltl
To enable debugging of LTL manager activity, use the debug ltl command. Use the no form of this command to disable debugging output.
debug ltl
no debug ltl
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable LTL manager debugging:
Switch-sp# debug ltlltl mgr debugging is onSwitch-sp#Related Commands
remote login
undebug ltl (same as no debug ltl)
debug mergeapi
To debug ACL merge activity, use the debug mergeapi command. Use the no form of this command to disable debugging output.
debug mergeapi {all | normal | profile | verbose}
no debug mergeapi {all | normal | profile | verbose}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug the CUDD library's internal cache:
Router# debug mergeapi profileACLMERGE debug time profile debugging is onRouter#Related Commands
undebug mergeapi (same as no debug mergeapi)
debug mls ip multicast
To debug MLS IP multicast activity, use the debug mls ip multicast command. Use the no form of this command to disable debugging output.
debug mls ip multicast {all | error | events | group | messages}
no debug mls ip multicast {all | error | events | group | messages}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable debugging of MLS IP multicast errors:
Router# debug mls ip multicast errormcast error debugging is onRouter#Related Commands
undebug mls ip multicast (same as no debug mls ip multicast)
debug mls rp
To debug MLS RP activity, use the debug mls rp command. Use the no form of this command to disable debugging output.
debug mls rp {all | error | events | ip | ipx | locator | packets | verbose packets}
no debug mls rp {all | error | events | ip | ipx | locator | packets | verbose packets}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable debugging of MLS RP IGMP events:
Switch-sp# debug mls rp eventsmls events debugging is onSwitch-sp#Related Commands
remote login
undebug mls rp (same as no debug mls rp)debug monitor
To display monitoring activity, use the debug monitor command. Use the no form of this command to disable debugging output.
debug monitor {all | errors | idb-update | list | notifications | platform | requests}
no debug monitor {all | errors | idb-update | list | notifications | platform | requests}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug monitoring errors:
Router# debug monitor errorsSPAN error detail debugging is onRouter#Related Commands
undebug monitor (same as no debug monitor)
debug msc
To debug MSC activity, use the debug msc command. Use the no form of this command to disable debugging output.
debug msc {all | events | pak}
no debug msc {all | events | pak}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug MSC packets:
Router# debug msc pakRouter#Related Commands
undebug msc (same as no debug msc)
debug netdr
To debug NetDriver activity, use the debug netdr command. Use the no form of this command to disable debugging output.
debug netdr {all | data}
no debug netdr {all | data}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug the NetDriver data flow:
Router# debug netdr dataNetDriver Receive Data on interrupt debugging is onNetDriver Receive Data debugging is onNetDriver Transmit Data debugging is onNetDriver Relay Data debugging is onRouter#2d21h: const_ether_vlan_vencap() Vlan1:2d21h: src_vlan=0x1 src_indx=0x3 len=0xE9 bpdu=02d21h: index_dir=0 dest_indx=0x0 dont_lrn=02d21h: Dbus hdr: 00000000 00010000 00030000 E90000002d21h: 00000000 00000000 00000000 000000002d21h: MAC hdr: dmac=00801C.938040, smac=00503E.8D6400, typelen=08002d21h: IP hdr: 45C000DB 02F30000 FF066331 AC143412 AB45C8CC2d21h: fx1000_process_receive_packet() Vlan1:2d21h: src_vlan=0x1 src_indx=0x108 len=0x40 bpdu=02d21h: index_dir=0 dest_indx=0x3 dont_lrn=02d21h: Dbus hdr: 60000000 00010000 01080000 401000002d21h: 0006AC14 3412AB45 C8CC0000 000300002d21h: MAC hdr: dmac=00503E.8D6400, smac=00605C.865B28, typelen=08002d21h: IP hdr: 45000028 B5254000 7D06F471 AB45C8CC AC143412<... output truncated ...>Router#Related Commands
undebug netdr (same as no debug netdr)
debug nvram
To debug NVRAM activity, use the debug nvram command. Use the no form of this command to disable debugging output.
debug nvram
no debug nvram
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug NVRAM:
Router# debug nvramNVRAM behaviour debugging is onRouter#Related Commands
undebug nvram (same as no debug nvram)
debug pagp
To debug PAgP activity, use the debug pagp command. Use the no form of this command to disable debugging output.
debug pagp [all | event | fsm | misc | packet]
no debug pagp
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable PAgP miscellaneous debugging:
Switch-sp# debug pagp miscPort Aggregation Protocol Miscellaneous debugging is onRouter#*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
remote login
undebug pagp (same as no debug pagp)debug pf
To debug PF activity, use the debug pf command. Use the no form of this command to disable debugging output.
debug pf {all | errors | events | learns | sm}
no debug pf {all | errors | events | learns | sm}
Syntax Description
all
Enables all PF debugging.
errors
Enables PF error debugging.
events
Enables PF event debugging.
learns
Debugs PF address learning.
sm
Debugs the state machine.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug the PF learned addresses:
Router# debug pf learnsAddress learning debugging is onRouter#Related Commands
undebug pf (same as no debug pf)
debug pm
To debug PM activity, use the debug pm command. Use the no form of this command to disable debugging output.
debug pm {all | card | cookies | etherchnl | messages | port | registry | scp | sm | span | split |
vlan | vp}no debug pm {all | card | cookies | etherchnl | messages | port | registry | scp | sm | span | split |
vlan | vp}Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to enable all PM debugging:
Router# debug pm allRouter#Related Commands
undebug pm (same as no debug pm)
debug priority
To debug priority output queueing, use the debug priority command. Use the no form of this command to disable debugging output.
debug priority
no debug priority
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug priority output queueing:
Router# debug priorityPriority output queueing debugging is onRouter#Related Commands
undebug priority (same as no debug priority)
debug qm
To debug QM activity, use the debug qm command. Use the no form of this command to disable debugging output.
debug qm {all | error | event | packet}
no debug qm {all | error | event | packet}
Syntax Description
all
Debugs all QM activity.
error
Enables debugging of QM errors.
event
Enables QM event debugging.
packet
Enables QM packet debugging.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug QM packets:
Router# debug qm packetQM packet debug debugging is onRouter#Related Commands
undebug qm (same as no debug qm)
debug qm-sp
To debug the switch processor QoS manager activity, use the debug qm-sp command. Use the no form of this command to disable debugging output.
debug qm-sp {all | event | packet}
no debug qm-sp {all | event | packet}
Syntax Description
all
Debugs all QM-SP activity.
event
Enables QM-SP event debugging.
packet
Enables QM-SP packet debugging.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example show how to debug QM packets:
Switch-sp# debug qm-sp packetQoS Manager Packet debugging is onSwitch-sp#Related Commands
remote login
undebug qm-sp (same as no debug qm-sp)
debug rpc
To debug RPC activity, use the debug rpc command. Use the no form of this command to disable debugging output.
debug rpc {all | errors | events | packets | requests}
no debug rpc {all | errors | events | packets | requests}
Syntax Description
all
Debugs all RPC activity.
errors
Enables debugging of RPC errors.
events
Enables RPC event debugging.
packets
Enables RPC packet debugging.
requests
Enables debugging of RPC requests.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
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 00...2d20h: 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)
debug scp
To debug SCP activity, use the debug scp command. Use the no form of this command to disable debugging output.
debug scp {all | async | data | errors | packets | timeouts}
no debug scp {all | async | data | errors | packets | timeouts}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug SCP packets:
Router# debug scp packetsSCP packets debugging is onRouter#Related Commands
undebug scp (same as no debug scp)
debug smf updates
To debug SMF address insertions and deletions, use the debug smf updates command. Use the no form of this command to disable debugging output.
debug smf updates
no debug smf updates
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug SMF updates:
Router# debug smf updatesSoftware MAC filter address insertions and deletions debugging is onRouterRelated Commands
undebug smf (same as no debug smf)
debug spanning-tree
To debug spanning tree activities, use the debug spanning-tree command. Use the no form of this command to disable debugging output.
debug spanning-tree {all | bpdu | bpdu-opt | etherchannel | config | events | exceptions | general | pvst+ | root | snmp}
no debug spanning-tree {all | bpdu | bpdu-opt | etherchannel | config | events | exceptions | general | pvst+ | root | snmp}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug spanning tree PVST+:
Router# debug spanning-tree pvst+Spanning Tree PVST+ debugging is onRouterRelated Commands
undebug spanning-tree (same as no debug spanning-tree)
debug spanning-tree backbonefast
To enable debugging of spanning tree BackboneFast events, use the debug spanning-tree backbonefast command. Use the no form of this command to disable debugging output.
debug spanning-tree backbonefast [detail | exceptions]
no debug spanning-tree backbonefast
Syntax Description
detail
(Optional) Displays detailed BackboneFast debugging messages.
exceptions
(Optional) Enables debugging of spanning tree BackboneFast exceptions.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router 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 detailSpanning Tree backbonefast detail debugging is onSwitch-sp#Related Commands
remote login
undebug spanning-tree backbonefast (same as no debug spanning-tree backbonefast)
debug spanning-tree switch
To enable switch shim debugging, use the debug spanning-tree switch command. 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]}
no debug spanning-tree switch {all | errors | general | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router 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 txSpanning Tree Switch Shim transmit bpdu debugging is onRouter#*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
remote login
undebug spanning-tree switch (same as no debug spanning-tree switch)debug spanning-tree uplinkfast
To enable debugging of spanning tree UplinkFast events, use the debug spanning-tree uplinkfast command. Use the no form of this command to disable debugging output.
debug spanning-tree uplinkfast [exceptions]
no debug spanning-tree uplinkfast
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to debug spanning tree UplinkFast exceptions:
Switch-sp# debug spanning-tree uplinkfast exceptionsSpanning Tree uplinkfast exceptions debugging is onSwitch-sp#Related Commands
remote login
undebug spanning-tree uplinkfast (same as no debug spanning-tree uplinkfast)
debug sw-vlan
To debug VLAN manager activities, use the debug sw-vlan command. Use the no form of this command to disable debugging output.
debug sw-vlan {badpmcookies | events | management | packets | registries}
no debug sw-vlan {badpmcookies | events | management | packets | registries}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug sw-vlan events:
Router# debug sw-vlan eventsvlan manager events debugging is onRouter#Related Commands
undebug sw-vlan (same as no debug sw-vlan)
debug sw-vlan ifs
To enable VLAN manager Cisco IOS file system error tests, use the debug sw-vlan ifs command. Use the no form of this command to disable debugging output.
debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
no debug sw-vlan ifs {open {open | read} | read {1 | 2 | 3 | 4} | write}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
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 4vlan manager ifs read #4 errors debugging is onRouter#Related Commands
undebug sw-vlan ifs (same as no debug sw-vlan ifs)
debug sw-vlan notification
To enable debugging messages that trace the activation and deactivation of ISL VLAN IDs, use the debug sw-vlan notification command.
debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange linkchange | modechange | pruningcfgchange | statechange}
no debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to debug sw-vlan interface mode change notifications:
Router# debug sw-vlan notification modechangevlan manager port mode change notification debugging is onRouter#Related Commands
undebug sw-vlan notification (same as no debug sw-vlan notification)
debug sw-vlan vtp
To enable debugging messages that are generated by the VTP code, use the debug sw-vlan vtp command. Use the no form of this command to disable debugging output.
debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
no debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
If you do not enter any parameters after entering pruning, the VTP pruning debugging messages are displayed. The messages are generated by the VTP_PRUNING_LOG_NOTICE, VTP_PRUNING_LOG_INFO, VTP_PRUNING_LOG_DEBUG, VTP_PRUNING_LOG_ALERT, and VTP_PRUNING_LOG_WARNING macros in the VTP pruning code.
Examples
This example shows how to debug sw-vlan outgoing VTP packets:
Router# debug sw-vlan vtp xmitvtp xmit debugging is onRouter#Related Commands
undebug sw-vlan vtp (same as no debug sw-vlan vtp)
debug tcam
To debug TCAM activity, use the debug tcam command. Use the no form of this command to disable debugging output.
debug tcam {all | events | messages | verbose}
no debug tcam {all | events | messages | verbose}
Syntax Description
all
Enables full TCAM debugging.
events
Enables TCAM event debugging.
messages
Enables debugging of messages sent to the TCAM.
verbose
Displays detailed TCAM debugging information.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to display detailed TCAM debugging information:
Router# debug tcam verboseTCAM verbose debugging is onRouter#Related Commands
undebug tcam (same as no debug tcam)
debug udld
To enable debugging of UDLD activity, use the debug udld command. Use the no form of this command to disable debugging output.
debug udld {events | packets | registries}
no debug udld {events | packets | registries}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Cisco 7600 series router console (see the remote login command).
Examples
This example shows how to enable debugging of UDLD events:
Switch-sp# debug udld eventsUDLD events debugging is onSwitch-sp#This example shows how to enable debugging of UDLD packets:
Switch-sp# debug udld packetsUDLD packets debugging is onSwitch-sp#This example shows how to enable debugging of UDLD registry events:
Switch-sp# debug udld registriesUDLD registries debugging is onRelated Commands
undebug udld (same as no debug udld)
debug vacl
To debug VACL activity, use the debug vacl command. Use the no form of this command to disable debugging output.
debug vacl {all | event | unusual | verbose}
no debug vacl {all | event | unusual | verbose}
Syntax Description
all
Enables full VACL debugging.
event
Enables VACL event debugging.
unusual
Enables VACL unusual event debugging.
verbose
Enables detailed VACL debugging information.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EX
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to display detailed VACL debugging information:
Router# debug vacl verboseVACL verbose debugging is onRouter#Related Commands
undebug vacl (same as no debug vacl)
debug vlog
To debug VACL logging activity, use the debug vlog command. Use the no form of this command to disable debugging output.
debug vlog {all | event | queue-event | unusual | verbose}
no debug vlog {all | event | queue-event | unusual | verbose}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EX
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to display detailed VACL logging debugging information:
Router# debug vlog verboseVACL logging verbose debugging is onRouter#Related Commands
undebug vlog (same as no debug vlog)
define interface-range
To create an interface-range macro, use the define interface-range command.
define interface-range macro-name interface-range
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
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 as follows:
•
•
•
•
•
•
•
•
•
Examples
This example shows how to create a multiple-interface macro:
Router(config)# define interface-range macro1 ethernet 1/2 - 5, fastethernet 5/5 - 10Router(config)#Related Commands
diagnostic level
To set the bootup online diagnostic level, use the diagnostic level command. Use the bypass keyword to bypass diagnostic testing.
diagnostic level [minimal | complete | bypass]
Syntax Description
Defaults
minimal
Command Modes
Global configuration
Command History
12.1(11b)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
This command is supported in Cisco 7600 series routers configured with a Supervisor Engine 2 with Layer 3 Switching Engine II (PFC2) only.
Setting the diagnostic level determines the level of testing that occurs when the system or module is reset. The three levels are as follows:
•
•
•
Note
In certain circumstances, you might want to skip the bootup online diagnostics completely. For example, you might skip the bootup online diagnostics to verify that a port is as bad as online diagnostics reports. To skip online diagnostic testing completely, enter the diagnostic level bypass command.
For information on the diagnostic test types, see the show diagnostic command.
The new level takes effect at the next reload or the next time an online insertion and removal is performed.
Examples
This example shows how to set the bootup online diagnostics level:
Router(config)# diagnostic level completeRouter(config)#Related Commands
disconnect qdm
To disconnect a QDM session, use the disconnect qdm command.
disconnect qdm [{client client-id}]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EX
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
QDM is not supported on OSM interfaces.
If you enter the disconnect qdm command without any arguments, all QDM sessions are disconnected. You can obtain the client-id by entering the show qdm status command.
Examples
This example shows how to disconnect a QDM session:
Router# disconnect qdm client 1Router#Related Commands
do
To execute EXEC-level commands from global configuration mode or other configuration modes or submodes, use the do command.
do command
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration or any other configuration mode or submode from which you are executing the EXEC-level command.
Command History
12.1(11b)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Caution
You cannot use the do command to execute the configure terminal EXEC command because issuing the configure terminal command changes the mode to configuration mode.
Examples
This example shows how to execute the EXEC-level show interface command from within global configuration mode:
Router(config)# do show interfaces serial 3/0Serial3/0 is up, line protocol is upHardware is M8T-RS232MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation HDLC, loopback not set, keepalive set (10 sec)Last input never, output 1d17h, output hang neverLast clearing of "show interface" counters never...Router(config)#dot1x default
To reset the configurable 802.1X parameters to the default values, use the dot1x default command.
dot1x default
Syntax Description
This command has no arguments or keywords.
Defaults
The default values are as follows:
•
•
•
•
•
•
•
•
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to reset the configurable 802.1X parameters to the default values:
Router(config-if)# dot1x defaultSetting the Default Configuration for Dot1x on this interfaceRouter(config-if)#Related Commands
dot1x max-req
To set the number of times that the switch sends an EAP-request/identity frame to the client before restarting the authentication process, use the dot1x max-req command. Use the no form of this command to return to the default settings.
dot1x max-req count
no dot1x max-req
Syntax Description
count
Number of times the switch sends an EAP-request/identity frame to the client before restarting the authentication process; valid values are from 1 to 10.
Defaults
count is 2.
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
You should change the default value only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
Examples
This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity request before restarting the authentication process:
Router(config-if)# dot1x max-req 5Router(config-if)#Related Commands
dot1x multi-hosts
To allow multiple hosts (clients) on an 802.1X-authorized port, use the dot1x multi-hosts command. Use the no form of this command to disallow multiple hosts.
dot1x multi-hosts
no dot1x multi-hosts
Syntax Description
This command has no arguments or keywords.
Defaults
Multiple host support is disabled.
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Before entering this command, ensure that the dot1x port-control interface configuration command set is set to auto for the specified interface.
Examples
This example shows how to allow multiple hosts:
Router(config-if)# dot1x multi-hostsRouter(config-if)#This example shows how to disallow multiple hosts:
Router(config-if)# no dot1x multi-hostsRouter(config-if)#Related Commands
dot1x port-control
To set the port control value, use the dot1x port-control command. Use the no form of this command to return to the default settings.
dot1x port-control value
no dot1x port-control
Syntax Description
value
Port-control value; valid values are auto, force-authorized, and force-unauthorized; see the "Usage Guidelines" section for more information.
Defaults
value is force-authorized.
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
The port-control value definitions are as follows:
•
•
•
To check the port-control configuration, enter the show dot1x command and check the Status column in the 802.1X Port Summary section. An enabled status means the port-control value is set either to auto or to force-unauthorized.
Examples
This example shows how to set the port control to auto:
Router(config-if)# dot1x port-control autoRouter(config-if)#Related Commands
dot1x reauthentication
To enable periodic reauthentication of the client, use the dot1x reauthentication command. Use the no form of this command to return to the default settings.
dot1x reauthentication
no dot1x reauthentication
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Reauthentication does not disturb the status of an already authorized port.
Examples
This example shows how to enable periodic reauthentication of the client:
Router(config-if)# dot1x reauthenticationRouter(config-if)#This example shows how to disable periodic reauthentication of the client:
Router(config-if)# no dot1x reauthenticationRouter(config-if)#Related Commands
dot1x system-auth-control
To enable 802.1X globally, use the dot1x system-auth-control command. Use the no form of this command to disable 802.1X globally.
dot1x system-auto-control
no dot1x system-auto-control
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
You must enable AAA and specify the authentication method list before enabling 802.1X. A method list describes the sequence and authentication methods to be queried to authenticate a user.
Examples
This example shows how to enable 802.1X:
Router(config)# dot1x system-auth-controlRouter(config)#This example shows how to disable 802.1X:
Router(config)# no dot1x system-auth-controlRouter(config)#Related Commands
aaa authentication dot1x (refer to the Cisco IOS Release 12.1 Command Reference)
aaa new-model (refer to the Cisco IOS Release 12.1 Command Reference)
show dot1xdot1x timeout
To set the reauthentication timer, use the dot1x timeout command. Use the no form of this command to return to the default settings.
dot1x timeout {{reauth-period seconds} | {quiet-period seconds} | {tx-period seconds} | {supp-timeout seconds} | {server-timeout seconds}}
no dot1x timeout {reauth-period | quiet-period | tx-period | supp-timeout | server-timeout}
Syntax Description
Defaults
The defaults are as follows:
•
•
•
•
•
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
You must enable periodic reauthentication before you enter the dot1x timeout reauth-period command. Enter the dot1x reauthentication command to enable periodic reauthentication. The dot1x timeout reauth-period command affects the behavior of the system only if periodic reauthentication is enabled.
Examples
This example shows how to set the number of seconds between reauthentication attempts to 4000:
Router(config-if)# dot1x timeout reauth-period 4000Router(config-if)#This example shows how to set the quiet time on the system to 30 seconds:
Router(config-if)# dot1x timeout quiet-period 30Router(config-if)#This example shows how to set 60 as the number of seconds to wait for a response to an EAP-request/identity frame from the client before retransmitting the request:
Router(config-if)# dot1x timeout tx-period 60Router(config-if)#This example shows how to set the system-to-client retransmission time for the EAP-request frame to 25 seconds:
Router(config-if)# dot1x timeout supp-timeout 25Router(config-if)#This example shows how to set the system-to-authentication-server retransmission time for transport layer packets to 25 seconds:
Router(config-if)# dot1x timeout server-timeout 25Router(config-if)#This example shows how to return to the default reauthorization period:
Router(config-if)# no dot1x timeout reauth-periodRouter(config-if)#Related Commands
dot1x reauthentication
show dot1xduplex
To configure the duplex operation on an interface, use the duplex command. Use the no form of this command to return the system to half-duplex mode.
duplex {full | half}
no duplex
Syntax Description
Defaults
Half-duplex mode
Command Modes
Interface configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Table 2-6 lists the supported command options by interface.
If the transmission speed on a 16-port RJ-45 Gigabit Ethernet port is set to 1000, the duplex mode is set to full. If the transmission speed is changed to 10 or 100, the duplex mode stays at half duplex. You must configure the correct duplex mode when the transmission speed is changed to 10 or 100 from 1000.
Gigabit Ethernet is full duplex only. You cannot change the duplex mode on Gigabit Ethernet ports or on a 10/100/1000-Mps port configured for Gigabit Ethernet.
When manually configuring the interface speed to either 10 or 100 Mbps, you should also configure duplex mode on the interface.
Note
Caution
Table 2-7 describes the relationship and the results for the different combinations of the duplex and speed commands.
Examples
This example shows how to configure the interface for full-duplex operation:
Router(config-if)# duplex fullRouter(config-if)#Related Commands
interface (refer to the Cisco IOS Release 12.1 Command Reference)
show controllers (refer to the Cisco IOS Release 12.1 Command Reference)
show interfaces (refer to the Cisco IOS Release 12.1 Command Reference)
speed
