Table Of Contents
show ddns update interface through show ipv6 traffic Commands
show ddns update interface
show ddns update method
show debug
show debug mmp
show dhcpd
show dhcprelay state
show dhcprelay statistics
show disk
show dns-hosts
show dynamic-filter data
show dynamic-filter dns-snoop
show dynamic-filter reports
show dynamic-filter statistics
show dynamic-filter updater-client
show eigrp events
show eigrp interfaces
show eigrp neighbors
show eigrp topology
show eigrp traffic
show failover
show failover exec
show file
show firewall
show flash
show flow-export counters
show fragment
show gc
show h225
show h245
show h323-ras
show history
show icmp
show idb
show igmp groups
show igmp interface
show igmp traffic
show import webvpn
show interface
show interface ip brief
show inventory
show ip address
show ip address dhcp
show ip address pppoe
show ip audit count
show ip verify statistics
show ips
show ipsec sa
show ipsec sa summary
show ipsec stats
show ipv6 access-list
show ipv6 interface
show ipv6 mld traffic
show ipv6 neighbor
show ipv6 route
show ipv6 routers
show ipv6 traffic
show ddns update interface through show ipv6 traffic Commands
show ddns update interface
To display the DDNS methods assigned to adaptive security appliance interfaces, use the show ddns update interface command in privileged EXEC mode.
show ddns update interface [interface-name]
Syntax Description
interface-name
|
(Optional) The name of a network interface.
|
Defaults
Omitting the interface-name string displays the DDNS method assigned to each interface.
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.2(1)
|
This command was introduced.
|
Examples
The following example displays the DDNS method assigned to the inside interface:
hostname# show ddns update interface inside
Dynamic DNS Update on inside:
Update Method Name Update Destination
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 adaptive security appliance interface with a DDNS update method or a DDNS update hostname.
|
ddns update method (global config mode)
|
Creates a method for dynamically updating DNS resource records.
|
show ddns update method
|
Displays the type and interval for each configured DDNS method. a DHCP server to perform DDNS updates.
|
show running-config ddns
|
Displays the type and interval of all configured DDNS methods in the running configuration.
|
show ddns update method
To display the DDNS update methods in the running configuration, use the show ddns update method command in privileged EXEC mode.
show ddns update method [method-name]
Syntax Description
method-name
|
(Optional) The name of a configured DDNS update method.
|
Defaults
Omitting the method-name string displays all configured DDNS update methods.
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.2(1)
|
This command was introduced.
|
Examples
The following example displays the DDNS method named ddns-2:
hostname(config)# show ddns update method ddns-2
Dynamic DNS Update Method: ddns-2
IETF standardized Dynamic DNS 'A' and 'PTR' records update
Maximum update interval: 0 days 0 hours 10 minutes 0 seconds
hostname(config)#
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 adaptive security appliance interface with a Dynamic DNS (DDNS) update method or a DDNS update hostname.
|
ddns update method (global config mode)
|
Creates a method for dynamically updating DNS resource records.
|
show ddns update interface
|
Displays the interfaces associated with each configured DDNS method.
|
show running-config ddns
|
Displays the type and interval of all configured DDNS methods in the running configuration.
|
show debug
To show the current debugging configuration, use the show debug command.
show debug [command [keywords]]
Syntax Description
command
|
(Optional) Specifies the debug command whose current configuration you want to view. For each command, the syntax following command is identical to the syntax supported by the associated debug command. For example, valid keywords following show debug aaa are the same as the valid keywords for the debug aaa command. Thus, show debug aaa supports an accounting keyword, which allows you to specify that you want to see the debugging configuration for that portion of AAA debugging.
|
Defaults
This command has no default settings.
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.
|
8.0(2)
|
The eigrp keyword was added to the list of possible command values.
|
Usage Guidelines
The valid command values follow. For each command, the syntax following command is identical to the syntax supported by the associated debug command. Refer to the associated debug command for information about the supported syntax.
Note
The availability of each command value depends upon the command modes that support the applicable debug command.
•
aaa
•
appfw
•
arp
•
asdm
•
context
•
crypto
•
ctiqbe
•
ctm
•
dhcpc
•
dhcpd
•
dhcprelay
•
disk
•
dns
•
eigrp
•
email
•
entity
•
fixup
•
fover
•
fsm
•
ftp
•
generic
•
gtp
•
h323
•
http
•
http-map
•
icmp
•
igmp
•
ils
•
imagemgr
•
ipsec-over-tcp
•
ipv6
•
iua-proxy
•
kerberos
•
ldap
•
mfib
•
mgcp
•
mrib
•
ntdomain
•
ntp
•
ospf
•
parser
•
pim
•
pix
•
pptp
•
radius
•
rip
•
rtsp
•
sdi
•
sequence
•
sip
•
skinny
•
smtp
•
sqlnet
•
ssh
•
ssl
•
sunrpc
•
tacacs
•
timestamps
•
vpn-sessiondb
•
webvpn
•
xdmcp
•
xml
Examples
The following commands enable debugging for authentication, accounting, and Flash memory. The show debug command is used in three ways to demonstrate how you can use it to view all debugging configuration, debugging configuration for a specific feature, and even debugging configuration for a subset of a feature.
hostname# debug aaa authentication
debug aaa authentication enabled at level 1
hostname# debug aaa accounting
debug aaa accounting enabled at level 1
hostname# debug disk filesystem
debug disk filesystem enabled at level 1
debug aaa authentication enabled at level 1
debug aaa accounting enabled at level 1
debug disk filesystem enabled at level 1
debug aaa authentication enabled at level 1
debug aaa authorization is disabled.
debug aaa accounting enabled at level 1
debug aaa internal is disabled.
debug aaa vpn is disabled.
hostname# show debug aaa accounting
debug aaa accounting enabled at level 1
Related Commands
Command
|
Description
|
debug
|
See all debug commands.
|
show debug mmp
To display current debug settings for the MMP inspection module, use the show debug mmp command in privileged EXEC mode.
show debug mmp
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
|
8.0(4)
|
The command was introduced.
|
Examples
The following example shows the use of the show debug mmp command to displaythe current debug settings for the MMP inspection module:
debug mmp enabled at level 1
Related Commands
Command
|
Description
|
debug mmp
|
Display inspect MMP events.
|
inspect mmp
|
Configures the MMP inspection engine.
|
show dhcpd
To view DHCP binding, state, and statistical information, use the show dhcpd command in privileged EXEC or global configuration mode.
show dhcpd {binding [IP_address] | state | statistics}
Syntax Description
binding
|
Displays binding information for a given server IP address and its associated client hardware address and lease length.
|
IP_address
|
Shows the binding information for the specified IP address.
|
state
|
Displays the state of the DHCP server, such as whether it is enabled in the current context and whether it is enabled on each of the interfaces.
|
statistics
|
Displays statistical information, such as the number of address pools, bindings, expired bindings, malformed messages, sent messages, and received messages.
|
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
If you include the optional IP address in the show dhcpd binding command, only the binding for that IP address is shown.
The show dhcpd binding | state | statistics commands are also available in global configuration mode.
Examples
The following is sample output from the show dhcpd binding command:
hostname# show dhcpd binding
IP Address Hardware Address Lease Expiration Type
10.0.1.100 0100.a0c9.868e.43 84985 seconds automatic
The following is sample output from the show dhcpd state command:
hostname# show dhcpd state
Context Not Configured for DHCP
Interface outside, Not Configured for DHCP
Interface inside, Not Configured for DHCP
The following is sample output from the show dhcpd statistics command:
hostname# show dhcpd statistics
DHCP UDP Unreachable Errors: 0
Related Commands
Command
|
Description
|
clear configure dhcpd
|
Removes all DHCP server settings.
|
clear dhcpd
|
Clears the DHCP server bindings and statistic counters.
|
dhcpd lease
|
Defines the lease length for DHCP information granted to clients.
|
show running-config dhcpd
|
Displays the current DHCP server configuration.
|
show dhcprelay state
To view the state of the DHCP relay agent, use the show dhcprelay state command in privileged EXEC or global configuration mode.
show dhcprelay state
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
This command displays the DHCP relay agent state information for the current context and each interface.
Examples
The following is sample output from the show dhcprelay state command:
hostname# show dhcprelay state
Context Configured as DHCP Relay
Interface outside, Not Configured for DHCP
Interface infrastructure, Configured for DHCP RELAY SERVER
Interface inside, Configured for DHCP RELAY
Related Commands
Command
|
Description
|
show dhcpd
|
Displays DHCP server statistics and state information.
|
show dhcprelay statistics
|
Displays the DHCP relay statistics.
|
show running-config dhcprelay
|
Displays the current DHCP relay agent configuration.
|
show dhcprelay statistics
To display the DHCP relay statistics, use the show dhcprelay statistics command in privileged EXEC mode.
show dhcprelay statistics
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
The output of the show dhcprelay statistics command increments until you enter the clear dhcprelay statistics command.
Examples
The following shows sample output for the show dhcprelay statistics command:
hostname# show dhcprelay statistics
DHCP UDP Unreachable Errors: 0
Related Commands
Command
|
Description
|
clear configure dhcprelay
|
Removes all DHCP relay agent settings.
|
clear dhcprelay statistics
|
Clears the DHCP relay agent statistic counters.
|
debug dhcprelay
|
Displays debug information for the DHCP relay agent.
|
show dhcprelay state
|
Displays the state of the DHCP relay agent.
|
show running-config dhcprelay
|
Displays the current DHCP relay agent configuration.
|
show disk
To display the contents of the flash memory for the adaptive security appliance only, use the show disk command in privileged EXEC mode.
show disk[0 | 1] [filesys | all] controller
Syntax Description
0 | 1
|
Specifies the internal flash memory (0, the default) or the external flash memory (1).
|
controller
|
Specifies the flash controller model number.
|
filesys
|
Shows information about the compact flash card.
|
all
|
Shows the contents of flash memory plus the file system information,
|
Defaults
Shows the internal flash memory 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.
|
Examples
The following is sample output from the show disk command:
-#- --length-- -----date/time------ path
11 1301 Feb 21 2005 18:01:34 test.cfg
12 1949 Feb 21 2005 20:13:36 test1.cfg
13 2551 Jan 06 2005 10:07:36 test2.cfg
14 609223 Jan 21 2005 07:14:18 test3.cfg
15 1619 Jul 16 2004 16:06:48 test4.cfg
16 3184 Aug 03 2004 07:07:00 old_running.cfg
17 4787 Mar 04 2005 12:32:18 test5.cfg
20 1792 Jan 21 2005 07:29:24 test6.cfg
21 7765184 Mar 07 2005 19:38:30 test7.cfg
22 1674 Nov 11 2004 02:47:52 test8.cfg
23 1863 Jan 21 2005 07:29:18 test9.cfg
24 1197 Jan 19 2005 08:17:48 test10.cfg
25 608554 Jan 13 2005 06:20:54 backupconfig.cfg
26 5124096 Feb 20 2005 08:49:28 cdisk1
27 5124096 Mar 01 2005 17:59:56 cdisk2
28 2074 Jan 13 2005 08:13:26 test11.cfg
29 5124096 Mar 07 2005 19:56:58 cdisk3
30 1276 Jan 28 2005 08:31:58 lead
31 7756788 Feb 24 2005 12:59:46 asdmfile.dbg
32 7579792 Mar 08 2005 11:06:56 asdmfile1.dbg
33 7764344 Mar 04 2005 12:17:46 asdmfile2.dbg
34 5124096 Feb 24 2005 11:50:50 cdisk4
35 15322 Mar 04 2005 12:30:24 hs_err.log
10170368 bytes available (52711424 bytes used)
The following is sample output from the show disk filesys command:
hostname# show disk filesys
******** Flash Card Geometry/Format Info ********
COMPACT FLASH CARD GEOMETRY
COMPACT FLASH CARD FORMAT
Number of Data Sectors 122976
The following is sample output from the show disk controller command:
hostname# show disk:1 controller
Flash Model: TOSHIBA THNCF064MBA
Related Commands
Command
|
Description
|
dir
|
Displays the directory contents.
|
show dns-hosts
To show the DNS cache, use the show dns-hosts command in privileged EXEC mode.The DNS cache includes dynamically learned entries from a DNS server as well as manually entered name and IP addresses using the name command.
show dns-hosts
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.
|
Examples
The following is sample output from the show dns-hosts command:
Host Flags Age Type Address(es)
ns2.example.com (temp, OK) 0 IP 10.102.255.44
ns1.example.com (temp, OK) 0 IP 192.168.241.185
snowmass.example.com (temp, OK) 0 IP 10.94.146.101
server.example.com (temp, OK) 0 IP 10.94.146.80
Table 11 shows each field description.
Table 25-1 show dns-hosts Fields
Field
|
Description
|
Host
|
Shows the hostname.
|
Flags
|
Shows the entry status, as a combination of the following:
• temp—This entry is temporary because it comes from a DNS server. The adaptive security appliance removes this entry after 72 hours of inactivity.
• perm—This entry is permanent because it was added with the name command.
• OK—This entry is valid.
• ??—This entry is suspect and needs to be revalidated.
• EX—This entry is expired.
|
Age
|
Shows the number of hours since this entry was last referenced.
|
Type
|
Shows the type of DNS record; this value is always IP.
|
Address(es)
|
The IP addresses.
|
Related Commands
Command
|
Description
|
clear dns-hosts
|
Clears the DNS cache.
|
dns domain-lookup
|
Enables the adaptive security appliance to perform a name lookup.
|
dns name-server
|
Configures a DNS server address.
|
dns retries
|
Specifies the number of times to retry the list of DNS servers when the adaptive security appliance does not receive a response.
|
dns timeout
|
Specifies the amount of time to wait before trying the next DNS server.
|
show dynamic-filter data
To show information about the Botnet Traffic Filter dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries, use the show dynamic-filter data command in privileged EXEC mode.
show dynamic-filter data
Syntax Description
This command has no arguments or keywords.
Command Default
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
|
8.2(1)
|
This command was introduced.
|
Usage Guidelines
To view dynamic database information, first enable use and download of the database with the dynamic-filter use-database and dynamic-filter updater-client enable commands.
Examples
The following is sample output from the show dynamic-filter data command:
hostname# show dynamic-filter data
Traffic filter is using downloaded database version '907'
Fetched at 18:00:16 UTC Jan 22 2009, size: 674381
Sample names from downloaded database:
example.com, example.net, example.org,
cisco.example, cisco.invalid, bad.example.com
bad.example.net, bad.example.org, bad.cisco.example
Total entries in Dynamic Filter database:
Dynamic data: 40909 domain names , 1080 IPv4 addresses
Local data: 0 domain names , 0 IPv4 addresses
Active rules in Dynamic Filter asp table:
Dynamic data: 0 domain names , 1080 IPv4 addresses
Local data: 0 domain names , 0 IPv4 addresses
Related Commands
Command
|
Description
|
address
|
Adds an IP address to the blacklist or whitelist.
|
clear configure dynamic-filter
|
Clears the running Botnet Traffic Filter configuration.
|
clear dynamic-filter dns-snoop
|
Clears Botnet Traffic Filter DNS snooping data.
|
clear dynamic-filter reports
|
Clears Botnet Traffic filter report data.
|
clear dynamic-filter statistics
|
Clears Botnet Traffic filter statistics.
|
dns domain-lookup
|
Enables the adaptive security appliance to send DNS requests to a DNS server to perform a name lookup for supported commands.
|
dns server-group
|
Identifies a DNS server for the adaptive security appliance.
|
dynamic-filter blacklist
|
Edits the Botnet Traffic Filter blacklist.
|
dynamic-filter database fetch
|
Manually retrieves the Botnet Traffic Filter dynamic database.
|
dynamic-filter database find
|
Searches the dynamic database for a domain name or IP address.
|
dynamic-filter database purge
|
Manually deletes the Botnet Traffic Filter dynamic database.
|
dynamic-filter enable
|
Enables the Botnet Traffic Filter for a class of traffic or for all traffic if you do not specify an access list.
|
dynamic-filter updater-client enable
|
Enables downloading of the dynamic database.
|
dynamic-filter use-database
|
Enables use of the dynamic database.
|
dynamic-filter whitelist
|
Edits the Botnet Traffic Filter whitelist.
|
inspect dns dynamic-filter-snoop
|
Enables DNS inspection with Botnet Traffic Filter snooping.
|
name
|
Adds a name to the blacklist or whitelist.
|
show asp table dynamic-filter
|
Shows the Botnet Traffic Filter rules that are installed in the accelerated security path.
|
show dynamic-filter data
|
Shows information about the dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries.
|
show dynamic-filter reports
|
Generates reports of the top 10 botnet sites, ports, and infected hosts.
|
show dynamic-filter statistics
|
Shows how many connections were monitored with the Botnet Traffic Filter, and how many of those connections match the whitelist, blacklist, and graylist.
|
show dynamic-filter updater-client
|
Shows information about the updater server, including the server IP address, the next time the adaptive security appliance will connect with the server, and the database version last installed.
|
show running-config dynamic-filter
|
Shows the Botnet Traffic Filter running configuration.
|
show dynamic-filter dns-snoop
To show the Botnet Traffic Filter DNS snooping summary, or the actual IP addresses and names, use the show dynamic-filter dns-snoop command in privileged EXEC mode.
show dynamic-filter dns-snoop [detail]
Syntax Description
detail
|
(Optional) Shows the IP addresses and names snooped from DNS responses.
|
Command Default
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
|
8.2(1)
|
This command was introduced.
|
Usage Guidelines
All inspected DNS data is included in this output, and not just matching names in the blacklist. DNS data from static entries are not included.
To clear the DNS snooping data, enter the clear dynamic-filter dns-snoop command.
Examples
The following is sample output from the show dynamic-filter dns-snoop command:
hostname# show dynamic-filter dns-snoop
DNS Reverse Cache Summary Information:
75 addresses, 124 names, 997 dnsrc address buckets
The following is sample output from the show dynamic-filter dns-snoop detail command:
hostname# show dynamic-filter dns-snoop detail
DNS Reverse Cache Summary Information:
75 addresses, 124 names, 997 dnsrc address buckets
DNS reverse Cache Information:
[10.67.22.34] flags=0x22, cat=2, unit=0 b:g:w=3:0:0, cookie=0xda148218
[www3.example.com] cat=2, ttl=3
[www.bad.example.com] cat=2, ttl=3
[www.example.com] cat=2, ttl=3
[10.6.68.133] flags=0x2, cat=2, unit=0 b:g:w=1:0:0, cookie=0xda13ed60
[cisco.example] cat=2, ttl=73
[10.166.226.25] flags=0x2, cat=2, unit=0 b:g:w=1:0:0, cookie=0xda608cb8
[cisco.invalid] cat=2, ttl=2
Related Commands
Command
|
Description
|
address
|
Adds an IP address to the blacklist or whitelist.
|
clear configure dynamic-filter
|
Clears the running Botnet Traffic Filter configuration.
|
clear dynamic-filter dns-snoop
|
Clears Botnet Traffic Filter DNS snooping data.
|
clear dynamic-filter reports
|
Clears Botnet Traffic filter report data.
|
clear dynamic-filter statistics
|
Clears Botnet Traffic filter statistics.
|
dns domain-lookup
|
Enables the adaptive security appliance to send DNS requests to a DNS server to perform a name lookup for supported commands.
|
dns server-group
|
Identifies a DNS server for the adaptive security appliance.
|
dynamic-filter blacklist
|
Edits the Botnet Traffic Filter blacklist.
|
dynamic-filter database fetch
|
Manually retrieves the Botnet Traffic Filter dynamic database.
|
dynamic-filter database find
|
Searches the dynamic database for a domain name or IP address.
|
dynamic-filter database purge
|
Manually deletes the Botnet Traffic Filter dynamic database.
|
dynamic-filter enable
|
Enables the Botnet Traffic Filter for a class of traffic or for all traffic if you do not specify an access list.
|
dynamic-filter updater-client enable
|
Enables downloading of the dynamic database.
|
dynamic-filter use-database
|
Enables use of the dynamic database.
|
dynamic-filter whitelist
|
Edits the Botnet Traffic Filter whitelist.
|
inspect dns dynamic-filter-snoop
|
Enables DNS inspection with Botnet Traffic Filter snooping.
|
name
|
Adds a name to the blacklist or whitelist.
|
show asp table dynamic-filter
|
Shows the Botnet Traffic Filter rules that are installed in the accelerated security path.
|
show dynamic-filter data
|
Shows information about the dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries.
|
show dynamic-filter reports
|
Generates reports of the top 10 botnet sites, ports, and infected hosts.
|
show dynamic-filter statistics
|
Shows how many connections were monitored with the Botnet Traffic Filter, and how many of those connections match the whitelist, blacklist, and graylist.
|
show dynamic-filter updater-client
|
Shows information about the updater server, including the server IP address, the next time the adaptive security appliance will connect with the server, and the database version last installed.
|
show running-config dynamic-filter
|
Shows the Botnet Traffic Filter running configuration.
|
show dynamic-filter reports
To generate reports of the top 10 botnet sites, ports, and infected hosts, use the show dynamic-filter reports top command in privileged EXEC mode.
show dynamic-filter reports top [botnet-sites | botnet-ports | infected-hosts]
Syntax Description
botnet-ports
|
(Optional) Shows a report for the top 10 botnet ports.
|
botnet-sites
|
(Optional) Shows a report for the top 10 botnet sites.
|
infected-hosts
|
(Optional) Shows a report for the top 10 infected hosts.
|
top
|
Shows the top 10 botnet sites, pots, and hosts.
|
Command Default
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
|
8.2(1)
|
This command was introduced.
|
Usage Guidelines
This report is a snapshot of the data, and may not match the top 10 items since the statistics started to be collected. For hosts, the timeout value is 1 hour (non-configurable) to reduce the memory impact. The site and port reports do not have a timeout value.
To clear the report data, enter the clear dynamic-filter reports command.
Examples
The following is sample output from the show dynamic-filter reports top botnet-sites command:
hostname# show dynamic-filter reports top botnet-sites
----------------------------------------------------------------------
bad1.example.com (10.67.22.34) 11
bad2.example.com (209.165.200.225) 8
bad1.cisco.example(10.131.36.158) 6
bad2.cisco.example(209.165.201.1) 2
horrible.example.net(10.232.224.2) 2
nono.example.org(209.165.202.130) 1
The following is sample output from the show dynamic-filter reports top botnet-ports command:
hostname# show dynamic-filter reports top botnet-ports
----------------------------------------------------------------------
The following is sample output from the show dynamic-filter reports top infected-hosts command:
hostname# show dynamic-filter reports top infected-hosts
----------------------------------------------------------------------
Related Commands
Command
|
Description
|
address
|
Adds an IP address to the blacklist or whitelist.
|
clear configure dynamic-filter
|
Clears the running Botnet Traffic Filter configuration.
|
clear dynamic-filter dns-snoop
|
Clears Botnet Traffic Filter DNS snooping data.
|
clear dynamic-filter reports
|
Clears Botnet Traffic filter report data.
|
clear dynamic-filter statistics
|
Clears Botnet Traffic filter statistics.
|
dns domain-lookup
|
Enables the adaptive security appliance to send DNS requests to a DNS server to perform a name lookup for supported commands.
|
dns server-group
|
Identifies a DNS server for the adaptive security appliance.
|
dynamic-filter blacklist
|
Edits the Botnet Traffic Filter blacklist.
|
dynamic-filter database fetch
|
Manually retrieves the Botnet Traffic Filter dynamic database.
|
dynamic-filter database find
|
Searches the dynamic database for a domain name or IP address.
|
dynamic-filter database purge
|
Manually deletes the Botnet Traffic Filter dynamic database.
|
dynamic-filter enable
|
Enables the Botnet Traffic Filter for a class of traffic or for all traffic if you do not specify an access list.
|
dynamic-filter updater-client enable
|
Enables downloading of the dynamic database.
|
dynamic-filter use-database
|
Enables use of the dynamic database.
|
dynamic-filter whitelist
|
Edits the Botnet Traffic Filter whitelist.
|
inspect dns dynamic-filter-snoop
|
Enables DNS inspection with Botnet Traffic Filter snooping.
|
name
|
Adds a name to the blacklist or whitelist.
|
show asp table dynamic-filter
|
Shows the Botnet Traffic Filter rules that are installed in the accelerated security path.
|
show dynamic-filter data
|
Shows information about the dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries.
|
show dynamic-filter dns-snoop
|
Shows the Botnet Traffic Filter DNS snooping summary, or with the detail keyword, the actual IP addresses and names.
|
show dynamic-filter statistics
|
Shows how many connections were monitored with the Botnet Traffic Filter, and how many of those connections match the whitelist, blacklist, and graylist.
|
show dynamic-filter updater-client
|
Shows information about the updater server, including the server IP address, the next time the adaptive security appliance will connect with the server, and the database version last installed.
|
show running-config dynamic-filter
|
Shows the Botnet Traffic Filter running configuration.
|
show dynamic-filter statistics
To show how many connections were monitored with the Botnet Traffic Filter, and how many of those connections match the whitelist, blacklist, and graylist, use the show dynamic-filter statistics command in privileged EXEC mode.
show dynamic-filter statistics [interface name]
Syntax Description
interface name
|
(Optional) Shows statistics for a particular interface.
|
Command Default
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
|
8.2(1)
|
This command was introduced.
|
Usage Guidelines
The graylist includes addresses that are associated with multiple domain names, but not all of these domain names are on the blacklist.
To clear the statistics, enter the clear dynamic-filter statistics command.
Examples
The following is sample output from the show dynamic-filter statistics command:
hostname# show dynamic-filter statistics
Enabled on interface outside
Total conns classified 2108, ingress 2108, egress 0
Total whitelist hits 0, ingress 0, egress 0
Total greylist hits 0, ingress 0, egress 0
Total blacklist hits 11, ingress 11, egress 0
Enabled on interface inside
Total conns classified 4908, ingress 4908, egress 0
Total whitelist hits 3, ingress 3, egress 0
Total greylist hits 0, ingress 0, egress 0
Total blacklist hits 1179, ingress 1179, egress 0
Related Commands
Command
|
Description
|
address
|
Adds an IP address to the blacklist or whitelist.
|
clear configure dynamic-filter
|
Clears the running Botnet Traffic Filter configuration.
|
clear dynamic-filter dns-snoop
|
Clears Botnet Traffic Filter DNS snooping data.
|
clear dynamic-filter reports
|
Clears Botnet Traffic filter report data.
|
clear dynamic-filter statistics
|
Clears Botnet Traffic filter statistics.
|
dns domain-lookup
|
Enables the adaptive security appliance to send DNS requests to a DNS server to perform a name lookup for supported commands.
|
dns server-group
|
Identifies a DNS server for the adaptive security appliance.
|
dynamic-filter blacklist
|
Edits the Botnet Traffic Filter blacklist.
|
dynamic-filter database fetch
|
Manually retrieves the Botnet Traffic Filter dynamic database.
|
dynamic-filter database find
|
Searches the dynamic database for a domain name or IP address.
|
dynamic-filter database purge
|
Manually deletes the Botnet Traffic Filter dynamic database.
|
dynamic-filter enable
|
Enables the Botnet Traffic Filter for a class of traffic or for all traffic if you do not specify an access list.
|
dynamic-filter updater-client enable
|
Enables downloading of the dynamic database.
|
dynamic-filter use-database
|
Enables use of the dynamic database.
|
dynamic-filter whitelist
|
Edits the Botnet Traffic Filter whitelist.
|
inspect dns dynamic-filter-snoop
|
Enables DNS inspection with Botnet Traffic Filter snooping.
|
name
|
Adds a name to the blacklist or whitelist.
|
show asp table dynamic-filter
|
Shows the Botnet Traffic Filter rules that are installed in the accelerated security path.
|
show dynamic-filter data
|
Shows information about the dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries.
|
show dynamic-filter dns-snoop
|
Shows the Botnet Traffic Filter DNS snooping summary, or with the detail keyword, the actual IP addresses and names.
|
show dynamic-filter reports
|
Generates reports of the top 10 botnet sites, ports, and infected hosts.
|
show dynamic-filter updater-client
|
Shows information about the updater server, including the server IP address, the next time the adaptive security appliance will connect with the server, and the database version last installed.
|
show running-config dynamic-filter
|
Shows the Botnet Traffic Filter running configuration.
|
show dynamic-filter updater-client
To show information about the Botnet Traffic Filter updater server, including the server IP address, the next time the adaptive security appliance will connect with the server, and the database version last installed, use the show dynamic-filter updater-client command in privileged EXEC mode.
show dynamic-filter updater-client
Syntax Description
This command has no arguments or keywords.
Command Default
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
|
8.2(1)
|
This command was introduced.
|
Examples
The following is sample output from the show dynamic-filter updater-client command:
hostname# show dynamic-filter updater-client
Traffic Filter updater client is enabled
Updater server url is https://10.15.80.240:446
Application name: trafmon, version: 1.0
0bb93985f42d941e50dc8f022350d1a8de96ba6c1f6d45f4bc0ead02a7d5990be32f483b
Next update is in 00:02:00
Database file version is '907' fetched at 22:51:41 UTC Oct 16 2006,
Related Commands
Command
|
Description
|
address
|
Adds an IP address to the blacklist or whitelist.
|
clear configure dynamic-filter
|
Clears the running Botnet Traffic Filter configuration.
|
clear dynamic-filter dns-snoop
|
Clears Botnet Traffic Filter DNS snooping data.
|
clear dynamic-filter reports
|
Clears Botnet Traffic filter report data.
|
clear dynamic-filter statistics
|
Clears Botnet Traffic filter statistics.
|
dns domain-lookup
|
Enables the adaptive security appliance to send DNS requests to a DNS server to perform a name lookup for supported commands.
|
dns server-group
|
Identifies a DNS server for the adaptive security appliance.
|
dynamic-filter blacklist
|
Edits the Botnet Traffic Filter blacklist.
|
dynamic-filter database fetch
|
Manually retrieves the Botnet Traffic Filter dynamic database.
|
dynamic-filter database find
|
Searches the dynamic database for a domain name or IP address.
|
dynamic-filter database purge
|
Manually deletes the Botnet Traffic Filter dynamic database.
|
dynamic-filter enable
|
Enables the Botnet Traffic Filter for a class of traffic or for all traffic if you do not specify an access list.
|
dynamic-filter updater-client enable
|
Enables downloading of the dynamic database.
|
dynamic-filter use-database
|
Enables use of the dynamic database.
|
dynamic-filter whitelist
|
Edits the Botnet Traffic Filter whitelist.
|
inspect dns dynamic-filter-snoop
|
Enables DNS inspection with Botnet Traffic Filter snooping.
|
name
|
Adds a name to the blacklist or whitelist.
|
show asp table dynamic-filter
|
Shows the Botnet Traffic Filter rules that are installed in the accelerated security path.
|
show dynamic-filter data
|
Shows information about the dynamic database, including when the dynamic database was last downloaded, the version of the database, how many entries the database contains, and 10 sample entries.
|
show dynamic-filter dns-snoop
|
Shows the Botnet Traffic Filter DNS snooping summary, or with the detail keyword, the actual IP addresses and names.
|
show dynamic-filter reports
|
Generates reports of the top 10 botnet sites, ports, and infected hosts.
|
show dynamic-filter statistics
|
Shows how many connections were monitored with the Botnet Traffic Filter, and how many of those connections match the whitelist, blacklist, and graylist.
|
show running-config dynamic-filter
|
Shows the Botnet Traffic Filter running configuration.
|
show eigrp events
To display the EIGRP event log, use the show eigrp events command in privileged EXEC mode.
show eigrp [as-number] events [{start end} | type]
Syntax Description
as-number
|
(Optional) Specifies the autonomous system number of the EIGRP process for which you are viewing the event log. Because the adaptive security appliance only supports one EIGRP routing process, you do not need to specify the autonomous system number.
|
end
|
(Optional) Limits the output to the entries with starting with the start index number and ending with the end index number.
|
start
|
(Optional) A number specifying the log entry index number. Specifying a start number causes the output to start with the specified event and end with the event specified by the end argument. Valid values are from 1 to 4294967295.
|
type
|
(Optional) Displays the events that are being logged.
|
Defaults
If a start and end is not specified, all log entries are shown.
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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
The show eigrp events output displays up to 500 events. Once the maximum number of events has been reached, new events are added to the bottom of the output and old events are removed from the top of the output.
You can use the clear eigrp events command to clear the EIGRP event log.
The show eigrp events type command displays the logging status of EIGRP events. By default, neighbor changes, neighbor warning, and DUAL FSM messages are logged. You can disable neighbor change event logging using the no eigrp log-neighbor-changes command. You can disable neighbor warning event logging using the no eigrp log-neighbor-warnings command. You cannot disable the logging of DUAL FSM events.
Examples
The following is sample output from the show eigrp events command:
hostname# show eigrp events
Event information for AS 100:
1 12:11:23.500 Change queue emptied, entries: 4
2 12:11:23.500 Metric set: 10.1.0.0/16 53760
3 12:11:23.500 Update reason, delay: new if 4294967295
4 12:11:23.500 Update sent, RD: 10.1.0.0/16 4294967295
5 12:11:23.500 Update reason, delay: metric chg 4294967295
6 12:11:23.500 Update sent, RD: 10.1.0.0/16 4294967295
7 12:11:23.500 Route install: 10.1.0.0/16 10.130.60.248
8 12:11:23.500 Find FS: 10.1.0.0/16 4294967295
9 12:11:23.500 Rcv update met/succmet: 53760 28160
10 12:11:23.500 Rcv update dest/nh: 10.1.0.0/16 10.130.60.248
11 12:11:23.500 Metric set: 10.1.0.0/16 4294967295
The following is sample output from the show eigrp events command with a start and stop number defined:
hostname# show eigrp events 3 8
Event information for AS 100:
3 12:11:23.500 Update reason, delay: new if 4294967295
4 12:11:23.500 Update sent, RD: 10.1.0.0/16 4294967295
5 12:11:23.500 Update reason, delay: metric chg 4294967295
6 12:11:23.500 Update sent, RD: 10.1.0.0/16 4294967295
7 12:11:23.500 Route install: 10.1.0.0/16 10.130.60.248
8 12:11:23.500 Find FS: 10.1.0.0/16 4294967295
The following is sample output from the show eigrp events command when there are no entries in the EIGRP event log:
hostname# show eigrp events
Event information for AS 100: Event log is empty.
The following is sample output from the show eigrp events type command:
hostname# show eigrp events type
EIGRP-IPv4 Event Logging for AS 100:
Related Commands
Command
|
Description
|
clear eigrp events
|
Clears the EIGRP event logging buffer.
|
eigrp log-neighbor-changes
|
Enables the logging of neighbor change events.
|
eigrp log-neighbor-warnings
|
Enables the logging of neighbor warning events.
|
show eigrp interfaces
To display the interfaces participating in EIGRP routing, use the show eigrp interfaces command in privileged EXEC mode.
show eigrp [as-number] interfaces [if-name] [detail]
Syntax Description
as-number
|
(Optional) Specifies the autonomous system number of the EIGRP process for which you are displaying active interfaces. Because the adaptive security appliance only supports one EIGRP routing process, you do not need to specify the autonomous system number.
|
detail
|
(Optional) Displays detail information.
|
if-name
|
(Optional) The name of an interface as specified by the nameif command. Specifying an interface name limits the display to the specified interface.
|
Defaults
If you do not specify an interface name, information for all EIGRP interfaces is displayed.
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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
Use the show eigrp interfaces command to determine on which interfaces EIGRP is active, and to learn information about EIGRP relating to those interfaces.
If an interface is specified, only that interface is displayed. Otherwise, all interfaces on which EIGRP is running are displayed.
If an autonomous system is specified, only the routing process for the specified autonomous system is displayed. Otherwise, all EIGRP processes are displayed.
Examples
The following is sample output from the show eigrp interfaces command:
hostname# show eigrp interfaces
EIGRP-IPv4 interfaces for process 100
Xmit Queue Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
outside 1 0/0 337 0/10 0 0
inside 1 0/0 10 1/63 103 0
Table 25-2 describes the significant fields shown in the display.
Table 25-2 show eigrp interfaces Field Descriptions
Field
|
Description
|
process
|
Autonomous system number for the EIGRP routing process.
|
Peers
|
Number of directly-connected peers.
|
Xmit Queue Un/Reliable
|
Number of packets remaining in the Unreliable and Reliable transmit queues.
|
Mean SRTT
|
Mean smooth round-trip time interval (in seconds).
|
Pacing Time Un/Reliable
|
Pacing time (in seconds) used to determine when EIGRP packets should be sent out the interface (unreliable and reliable packets).
|
Multicast Flow Timer
|
Maximum number of seconds in which the adaptive security appliance will send multicast EIGRP packets.
|
Pending Routes
|
Number of routes in the packets in the transmit queue waiting to be sent.
|
Related Commands
Command
|
Description
|
network
|
Defines the networks and interfaces that participate in the EIGRP routing process.
|
show eigrp neighbors
To display the EIGRP neighbor table, use the show eigrp neighbors command in privileged EXEC mode.
show eigrp [as-number] neighbors [detail | static] [if-name]
Syntax Description
as-number
|
(Optional) Specifies the autonomous system number of the EIGRP process for which you are deleting neighbor entries. Because the adaptive security appliance only supports one EIGRP routing process, you do not need to specify the autonomous system number.
|
detail
|
(Optional) Displays detail neighbor information.
|
if-name
|
(Optional) The name of an interface as specified by the nameif command. Specifying an interface name displays all neighbor table entries that were learned through that interface.
|
static
|
(Optional) Displays EIGRP neighbors that are statically defined using the neighbor command.
|
Defaults
If you do not specify an interface name, the neighbors learned through all interfaces are displayed.
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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
You can use the clear eigrp neighbors command to clear the dynamically-learned neighbors from the EIGRP neighbor table.
Static neighbors are not included in the output unless you use the static keyword.
Examples
The following is sample output from the show eigrp neighbors command:
hostname# show eigrp neighbors
EIGRP-IPv4 Neighbors for process 100
Address Interface Holdtime Uptime Q Seq SRTT RTO
(secs) (h:m:s) Count Num (ms) (ms)
172.16.81.28 Ethernet1 13 0:00:41 0 11 4 20
172.16.80.28 Ethernet0 14 0:02:01 0 10 12 24
172.16.80.31 Ethernet0 12 0:02:02 0 4 5 20
Table 25-2 describes the significant fields shown in the display.
Table 25-3 show eigrp neighbors Field Descriptions
Field
|
Description
|
process
|
Autonomous system number for the EIGRP routing process.
|
Address
|
IP address of the EIGRP neighbor.
|
Interface
|
Interface on which the adaptive security appliance receives hello packets from the neighbor.
|
Holdtime
|
Length of time (in seconds) that the adaptive security appliance waits to hear from the neighbor before declaring it down. This hold time is received from the neighbor in the hello packet, and begins decreasing until another hello packet is received from the neighbor.
If the neighbor is using the default hold time, this number will be less than 15. If the peer configures a non-default hold time, the non-default hold time will be displayed.
If this value reaches 0, the adaptive security appliance considers the neighbor unreachable.
|
Uptime
|
Elapsed time (in hours:minutes: seconds) since the adaptive security appliance first heard from this neighbor.
|
Q Count
|
Number of EIGRP packets (update, query, and reply) that the adaptive security appliance is waiting to send.
|
Seq Num
|
Sequence number of the last update, query, or reply packet that was received from the neighbor.
|
SRTT
|
Smooth round-trip time. This is the number of milliseconds required for an EIGRP packet to be sent to this neighbor and for the adaptive security appliance to receive an acknowledgment of that packet.
|
RTO
|
Retransmission timeout (in milliseconds). This is the amount of time the adaptive security appliance waits before resending a packet from the retransmission queue to a neighbor.
|
The following is sample output from the show eigrp neighbors static command:
hostname# show eigrp neighbors static
EIGRP-IPv4 neighbors for process 100
Table 25-4 describes the significant fields shown in the display.
Table 25-4 show ip eigrp neighbors static Field Descriptions
Field
|
Description
|
process
|
Autonomous system number for the EIGRP routing process.
|
Static Address
|
IP address of the EIGRP neighbor.
|
Interface
|
Interface on which the adaptive security appliance receives hello packets from the neighbor.
|
The following is sample output from the show eigrp neighbors detail command:
hostname# show eigrp neighbors detail
EIGRP-IPv4 neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq Tye
3 1.1.1.3 Et0/0 12 00:04:48 1832 5000 0 14
Version 12.2/1.2, Retrans: 0, Retries: 0
0 10.4.9.5 Fa0/0 11 00:04:07 768 4608 0 4 S
Version 12.2/1.2, Retrans: 0, Retries: 0
2 10.4.9.10 Fa0/0 13 1w0d 1 3000 0 6 S
Version 12.2/1.2, Retrans: 1, Retries: 0
1 10.4.9.6 Fa0/0 12 1w0d 1 3000 0 4 S
Version 12.2/1.2, Retrans: 1, Retries: 0
Table 25-5 describes the significant fields shown in the display.
Table 25-5 show ip eigrp neighbors details Field Descriptions
Field
|
Description
|
process
|
Autonomous system number for the EIGRP routing process.
|
H
|
This column lists the order in which a peering session was established with the specified neighbor. The order is specified with sequential numbering starting with 0.
|
Address
|
IP address of the EIGRP neighbor.
|
Interface
|
Interface on which the adaptive security appliance receives hello packets from the neighbor.
|
Holdtime
|
Length of time (in seconds) that the adaptive security appliance waits to hear from the neighbor before declaring it down. This hold time is received from the neighbor in the hello packet, and begins decreasing until another hello packet is received from the neighbor.
If the neighbor is using the default hold time, this number will be less than 15. If the peer configures a non-default hold time, the non-default hold time will be displayed.
If this value reaches 0, the adaptive security appliance considers the neighbor unreachable.
|
Uptime
|
Elapsed time (in hours:minutes: seconds) since the adaptive security appliance first heard from this neighbor.
|
SRTT
|
Smooth round-trip time. This is the number of milliseconds required for an EIGRP packet to be sent to this neighbor and for the adaptive security appliance to receive an acknowledgment of that packet.
|
RTO
|
Retransmission timeout (in milliseconds). This is the amount of time the adaptive security appliance waits before resending a packet from the retransmission queue to a neighbor.
|
Q Count
|
Number of EIGRP packets (update, query, and reply) that the adaptive security appliance is waiting to send.
|
Seq Num
|
Sequence number of the last update, query, or reply packet that was received from the neighbor.
|
Version
|
The software version that the specified peer is running.
|
Retrans
|
The number of times that a packet has been retransmitted.
|
Retries
|
The number of times an attempt was made to retransmit a packet.
|
Restart time
|
Elapsed time (in hours:minutes: seconds) since the specified neighbor has restarted.
|
Related Commands
Command
|
Description
|
clear eigrp neighbors
|
Clear the EIGRP neighbor table.
|
debug eigrp neighbors
|
Display EIGRP neighbor debug messages.
|
debug ip eigrp
|
Display EIGRP packet debug messages.
|
show eigrp topology
To display the EIGRP topology table, use the show eigrp topology command in privileged EXEC mode.
show eigrp [as-number] topology [ip-addr [mask] | active | all-links | pending | summary |
zero-successors]
Syntax Description
active
|
(Optional) Displays only active entries in the EIGRP topology table.
|
all-links
|
(Optional) Displays all routes in the EIGRP topology table, even those that are not feasible successors.
|
as-number
|
(Optional) Specifies the autonomous system number of the EIGRP process. Because the adaptive security appliance only supports one EIGRP routing process, you do not need to specify the autonomous system number.
|
ip-addr
|
(Optional) The IP address from the topology table to display. When specified with a mask, a detailed description of the entry is provided.
|
mask
|
(Optional) The network mask to apply to the ip-addr argument.
|
pending
|
(Optional) Displays all entries in the EIGRP topology table that are waiting for an update from a neighbor or are waiting to reply to a neighbor.
|
summary
|
(Optional) Displays a summary of the EIGRP topology table.
|
zero-successors
|
(Optional) Displays available routes in the EIGRP topology table.
|
Defaults
Only routes that are feasible successors are displayed. Use the all-links keyword to display all routes, including those that are not feasible successors.
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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
You can use the clear eigrp topology command to remove the dynamic entries from the topology table.
Examples
The following is sample output from the show eigrp topology command:
hostname# show eigrp topology
EIGRP-IPv4 Topology Table for AS(100)/ID(192.168.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
P 10.16.90.0 255.255.255.0, 2 successors, FD is 0
via 10.16.80.28 (46251776/46226176), Ethernet0
via 10.16.81.28 (46251776/46226176), Ethernet1
P 10.16.81.0 255.255.255.0, 1 successors, FD is 307200
via 10.16.81.28 (307200/281600), Ethernet1
via 10.16.80.28 (307200/281600), Ethernet0
Table 25-6 describes the significant fields shown in the displays.
Table 25-6 show eigrp topology Field Information
Field
|
Description
|
Codes
|
State of this topology table entry. Passive and Active refer to the EIGRP state with respect to this destination; Update, Query, and Reply refer to the type of packet that is being sent.
|
P - Passive
|
The route is known to be good and no EIGRP computations are being performed for this destination.
|
A - Active
|
EIGRP computations are being performed for this destination.
|
U - Update
|
Indicates that an update packet was sent to this destination.
|
Q - Query
|
Indicates that a query packet was sent to this destination.
|
R - Reply
|
Indicates that a reply packet was sent to this destination.
|
r - Reply status
|
Flag that is set after the software has sent a query and is waiting for a reply.
|
address mask
|
Destination IP address and mask.
|
successors
|
Number of successors. This number corresponds to the number of next hops in the IP routing table. If "successors" is capitalized, then the route or next hop is in a transition state.
|
FD
|
Feasible distance. The feasible distance is the best metric to reach the destination or the best metric that was known when the route went active. This value is used in the feasibility condition check. If the reported distance of the router (the metric after the slash) is less than the feasible distance, the feasibility condition is met and that path is a feasible successor. Once the software determines it has a feasible successor, it need not send a query for that destination.
|
via
|
IP address of the peer that told the software about this destination. The first n of these entries, where n is the number of successors, is the current successors. The remaining entries on the list are feasible successors.
|
(cost/adv_cost)
|
The first number is the EIGRP metric that represents the cost to the destination. The second number is the EIGRP metric that this peer advertised.
|
interface
|
The interface from which the information was learned.
|
The following is sample output from the show eigrp topology used with an IP address. The output shown is for an internal route.
hostname# show eigrp topology 10.2.1.0 255.255.255.0
EIGRP-IPv4 (AS 100): Topology Default-IP-Routing-Table(0) entry for entry for 10.2.1.0
255.255.255.0
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 281600
Routing Descriptor Blocks:
0.0.0.0 (Ethernet0/0), from Connected, Send flag is 0x0
Composite metric is (281600/0), Route is Internal
Minimum bandwidth is 10000 Kbit
Total delay is 1000 microseconds
The following is sample output from the show eigrp topology used with an IP address. The output shown is for an external route.
hostname# show eigrp topology 10.4.80.0 255.255.255.0
EIGRP-IPv4 (AS 100): Topology Default-IP-Routing-Table(0) entry for entry for 10.4.80.0
255.255.255.0
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 409600
Routing Descriptor Blocks:
10.2.1.1 (Ethernet0/0), from 10.2.1.1, Send flag is 0x0
Composite metric is (409600/128256), Route is External
Minimum bandwidth is 10000 Kbit
Total delay is 6000 microseconds
Originating router is 10.89.245.1
External protocol is Connected, external metric is 0
Administrator tag is 0 (0x00000000)
Related Commands
Command
|
Description
|
clear eigrp topology
|
Clears the dynamically discovered entries from the EIGRP topology table.
|
show eigrp traffic
To display the number of EIGRP packets sent and received, use the show eigrp traffic command in privileged EXEC mode.
show eigrp [as-number] traffic
Syntax Description
as-number
|
(Optional) Specifies the autonomous system number of the EIGRP process for which you are viewing the event log. Because the adaptive security appliance only supports one EIGRP routing process, you do not need to specify the autonomous system number.
|
Defaults
No default behaviors 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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
You can use the clear eigrp traffic command to clear the EIGRP traffic statistics.
Examples
The following is sample output from the show eigrp traffic command:
hostname# show eigrp traffic
EIGRP-IPv4 Traffic Statistics for AS 100
Hellos sent/received: 218/205
Updates sent/received: 7/23
Queries sent/received: 2/0
Replies sent/received: 0/2
Acks sent/received: 21/14
Input queue high water mark 0, 0 drops
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 1719439416
PDM Process ID: 1719439824
Table 25-4 describes the significant fields shown in the display.
Table 25-7 show eigrp traffic Field Descriptions
Field
|
Description
|
process
|
Autonomous system number for the EIGRP routing process.
|
Hellos sent/received
|
Number of hello packets sent and received.
|
Updates sent/received
|
Number of update packets sent and received.
|
Queries sent/received
|
Number of query packets sent and received.
|
Replies sent/received
|
Number of reply packets sent and received.
|
Acks sent/received
|
Number of acknowledgment packets sent and received.
|
Input queue high water mark/drops
|
Number of received packets that are approaching the maximum receive threshold and number of dropped packets.
|
SIA-Queries sent/received
|
Stuck in active queries sent and received.
|
SIA-Replies sent/received
|
Stuck in active replies sent and received.
|
Related Commands
Command
|
Description
|
debug eigrp packets
|
Displays debug information for EIGRP packets sent and received.
|
debug eigrp transmit
|
Displays debug information for EIGRP messages sent.
|
show failover
To display information about the failover status of the unit, use the show failover command in privileged EXEC mode.
show failover [group num | history | interface | state | statistics]
Syntax Description
group
|
Displays the running state of the specified failover group.
|
history
|
Displays failover history. The failover history displays past failover state changes and the reason for the state change. History information is cleared with the device is rebooted.
|
interface
|
Displays failover command and stateful link information.
|
num
|
Failover group number.
|
state
|
Displays the failover state of both failover units. The information displayed includes the primary or secondary status of the unit, the Active/Standby status of the unit, and the last reported reason for failover. The fail reason remains in the output even when the reason for failure is cleared.
|
statistics
|
Displays transmit and receive packet count of failover command interface.
|
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 modified. The output includes additional information.
|
Usage Guidelines
The show failover command displays the dynamic failover information, interface status, and Stateful Failover statistics. The Stateful Failover Logical Update Statistics output appears only when Stateful Failover is enabled. The "xerr" and "rerr" values do not indicate errors in failover, but rather the number of packet transmit or receive errors.
Note
Stateful Failover, and therefore Stateful Failover statistics output, is not available on the ASA 5505 adaptive adaptive security appliance.
In the show failover command output, the stateful failover fields have the following values:
•
Stateful Obj has these values:
–
xmit—Indicates the number of packets transmitted.
–
xerr—Indicates the number of transmit errors.
–
rcv—Indicates the number of packets received.
–
rerr—Indicates the number of receive errors.
•
Each row is for a particular object static count as follows:
–
General—Indicates the sum of all stateful objects.
–
sys cmd—Refers to the logical update system commands, such as login or stay alive.
–
up time—Indicates the value for the adaptive security appliance up time, which the active adaptive security appliance passes on to the standby adaptive security appliance.
–
RPC services—Remote Procedure Call connection information.
–
TCP conn—Dynamic TCP connection information.
–
UDP conn—Dynamic UDP connection information.
–
ARP tbl—Dynamic ARP table information.
–
Xlate_Timeout—Indicates connection translation timeout information.
–
VPN IKE upd—IKE connection information.
–
VPN IPSEC upd—IPSec connection information.
–
VPN CTCP upd—cTCP tunnel connection information.
–
VPN SDI upd—SDI AAA connection information.
–
VPN DHCP upd—Tunneled DHCP connection information.
–
SIP Sesson—SIP signalling session information.
If you do not enter a failover IP address, the show failover command displays 0.0.0.0 for the IP address, and monitoring of the interfaces remain in a "waiting" state. You must set a failover IP address for failover to work.
Table 25-8 describes the interface states for failover.
Table 25-8 Failover Interface States
State
|
Description
|
Normal
|
The interface is up and receiving hello packets from the corresponding interface on the peer unit.
|
Normal (Waiting)
|
The interface is up but has not yet received a hello packet from the corresponding interface on the peer unit. Verify that a standby IP address has been configured for the interface and that there is connectivity between the two interfaces.
|
Normal (Not-Monitored)
|
The interface is up but is not monitored by the failover process. The failure of an interface that is not monitored does not trigger failover.
|
No Link
|
The physical link is down.
|
No Link (Waiting)
|
The physical link is down and the interface has not yet received a hello packet from the corresponding interface on the peer unit. After restoring the link, verify that a standby IP address has been configured for the interface and that there is connectivity between the two interfaces.
|
No Link (Not-Monitored)
|
The physical link is down but is not monitored by the failover process. The failure of an interface that is not monitored does not trigger failover.
|
Link Down
|
The physical link is up, but the interface is administratively down.
|
Link Down (Waiting)
|
The physical link is up, but the interface is administratively down and the interface has not yet received a hello packet from the corresponding interface on the peer unit. After bringing the interface up (using the no shutdown command in interface configuration mode), verify that a standby IP address has been configured for the interface and that there is connectivity between the two interfaces.
|
Link Down (Not-Monitored)
|
The physical link is up, but the interface is administratively down but is not monitored by the failover process. The failure of an interface that is not monitored does not trigger failover.
|
Testing
|
The interface is in testing mode due to missed hello packets from the corresponding interface on the peer unit.
|
Failed
|
Interface testing has failed and the interface is marked as failed. If the interface failure causes the failover criteria to be met, then the interface failure causes a failover to the secondary unit or failover group.
|
In multiple configuration mode, only the show failover command is available in a security context; you cannot enter the optional keywords.
Examples
The following is sample output from the show failover command for Active/Standby Failover. The adaptive security appliances are ASA 5500 series adaptive adaptive security appliances, each equipped with a CSC SSM as shown in the details for slot 1 of each adaptive security appliance.
Cable status: N/A - LAN-based failover enabled
Failover LAN Interface: fover Ethernet2 (up)
Unit Poll frequency 1 seconds, holdtime 3 seconds
Interface Poll frequency 15 seconds
Monitored Interfaces 2 of 250 maximum
failover replication http
Last Failover at: 22:44:03 UTC Dec 8 2004
This host: Primary - Active
slot 0: ASA5520 hw/sw rev (1.0/7.1(0)10) status (Up Sys)
Interface inside (10.130.9.3): Normal
Interface outside (10.132.9.3): Normal
slot 1: ASA-SSM-20 hw/sw rev (1.0/CSC-SSM 5.0 (Build#1176)) status (Up/Up)
Logging port IP: 10.0.0.3/24
CSC-SSM, 5.0 (Build#1176)
Other host: Secondary - Standby Ready
slot 0: ASA5520 hw/sw rev (1.0/7.1(0)10) status (Up Sys)
Interface inside (10.130.9.4): Normal
Interface outside (10.132.9.4): Normal
slot 1: ASA-SSM-20 hw/sw rev (1.0/CSC-SSM 5.0 (Build#1176)) status (Up/Up)
Logging port IP: 10.0.0.4/24
CSC-SSM, 5.0 (Build#1176)
Stateful Failover Logical Update Statistics
Link : fover Ethernet2 (up)
Stateful Obj xmit xerr rcv rerr
Logical Update Queue Information
The following is sample output from the show failover command for Active/Active Failover:
Failover LAN Interface: third GigabitEthernet0/2 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 4 seconds
Monitored Interfaces 8 of 250 maximum
failover replication http
Group 1 last failover at: 13:40:18 UTC Dec 9 2004
Group 2 last failover at: 13:40:06 UTC Dec 9 2004
Group 2 State: Standby Ready
slot 0: ASA-5530 hw/sw rev (1.0/7.0(0)79) status (Up Sys)
slot 1: SSM-IDS-20 hw/sw rev (1.0/5.0(0.11)S91(0.11)) status (Up)
admin Interface outside (10.132.8.5): Normal
admin Interface third (10.132.9.5): Normal
admin Interface inside (10.130.8.5): Normal
admin Interface fourth (10.130.9.5): Normal
ctx1 Interface outside (10.1.1.1): Normal
ctx1 Interface inside (10.2.2.1): Normal
ctx2 Interface outside (10.3.3.2): Normal
ctx2 Interface inside (10.4.4.2): Normal
Group 1 State: Standby Ready
slot 0: ASA-5530 hw/sw rev (1.0/7.0(0)79) status (Up Sys)
slot 1: SSM-IDS-20 hw/sw rev (1.0/5.0(0.1)S91(0.1)) status (Up)
admin Interface outside (10.132.8.6): Normal
admin Interface third (10.132.9.6): Normal
admin Interface inside (10.130.8.6): Normal
admin Interface fourth (10.130.9.6): Normal
ctx1 Interface outside (10.1.1.2): Normal
ctx1 Interface inside (10.2.2.2): Normal
ctx2 Interface outside (10.3.3.1): Normal
ctx2 Interface inside (10.4.4.1): Normal
Stateful Failover Logical Update Statistics
Link : third GigabitEthernet0/2 (up)
Stateful Obj xmit xerr rcv rerr
Logical Update Queue Information
The following is sample output from the show failover command on the ASA 5505 series adaptive adaptive security appliance:
Failover LAN Interface: fover Vlan150 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Monitored Interfaces 4 of 250 maximum
Version: Ours 7.2(0)55, Mate 7.2(0)55
Last Failover at: 19:59:58 PST Apr 6 2006
This host: Primary - Active
slot 0: ASA5505 hw/sw rev (1.0/7.2(0)55) status (Up Sys)
Interface inside (192.168.1.1): Normal
Interface outside (192.168.2.201): Normal
Interface dmz (172.16.0.1): Normal
Interface test (172.23.62.138): Normal
Other host: Secondary - Standby Ready
slot 0: ASA5505 hw/sw rev (1.0/7.2(0)55) status (Up Sys)
Interface inside (192.168.1.2): Normal
Interface outside (192.168.2.211): Normal
Interface dmz (172.16.0.2): Normal
Interface test (172.23.62.137): Normal
The following is sample output from the show failover state command:
hostname# show failover state
====Configuration State===
====Communication State===
=========Failed Reason==============
Table 25-9 describes the output of the show failover state command.
Table 25-9 show failover state Output Description
Field
|
Description
|
My State
|
Displays the Primary/Secondary and Active/Standby status for the unit.
|
Other State
|
Displays the Primary/Secondary and Active/Standby status for peer unit.
|
Configuration State
|
Displays the state of configuration synchronization.
The following are possible configuration states for the standby unit:
• Config Syncing - STANDBY—Set while the synchronized configuration is being executed.
• Sync Done - STANDBY—Set when the standby unit has completed a configuration synchronization from the active unit.
The following are possible configuration states for the active unit:
• Config Syncing—Set on the active unit when it is performing a configuration synchronization to the standby unit.
• Sync Done—Set when the active unit has completed a successful configuration synchronization to the standby unit.
• Ready for Config Sync—Set on the active unit when the standby unit signals that it is ready to receive a configuration synchronization.
|
Communication State
|
Displays the status of the MAC address synchronization.
• Mac set—The MACs have been synchronized from the peer unit to this unit.
• Updated Mac—Used when a MAC address is updated and needs to be synchronized to the other unit. Also used during the transition period where the unit is updating the local MAC addresses synchronized from the peer unit.
|
Failed Reason
|
Displays the reason for the last reported failure. This information is not cleared, even if the failure condition is cleared. This information only changes when a failover occurs.
The following are possible fail reasons:
• Ifc Failure—The number of interfaces that failed met the failover criteria and caused failover.
• Comm Failure—The failover link failed or peer is down.
• Service card Failure—The SSM card failed (ASA only).
|
The following is sample output from the show failover history command:
hostname# show failover history
==========================================================================
From State To State Reason
==========================================================================
At 16:28:50 UTC Sep 9 2006
Not Detected Negotiation No Error
At 16:29:18 UTC Sep 9 2006
Negotiation Cold Standby Detected an Active mate
At 16:29:19 UTC Sep 9 2006
Cold Standby Sync Config Detected an Active mate
At 16:29:31 UTC Sep 9 2006
Sync Config Sync File System Detected an Active mate
At 16:29:31 UTC Sep 9 2006
Sync File System Bulk Sync Detected an Active mate
At 16:29:36 UTC Sep 9 2006
Bulk Sync Standby Ready Detected an Active mate
At 16:30:52 UTC Sep 9 2006
Standby Ready Just Active Set by the CI config cmd
At 16:30:52 UTC Sep 9 2006
Just Active Active Drain Set by the CI config cmd
At 16:30:52 UTC Sep 9 2006
Active Drain Active Applying Config Set by the CI config cmd
At 16:30:52 UTC Sep 9 2006
Active Applying Config Active Config Applied Set by the CI config cmd
At 16:30:52 UTC Sep 9 2006
Active Config Applied Active Set by the CI config cmd
At 16:30:55 UTC Sep 9 2006
Active Disabled Set by the CI config cmd
==========================================================================
Each entry provides the time and date the state change occurred, the beginning state, the resulting state, and the reason for the state change. The newest entries are located at the bottom of the display. Older entries appear at the top. A maximum of 60 entries can be displayed. Once the maximum number of entries has been reached, the oldest entries are removed from the top of the output as new entries are added to the bottom.
Table 25-10 shows the failover states. There are two types of states—stable and transient. Stable states are states that the unit can remain in until some occurrence, such as a failure, causes a state change. A transient state is a state that the unit passes through while reaching a stable state.
Table 25-10 Failover States
State
|
Description
|
Initialization
|
The unit checks platform capabilities and configuration and prepares the failover communication channels. This is a transient state.
|
Disabled
|
Failover is disabled. This is a stable state.
|
Negotiation
|
The unit establishes the connection with peer and negotiates with peer to determine software version compatibility and Active/Standby role. Depending upon the role that is negotiated, the unit will go through the Standby Unit States or the Active Unit States or enter the failed state. This is a transient state.
|
Failed
|
The unit is in the failed state. This is a stable state.
|
Standby Unit States
|
Cold Standby
|
The unit waits for the peer to reach the Active state. When the peer unit reaches the Active state, this unit progresses to the Standby Config state. This is a transient state.
|
Sync Config
|
The unit requests the running configuration from the peer unit. If an error occurs during the configuration synchronization, the unit returns to the Initialization state. This is a transient state.
|
Sync File System
|
The unit synchronizes the file system with the peer unit. This is a transient state.
|
Bulk Sync
|
The unit receives state information from the peer. This state only occurs when Stateful Failover is enabled. This is a transient state.
|
Standby Ready
|
The unit is ready to take over if the active unit fails. This is a stable state.
|
Active Unit States
|
Just Active
|
The first state the unit enters when becoming the active unit. During this state a message is sent to the peer alerting the peer that the unit is becoming active and the IP and MAC addresses are set for the interfaces. This is a transient state.
|
Active Drain
|
Queues messages from the peer are discarded. This is a transient state.
|
Active Applying Config
|
The unit is applying the system configuration. This is a transient state.
|
Active Config Applied
|
The unit has finished applying the system configuration. This is a transient state.
|
Active
|
The unit is active and processing traffic. This is a stable state.
|
Each state change is followed by a reason for the state change. The reason typically remains the same as the unit progresses through the transient states to the stable state. The following are the possible state change reasons:
•
No Error
•
Set by the CI config cmd
•
Failover state check
•
Failover interface become OK
•
HELLO not heard from mate
•
Other unit has different software version
•
Other unit operating mode is different
•
Other unit license is different
•
Other unit chassis configuration is different
•
Other unit card configuration is different
•
Other unit want me Active
•
Other unit want me Standby
•
Other unit reports that I am failed
•
Other unit reports that it is failed
•
Configuration mismatch
•
Detected an Active mate
•
No Active unit found
•
Configuration synchronization done
•
Recovered from communication failure
•
Other unit has different set of vlans configured
•
Unable to verify vlan configuration
•
Incomplete configuration synchronization
•
Configuration synchronization failed
•
Interface check
•
My communication failed
•
ACK not received for failover message
•
Other unit got stuck in learn state after sync
•
No power detected from peer
•
No failover cable
•
HA state progression failed
•
Detect service card failure
•
Service card in other unit has failed
•
My service card is as good as peer
•
LAN Interface become un-configured
•
Peer unit just reloaded
•
Switch from Serial Cable to LAN-Based fover
•
Unable to verify state of config sync
•
Auto-update request
•
Unknown reason
Related Commands
Command
|
Description
|
show running-config failover
|
Displays the failover commands in the current configuration.
|
show failover exec
To display the failover exec command mode for the specified unit, use the show failover exec command in privileged EXEC mode.
show failover exec {active | standby | mate}
Syntax Description
active
|
Displays the failover exec command mode for the active unit.
|
mate
|
Displays the failover exec command mode for the peer unit.
|
standby
|
Displays the failover exec command mode for the standby unit.
|
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
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
The failover exec command creates a session with the specified device. By default, that session is in global configuration mode. You can change the command mode of that session by sending the appropriate command (such as the interface command) using the failover exec command. Changing failover exec command modes for the specified device does not change the command mode for the session you are using to access the device. Changing commands modes for your current session to the device does not affect the command mode used by the failover exec command.
The show failover exec command displays the command mode on the specified device in which commands sent with the failover exec command are executed.
Examples
The following is sample output from the show failover exec command. This example demonstrates that the command mode for the unit where the failover exec commands are being entered does not have to be the same as the failover exec command mode where the commands are being executed.
In this example, an administrator logged into the standby unit adds a name to an interface on the active unit. The second time the show failover exec mate command is entered in this example shows the peer device in interface configuration mode. Commands sent to the device with the failover exec command are executed in that mode.
hostname(config)# show failover exec mate
Active unit Failover EXEC is at config mode
! The following command changes the standby unit failover exec mode
! to interface configuration mode.
hostname(config)# failover exec mate interface GigabitEthernet0/1
hostname(config)# show failover exec mate
Active unit Failover EXEC is at interface sub-command mode
! Because the following command is sent to the active unit, it is replicated
! back to the standby unit.
hostname(config)# failover exec mate nameif test
Related Commands
Command
|
Description
|
failover exec
|
Executes the supplied command on the designated unit in a failover pair.
|
show file
To display information about the file system, use the show file command in privileged EXEC mode.
show file descriptors | system | information filename
Syntax Description
descriptors
|
Displays all open file descriptors.
|
filename
|
Specifies the filename.
|
information
|
Displays information about a specific file, including partner application package files.
|
system
|
Displays the size, bytes available, type of media, flags, and prefix information about the disk file system.
|
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.
|
8.2(1)
|
The capability to view information about partner application package files was added.
|
Examples
The following is sample output from the show file descriptors command:
hostname# show file descriptors
hostname# show file system
Size(b) Free(b) Type Flags Prefixes
* 60985344 60973056 disk rw disk:
The following is sample output fromthe show file info command:
hostname# show file info disk0:csc_embd1.0.1000.pkg
file size is 17204149 bytes version 1
Related Commands
Command
|
Description
|
dir
|
Displays the directory contents.
|
pwd
|
Displays the current working directory.
|
show firewall
To show the current firewall mode (routed or transparent), use the show firewall command in privileged EXEC mode.
show firewall
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.
|
Examples
The following is sample output from the show firewall command:
Related Commands
Command
|
Description
|
firewall transparent
|
Sets the firewall mode.
|
show mode
|
Shows the current context mode, either single or multiple.
|
show flash
To display the contents of the internal Flash memory, use the show flash: command in privileged EXEC mode.
show flash:
Note
In the ASA 5500 series adaptive security appliances, the flash keyword is aliased to disk0.
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.
|
Examples
The following is sample output from the show flash: command:
-#- --length-- -----date/time------ path
11 1301 Feb 21 2005 18:01:34 test.cfg
12 1949 Feb 21 2005 20:13:36 pepsi.cfg
13 2551 Jan 06 2005 10:07:36 Leo.cfg
14 609223 Jan 21 2005 07:14:18 rr.cfg
15 1619 Jul 16 2004 16:06:48 hackers.cfg
16 3184 Aug 03 2004 07:07:00 old_running.cfg
17 4787 Mar 04 2005 12:32:18 admin.cfg
20 1792 Jan 21 2005 07:29:24 Marketing.cfg
21 7765184 Mar 07 2005 19:38:30 asdmfile-RLK
22 1674 Nov 11 2004 02:47:52 potts.cfg
23 1863 Jan 21 2005 07:29:18 r.cfg
24 1197 Jan 19 2005 08:17:48 tst.cfg
25 608554 Jan 13 2005 06:20:54 500kconfig
26 5124096 Feb 20 2005 08:49:28 cdisk70102
27 5124096 Mar 01 2005 17:59:56 cdisk70104
28 2074 Jan 13 2005 08:13:26 negateACL
29 5124096 Mar 07 2005 19:56:58 cdisk70105
30 1276 Jan 28 2005 08:31:58 steel
31 7756788 Feb 24 2005 12:59:46 asdmfile.50074.dbg
32 7579792 Mar 08 2005 11:06:56 asdmfile.gusingh
33 7764344 Mar 04 2005 12:17:46 asdmfile.50075.dbg
34 5124096 Feb 24 2005 11:50:50 cdisk70103
35 15322 Mar 04 2005 12:30:24 hs_err_pid2240.log
10170368 bytes available (52711424 bytes used)
Related Commands
Command
|
Description
|
dir
|
Displays the directory contents.
|
show disk0:
|
Displays the contents of the internal Flash memory.
|
show disk1:
|
Displays the contents of the external Flash memory card.
|
show flow-export counters
To display runtime counters associated with NetFlow data, use the show flow-export counters command in privileged EXEC mode.
show flow-export counters
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
|
8.1(1)
|
This command was introduced.
|
Usage Guidelines
The runtime counters include statistical data as well as error data.
Examples
The following is sample output from the show flow-export counters command that shows runtime counters that are associated with NetFlow data:
hostname# show flow-export counters
destination: inside 209.165.200.224 2055
block allocation failure 0
Related Commands
Commands
|
Description
|
clear flow-export counters
|
Resets all runtime counters in NetFlow to zero.
|
flow-export destination interface-name ipv4-address | hostname udp-port
|
Specifies the IP address or hostname of the NetFlow collector, and the UDP port on which the NetFlow collector is listening.
|
flow-export template timeout-rate minutes
|
Controls the interval at which the template information is sent to the NetFlow collector.
|
logging flow-export-syslogs enable
|
Enables syslog messages after you have entered the logging flow-export-syslogs disable command, and the syslog messages that are associated with NetFlow data.
|
show fragment
To display the operational data of the IP fragment reassembly module, enter the show fragment command in privileged EXEC mode.
show fragment [interface]
Syntax Description
interface
|
(Optional) Specifies the adaptive security appliance interface.
|
Defaults
If an interface is not specified, the command applies to all interfaces.
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 mode
|
•
|
•
|
•
|
•
|
•
|
Command History
Release
|
Modification
|
7.0(1)
|
The command was separated into two commands, show fragment and show running-config fragment, to separate the configuration data from the operational data.
|
Examples
This example shows how to display the operational data of the IP fragment reassembly module:
Size: 200, Chain: 24, Timeout: 5, Threshold: 133
Queue: 0, Assembled: 0, Fail: 0, Overflow: 0
Size: 200, Chain: 24, Timeout: 5, Threshold: 133
Queue: 0, Assembled: 0, Fail: 0, Overflow: 0
Size: 200, Chain: 24, Timeout: 5, Threshold: 133
Queue: 0, Assembled: 0, Fail: 0, Overflow: 0
Size: 200, Chain: 24, Timeout: 5, Threshold: 133
Queue: 0, Assembled: 0, Fail: 0, Overflow: 0
Related Commands
Command
|
Description
|
clear configure fragment
|
Clears the IP fragment reassembly configuration and resets the defaults.
|
clear fragment
|
Clears the operational data of the IP fragment reassembly module.
|
fragment
|
Provides additional management of packet fragmentation and improves compatibility with NFS.
|
show running-config fragment
|
Displays the IP fragment reassembly configuration.
|
show gc
To display the garbage collection process statistics, use the show gc command in privileged EXEC mode.
show gc
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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Privileged EXEC
|
•
|
•
|
•
|
•
|
•
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Examples
The following is sample output from the show gc command:
Garbage collection process stats:
Total tcp conn delete response : 0
Total udp conn delete response : 0
Total number of zombie cleaned : 0
Total number of embryonic conn cleaned : 0
Total queries generated : 0
Total queries with conn present response : 0
Total number of sweeps : 946
Total number of invalid vcid : 0
Total number of zombie vcid : 0
Related Commands
Command
|
Description
|
clear gc
|
Removes the garbage collection process statistics.
|
show h225
To display information for H.225 sessions established across the adaptive security appliance, use the show h225 command in privileged EXEC mode.
show h225
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
The show h225 command displays information for H.225 sessions established across the adaptive security appliance. Along with the debug h323 h225 event, debug h323 h245 event, and show local-host commands, this command is used for troubleshooting H.323 inspection engine issues.
Before using the show h225, show h245, or show h323-ras commands, we recommend that you configure the pager command. If there are a lot of session records and the pager command is not configured, it may take a while for the show output to reach its end. If there is an abnormally large number of connections, check that the sessions are timing out based on the default timeout values or the values set by you. If they are not, then there is a problem that needs to be investigated.
Examples
The following is sample output from the show h225 command:
| Local: | 10.130.56.3/1040 | Foreign: 172.30.254.203/1720
| Local: | 10.130.56.3/1040 | Foreign: 172.30.254.203/1720
| Local: | 10.130.56.4/1050 | Foreign: 172.30.254.205/1720
This output indicates that there is currently 1 active H.323 call going through the adaptive security appliance between the local endpoint 10.130.56.3 and foreign host 172.30.254.203, and for these particular endpoints, there is 1 concurrent call between them, with a CRV (Call Reference Value) for that call of 9861.
For the local endpoint 10.130.56.4 and foreign host 172.30.254.205, there are 0 concurrent Calls. This means that there is no active call between the endpoints even though the H.225 session still exists. This could happen if, at the time of the show h225 command, the call has already ended but the H.225 session has not yet been deleted. Alternately, it could mean that the two endpoints still have a TCP connection opened between them because they set "maintainConnection" to TRUE, so the session is kept open until they set it to FALSE again, or until the session times out based on the H.225 timeout value in your configuration.
Related Commands
Commands
|
Description
|
debug h323
|
Enables the display of debug information for H.323.
|
inspect h323
|
Enables H.323 application inspection.
|
show h245
|
Displays information for H.245 sessions established across the adaptive security appliance by endpoints using slow start.
|
show h323-ras
|
Displays information for H.323 RAS sessions established across the adaptive security appliance.
|
timeout h225 | h323
|
Configures idle time after which an H.225 signalling connection or an H.323 control connection will be closed.
|
show h245
To display information for H.245 sessions established across the adaptive security appliance by endpoints using slow start, use the show h245 command in privileged EXEC mode.
show h245
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
The show h245 command displays information for H.245 sessions established across the adaptive security appliance by endpoints using slow start. (Slow start is when the two endpoints of a call open another TCP control channel for H.245. Fast start is where the H.245 messages are exchanged as part of the H.225 messages on the H.225 control channel.) Along with the debug h323 h245 event, debug h323 h225 event, and show local-host commands, this command is used for troubleshooting H.323 inspection engine issues.
Examples
The following is sample output from the show h245 command:
| LOCAL | TPKT | FOREIGN | TPKT
1 | 10.130.56.3/1041 | 0 | 172.30.254.203/1245 | 0
| MEDIA: LCN 258 Foreign 172.30.254.203 RTP 49608 RTCP 49609
| Local | 10.130.56.3 RTP 49608 RTCP 49609
| MEDIA: LCN 259 Foreign 172.30.254.203 RTP 49606 RTCP 49607
| Local | 10.130.56.3 RTP 49606 RTCP 49607
There is currently one H.245 control session active across the adaptive security appliance. The local endpoint is 10.130.56.3, and we are expecting the next packet from this endpoint to have a TPKT header because the TPKT value is 0. (The TKTP header is a 4-byte header preceding each H.225/H.245 message. It gives the length of the message, including the 4-byte header.) The foreign host endpoint is 172.30.254.203, and we are expecting the next packet from this endpoint to have a TPKT header because the TPKT value is 0.
The media negotiated between these endpoints have a LCN (logical channel number) of 258 with the foreign RTP IP address/port pair of 172.30.254.203/49608 and a RTCP IP address/port of 172.30.254.203/49609 with a local RTP IP address/port pair of 10.130.56.3/49608 and a RTCP port of 49609.
The second LCN of 259 has a foreign RTP IP address/port pair of 172.30.254.203/49606 and a RTCP IP address/port pair of 172.30.254.203/49607 with a local RTP IP address/port pair of 10.130.56.3/49606 and RTCP port of 49607.
Related Commands
Commands
|
Description
|
debug h323
|
Enables the display of debug information for H.323.
|
inspect h323
|
Enables H.323 application inspection.
|
show h245
|
Displays information for H.245 sessions established across the adaptive security appliance by endpoints using slow start.
|
show h323-ras
|
Displays information for H.323 RAS sessions established across the adaptive security appliance.
|
timeout h225 | h323
|
Configures idle time after which an H.225 signalling connection or an H.323 control connection will be closed.
|
show h323-ras
To display information for H.323 RAS sessions established across the adaptive security appliance between a gatekeeper and its H.323 endpoint, use the show h323-ras command in privileged EXEC mode.
show h323-ras
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
The show h323-ras command displays information for H.323 RAS sessions established across the adaptive security appliance between a gatekeeper and its H.323 endpoint. Along with the debug h323 ras event and show local-host commands, this command is used for troubleshooting H.323 RAS inspection engine issues.
The show h323-ras command displays connection information for troubleshooting H.323 inspection engine issues, and is described in the inspect protocol h323 {h225 | ras} command page.
Examples
The following is sample output from the show h323-ras command:
| 172.30.254.214 10.130.56.14
This output shows that there is one active registration between the gatekeeper 172.30.254.214 and its client 10.130.56.14.
Related Commands
Commands
|
Description
|
debug h323
|
Enables the display of debug information for H.323.
|
inspect h323
|
Enables H.323 application inspection.
|
show h245
|
Displays information for H.245 sessions established across the adaptive security appliance by endpoints using slow start.
|
show h323-ras
|
Displays information for H.323 RAS sessions established across the adaptive security appliance.
|
timeout h225 | h323
|
Configures idle time after which an H.225 signalling connection or an H.323 control connection will be closed.
|
show history
To display the previously entered commands, use the show history command in user EXEC mode.
show history
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
|
User EXEC
|
•
|
•
|
•
|
•
|
•
|
Command History
Release
|
Modification
|
Preexisting
|
This command was preexisting.
|
Usage Guidelines
The show history command lets you display previously entered commands. You can examine commands individually with the up and down arrows, enter ^p to display previously entered lines, or enter ^n to display the next line.
Examples
The following example shows sample output from the show history command in user EXEC mode:
The following example shows sample output from the show history command in privileged EXEC mode:
The following example shows sample output from the show history command in global configuration mode:
hostname(config)# show history
Related Commands
Command
|
Description
|
help
|
Displays help information for the command specified.
|
show icmp
To display the ICMP configuration, use the show icmp command in privileged EXEC mode.
show icmp
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 previously existing.
|
Usage Guidelines
The show icmp command displays the ICMP configuration.
Examples
The following example shows the ICMP configuration:
Related Commands
clear configure icmp
|
Clears the ICMP configuration.
|
debug icmp
|
Enables the display of debug information for ICMP.
|
icmp
|
Configures access rules for ICMP traffic that terminates at a adaptive security appliance interface.
|
inspect icmp
|
Enables or disables the ICMP inspection engine.
|
timeout icmp
|
Configures the idle timeout for ICMP.
|
show idb
To display information about the status of interface descriptor blocks, use the show idb command in privileged EXEC mode.
show idb
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
|
User EXEC
|
•
|
•
|
•
|
—
|
•
|
Command History
Release
|
Modification
|
7.0(1)
|
This command was introduced.
|
Usage Guidelines
IDBs are the internal data structure representing interface resources. See the "Examples" section for a description of the display output.
Examples
The following is sample output from the show idb command:
Maximum number of Software IDBs 280. In use 23.
Size each (bytes) 116 212
HWIDB# 1 0xbb68ebc Control0/0
HWIDB# 2 0xcd47d84 GigabitEthernet0/0
HWIDB# 3 0xcd4c1dc GigabitEthernet0/1
HWIDB# 4 0xcd5063c GigabitEthernet0/2
HWIDB# 5 0xcd54a9c GigabitEthernet0/3
HWIDB# 6 0xcd58f04 Management0/0
SWIDB# 1 0x0bb68f54 0x01010001 Control0/0
SWIDB# 2 0x0cd47e1c 0xffffffff GigabitEthernet0/0
SWIDB# 3 0x0cd772b4 0xffffffff GigabitEthernet0/0.1
PEER IDB# 1 0x0d44109c 0xffffffff 3 GigabitEthernet0/0.1
PEER IDB# 2 0x0d2c0674 0x00020002 2 GigabitEthernet0/0.1
PEER IDB# 3 0x0d05a084 0x00010001 1 GigabitEthernet0/0.1
SWIDB# 4 0x0bb7501c 0xffffffff GigabitEthernet0/0.2
SWIDB# 5 0x0cd4c274 0xffffffff GigabitEthernet0/1
SWIDB# 6 0x0bb75704 0xffffffff GigabitEthernet0/1.1
PEER IDB# 1 0x0cf8686c 0x00020003 2 GigabitEthernet0/1.1
SWIDB# 7 0x0bb75dec 0xffffffff GigabitEthernet0/1.2
PEER IDB# 1 0x0d2c08ac 0xffffffff 2 GigabitEthernet0/1.2
SWIDB# 8 0x0bb764d4 0xffffffff GigabitEthernet0/1.3
PEER IDB# 1 0x0d441294 0x00030001 3 GigabitEthernet0/1.3
SWIDB# 9 0x0cd506d4 0x01010002 GigabitEthernet0/2
SWIDB# 10 0x0cd54b34 0xffffffff GigabitEthernet0/3
PEER IDB# 1 0x0d3291ec 0x00030002 3 GigabitEthernet0/3
PEER IDB# 2 0x0d2c0aa4 0x00020001 2 GigabitEthernet0/3
PEER IDB# 3 0x0d05a474 0x00010002 1 GigabitEthernet0/3
SWIDB# 11 0x0cd58f9c 0xffffffff Management0/0
PEER IDB# 1 0x0d05a65c 0x00010003 1 Management0/0
Table 25-1 shows each field description.
Table 25-11 show idb stats Fields
Field
|
Description
|
HWIDBs
|
Shows the statistics for all HWIDBs. HWIDBs are created for each hardware port in the system.
|
SWIDBs
|
Shows the statistics for all SWIDBs. SWIDBs are created for each main and subinterface in the system, and for each interface that is allocated to a context.
Some other internal software modules also create IDBs.
|
HWIDB#
|
Specifies a hardware interface entry. The IDB sequence number, address, and interface name is displayed in each line.
|
SWIDB#
|
Specifies a software interface entry. The IDB sequence number, address, corresponding vPif id, and interface name are displayed in each line.
|
PEER IDB#
|
Specifies an interface allocated to a context. The IDB sequence number, address, corresponding vPif id, context id and interface name are displayed in each line.
|
Related Commands
Command
|
Description
|
interface
|
Configures an interface and enters interface configuration mode.
|
show interface
|
Displays the runtime status and statistics of interfaces.
|
show igmp groups
To display the multicast groups with receivers that are directly connected to the adaptive security appliance and that were learned through IGMP, use the show igmp groups command in privileged EXEC mode.
show igmp groups [[reserved | group] [if_name] [detail]] | summary]
Syntax Description
detail
|
(Optional) Provides a detailed description of the sources.
|
group
|
(Optional) The address of an IGMP group. Including this optional argument limits the display to the specified group.
|
if_name
|
(Optional) Displays group information for the specified interface.
|
reserved
|
(Optional) Displays information about reserved groups.
|
summary
|
(Optional) Displays group joins summary information.
|
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
If you omit all optional arguments and keywords, the show igmp groups command displays all directly connected multicast groups by group address, interface type, and interface number.
Examples
The following is sample output from the show igmp groups command:
hostname#show igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
224.1.1.1 inside 00:00:53 00:03:26 192.168.1.6
Related Commands
Command
|
Description
|
show igmp interface
|
Displays multicast information for an interface.
|
show igmp interface
To display multicast information for an interface, use the show igmp interface command in privileged EXEC mode.
show igmp interface [if_name]
Syntax Description
if_name
|
(Optional) Displays IGMP group information for the selected interface.
|
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 modified. The detail keyword was removed.
|
Usage Guidelines
If you omit the optional if_name argument, the show igmp interface command displays information about all interfaces.
Examples
The following is sample output from the show igmp interface command:
hostname# show igmp interface inside
inside is up, line protocol is up
Internet address is 192.168.37.6, subnet mask is 255.255.255.0
IGMP is enabled on interface
IGMP query interval is 60 seconds
Inbound IGMP access group is not set
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 192.168.37.33
No multicast groups joined
Related Commands
Command
|
Description
|
show igmp groups
|
Displays the multicast groups with receivers that are directly connected to the adaptive security appliance and that were learned through IGMP.
|
show igmp traffic
To display IGMP traffic statistics, use the show igmp traffic command in privileged EXEC mode.
show igmp traffic
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.
|
Examples
The following is sample output from the show igmp traffic command:
hostname# show igmp traffic
Elapsed time since counters cleared: 00:02:30
Related Commands
Command
|
Description
|
clear igmp counters
|
Clears all IGMP statistic counters.
|
clear igmp traffic
|
Clear the IGMP traffic counters.
|
show import webvpn
To list the WebVPN custom data and plug-ins that currently are present in flash memory on the adaptive security appliance, enter the show import webvpn (option) command in privileged EXEC mode.
show import webvpn | customization | plug-in | translation-table | url-list | webcontent
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 mode
|
•
|
—
|
•
|
—
|
—
|
Command History
Release
|
Modification
|
8.0(2)
|
This command was introduced.
|
Usage Guidelines
Use the show import webvpn command to identify the custom data and the Java-based client applications available to WebVPN users. The displayed list itemizes all of the requested data types that are in flash memory on the adaptive security appliance.
Each of the show import webvpn command displays the following currently loaded WebVPN data:
•
Customization - customization object (file names base64 decoded)
•
Plug-in - Third-party Java-based client applications (SSH, VNC, and RDP)
•
Translation Table - Localization/internationalization dictionary tables
•
URL-list - URL list objects (file names base64 decoded)
•
Web content - disk0:/csco_config/htms recursively (all files full names)
Example
The following illustrates the WebVPN data displayed by various show import webvpn command:
hostname# show import webvpn plug-in
hostname# show import webvpn customization
hostname# show import webvpn translation-table
Translation Tables' Templates:
hostname# show import webvpn url-list
No bookmarks are currently defined
hostname# show import webvpn webcontent
No custom webcontent is loaded
Related Commands
Command
|
Description
|
revert webvpn all
|
Removes all WebVPN data and plug-in current on the adaptive security appliance.
|
show interface
To view interface statistics, use the show interface command in privileged EXEC mode.
show interface [{physical_interface | redundantnumber}[.subinterface] | mapped_name |
interface_name | vlan number] [stats | detail]
Syntax Description
detail
|
(Optional) Shows detailed interface information, including the order in which the interface was added, the configured state, the actual state, and asymmetrical routing statistics, if enabled by the asr-group command. If you show all interfaces, then information about the internal interfaces for SSMs displays, if installed on the ASA 5500 series adaptive security appliance. The internal interface is not user-configurable, and the information is for debugging purposes only.
|
interface_name
|
(Optional) Identifies the interface name set with the nameif command.
|
mapped_name
|
(Optional) In multiple context mode, identifies the mapped name if it was assigned using the allocate-interface command.
|
physical_interface
|
(Optional) Identifies the interface ID, such as gigabitethernet 0/1. See the interface command for accepted values.
|
redundantnumber
|
(Optional) Identifies the redundant interface ID, such as redundant1.
|
stats
|
(Default) Shows interface information and statistics. This keyword is the default, so this keyword is optional.
|
subinterface
|
(Optional) Identifies an integer between 1 and 4294967293 designating a logical subinterface.
|
vlan number
|
(Optional) For models with a built-in switch, such as the ASA 5505 adaptive security appliance, specifies the VLAN interface.
|
Defaults
If you do not identify any options, this command shows basic statistics for all interfaces.
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 the new interface numbering scheme, and to add the stats keyword for clarity, and the detail keyword.
|
7.0(4)
|
This command added support for the 4GE SSM interfaces.
|
7.2(1)
|
This command added support for switch interfaces.
|
8.0(2)
|
This command added support for redundant interfaces. Also, the delay is added for subinterfaces. Two new counters were added: input reset drops and output reset drops.
|
8.2(1)
|
The no buffer number was changed to show the number of failures from block allocations.
|
Usage Guidelines
If an interface is shared among contexts, and you enter this command within a context, the adaptive security appliance shows only statistics for the current context. When you enter this command in the system execution space for a physical interface, the adaptive security appliance shows the combined statistics for all contexts.
The number of statistics shown for subinterfaces is a subset of the number of statistics shown for a physical interface.
You cannot use the interface name in the system execution space, because the nameif command is only available within a context. Similarly, if you mapped the interface ID to a mapped name using the allocate-interface command, you can only use the mapped name in a context. If you set the visible keyword in the allocate-interface command, the adaptive security appliance shows the interface ID in the output of the show interface command.

Note
The number of bytes transmitted or received in the Hardware count and the Traffic Statistics count are different.
In the hardware count, the amount is retrieved directly from hardware, and reflects the Layer 2 packet size. While in traffic statistics, it reflects the Layer 3 packet size.
The count difference is varied based upon the design of the interface card hardware.
For example, for a Fast Ethernet card, the Layer 2 count is 14 bytes greater than the traffic count, because it includes the Ethernet header. On the Gigabit Ethernet card, the Layer 2 count is 18 bytes greater than the traffic count, because it includes both the Ethernet header and the CRC.
See the "Examples" section for a description of the display output.
Examples
The following is sample output from the show interface command:
Interface GigabitEthernet0/0 "outside", is up, line protocol is up
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)
MAC address 000b.fcf8.c44e, MTU 1500
IP address 10.86.194.60, subnet mask 255.255.254.0
1328522 packets input, 124426545 bytes, 0 no buffer
Received 1215464 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
124606 packets output, 86803402 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (curr/max packets): hardware (0/7)
output queue (curr/max packets): hardware (0/13)
Traffic Statistics for "outside":
1328509 packets input, 99873203 bytes
124606 packets output, 84502975 bytes
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface GigabitEthernet0/1 "inside", is administratively down, line protocol is down
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
MAC address 000b.fcf8.c44f, MTU 1500
IP address 10.10.0.1, subnet mask 255.255.0.0
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (curr/max packets): hardware (0/0)
output queue (curr/max packets): hardware (0/0)
Traffic Statistics for "inside":
0 packets output, 0 bytes
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface GigabitEthernet0/2 "faillink", is administratively down, line protocol is down
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
Description: LAN/STATE Failover Interface
MAC address 000b.fcf8.c450, MTU 1500
IP address 192.168.1.1, subnet mask 255.255.255.0
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (curr/max packets): hardware (0/0)
output queue (curr/max packets): hardware (0/0)
Traffic Statistics for "faillink":
1 packets output, 28 bytes
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Interface GigabitEthernet0/3 "", is administratively down, line protocol is down
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
Active member of Redundant5
MAC address 000b.fcf8.c451, MTU not set
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (curr/max packets): hardware (0/0)
output queue (curr/max packets): hardware (0/0)
Interface Management0/0 "", is administratively down, line protocol is down
Hardware is i82557, BW 100 Mbps, DLY 1000 usec
Available but not configured via nameif
MAC address 000b.fcf8.c44d, MTU not set
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max packets): hardware (128/128) software (0/0)
output queue (curr/max packets): hardware (0/0) software (0/0)
Interface Redundant1 "", is down, line protocol is down
Interface Redundant5 "redundant", is administratively down, line protocol is down
Hardware is i82546GB rev03, BW 1000 Mbps, DLY 1000 usec
MAC address 000b.fcf8.c451, MTU 1500
IP address 10.2.3.5, subnet mask 255.255.255.0
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (curr/max packets): hardware (0/0) software (0/0)
output queue (curr/max packets): hardware (0/0) software (0/0)
Traffic Statistics for "redundant":
0 packets output, 0 bytes
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
Member GigabitEthernet0/3(Active), GigabitEthernet0/2
Last switchover at 15:15:26 UTC Oct 24 2006
Interface Redundant5.1 "", is down, line protocol is down
Available but not configured with VLAN or via nameif
Table 25-12 shows each field description.
Table 25-12 show interface Fields
Field
|
Description
|
Interface ID
|
The interface ID. Within a context, the adaptive security appliance shows the mapped name (if configured), unless you set the allocate-interface command visible keyword.
|
"interface_name"
|
The interface name set with the nameif command. In the system execution space, this field is blank because you cannot set the name in the system. If you do not configure a name, the following message appears after the Hardware line:
Available but not configured via nameif
|
is state
|
The administrative state, as follows:
• up—The interface is not shut down.
• administratively down—The interface is shut down with the shutdown command.
|
Line protocol is state
|
The line status, as follows:
• up—A working cable is plugged into the network interface.
• down—Either the cable is incorrect or not plugged into the interface connector.
|
VLAN identifier
|
For subinterfaces, the VLAN ID.
|
Hardware
|
The interface type, maximum bandwidth, delay, duplex, and speed. When the link is down, the duplex and speed show the configured values. When the link is up, these fields show the configured values with the actual settings in parentheses. The following list describes the common hardware types:
• i82542 - Intel PCI Fiber Gigabit card used on PIX platforms
• i82543 - Intel PCI-X Fiber Gigabit card used on PIX platforms
• i82546GB - Intel PCI-X Copper Gigabit used on ASA platforms
• i82547GI - Intel CSA Copper Gigabit used as backplane on ASA platforms
• i82557 - Intel PCI Copper Fast Ethernet used on ASA platforms
• i82559 - Intel PCI Copper Fast Ethernet used on PIX platforms
• VCS7380 - Vitesse Four Port Gigabit Switch used in SSM-4GE
|
Media-type
|
(For 4GE SSM interfaces only) Shows if the interface is set as RJ-45 or SFP.
|
message area
|
A message might be displayed in some circumstances. See the following examples:
• In the system execution space, you might see the following message:
Available for allocation to a context
• If you do not configure a name, you see the following message:
Available but not configured via nameif
• If an interface is a member of a redundant interface, you see the following message:
Active member of Redundant5
|
MAC address
|
The interface MAC address.
|
MTU
|
The maximum size, in bytes, of packets allowed on this interface. If you do not set the interface name, this field shows "MTU not set."
|
IP address
|
The interface IP address set using the ip address command or received from a DHCP server. In the system execution space, this field shows "IP address unassigned" because you cannot set the IP address in the system.
|
Subnet mask
|
The subnet mask for the IP address.
|
Packets input
|
The number of packets received on this interface.
|
Bytes
|
The number of bytes received on this interface.
|
No buffer
|
The number of failures from block allocations.
|
Received:
|
|
Broadcasts
|
The number of broadcasts received.
|
Input errors
|
The number of total input errors, including the types listed below. Other input-related errors can also cause the input error count to increase, and some datagrams might have more than one error; therefore, this sum might exceed the number of errors listed for the types below.
|
Runts
|
The number of packets that are discarded because they are smaller than the minimum packet size, which is 64 bytes. Runts are usually caused by collisions. They might also be caused by poor wiring and electrical interference.
|
Giants
|
The number of packets that are discarded because they exceed the maximum packet size. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant.
|
CRC
|
The number of Cyclical Redundancy Check errors. When a station sends a frame, it appends a CRC to the end of the frame. This CRC is generated from an algorithm based on the data in the frame. If the frame is altered between the source and destination, the adaptive security appliance notes that the CRC does not match. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
|
Frame
|
The number of frame errors. Bad frames include packets with an incorrect length or bad frame checksums. This error is usually the result of collisions or a malfunctioning Ethernet device.
|
Overrun
|
The number of times that the adaptive security appliance was incapable of handing received data to a hardware buffer because the input rate exceeded the adaptive security appliance capability to handle the data.
|
Ignored
|
This field is not used. The value is always 0.
|
Abort
|
This field is not used. The value is always 0.
|
L2 decode drops
|
The number of packets dropped because the name is not configured (nameif command) or a frame with an invalid VLAN id is received.
|
Packets output
|
The number of packets sent on this interface.
|
Bytes
|
The number of bytes sent on this interface.
|
Underruns
|
The number of times that the transmitter ran faster than the adaptive security appliance could handle.
|
Output Errors
|
The number of frames not transmitted because the configured maximum number of collisions was exceeded. This counter should only increment during heavy network traffic.
|
Collisions
|
The number of messages retransmitted due to an Ethernet collision (single and multiple collisions). This usually occurs on an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once by the output packets.
|
Interface resets
|
The number of times an interface has been reset. If an interface is unable to transmit for three seconds, the adaptive security appliance resets the interface to restart transmission. During this interval, connection state is maintained. An interface reset can also happen when an interface is looped back or shut down.
|
Babbles
|
Unused. ("babble" means that the transmitter has been on the interface longer than the time taken to transmit the largest frame.)
|
Late collisions
|
The number of frames that were not transmitted because a collision occurred outside the normal collision window. A late collision is a collision that is detected late in the transmission of the packet. Normally, these should never happen. When two Ethernet hosts try to talk at once, they should collide early in the packet and both back off, or the second host should see that the first one is talking and wait.
If you get a late collision, a device is jumping in and trying to send the packet on the Ethernet while the adaptive security appliance is partly finished sending the packet. The adaptive security appliance does not resend the packet, because it may have freed the buffers that held the first part of the packet. This is not a real problem because networking protocols are designed to cope with collisions by resending packets. However, late collisions indicate a problem exists in your network. Common problems are large repeated networks and Ethernet networks running beyond the specification.
|
Deferred
|
The number of frames that were deferred before transmission due to activity on the link.
|
input reset drops
|
Counts the number of packets dropped in the RX ring when a reset occurs.
|
output reset drops
|
Counts the number of packets dropped in the TX ring when a reset occurs.
|
Rate limit drops
|
(For 4GE SSM interfaces only) The number of packets dropped if you configured the interface at non-Gigabit speeds and attempted to transmit more than 10 Mbps or 100 Mbps, depending on configuration..
|
Lost carrier
|
Th |