-
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Command Reference, 4.0
-
About This Guide
-
Using the Command Line Interface
- A through B Commands
- C Commands
- D through F Commands
- G through I Commands
- J through L Commands
- M through O Commands
- P though R Commands
-
S Commands
-
same-security-traffic -- show asdm sessions
-
show asp drop -- show curpriv
-
show debug -- show ipv6 traffic
-
show isakmp sa -- show route
-
show running-config -- show running-config isakmp
-
show running-config logging -- show running-config vpn-sessiondb
-
show service-policy -- show xlate
-
shun -- sysopt uauth allow-http-cache
-
- T through Z Commands
-
Feedback
Table Of Contents
debug aaa through debug sip Commands
debug aaa through debug sip 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 acl optimization
To show debug messages for access list optimization, use the debug acl optimization command in privileged EXEC mode. To stop showing access list optimization messages, use the no form of this command.
debug optimization
no debug optimization
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
The debug acl optimization command displays detailed information about access list optimization activity. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables debugging for access list optimization functions:
hostname(config)# debug acl optimizationcontext 0 :: access-list test :: start time = 11:38:38, end time = 11:38:40, total time = 2.231 secRelated Commands
debug appfw
To display detailed information about application inspection, use the debug appfw command in privileged EXEC mode. To disable debugging, Use the no form of this command.
debug appfw [chunk | event | eventverb | regex]
no debug appfw [chunk | event | eventverb | regex]
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 appfw command displays detailed information about HTTP application inspection. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed information about application inspection:
hostname# debug appfwRelated Commands
http-map
Defines an HTTP map for configuring enhanced HTTP inspection.
inspect http
Applies a specific HTTP map to use for application inspection.
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
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 example enables debug messages for ARP:
hostname# debug arpRelated Commands
show debug
Shows all enabled debuggers.
arp
Adds a static ARP entry.
show arp statistics
Shows ARP statistics.
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
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 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
1.1(1)
This command was introduced (as debug pdm history).
3.1(1)
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 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 example enables level 1 debugging of ASDM:
hostname# debug asdm historydebug asdm history enabled at level 1hostname#Related 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
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 example enables debug messages for context management:
hostname# debug contextRelated Commands
debug control-plane
To show debug messages for the control plane, use the debug control-plane command in privileged EXEC mode. To stop showing debug messages for the control-plane, use the no form of this command.
debug control-plane {egress | gc | ingress | tcp | tlv | udp | xlate} [level]
no debug control-plane {egress | gc | ingress | tcp | tlv | udp | xlate} [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
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 example enables debug messages for TCP packets:
hostname# debug control-plane tcpRelated 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
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 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
1.1(1)
This command was introduced.
3.1(1)
This command was changed from debug.
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 dcerpc
To display detailed information about DCERPC traffic, use the debug dcerpc command in privileged EXEC mode. To disable debugging, Use the no form of this command.
debug dcerpc [ packet | error | event ]
no debug dcerpc [ packet | error | 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
The debug dcerpc command displays detailed information about DCERPC traffic. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed information about DCERPC traffic:
hostname# debug dcerpcRelated Commands
inspect dcerpc
Configures DCERPC inspection parameters.
dcerpc-map
Defines a DCERPC inspection map for DCERPC application inspection.
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
1.1(1)
This command was introduced.
3.1(1)
This command was changed from debug.
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 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 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
1.1(1)
This command was introduced.
3.1(1)
This command was changed from debug.
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 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 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
1.1(1)
This command was introduced.
3.1(1)
This command was changed from debug.
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 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
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
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 file-level disk debug messages. The show debug command reveals that file-level disk debug messages are enabled. The dir command causes several debug messages.
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 debug messages for DNS, use the debug dns command in privileged EXEC mode. To stop showing debug messages for DNS, use the no form of this command.
debug dns [resolver | all] [level]
no debug dns ]
Syntax Description
Defaults
The default level is 1. If you do not specify any keywords, the FWSM shows all messages.
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 DNS:
hostname# debug dnsRelated Commands
debug eigrp fsm
To display debug information the DUAL finite state machine, use the debug eigrp fsm command in privileged EXEC mode. To disable the debug 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 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 and 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 contains 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 debug information for neighbors discovered by EIGRP, use the debug eigrp neighbors command in privileged EXEC mode. To disable the debug 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 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 debug 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 debug information for EIGRP packets, use the debug eigrp packets command in privileged EXEC mode. To disable the debug 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:
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 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 transmittal messages sent by EIGRP, use the debug eigrp transmit command in privileged EXEC mode. To disable the debug 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 transmittal event is not specified, all transmittal events are shown in the debug 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 transmittal 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 transmittal event debug 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 debug information for EIGRP user events, use the debug eigrp user-interface command in privileged EXEC mode. To disable the debug 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 entity
To display management information base (MIB) debug information, use the debug entity command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug entity [level]
no debug entity
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
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 debug messages. The show debug command reveals that MIB debug messages are enabled.
hostname# debug entitydebug entity enabled at level 1hostname# show debugdebug entity enabled at level 1hostname#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 {onat | tcp | udp} [level]
no debug fixup
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 fixup command displays detailed information about application inspection. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed TCP-related information:
hostname# debug fixup tcpRelated 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 | 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
1.1(1)
This command was introduced.
3.1(1)
This command was modified. It includes additional debug keywords.
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 example shows how to display debug information for failover command replication:
hostname# debug fover syncfover event trace onRelated Commands
show failover
Displays information about the failover configuration and operational statistics.
debug fsm
To display FSM debug information, use the debug fsm command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug fsm [level]
no debug fsm
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
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 example enables FSM debug messages. The show debug command reveals that FSM debug 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 debug messages for FTP, use the debug ftp client command in privileged EXEC mode. To stop showing debug 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 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 FTP:
hostname# debug ftp clientRelated Commands
debug generic
To display miscellaneous debug information, use the debug generic command in privileged EXEC mode. To disable the display of miscellaneous debug information, use the no form of this command.
debug generic [level]
no debug generic
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
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 example enables miscellaneous debug messages. The show debug command reveals that miscellaneous debug 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 commands turn off all enabled debugs.
Note
Examples
The following example enables the display of detailed information about GTP inspection:
hostname# debug gtpRelated Commands
debug h323
To show debug messages for H.323, use the debug h323 command in privileged EXEC mode. To stop showing debug messages for H.323, use the no form of this command.
debug h323 {gup | h225 | h245 | ras} [asn | event]
no debug h323 {gup | 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 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 is sample output when debug messages are enabled 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 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 defafult 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
The debug http command displays detailed information about HTTP traffic. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed information about HTTP traffic:
hostname# debug httpRelated Commands
http
Specifies hosts that can access the HTTP server internal to the FWSM.
http-proxy
Configures an HTTP proxy server.
http server enable
Enables the FWSM HTTP server.
debug http-map
To show debug messages for HTTP application inspection maps, use the debug http-map command in privileged EXEC mode. To stop showing debug messages for HTTP application inspection, use the no form of this command.
debug http-map
no debug http-map
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 HTTP application inspection:
hostname# debug http-mapRelated Commands
debug icmp
To display detailed information about ICMP inspection, use the debug icmp command in privileged EXEC mode. To disable debugging, Use the no form of this command.
debug icmp trace [ level ]
no debug icmp trace [ level ]
Syntax Description
Defaults
All options are enabled.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
The debug icmp command displays detailed information about ICMP inspection. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed information about ICMP inspection:
hostname# debug icmpRelated Commands
debug igmp
To display IGMP debug information, use the debug igmp command in privileged EXEC mode. To stop the display of debug information, use the no form of this command.
debug igmp [group group_id | interface if_name]
no debug igmp [group group_id | interface if_name]
Syntax Description
group group_id
Displays IGMP debug information for the specified group.
interface if_name
Display IGMP debug information for the specified interface.
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 CiscoTAC. 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 igmp command:
hostname# debug igmpIGMP debugging is onIGMP: Received v2 Query on outside from 192.168.3.2IGMP: Send v2 general Query on dmzIGMP: Received v2 Query on dmz from 192.168.4.1IGMP: Send v2 general Query on outsideIGMP: Received v2 Query on outside from 192.168.3.1IGMP: Send v2 general Query on insideIGMP: Received v2 Query on inside from 192.168.1.1IGMP: Received v2 Report on inside from 192.168.1.6 for 224.1.1.1IGMP: Updating EXCLUDE group timer for 224.1.1.1Related Commands
debug ils
To show debug messages for ILS, use the debug ils command in privileged EXEC mode. To stop showing debug messages for ILS, use the no form of this command.
debug ils [level]
no debug ils [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 ILS application inspection:
hostname# debug ilsRelated Commands
debug imagemgr
To display Image Manager debug information, use the debug imagemgr command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug imagemgr [level]
no debug imagemgr
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
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 Image Manager debug messages. The show debug command reveals that Image Manager debug messages are enabled.
hostname# debug imagemgrdebug imagemgr enabled at level 1hostname# show debugdebug imagemgr enabled at level 1hostname#Related Commands
debug ip bgp
To display debug information for the BGP routing processes, use the debug ip bgp command in privileged EXEC mode. To disable the display of debug information for the BGP routing processes, use the no form of this command.
debug ip bgp
no debug ip bgp
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
•
—
•
•
—
1 This command is only available in the admin context.
Command History
Usage Guidelines
In multiple context mode, this command is only available in the admin context. The admin context must be in routed mode. The BGP stub routing configuration entered in the admin context applies to all contexts configured on the device; you cannot configure BGP stub routing on a per-context basis.
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 ip bgp command:
hostname# debug ip bgpRelated Commands
debug ipsec-over-tcp
To display IPSec-over-TCP debug information, use the debug ipsec-over-tcp command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug ipsec-over-tcp [level]
no debug ipsec-over-tcp
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
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 IPSec-over-TCP debug messages. The show debug command reveals that IPSec-over-TCP debug messages are enabled.
hostname# debug ipsec-over-tcpdebug ipsec-over-tcp enabled at level 1hostname# show debugdebug ipsec-over-tcp enabled at level 1hostname#Related Commands
debug ipv6
To display IPv6 debug messages, use the debug ipv6 command in privileged EXEC mode. To stop the display of debug messages, use the no form of this command.
debug ipv6 {icmp | interface | nd | packet | routing}
no debug ipv6 {icmp | interface | nd | packet | routing}
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 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 ipv6 icmp command:
hostname# debug ipv6 icmp13:28:40:ICMPv6:Received ICMPv6 packet from 2000:0:0:3::2, type 13613:28:45:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 13513:28:50:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 13613:28:55:ICMPv6:Received ICMPv6 packet from FE80::203:A0FF:FED6:1400, type 135Related Commands
debug iua-proxy
To display individual user authentication (IUA) proxy debug information, use the debug iua-proxy command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug iua-proxy [level]
no debug iua-proxy
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
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 example enables IUA-proxy debug messages. The show debug command reveals that IUA-proxy debug messages are enabled.
hostname# debug iua-proxydebug iua-proxy enabled at level 1hostname# show debugdebug iua-proxy enabled at level 1hostname#Related Commands
debug kerberos
To display Kerberos authentication debug information, use the debug kerberos command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug kerberos [level]
no debug kerberos
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
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 example enables Kerberos debug messages. The show debug command reveals that Kerberos debug messages are enabled.
hostname# debug kerberosdebug kerberos enabled at level 1hostname# show debugdebug kerberos enabled at level 1hostname#Related Commands
debug ldap
To display LDAP debug information, use the debug ldap command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug ldap [level]
no debug ldap
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
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 example enables LDAP debug messages. The show debug command reveals that LDAP debug messages are enabled.
hostname# debug ldapdebug ldap enabled at level 1hostname# show debugdebug ldap enabled at level 1hostname#Related Commands
debug mac-address-table
To show debug messages for the MAC address table, use the debug mac-address-table command in privileged EXEC mode. To stop showing debug messages for the MAC address table, use the no form of this command.
debug mac-address-table [level]
no debug mac-address-table [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
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 example enables debug messages for the MAC address table:
hostname# debug mac-address-tableRelated Commands
debug menu
To display detailed debug information for specific features, use the debug menu command in privileged EXEC mode.
debug menu
Caution
Syntax Description
This command should be used only under the supervision of Cisco technical support staff.
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
This command should be used only under the supervision of Cisco technical support staff.
Related Commands
debug mfib
To display MFIB debug information, use the debug mfib command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.
debug mfib {db | init | mrib | pak | ps | signal} [group]
no debug mfib {db | init | mrib | pak | ps | signal} [group]
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 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 displays MFIB dabase operation debug information:
hostname# debug mfib dbMFIB IPv4 db debugging enabledRelated Commands
debug mgcp
To display detailed information about MGCP application inspection, use the debug mgcp command in privileged EXEC mode. To disable debugging, Use the no form of this command.
debug mgcp {messages | parser | sessions}
no debug mgcp {messages | parser | sessions}
messages
Displays debug information about MGCP messages.
parser
Displays debug information for parsing MGCP messages.
sessions
Displays debug information about MGCP sessions.
Defaults
All options are enabled.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
The debug mgcp command displays detailed information about mgcp inspection. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example enables the display of detailed information about MGCP application inspection:
hostname# debug mgcpRelated Commands
debug mrib
To display MRIB debug information, use the debug mrib command in privileged EXEC mode. To stop the display of debug information, use the no form of this command.
debug mrib {client | io | route [group] | table}
no debug mrib {client | io | route [group] | table}
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 CiscoTAC. 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 of MRIB I/O events:
hostname# debug mrib ioIPv4 MRIB io debugging is onRelated Commands
show mrib client
Displays information about the MRIB client connections.
show mrib route
Displays MRIB table entries.
debug ntdomain
To display NT domain authentication debug information, use the debug ntdomain command in privileged EXEC mode. To disable the display of NT domain debug information, use the no form of this command.
debug ntdomain [level]
no debug ntdomain
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
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 example enables NT domain debug messages. The show debug command reveals that NT domain debug messages are enabled.
hostname# debug ntdomaindebug ntdomain enabled at level 1hostname# show debugdebug ntdomain enabled at level 1hostname#Related Commands
debug ospf
To display debug information about the OSPF routing processes, use the debug ospf command in privileged EXEC mode. To disable the display of debug information for the OSPF routing processes, use the no form of the command.
debug ospf [adj | database-timer | events | flood | lsa-generation | packet | retransmission | spf [external | inter | intra] | tree]
no debug ospf [adj | database-timer | events | flood | lsa-generation | packet | retransmission | spf [external | inter | intra] | tree]
Syntax Description
Defaults
Displays all OSPF debug information if no keyword is provided.
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 ospf events command:
hostname# debug ospf eventsospf event debugging is onOSPF:hello with invalid timers on interface Ethernet0hello interval received 10 configured 10net mask received 255.255.255.0 configured 255.255.255.0dead interval received 40 configured 30Related Commands
debug parser cache
To display CLI parser debug information, use the debug parser cache command in privileged EXEC mode. To disable the display of CLI parser debug information, use the no form of this command.
debug parser cache [level]
no debug parser cache
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
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 example enables CLI parser debug messages. The show debug command reveals the current debug configuration. The CLI parser debug messages appear before and after the output of the show debug command.
hostname# debug parser cachedebug parser cache enabled at level 1hostname# show debugparser cache: try to match 'show debug' in exec modedebug parser cache enabled at level 1parser cache: hit at index 8hostname#Related Commands
debug pim
To display PIM debug information, use the debug pim command in privileged EXEC mode. To stop displaying debug information, use the no form of this command.
debug pim [df-election [interface if_name | rp rp] | group group | interface if_name | neighbor]
no debug pim [df-election [interface if_name | rp rp] | group group | interface if_name | neighbor]
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
Logs PIM packets received and transmitted and also PIM-related events.
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 pim command:
hostname# debug pimPIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Received RP-Reachable on Vlan101 from 172.16.20.31PIM: Update RP expiration timer for 224.2.0.1PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0PIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Prune-list (10.221.196.51/32, 224.2.0.1)PIM: Set join delay timer to 2 seconds for (10.221.0.0/16, 224.2.0.1) on Vlan101PIM: Received Join/Prune on Vlan101 from 172.24.37.6PIM: Received Join/Prune on Vlan101 from 172.24.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Join-list: (*, 224.2.0.1) RP 172.16.20.31PIM: Add Tunnel0 to (*, 224.2.0.1), Forward statePIM: Join-list: (10.0.0.0/8, 224.2.0.1)PIM: Add Tunnel0 to (10.0.0.0/8, 224.2.0.1), Forward statePIM: Join-list: (10.4.0.0/16, 224.2.0.1)PIM: Prune-list (172.24.84.16/28, 224.2.0.1) RP-bit set RP 172.24.84.16PIM: Send Prune on Vlan101 to 172.24.37.6 for (172.24.84.16/28, 224.2.0.1), RPPIM: For RP, Prune-list: 10.9.0.0/16PIM: For RP, Prune-list: 10.16.0.0/16PIM: For RP, Prune-list: 10.49.0.0/16PIM: For RP, Prune-list: 10.84.0.0/16PIM: For RP, Prune-list: 10.146.0.0/16PIM: For 10.3.84.1, Join-list: 172.24.84.16/28PIM: Send periodic Join/Prune to RP via 172.24.37.6 (Vlan101)Related Commands
debug pix acl
To show pix acl debug messages, use the debug pix acl command in privileged EXEC mode. To stop showing debug messages, use the no form of this command.
debug pix acl
no debug pix acl
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
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 example enables debug messages:
hostname# debug pix aclRelated Commands
debug pix process
Shows debug messages for xlate and secondary connections processing.
show debug
Shows all enabled debuggers.
debug pix cls
To show pix cls debug messages, use the debug pix cls command in privileged EXEC mode. To stop showing debug messages, use the no form of this command.
debug pix cls
no debug pix cls
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
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 example enables debug messages:
hostname# debug pix clsRelated Commands
debug pix process
Shows debug messages for xlate and secondary connections processing.
show debug
Shows all enabled debuggers.
debug pix pkt2pc
To show debug messages that trace packets sent to the uauth code and that trace the event where the uauth proxy session is cut through to the data path, use the debug pix pkt2pc command in privileged EXEC mode. To stop showing debug messages, use the no form of this command.
debug pix pkt2pc
no debug pix pkt2pc
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
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 debug messages that trace packets sent to the uauth code and that trace the event where the uauth proxy session is cut through to the data path:
hostname# debug pix pkt2pcRelated Commands
debug pix process
Shows debug messages for xlate and secondary connections processing.
show debug
Shows all enabled debuggers.
debug pix process
To show debug messages for xlate and secondary connections processing, use the debug pix process command in privileged EXEC mode. To stop showing debug messages, use the no form of this command.
debug pix process
no debug pix process
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
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 debug messages for xlate and secondary connections processing:
hostname# debug pix processRelated Commands
debug pix uauth
To show pix uauth debug messages, use the debug pix uauth command in privileged EXEC mode. To stop showing debug messages, use the no form of this command.
debug pix uauth
no debug pix uauth
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
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 example enables debug messages that :
hostname# debug pix uauthRelated Commands
debug pix process
Shows debug messages for xlate and secondary connections processing.
show debug
Shows all enabled debuggers.
debug pptp
To show debug messages for PPTP, use the debug pptp command in privileged EXEC mode. To stop showing debug messages for PPTP, use the no form of this command.
debug pptp [level]
no debug pptp [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 PPTP application inspection:
hostname# debug pptpRelated Commands
debug radius
To show debug messages for AAA, use the debug radius command in privileged EXEC mode. To stop showing RADIUS messages, use the no form of this command.
debug radius [ all | decode | session | user username ] ]
no debug radius
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
The debug radius command displays detailed information about RADIUS messaging between the FWSM and a RADIUS AAA server. The no debug all or undebug all commands turn off all enabled debugs.
Examples
The following example shows decoded RADIUS messages, which happen to be accounting packets:
hostname(config)# debug radius decodehostname(config)# RADIUS packet decode (accounting request)--------------------------------------Raw packet data (length = 216).....iParsed packet data.....Radius: Code = 4 (0x04)Radius: Identifier = 105 (0x69)Radius: Length = 216 (0x00D8)Radius: Vector: 842E0E99F44C00C05A0A19AB88A81312Radius: Type = 40 (0x28) Acct-Status-TypeRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x2Radius: Type = 5 (0x05) NAS-PortRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x1Radius: Type = 4 (0x04) NAS-IP-AddressRadius: Length = 6 (0x06)Radius: Value (IP Address) = 10.1.1.1 (0x0A010101)Radius: Type = 14 (0x0E) Login-IP-HostRadius: Length = 6 (0x06)Radius: Value (IP Address) = 10.2.0.50 (0xD0FE1291)Radius: Type = 16 (0x10) Login-TCP-PortRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x50Radius: Type = 44 (0x2C) Acct-Session-IdRadius: Length = 12 (0x0C)Radius: Value (String) =30 78 31 33 30 31 32 39 66 65 | 0x130129feRadius: Type = 1 (0x01) User-NameRadius: Length = 9 (0x09)Radius: Value (String) =62 72 6f 77 73 65 72 | browserRadius: Type = 46 (0x2E) Acct-Session-TimeRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x0Radius: Type = 42 (0x2A) Acct-Input-OctetsRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x256DRadius: Type = 43 (0x2B) Acct-Output-OctetsRadius: Length = 6 (0x06)Radius: Value (Hex) = 0x3E1Radius: Type = 26 (0x1A) Vendor-SpecificRadius: Length = 30 (0x1E)Radius: Vendor ID = 9 (0x00000009)Radius: Type = 1 (0x01) Cisco-AV-pairRadius: Length = 24 (0x18)Radius: Value (String) =69 70 3a 73 6f 75 72 63 65 2d 69 70 3d 31 30 2e | ip:source-ip=10.31 2e 31 2e 31 30 | 1.1.10Radius: Type = 26 (0x1A) Vendor-SpecificRadius: Length = 27 (0x1B)Radius: Vendor ID = 9 (0x00000009)Radius: Type = 1 (0x01) Cisco-AV-pairRadius: Length = 21 (0x15)Radius: Value (String) =69 70 3a 73 6f 75 72 63 65 2d 70 6f 72 74 3d 33 | ip:source-port=334 31 33 | 413Radius: Type = 26 (0x1A) Vendor-SpecificRadius: Length = 40 (0x28)Radius: Vendor ID = 9 (0x00000009)Radius: Type = 1 (0x01) Cisco-AV-pairRadius: Length = 34 (0x22)Radius: Value (String) =69 70 3a 64 65 73 74 69 6e 61 74 69 6f 6e 2d 69 | ip:destination-i70 3d 32 30 38 2e 32 35 34 2e 31 38 2e 31 34 35 | p=10.2.0.50Radius: Type = 26 (0x1A) Vendor-SpecificRadius: Length = 30 (0x1E)Radius: Vendor ID = 9 (0x00000009)Radius: Type = 1 (0x01) Cisco-AV-pairRadius: Length = 24 (0x18)Radius: Value (String) =69 70 3a 64 65 73 74 69 6e 61 74 69 6f 6e 2d 70 | ip:destination-p6f 72 74 3d 38 30 | ort=80Related Commands
debug route-inject
To enable debugging of the route-injections that have been configured on FWSM, use the debug route-inject command in global configuration mode.
debug route-inject
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:
Global configuration
•
—
•
•
—
Command History
Usage Guidelines
The debug route-inject command allows you debug the route-injections that have been configured on FWSM.
Examples
The following is sample output from the debug route-inject command:
hostname(config)# debug route-injecthostname(config)# route-injecthostname(config-route-inject)# redistribute connected interface blah31route_inject_walk_routes_type: operation inject, context single_vf (0), type connectedchecking: ip 10.94.180.0, mask 255.255.255.0, gw 10.94.180.35, proto 15, weight 1, vlan 31, SysIP 31.1.1.1hostname(config-route-inject)# match 1, injected 0, send_update 1, advertise 1add: ip 10.94.180.0, mask 255.255.255.0, gw 10.94.180.35, proto 15, weight 1, vlan 31, SysIP 31.1.1.1 checking: ip 20.1.1.0, mask 255.255.255.0, gw 20.1.1.1, proto 15, weight 1, vlan 31, SysIP 31.1.1.1 operation inject, match 1, injected 0, send_update 1, advertise 1add: ip 20.1.1.0, mask 255.255.255.0, gw 20.1.1.1, proto 15, weight 1, vlan 31, SysIP 31.1.1.1FWSM(config-route-inject)#Related Commands
debug rtsp
To show debug messages for RTSP application inspection, use the debug rtsp command in privileged EXEC mode. To stop showing debug messages for RTSP application inspection, use the no form of this command.
debug rtsp [level]
no debug rtsp [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 RTSP application inspection:
hostname# debug rtspRelated Commands
debug sdi
To display SDI authentication debug information, use the debug sdi command in privileged EXEC mode. To disable the display of SDI debug information, use the no form of this command.
debug sdi [level]
no debug sdi
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
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 example enables SDI debug messages. The show debug command reveals that SDI debug messages are enabled.
hostname# debug sdidebug sdi enabled at level 1hostname# show debugdebug sdi enabled at level 1hostname#Related Commands
debug sequence
To add a sequence number to the beginning of all debug messages, use the debug sequence command in privileged EXEC mode. To disable the use of debug sequence numbers, use the no form of this command.
debug sequence [level]
no debug sequence
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 defaults are as follows:
•
•
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 example enables sequence numbers in debug messages. The debug parser cache command enables CLI parser debug messages. The show debug command reveals the current debug configuration. The CLI parser debug messages shown include sequence numbers before each message.
hostname# debug sequencedebug sequence enabled at level 1hostname# debug parser cachedebug parser cache enabled at level 1hostname# show debug0: parser cache: try to match 'show debug' in exec modedebug parser cache enabled at level 1debug sequence enabled at level 11: parser cache: hit at index 8hostname#Related Commands
debug sip
To show debug messages for SIP application inspection, use the debug sip command in privileged EXEC mode. To stop showing debug messages for SIP application inspection, use the no form of this command.
debug sip [level]
no debug sip [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 SIP application inspection:
hostname# debug sipRelated Commands
debug skinny
To show debug messages for SCCP (Skinny) application inspection, use the debug skinny command in privileged EXEC mode. To stop showing debug messages for SCCP application inspection, use the no form of this command.
debug skinny [level]
no debug skinny [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 SCCP application inspection:
hostname# debug skinnyRelated Commands
debug smtp
To show debug messages for SMTP/ESMTP application inspection, use the debug smtp command in privileged EXEC mode. To stop showing debug messages for SMTP/ESMTP application inspection, use the no form of this command.
debug smtp [level]
no debug smtp [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 SMTP/ESMTP application inspection:
hostname# debug smtpRelated Commands
debug sqlnet
To show debug messages for SQL*Net application inspection, use the debug sqlnet command in privileged EXEC mode. To stop showing debug messages for SQL*Net application inspection, use the no form of this command.
debug sqlnet [level]
no debug sqlnet [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 SQL*Net application inspection:
hostname# debug sqlnetRelated Commands
debug ssh
To display debug information and error messages associated with SSH, use the debug ssh command in privileged EXEC mode. To disable the display of debug information, use the no form of this command.
debug ssh [level]
no debug ssh [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
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 ssh 255 command:
hostname# debug ssh 255debug ssh enabled at level 255SSH2 0: send: len 64 (includes padlen 17)SSH2 0: done calc MAC out #239SSH2 0: send: len 32 (includes padlen 7)SSH2 0: done calc MAC out #240SSH2 0: send: len 64 (includes padlen 15)SSH2 0: done calc MAC out #241SSH2 0: send: len 32 (includes padlen 16)SSH2 0: done calc MAC out #242SSH2 0: send: len 64 (includes padlen 7)SSH2 0: done calc MAC out #243SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #244SSH2 0: send: len 64 (includes padlen 8)SSH2 0: done calc MAC out #245SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #246SSH2 0: send: len 64 (includes padlen 7)SSH2 0: done calc MAC out #247SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #248SSH2 0: send: len 64 (includes padlen 7)SSH2 0: done calc MAC out #249SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #250SSH2 0: send: len 64 (includes padlen 8)SSH2 0: done calc MAC out #251SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #252SSH2 0: send: len 64 (includes padlen 7)SSH2 0: done calc MAC out #253SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #254SSH2 0: send: len 64 (includes padlen 8)SSH2 0: done calc MAC out #255SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #256SSH2 0: send: len 64 (includes padlen 7)SSH2 0: done calc MAC out #257SSH2 0: send: len 64 (includes padlen 18)SSH2 0: done calc MAC out #258Related Commands
debug sunrpc
To show debug messages for RPC application inspection, use the debug sunrpc command in privileged EXEC mode. To stop showing debug messages for RPC application inspection, use the no form of this command.
debug sunrpc [level]
no debug sunrpc [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 RPC application inspection:
hostname# debug sunrpcRelated Commands
debug tacacs
To display TACACS+ debug information, use the debug tacacs command in privileged EXEC mode. To disable the display of TACACS+ debug information, use the no form of this command.
debug tacacs [session | user username]
no debug tacacs [session | user username]
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 example enables TACACS+ debug messages. The show debug command reveals that TACACS+ debug messages are enabled.
hostname# debug tacacs user admin342hostname# show debugdebug tacacs user admin342hostname#Related Commands
debug timestamps
To add timestamp information to the beginning of all debug messages, use the debug timestamps command in privileged EXEC mode. To disable the use of debug timestamps, use the no form of this command.
debug timestamps [level]
no debug timestamps
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 defaults are as follows:
•
•
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 example enables timestamps in debug messages. The debug parser cache command enables CLI parser debug messages. The show debug command reveals the current debug configuration. The CLI parser debug messages shown include timestamps before each message.
hostname# debug timestampsdebug timestamps enabled at level 1hostname# debug parser cachedebug parser cache enabled at level 1hostname# show debug1982769.770000000: parser cache: try to match 'show debug' in exec mode1982769.770000000: parser cache: hit at index 8hostname#Related Commands
debug vpn-sessiondb
To display VPN-session database debug information, use the debug vpn-sessiondb command in privileged EXEC mode. To disable the display of VPN-session database debug information, use the no form of this command.
debug vpn-sessiondb [level]
no debug vpn-sessiondb
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
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 VPN-session database debug messages. The show debug command reveals that VPN-session database debug messages are enabled.
hostname# debug vpn-sessiondbdebug vpn-sessiondb enabled at level 1hostname# show debugdebug vpn-sessiondb enabled at level 1hostname#Related Commands
debug xdmcp
To show debug messages for XDMCP application inspection, use the debug xdmcp command in privileged EXEC mode. To stop showing debug messages for XDMCP application inspection, use the no form of this command.
debug xdmcp [level]
no debug xdmcp [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 XDMCP application inspection:
hostname# debug xdmcpRelated Commands
