Table Of Contents
ddns through debug xdmcp Commands
ddns (DDNS-update-method)
ddns update (interface configuration)
ddns update method (global configuration mode)
debug aaa
debug appfw
debug arp
debug arp-inspection
debug asdm history
debug context
debug cplane
debug crypto ca
debug crypto engine
debug crypto ipsec
debug crypto isakmp
debug ctiqbe
debug ddns
debug dhcpc
debug dhcpd
debug dhcpd ddns
debug dhcprelay
debug disk
debug dns
debug eap
debug entity
debug eou
debug esmtp
debug fixup
debug fover
debug fsm
debug ftp client
debug generic
debug gtp
debug h323
debug http
debug http-map
debug icmp
debug igmp
debug ils
debug imagemgr
debug ipsec-over-tcp
debug ipv6
debug iua-proxy
debug kerberos
debug l2tp
debug ldap
debug mac-address-table
debug menu
debug mfib
debug mgcp
debug module-boot
debug mrib
debug nac
debug ntdomain
debug ntp
debug ospf
debug parser cache
debug pim
debug pix pkt2pc
debug pix process
debug pptp
debug radius
debug rip
debug rtp
debug rtsp
debug sdi
debug sequence
debug session-command
debug sip
debug skinny
debug sla monitor
debug sqlnet
debug ssh
debug ssl
debug sunrpc
debug switch ilpm
debug switch manager
debug tacacs
debug tcp-map
debug timestamps
debug vpn-sessiondb
debug wccp
debug webvpn
debug xdmcp
ddns through debug xdmcp Commands
ddns (DDNS-update-method)
To specify a DDNS update method type, use the ddns command in DDNS-update-method mode. To remove an update method type from the running configuration, use the no form of this command.
ddns [both]
no ddns [both]
Syntax Description
both
|
(Optional) Specifies updating to both the DNS A and PTR resource records (RRs).
|
Defaults
Update only A RRs.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
DDNS-update-method
|
•
|
—
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.2(1)
|
This command was introduced.
|
Usage Guidelines
Dynamic DNS (DDNS) updates the name to address and address to name mappings maintained by DNS. Of the two methods for performing DDNS updates—the IETF standard defined by RFC 2136 and a generic HTTP method—the security appliance supports the IETF method in this release.
Name and address mappings are contained in two types of resource records (RR):
•
The A resource record contains domain name to IP address mappings.
•
The PTR resource record contains IP address to domain name mappings.
DDNS updates can be used to maintain consistent information between the A and PTR RR types.
When issued in DDNS-update-method configuration mode, the ddns command defines whether the update is just to A RR, or to both A RR and PTR RR.
Examples
The following example configures updating to both the A and PTR RRs for the DDNS update method named ddns-2:
hostname(config)# ddns update method ddns-2
hostname(DDNS-update-method)# ddns both
Related Commands
Command
|
Description
|
ddns update (interface config mode)
|
Associates a dynamic DNS (DDNS) update method with a security appliance interface or a DDNS update hostname.
|
ddns update method (global config mode)
|
Creates a method for dynamically updating DNS resource records.
|
dhcp-client update dns
|
Configures the update parameters that the DHCP client passes to the DHCP server.
|
dhcpd update dns
|
Enables a DHCP server to perform DDNS updates.
|
interval maximum
|
Configures the maximum interval between update attempts by a DDNS update method.
|
ddns update (interface configuration)
To associate a dynamic DNS (DDNS) update method with a security appliance interface or an update hostname, use the ddns update command in interface configuration mode. To remove the association between the DDNS update method and the interface or the hostname from the running configuration, use the no form of this command.
ddns update [method-name | hostname hostname]
no ddns update [method-name | hostname hostname]
Syntax Description
hostname
|
Specifies that the next term in the command string is a hostname.
|
hostname
|
Specifies a hostname to be used for updates.
|
method-name
|
Specifies a method name for association with the interface being configured.
|
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Interface configuration
|
•
|
—
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.2(1)
|
This command was introduced.
|
Usage Guidelines
After defining a DDNS update method, you must associate it with a security appliance interface to trigger DDNS updates.
A hostname could be a Fully Qualified Domain Name (FQDN) or just a hostname. If just a hostname, the security appliance appends a domain name to the hostname to create a FQDN.
Examples
The following example associates the interface GigabitEthernet0/2 with the DDNS update method named ddns-2 and the hostname hostname1.example.com:
hostname(config)# interface GigabitEthernet0/2
hostname(config-if)# ddns update ddns-2
hostname(config-if)# ddns update hostname hostname1.example.com
Related Commands
Command
|
Description
|
ddns (DDNS-update-
method mode)
|
Specifies a DDNS update method type for a created DDNS method.
|
ddns update method (global config mode)
|
Creates a method for dynamically updating DNS resource records.
|
dhcp-client update dns
|
Configures the update parameters that the DHCP client passes to the DHCP server.
|
dhcpd update dns
|
Enables a DHCP server to perform DDNS updates.
|
interval maximum
|
Configures the maximum interval between update attempts by a DDNS update method.
|
ddns update method (global configuration mode)
To create a method for dynamically updating a DNS resource records (RRs), use the ddns update method command in global configuration mode. To remove a dynamic DNS (DDNS) update method from the running configuration, use the no form of this command.
ddns update method name
no ddns update method name
Syntax Description
name
|
Specifies the name of a method for dynamically updating DNS records.
|
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Global configuration
|
•
|
—
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.2(1)
|
This command was introduced.
|
Usage Guidelines
DDNS updates the name to address and address to name mappings maintained by DNS. The update method configured by the ddns update method command determines what and how often dynamic DNS updates are performed. Of the two methods for performing DDNS updates—the IETF standard defined by RFC 2136 and a generic HTTP method—the security appliance supports the IETF method in this release.
Name and address mappings are contained in two types of resource records (RR):
•
The A resource record contains domain name to IP address mappings.
•
The PTR resource record contains IP address to domain name mappings.
DDNS updates can be used to maintain consistent information between the A and PTR RR types.
Note
Before ddns update method will work, you must configure a reachable default DNS server using the dns command with domain lookup enabled on the interface.
Examples
The following example configures the DDNS update method named ddns-2:
hostname(config)# ddns update method ddns-2
Related Commands
Command
|
Description
|
ddns (DDNS-update-
method mode)
|
Specifies a DDNS update method type for a created DDNS method.
|
ddns update (interface config mode)
|
Associates a dynamic DNS (DDNS) update method with a security appliance interface or a DDNS update hostname.
|
dhcp-client update dns
|
Configures the update parameters that the DHCP client passes to the DHCP server.
|
dhcpd update dns
|
Enables a DHCP server to perform dynamic DNS updates.
|
interval maximum
|
Configures the maximum interval between update attempts by a DDNS update method.
|
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 | common | internal | vpn [ level ] ]
no debug aaa
Syntax Description
accounting
|
(Optional) Show debug messages for accounting only.
|
authentication
|
(Optional) Show debug messages for authentication only.
|
authorization
|
(Optional) Show debug messages for authorization only.
|
common
|
(Optional) Show debug messages for different states within the AAA feature.
|
internal
|
(Optional) Show debug messages for AAA functions supported by the local database only.
|
level
|
(Optional) Specifies the debug level. Valid with the common and vpn keywords only.
|
vpn
|
(Optional) Show debug messages for VPN-related AAA functions only.
|
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
•
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was modified to include new keywords.
|
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 internal
debug aaa internal enabled at level 1
hostname(config)# uap allocated. remote address: 10.42.15.172, Session_id: 2147483841
uap freed for user . remote address: 10.42.15.172, session id: 2147483841
Related Commands
Command
|
Description
|
show running-config aaa
|
Displays running configuration related to AAA.
|
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
chunk
|
(Optional) Displays runtime information about processing of chunked transfer encoded packets.
|
event
|
(Optional) Displays debug information about packet inspection events.
|
eventverb
|
(Optional) Displays the action taken by the security appliance in response to an event.
|
regex
|
(Optional) Displays information about matching patterns with predefined signatures.
|
Defaults
All options are enabled by default.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
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:
Related Commands
Commands
|
Description
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ARP:
Related Commands
Command
|
Description
|
arp
|
Adds a static ARP entry.
|
show arp statistics
|
Shows ARP statistics.
|
show debug
|
Shows all enabled debuggers.
|
debug arp-inspection
To show debug messages for ARP inspection, use the debug arp-inspection command in privileged EXEC mode. To stop showing debug messages for ARP inspection, use the no form of this command.
debug arp-inspection
no debug arp-inspection
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
—
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ARP inspection:
hostname# debug arp-inspection
Related Commands
Command
|
Description
|
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
level
|
(Optional) Specifies the debug level.
|
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
•
|
Command History
Release
|
Modification
|
7.0(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 technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
Examples
The following example enables level 1 debugging of ASDM:
hostname# debug asdm history
debug asdm history enabled at level 1
Related Commands
Command
|
Description
|
show asdm history
|
Displays the contents of the ASDM history buffer.
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
—
|
—
|
•
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for context management:
Related Commands
Command
|
Description
|
context
|
Creates a security context in the system configuration and enters context configuration mode.
|
show context
|
Shows context information.
|
show debug
|
Shows all enabled debuggers.
|
debug cplane
To show debug messages about the control plane that connects internally to an SSM, use the debug cplane command in privileged EXEC mode. To stop showing debug messages for the control plane, use the no form of this command.
debug cplane [level]
no debug cplane [level]
Syntax Description
level
|
(Optional) Sets the debug message level to display, between 1 and 255. The default is 1. To display additional messages at higher levels, set the level to a higher number.
|
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
—
|
•
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for the control plane:
Related Commands
Command
|
Description
|
hw-module module recover
|
Recovers an intelligent SSM by loading a recovery image from a TFTP server.
|
hw-module module reset
|
Shuts down an SSM and performs a hardware reset.
|
hw-module module reload
|
Reloads the intelligent SSM software.
|
hw-module module shutdown
|
Shuts down the SSM software in preparation for being powered off without losing configuration data.
|
show module
|
Shows SSM information.
|
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
messages
|
(Optional) Shows only debug messages for PKI input and output messages.
|
transactions
|
(Optional) Shows only debug messages for PKI transactions.
|
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. Level 1 (the default) shows messages only when errors occur. Level 2 shows warnings. Level 3 shows informational messages. Levels 4 and up show additional information for troubleshooting.
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for PKI:
hostname# debug crypto ca
Related Commands
Command
|
Description
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
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 engine
Related Commands
Command
|
Description
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
—
|
—
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for IPSec:
hostname# debug crypto ipsec
Related Commands
Command
|
Description
|
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
timers
|
(Optional) Shows debug messages for ISAKMP timer expiration.
|
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. Level 1 (the default) shows messages only when errors occur. Levels 2 through 7 show additional information. Level 254 shows decrypted ISAKMP packets in a human readable format. Level 255 shows hexadecimal dumps of decrypted ISAKMP packets.
|
Defaults
The default level is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
—
|
—
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Usage Guidelines
Using debug commands might slow down traffic on busy networks.
Examples
The following example enables debug messages for ISAKMP:
hostname# debug crypto isakmp
Related Commands
Command
|
Description
|
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
• |