Table Of Contents
D through F Commands
debug aaa
To show debug messages for AAA, use the debug aaa command in privileged EXEC mode. To stop showing AAA messages, use the no form of this command.
debug aaa [ accounting | authentication | authorization | internal | vpn [ level ] ]
no debug aaa
Syntax Description
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
•
Command History
Usage Guidelines
The debug aaa command displays detailed information about AAA activity. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables debugging for AAA functions supported by the local database:
hostname(config)# debug aaa internaldebug aaa internal enabled at level 1hostname(config)# uap allocated. remote address: 10.42.15.172, Session_id: 2147483841uap freed for user . remote address: 10.42.15.172, session id: 2147483841Related Commands
debug arp
To show debug messages for ARP, use the debug arp command in privileged EXEC mode. To stop showing debug messages for ARP, use the no form of this command.
debug arp
no debug arp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ARP:
hostname# debug arpRelated Commands
arp
Adds a static ARP entry.
show arp statistics
Shows ARP statistics.
show debug
Shows all enabled debuggers.
debug arp-inspection
To show debug messages for ARP inspection, use the debug arp-inspection command in privileged EXEC mode. To stop showing debug messages for ARP inspection, use the no form of this command.
debug arp-inspection
no debug arp-inspection
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
—
•
•
•
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ARP inspection:
hostname# debug arp-inspectionRelated Commands
arp
Adds a static ARP entry.
arp-inspection
For transparent firewall mode, inspects ARP packets to prevent ARP spoofing.
show debug
Shows all enabled debuggers.
debug asdm history
To view debug information for ASDM, use the debug asdm history command in privileged EXEC mode.
debug asdm history level
Syntax Description
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
•
Command History
7.0
This command was changed from the debug pdm history command to the debug asdm history command.
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following example enables level 1 debugging of ASDM:
hostname# debug asdm historydebug asdm history enabled at level 1hostname#Related Commands
debug cmgr
To show debug messages about the SSM card manager, use the debug cmgr command in privileged EXEC mode. To stop showing debug messages for the card manager, use the no form of this command.
debug cmgr [level]
no debug cmgr [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
•
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for the card manager:
hostname# debug cmgrRelated Commands
debug context
To show debug messages when you add or delete a security context, use the debug context command in privileged EXEC mode. To stop showing debug messages for contexts, use the no form of this command.
debug context [level]
no debug context [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
—
—
•
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for context management:
hostname# debug contextRelated Commands
debug cplane
To show debug messages about the control plane that connects internally to an SSM, use the debug cplane command in privileged EXEC mode. To stop showing debug messages for the control plane, use the no form of this command.
debug cplane [level]
no debug cplane [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
•
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for the control plane:
hostname# debug cplaneRelated Commands
debug crypto ca
To show debug messages for PKI activity (used with CAs), use the debug crypto ca command in privileged EXEC mode. To stop showing debug messages for PKI, use the no form of this command.
debug crypto ca [messages | transactions] [level]
no debug crypto ca [messages | transactions] [level]
Syntax Description
Defaults
By default, this command shows all debug messages. The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for PKI:
hostname# debug crypto caRelated Commands
debug crypto engine
Shows debug messages for the crypto engine.
debug crypto ipsec
Shows debug messages for IPSec.
debug crypto isakmp
Shows debug messages for ISAKMP.
debug crypto engine
To show debug messages for the crypto engine, use the debug crypto engine command in privileged EXEC mode. To stop showing debug messages for the crypto engine, use the no form of this command.
debug crypto engine [level]
no debug crypto engine [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for the crypto engine:
hostname# debug crypto engineRelated Commands
debug crypto ca
Shows debug messages for the CA.
debug crypto ipsec
Shows debug messages for IPSec.
debug crypto isakmp
Shows debug messages for ISAKMP.
debug crypto ipsec
To show debug messages for IPSec, use the debug crypto ipsec command in privileged EXEC mode. To stop showing debug messages for IPSec, use the no form of this command.
debug crypto ipsec [level]
no debug crypto ipsec [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for IPSec:
hostname# debug crypto ipsecRelated Commands
debug crypto ca
Shows debug messages for the CA.
debug crypto engine
Shows debug messages for the crypto engine.
debug crypto isakmp
Shows debug messages for ISAKMP.
debug crypto isakmp
To show debug messages for ISAKMP, use the debug crypto isakmp command in privileged EXEC mode. To stop showing debug messages for ISAKMP, use the no form of this command.
debug crypto isakmp [timers] [level]
no debug crypto isakmp [timers] [level]
Syntax Description
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
—
Command History
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ISAKMP:
hostname# debug crypto isakmpRelated Commands
debug crypto ca
Shows debug messages for the CA.
debug crypto engine
Shows debug messages for the crypto engine.
debug crypto ipsec
Shows debug messages for IPSec.
debug ctiqbe
To show debug messages for CTIQBE application inspection, use the debug ctiqbe command in privileged EXEC mode. To stop showing debug messages for CTIQBE application inspection, use the no form of this command.
debug ctiqbe [level]
no debug ctiqbe [level]
Syntax Description
level
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default value for level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
To see the current debug command settings, enter the show debug command. To stop the debug output, enter the no debug command. To stop all debug messages from being displayed, enter the no debug all command.
Note
Examples
The following example enables debug messages at the default level (1) for CTIQBE application inspection:
hostname# debug ctiqbeRelated Commands
debug dhcpc
To enable debugging of the DHCP client, use the debug dhcpc command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug dhcpc {detail | packet | error} [level]
no debug dhcpc {detail | packet | error} [level]
Syntax Description
Defaults
The default debug level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
Displays DHCP client debug information.
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following example shows how to enable debugging for the DHCP client:
hostname# debug dhcpc detail 5debug dhcpc detail enabled at level 5Related Commands
debug dhcpd
To enable debugging of the DHCP server, use the debug dhcpd command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug dhcpd {event | packet} [level]
no debug dhcpd {event | packet} [level]
Syntax Description
Defaults
The default debug level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
The debug dhcpd event command displays event information about the DHCP server. The debug dhcpd packet command displays packet information about the DHCP server.
Use the no form of the debug dhcpd commands to disable debugging.
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following shows an example of enabling DHCP event debugging:
hostname# debug dhcpd eventdebug dhcpd event enabled at level 1Related Commands
show dhcpd
Displays DHCP binding, statistic, or state information.
show running-config dhcpd
Displays the current DHCP server configuration.
debug dhcprelay
To enable debugging of the DHCP relay server, use the debug dhcpreleay command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug dhcprelay {event | packet | error} [level]
no debug dhcprelay {event | packet | error} [level]
Syntax Description
Defaults
The default debug level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following example shows how to enable debugging for DHCP relay agent error messages:
hostname# debug dhcprelay errordebug dhcprelay error enabled at level 1Related Commands
debug disk
To display file system debug information, use the debug disk command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug disk {file | file-verbose | filesystem} [level]
no debug disk {file | file-verbose | filesystem}
Syntax Description
