-
Cisco ASA Series Command Reference
-
About this Guide
-
Using the Command Line Interface
- A through B Commands
-
C Commands
-
cache -- clear compression
-
clear configure -- clear configure http
-
clear configure flow-export-- clear configure zonelabs-integrity
-
clear conn -- clear isakmp sa
-
clear local-host -- clear xlate
-
client-access-rule -- crl-configure
-
crypto ca authenticate -- crypto ipsec ikev1 transform-set mode transport
-
crypto isakmp disconnect-notify -- cxsc auth-proxy port
-
-
D through F Commands
-
database path -- debug cxsc
-
debug dap -- debug http-map
-
debug icmp -- debug ospfv3
-
debug parser cache -- debug xml
-
default -- dhcp-server
-
dhcpd address -- distribute-list out
-
dns domain-lookup -- dynamic-filter whitelist
-
eigrp log-neighbor-changes -- export webvpn webcontent
-
failover -- fallback
-
file-bookmarks -- functions
-
- G through I Commands
- J through L Commands
- M through O Commands
- P through R Commands
-
S Commands
-
same-security-traffic -- shape
-
show aaa kerberos -- show asdm sessions
-
show asp cluster counter -- show asp table vpn-context
-
show blocks -- show cpu
-
show crashinfo -- show curpriv
-
show ddns update interface -- show environment
-
show failover -- show ipsec stats traffic
-
show ipv6 access-list -- show ipv6
-
show isakmp ipsec-over-tcp stats -- show ospf virtual-links
-
show nac-policy -- show ospf virtual-links
-
show pager -- show route
-
show running-config -- show running-config ctl-provider
-
show running-config ddns -- show running-config isakmp
-
show running-config ipv6 router -- show running-config router
-
show running-config same-security-traffic -- show running-config xlate
-
show scansafe -- show switch vlan
-
show tcpstat -- show traffic
-
show uauth -- show xlate
-
shun -- snmp-server user
-
software-version -- storage-objects
-
subject-name -- sysopt radius ignore-secret
-
- T through Z Commands
-
Cisco IOS Commands for the ASASM
-
Feedback
Table Of Contents
debug dap through debug http-map Commands
debug dap through debug http-map Commands
debug dap
To enable logging of Dynamic Access Policy events, use the debug dap command in privileged EXEC mode. To disable the logging of DAP debugging messages, use the no form of this command.
debug dap {errors | trace}
no debug dap {errors | trace}
Syntax Description
Defaults
No default value or behaviors.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
—
Command History
Usage Guidelines
The high priority assigned to debugging output 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 DAP trace debugging:
hostname #debug dap tracehostname #Related Commands
debug ddns
To show debugging messages for DDNS, use the debug ddns command in privileged EXEC mode. To disable debugging messages, use the no form of this command.
debug ddns
no debug ddns
Syntax Description
This command has no arguments or keywords.
Defaults
The 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
The debug ddns command displays detailed information about DDNS. The undebug ddns command and the no debug ddns command turn off DDNS debugging 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 an example of enabling DDNS debugging messages:
hostname# debug ddnsdebug ddns enabled at level 1Related 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 debugging level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
This command displays DHCP client debugging 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.
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 an example of enabling DHCP event debugging:
hostname# debug dhcpd eventdebug dhcpd event enabled at level 1Related Commands
show dhcpd
Displays DHCP binding, statistical, or state information.
show running-config dhcpd
Displays the current DHCP server configuration.
debug dhcpd ddns
To enable debugging of the DHCP DDNS, use the debug dhcpd ddns command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug dhcpd ddns [level]
no debug dhcpd ddns [level]
Syntax Description
Defaults
The default debugging 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 ddns command displays detailed information about DHCP and DDNS. The undebug dhcpd ddns command and the no debug dhcpd ddns command turn off DHCP and DDNS debugging 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 DHCP DDNS debugging being enabled:
hostname# debug dhcpd ddnsdebug dhcpd ddns enabled at level 1Related Commands
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 debugging information, use the debug disk command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug disk {file | file-verbose | filesystem} [level]
no debug disk {file | file-verbose | filesystem}
Syntax Description
Defaults
The default value for the debugging 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 is sample output from the debug disk and the show debug commands:
hostname# debug disk filedebug disk file enabled at level 1hostname# show debugdebug vpn-sessiondb enabled at level 1hostname# dirIFS: Opening: file flash:/, flags 1, mode 0IFS: Opened: file flash:/ as fd 3IFS: Getdent: fd 3IFS: Getdent: fd 3IFS: Getdent: fd 3IFS: Getdent: fd 3Directory of flash:/IFS: Close: fd 3IFS: Opening: file flash:/, flags 1, mode 04 -rw- 5124096 14:42:27 Apr 04 2005 cdisk.binIFS: Opened: file flash:/ as fd 39 -rw- 5919340 14:53:39 Apr 04 2005 ASDMIFS: Getdent: fd 311 drw- 0 15:18:56 Apr 21 2005 syslogIFS: Getdent: fd 3IFS: Getdent: fd 3IFS: Getdent: fd 3IFS: Close: fd 316128000 bytes total (5047296 bytes free)Related Commands
debug dns
To show debugging messages for DNS, use the debug dns command in privileged EXEC mode. To stop showing debugging messages for DNS, use the no form of this command.
debug dns [resolver | all] [level]
no debug dns [resolver | all] [level]
Syntax Description
Defaults
The default level is 1. If you do not specify any keywords, the ASA shows all mesages.
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 debugging messages for DNS:
hostname# debug dnsRelated Commands
debug eap
To enable logging of EAP events to debug NAC messaging, use the debug eap command in privileged EXEC mode. To disable the logging of EAP debugging messages, use the no form of this command.
debug eap {all | errors | events | packets | sm}
no debug eap {all | errors | events | packets | sm}
Syntax Description
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
When you use this command, the ASA records EAP session state changes and EAP status query events, and generates a complete record of EAP and packet contents in hexadecimal format.
The high priority assigned to debugging output 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 the logging of all EAP session events:
hostname# debug eap eventshostname#The following example enables the logging of all EAP debugging messages:
hostname# debug eap allhostname#The following example disables the logging of all EAP debugging messages:
hostname# no debug eaphostname#Related Commands
debug eigrp fsm
To display debugging information the DUAL finite state machine, use the debug eigrp fsm command in privileged EXEC mode. To disable the debugging information display, use the no form of this command.
debug eigrp fsm
no debug eigrp fsm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
This command lets you observe EIGRP feasible successor activity and to determine whether or not route updates are being installed and deleted by the routing process.
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 TAC. 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 is sample output from the debug eigrp fsm command:
hostname# debug eigrp fsmDUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 4294967295 foundDUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/4294967295DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0In the fist line, DUAL stands for diffusing update algorithm. It is the basic mechanism within EIGRP that makes the routing decisions. The next three fields are the Internet address, mask of the destination network, and the address through which the update was received. The metric field shows the metric stored in the routing table and the metric advertised by the neighbor sending the information. If shown, the term "Metric... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in a hold-down state.
In the following output, EIGRP is attempting to find a feasible successor for the destination. Feasible successors are part of the DUAL loop avoidance methods. The FD field includes more loop avoidance state information. The RD field is the reported distance, which is the metric used in update, query, or reply packets. The indented line with the "not found" message means a feasible successor was not found for 192.168.4.0, and EIGRP must start a diffusing computation. This means it begins to actively probe (sends query packets about destination 192.168.4.0) the network looking for alternate paths to 192.164.4.0.
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295The following output indicates the route DUAL successfully installed into the routing table:
DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0The following output shows that no routes to the destination were discovered and that the route information is being removed from the topology table:
DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0Related Commands
debug eigrp neighbors
To display debugging information for neighbors discovered by EIGRP, use the debug eigrp neighbors command in privileged EXEC mode. To disable the debugging information display, use the no form of this command.
debug eigrp neighbors [siatimer | static]
no debug eigrp neighbors [siatimer | static]
Syntax Description
siatimer
(Optional) Displays EIGRP stuck-in-active (SIA) messages.
static
(Optional) Displays EIGRP static neighbor messages.
Defaults
No default behaviors or values.
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 TAC. 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 is sample output from the debug eigrp neighbors static command. The example shows a static neighbor being added and then removed, and the corresponding debugging messages.
hostname# debug eigrp neighbors staticEIGRP Static Neighbors debugging is onhostname# configure terminalhostname(config) router eigrp 100hostname(config-router)# neighbor 10.86.194.3 interface outsidehostname(config-router)#EIGRP: Multicast Hello is disabled on Ethernet0/0!EIGRP: Add new static nbr 10.86.194.3 to AS 100 Ethernet0/0hostname(config-router)# no neighbor 10.86.194.3 interface outsidehostname(config-router)#EIGRP: Static nbr 10.86.194.3 not in AS 100 Ethernet0/0 dynamic listEIGRP: Delete static nbr 10.86.194.3 from AS 100 Ethernet0/0EIGRP: Multicast Hello is enabled on Ethernet0/0!hostname(config-router)# no debug eigrp neighbors staticEIGRP Static Neighbors debugging is offRelated Commands
neighbor
Defines an EIGRP neighbor.
show eigrp neighbors
Displays the EIGRP neighbor table.
debug eigrp packets
To display debugging information for EIGRP packets, use the debug eigrp packets command in privileged EXEC mode. To disable the debugging information display, use the no form of this command.
debug eigrp packets [SIAquery | SIAreply | ack | hello | probe | query | reply | request | retry | stub | terse | update | verbose]
no debug eigrp packets [SIAquery | SIAreply | ack | hello | probe | query | reply | request | retry | stub | terse | update | verbose]
Syntax Description
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
You can specify more than one packet type in a single command, for example:
hostname# debug eigrp packets query replyBecause 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 TAC. 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 is sample output from the debug eigrp packets command:
hostname# debug eigrp packetsEIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x1, Seq 1, Ack 0EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x0, Seq 2, Ack 0The output shows the transmission and receipt of EIGRP packets. The sequence and acknowledgment numbers used by the EIGRP reliable transport algorithm are shown in the output. Where applicable, the network-layer address of the neighboring router is also included.
Related Commands
debug eigrp transmit
To display transmission messages sent by EIGRP, use the debug eigrp transmit command in privileged EXEC mode. To disable the debugging information display, use the no form of this command.
debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
no debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
Syntax Description
Defaults
If at least one transmission event is not specified, all transmission events are shown in the debugging output.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
—
•
•
—
Command History
Usage Guidelines
You can specify more than one transmission event in a single command, For example:
hostname# debug eigrp ack build linkBecause 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 TAC. 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 is sample output from the debug eigrp transmit command. The example shows a network command being entered and the transmission event debugging message that is generated.
hostname# debug eigrp transmitEIGRP Transmission Events debugging is on(ACK, PACKETIZE, STARTUP, PEERDOWN, LINK, BUILD, STRANGE, SIA, DETAIL)hostname# configure terminalhostname(config)# router eigrp 100hostname(config-router)# network 10.86.194.0 255.255.255.0DNDB UPDATE 10.86.194.0 255.255.255.0, serno 0 to 1, refcount 0hostname(config-router)# no debug eigrp transmitEIGRP Transmission Events debugging is offRelated Commands
debug eigrp user-interface
To display debugging information for EIGRP user events, use the debug eigrp user-interface command in privileged EXEC mode. To disable the debugging information display, use the no form of this command.
debug eigrp user-interface
no debug eigrp user-interface
Syntax Description
This command has no arguments or keywords.
Defaults
No default behaviors or values.
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 TAC. 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 is sample output from the debug eigrp user-interface command. The output is caused by an administrator removing a passive-interface command from an EIGRP configuration.
hostname# debug eigrp user-interfaceEIGRP UI Events debugging is onhostname# configure terminalhostname(config) router eigrp 100hostname(config-router)# no passive-interface insideCSB2AF: FOUND (AS=100, Name=, VRF=0, AFI=ipv4)hostname(config-router)# no debug eigrp user-interfaceEIGRP UI Events debugging is offRelated Commands
router eigrp
Enables an EIGRP routing process and enters router configuration mode.
show running-config eigrp
Displays the EIGRP commands in the running configuration.
debug email
To display e-mail debugging information, use the debug email command in privileged EXEC mode. To disable the display of e-mail debugging information, use the no form of this command.
debug email [level]
no debug email [level]
Syntax Description
Defaults
The default value for the debugging 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 is sample output from the debug email and the show debug email commands:
hostname# debug emaildebug email enabled at level 1hostname# show debug emaildebug email enabled at level 1Related Commands
debug entity
To display MIB debugging information, use the debug entity command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug entity [level]
no debug entity
Syntax Description
level
(Optional) Sets the debugging 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 the debugging 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 enables MIB debugging messages. The show debug command indicates that MIB debugging messages are enabled.
hostname# debug entitydebug entity enabled at level 1hostname# show debugdebug entity enabled at level 1hostname#Related Commands
debug eou
To enable logging of EAPoUDP events to debug NAC messaging, use the debug eou command in privileged EXEC mode. To disable the logging of EAPoUDP debugging messages, use the no form of this command.
debug eou {all | eap | errors | events | packets | sm}
no debug eou [all | eap | errors | events | packets | sm]
Syntax Description
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
When you use this command, the ASA records EAPoUDP session state changes and timer events, and generates a complete record of EAPoUDP header and packet contents in hexadecimal format.
The high priority assigned to debugging output 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 the logging of all EAPoUDP session events:
hostname# debug eou eventshostname#The following example enables the logging of all EAPoUDP debugging messages:
hostname# debug eou allhostname#The following example disables the logging of all EAPoUDP debugging messages:
hostname# no debug eouhostname#Related Commands
debug esmtp
To show debugging messages for SMTP/ESMTP application inspection, use the debug esmtp command in privileged EXEC mode. To stop showing debugging messages for SMTP/ESMTP application inspection, use the no form of this command.
debug esmtp [level]
no debug esmtp [level]
Syntax Description
level
(Optional) Sets the debugging 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 the debugging 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 debugging command settings, enter the show debug command. To stop the debugging output, enter the no debug command. To stop all debugging messages from being displayed, enter the no debug all command.
Note
Examples
The following example enables debugging messages at the default level (1) for SMTP/ESMTP application inspection:
hostname# debug esmtpRelated Commands
debug etherchannel
To display EtherChannel debugging information, use the debug etherchannel command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug etherchannel [all | error | event]
no debug etherchannel [all | error | event]
Syntax Description
all
(Optional) Displays all EtherChannel information.
event
(Optional) Displays major EtherChannel events.
error
(Optional) Displays EtherChannel errors.
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
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 EtherChannel debug messages for events. The show debug command indicates that EtherChannel debugging messages are enabled.
hostname# debug etherchannel eventhostname# show debugdebug etherchannel event enabledhostname#Related Commands
debug fixup
To display detailed information about application inspection, use the debug fixup command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug fixup
no debug fixup
Defaults
All options are enabled by default.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
The debug fixup command displays detailed information about application inspection. The no debug all or undebug all command turns off all enabled debug commands.
Examples
The following example enables the display of detailed information about application inspection:
hostname# debug fixupRelated Commands
debug fover
To display failover debug information, use the debug fover command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug fover {cable | cmd-exec | fail | fmsg | ifc | open | rx | rxdmp | rxip | switch | sync | tx | txdmp | txip | verify}
no debug fover {cable | fail | fmsg | ifc | open | rx | rxdmp | rxip | switch | sync | tx | txdmp | txip | verify}
Syntax Description
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
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 TAC. 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 is sample output from the debug fover cmd-exec command. After debugging is enabled, a failover exec command is entered. The results of the failover exec command are shown after the debugging output.
hostname(config)# debug fover cmd-execfover event trace onhostname(config)# failover exec mate show running-config failoverci/console: Sending cmd: show runn failovero to peer for execution, seq = 4ci/console: frep_execv_cmd: replicating exec cmd: show runn failover...fover_parse: Fover rexec response: seq=4, size=228, data="fail..."ci/console: Fover rexec waiting at clock tick 2670960fover_parse: Fover rexec ack: seq = 4, ret_val = 0ci/console: Fover rexec conteinuer at clock tick: 2671040ci/console: Fover exec succeeded, seq = 5failoverfailover lan interface failover GigabitEthernet0/3failover polltime unit 1 holdtime 3failover key *****failover link failover GigabitEthernet0/3failover interface ip failover 10.0.5.1 255.255.255.0 standby 10.0.5.2ciscoasa(config)#Related Commands
show failover
Displays information about the failover configuration and operational statistics.
debug fsm
To display FSM debugging information, use the debug fsm command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug fsm [level]
no debug fsm
Syntax Description
level
(Optional) Sets the debugging 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 the debugging 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 enables FSM debugging messages. The show debug command indicates that FSM debugging messages are enabled.
hostname# debug fsmdebug fsm enabled at level 1hostname# show debugdebug fsm enabled at level 1hostname#Related Commands
debug ftp client
To show debugging messages for FTP, use the debug ftp client command in privileged EXEC mode. To disable the display of debugging messages for FTP, use the no form of this command.
debug ftp client [level]
no debug ftp client [level]
Syntax Description
level
(Optional) Sets the level to display debugging messages. The range of values is between 1 and 255. To display additional messages at higher levels, set the level to a higher number.
Defaults
The default value for the debugging 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 debugging command settings, enter the show debug command. To disable the debugging message output, enter the no debug command. To stop all debugging messages from being displayed, enter the no debug all command.
Note
Examples
The following example enables debugging messages at the default level (1) for FTP:
hostname# debug ftp clientRelated Commands
debug generic
To display miscellaneous debugging information, use the debug generic command in privileged EXEC mode. To disable the display of miscellaneous debugging information, use the no form of this command.
debug generic [level]
no debug generic
Syntax Description
level
(Optional) Sets the debugging 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 the debugging 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 enables miscellaneous debug messages. The show debug command indicates that miscellaneous debugging messages are enabled.
hostname# debug genericdebug generic enabled at level 1hostname# show debugdebug generic enabled at level 1hostname#Related Commands
debug gtp
To display detailed information about GTP inspection, use the debug gtp command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug gtp {error | event | ha | parser}
no debug gtp {error | event | ha | parser}
Syntax Description
Defaults
All options are enabled by default.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
The debug gtp command displays detailed information about GTP inspection. The no debug all or undebug all command turns off all enabled debug commands.
Note
Examples
The following example enables the display of detailed information about GTP inspection:
hostname# debug gtpRelated Commands
debug h323
To show debugging messages for H.323, use the debug h323 command in privileged EXEC mode. To stop showing debugging messages for H.323, use the no form of this command.
debug h323 {h225 | h245 | ras} [asn | event]
no debug h323 {h225 | h245 | ras} [asn | event]
Syntax Description
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
To see the current debugging command settings, enter the show debug command. To stop the debugging output, enter the no debug command. To stop all debugging messages from being displayed, enter the no debug all command.
Note
Examples
The following example enables debugging messages at the default level (1) for H.225 signaling:
hostname# debug h323 h225Related Commands
debug http
To display detailed information about HTTP traffic, use the debug http command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug http [ level ]
no debug http [ level ]
Syntax Description
level
(Optional) Sets the debugging 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 for the debugging 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 http command displays detailed information about HTTP traffic. The no debug all or undebug all command turns off all enabled debug commands.
Examples
The following example enables the display of detailed information about HTTP traffic:
hostname# debug httpRelated Commands
debug http-map
To show debugging messages for HTTP application inspection maps, use the debug http-map command in privileged EXEC mode. To stop showing debugging messages for HTTP application inspection, use the no form of this command.
debug http-map
no debug http-map
Defaults
The default value for the debugging 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 debugging command settings, enter the show debug command. To stop the debugging output, enter the no debug command. To stop all debugging messages from being displayed, enter the no debug all command.
Note
Examples
The following example enables debugging messages at the default level (1) for HTTP application inspection:
hostname# debug http-mapRelated Commands
