-
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Command Reference, 4.0
-
About This Guide
-
Using the Command Line Interface
- A through B Commands
- C Commands
- D through F Commands
- G through I Commands
- J through L Commands
- M through O Commands
- P though R Commands
-
S Commands
-
same-security-traffic -- show asdm sessions
-
show asp drop -- show curpriv
-
show debug -- show ipv6 traffic
-
show isakmp sa -- show route
-
show running-config -- show running-config isakmp
-
show running-config logging -- show running-config vpn-sessiondb
-
show service-policy -- show xlate
-
shun -- sysopt uauth allow-http-cache
-
- T through Z Commands
-
Feedback
Table Of Contents
activation-key through auto-update timeout Commands
activation-key through auto-update timeout Commands
activation-key
To change the activation key on the FWSM and check the activation key running on the FWSM against the activation key that is stored as a hidden file in the Flash partition of the FWSM, use the activation-key command in global configuration mode.
activation-key [activation-key-four-tuple| activation-key-five-tuple]
Syntax Description
Defaults
This command has no default settings.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
•
Command History
Usage Guidelines
Enter the activation-key-four-tuple as a four-element hexadecimal string with one space between each element, or activation-key-five-tuple as a five-element hexidecimal string with one space between each element as follows:
0xe02888da 0x4ba7bed6 0xf1c123ae 0xffd8624eThe leading 0x specifier is optional; all values are assumed to be hexadecimal.
The key is not stored in the configuration file. The key is tied to the serial number.
Examples
This example shows how to change the activation key on the FWSM:
hostname(config)# activation-key 0xe02888da 0x4ba7bed6 0xf1c123ae 0xffd8624eRelated Commands
address-pool
To specify a list of address pools for allocating addresses to remote clients, use the address-pool command in tunnel-group general-attributes configuration mode. To eliminate address pools, use the no form of this command.
address-pool [(interface name)] address_pool1 [...address_pool6]
no address-pool [(interface name)] address_pool1 [...address_pool6]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Tunnel-group general-attributes configuration
•
—
•
—
—
Command History
Usage Guidelines
You can enter multiples of each of these commands, one per interface. If an interface is not specified, then the command specifies the default for all interfaces that are not explicitly referenced.
Examples
The following example entered in config-general configuration mode, specifies a list of address pools for allocating addresses to remote clients for an IPSec remote-access tunnel group xyz:
hostname(config)# tunnel-group xyzhostname(config)# tunnel-group xyz generalhostname(config-general)# address-pool (inside) addrpool1 addrpool2 addrpool3hostname(config-general)#Related Commands
admin-context
To set the admin context for the system configuration, use the admin-context command in global configuration mode.
admin-context name
Syntax Description
Defaults
For a new FWSM in multiple context mode, the admin context is called "admin."
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
N/A
N/A
—
—
•
Command History
Usage Guidelines
The system configuration does not include any network interfaces or network settings for itself; rather, when the system needs to access network resources (such as downloading the FWSM software or allowing remote management for an administrator), it uses one of the contexts that is designated as the admin context.
You can set any context to be the admin context, as long as the context configuration resides on the internal Flash memory.
You cannot remove the current admin context, unless you remove all contexts using the clear configure context command.
Examples
The following example sets the admin context to be "administrator":
hostname(config)# admin-context administratorRelated Commands
alias
To manually translate an address and perform DNS reply modification, use the alias command in global configuration mode. To remove an alias command, use the no form of this command.
alias interface_name mapped_ip real_ip [netmask]
[no] alias interface_name mapped_ip real_ip [netmask]
Syntax Description
Defaults
This command has no default settings.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
—
•
•
—
Command History
Usage Guidelines
This command functionality has been replaced by outside NAT commands, including the nat and static commands with the dns keyword. We recommend that you use outside NAT instead of the alias command.
You can also use this command to perform address translation on a destination address. For example, if a host sends a packet to 209.165.201.1, you can use the alias command to redirect traffic to another address, such as 209.165.201.30.
Note
After changing or removing an alias command, use the clear xlate command.
You must have an A (address) record in the DNS zone file for the "dnat" address in the alias command.
The alias command has two uses that can be summarized in the following ways:
•
•
The alias command automatically interacts with the DNS servers on your network to ensure that domain name access to the aliased IP address is handled transparently.
You can specify a net alias by using network addresses for the real_ip and mapped_ip IP addresses. For example, the alias 192.168.201.0 209.165.201.0 255.255.255.224 command creates aliases for each IP address between 209.165.201.1 and 209.165.201.30.
To access an alias mapped_ip address with static and access-list commands, specify the mapped_ip address in the access-list command as the address from which traffic is permitted as follows:
hostname(config)# alias (inside) 192.168.201.1 209.165.201.1 255.255.255.255hostname(config)# static (inside,outside) 209.165.201.1 192.168.201.1 netmask 255.255.255.255hostname(config)# access-list acl_out permit tcp host 192.168.201.1 host 209.165.201.1 eq ftp-datahostname(config)# access-group acl_out in interface outsideAn alias is specified with the inside address 192.168.201.1 mapping to the destination address 209.165.201.1.
When the inside network client 209.165.201.2 connects to example.com, the DNS response from an external DNS server to the internal client's query would be altered by the FWSM to be 192.168.201.29. If the FWSM uses 209.165.200.225 through 209.165.200.254 as the global pool IP addresses, the packet goes to the FWSM with SRC=209.165.201.2 and DST=192.168.201.29. The FWSM translates the address to SRC=209.165.200.254 and DST=209.165.201.29 on the outside.
Examples
The following example shows that the inside network contains the IP address 209.165.201.29, which on the Internet belongs to example.com. When inside clients try to access example.com, the packets do not go to the FWSM because the client assumes that the 209.165.201.29 is on the local inside network.
To correct this, use the alias command as follows:
hostname(config)#alias (inside) 192.168.201.0 209.165.201.0 255.255.255.224hostname(config)# show running-config aliasalias 192.168.201.0 209.165.201.0 255.255.255.224The following example shows a web server that is on the inside at 10.1.1.11 and the static command that was created at 209.165.201.11. The source host is on the outside with address 209.165.201.7. A DNS server on the outside has a record for www.example.com as follows:
dns-server# www.example.com. IN A 209.165.201.11You must include the period at the end of the www.example.com. domain name.
The following example shows how to use the alias command:
hostname(config)# alias 10.1.1.11 209.165.201.11 255.255.255.255The FWSM changes the name server replies to 10.1.1.11 for inside clients to directly connect to the web server.
The following example shows the commands you need to provide access:
hostname(config)# static (inside,outside) 209.165.201.11 10.1.1.11hostname(config)# access-list acl_grp permit tcp host 209.165.201.7 host 209.165.201.11 eq telnethostname(config)# access-list acl_grp permit tcp host 209.165.201.11 eq telnet host 209.165.201.7Related Commands
allocate-acl-partition
To assign a context to a memory partition, use the allocate-acl-partition command in context configuration mode. To remove the assignment, use the no form of this command.
allocate-acl-partition partition_number
no allocate-acl-partition partition_number
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Context configuration
N/A
N/A
—
—
•
Command History
Usage Guidelines
In multiple context mode, the FWSM partitions the memory allocated to rule configuration, and assigns each context to a partition. By default, a context belongs to one of 12 partitions that offers a maximum of 12,130 rules, including ACEs, AAA rules, and others. The FWSM assigns contexts to the partitions in the order they are loaded at startup. For example, if you have 12 contexts, each context is assigned to its own partition, and can use 12,130 rules. If you add one more context, then context number 1 and the new context number 13 are both assigned to partition 1, and can use 12,130 rules divided between them; the other 11 contexts continue to use 12,130 rules each. If you delete contexts, the partition membership does not shift, so you might have some unequal distribution until you reboot, at which time the contexts are evenly distributed.
Note
Alternatively, you can manually assign a context to a partition with the allocate-acl-partition command. You can also reduce the number of partitions to better match the number of contexts you have with the resource acl-partition command.
When you assign a context to a partition, then the partition becomes exclusive. An exclusive partition only includes contexts that you specifically assign to it. Partitions that do not have contexts specifically assigned to them are non-exclusive and contexts are allocated to them in a round-robin fashion.
Note
Examples
The following example assigns context test to partition 0:
hostname# context testhostname(config-ctx)# allocate-acl-partition 0Related Commands
allocate-interface
To allocate interfaces to a security context, use the allocate-interface command in context configuration mode. To remove an interface from a context, use the no form of this command.
allocate-interface vlannumber[-vlannumber] [map_name[-map_name]] [visible | invisible]
no allocate-interface vlannumber[-vlannumber]
Syntax Description
invisible
(Default) Allows context users to only see the mapped name (if configured) in the show interface command.
map_name
(Optional) Sets a mapped name.
The map_name is an alphanumeric alias for the interface that can be used within the context instead of the VLAN ID. If you do not specify a mapped name, the VLAN ID is used within the context. For security purposes, you might not want the context administrator to know which interfaces are being used by the context. You can use the same name in multiple contexts; the VLAN ID in multiple contexts can be the same or different for a given name. You cannot use the same name for different VLAN IDs in the same context.
A mapped name must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, or an underscore. For example, you can use the following names:
int0intaint_0You can specify a range of mapped names. See the "Usage Guidelines" section for more information about ranges.
visible
(Optional) Allows context users to see physical interface properties in the show interface command even if you set a mapped name.
vlannumber
Sets the VLAN number, typically from 2 to 1000 and from 1025 to 4094 (see the switch documentation for supported VLANs). To view all interfaces currently configured on the FWSM, enter the show running-config interface command or the show interface command. You can only allocate an interface that exists in the system configuration. By default, all VLANs assigned to the FWSM by the switch are added to the system configuration. You can also add VLANs manually to the system configuration, but you need to assign them from the switch if you want them to pass traffic.
Defaults
The VLAN ID is invisible in the show interface command output by default if you set a mapped name.
Command Modes
The following table shows the modes in which you can enter the command:
Context configuration
N/A
N/A
—
—
•
Command History
Usage Guidelines
You can enter this command multiple times to specify different ranges. To change the mapped name or visible setting, reenter the command for a given VLAN ID, and set the new values; you do not need to enter the no allocate-interface command and start over. If you remove the allocate-interface command, the FWSM removes any interface-related configuration in the context.
You can assign the same interfaces to multiple contexts in routed mode, if desired. Transparent mode does not allow shared interfaces.
If you specify a range of VLAN IDs, you can specify a matching range of mapped names. Follow these guidelines for ranges:
•
int0-int10•
vlan100-vlan199 int1-int100If you enter vlan100-vlan199 int1-int15 or vlan100-vlan199 happy1-sad5, for example, the command fails.
Examples
The following example shows VLANs 100, 200, and 300 through 305 assigned to the context. The mapped names are int1 through int8.
hostname(config-ctx)# allocate-interface vlan100 int1hostname(config-ctx)# allocate-interface vlan200 int2hostname(config-ctx)# allocate-interface vlan300-vlan305 int3-int8Related Commands
area
To create an OSPF area, use the area command in router configuration mode. To remove the area, use the no form of this command.
area area_id
no area area_id
Syntax Description
area_id
The ID of the area being created. You can specify the identifier as either a decimal number or an IP address. Valid decimal values range from 0 to 4294967295.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
The area that you create does not have any parameters set. Use the related area commands to set the area parameters.
Examples
The following example shows how to create an OSPF area with an area ID of 1:
hostname(config-router)# area 1hostname(config-router)#Related Commands
area authentication
To enable authentication for an OSPF area, use the area authentication command in router configuration mode. To disable area authentication, use the no form of this command.
area area_id authentication [message-digest]
no area area_id authentication [message-digest]
Syntax Description
Defaults
Area authentication is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
If the specified OSPF area does not exist, it is created when this command is entered. Entering the area authentication command without the message-digest keyword enables simple password authentication. Including the message-digest keyword enables MD5 authentication.
Examples
The following example shows how to enable MD5 authentication for area 1:
hostname(config-router)# area 1 authentication message-digesthostname(config-router)#Related Commands
router ospf
Enters router configuration mode.
show running-config router
Displays the commands in the global router configuration.
area default-cost
To specify a cost for the default summary route sent into a stub or NSSA, use the area default-cost command in router configuration mode. To restore the default cost value, use the no form of this command.
area area_id default-cost cost
no area area_id default-cost
Syntax Description
Defaults
The default value of cost is 1.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
If the specified area has not been previously defined using the area command, this command creates the area with the specified parameters.
Examples
The following example show how to specify a default cost for summary route sent into a stub or NSSA:
hostname(config-router)# area 1 default-cost 5hostname(config-router)#Related Commands
area filter-list prefix
To filter prefixes advertised in Type 3 LSAs between OSPF areas of an ABR, use the area filter-list prefix command in router configuration mode. To change or cancel the filter, use the no form of this command.
area area_id filter-list prefix list_name {in | out}
no area area_id filter-list prefix list_name {in | out}
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
If the specified area has not been previously defined using the area command, this command creates the area with the specified parameters.
OnlyType 3 LSAs can be filtered. If an ASBR is configured in the private network, then it will send type 5 LSAs (describing private networks) which are flooded to the entire AS including the public areas.
Examples
The following example filters prefixes that are sent from all other areas to area 1:
hostname(config-router)# area 1 filter-list prefix-list AREA_1 inhostname(config-router)#Related Commands
router ospf
Enters router configuration mode.
show running-config router
Displays the commands in the global router configuration.
area nssa
To configure an area as an NSSA, use the area nssa command in router configuration mode. To remove the NSSA designation from the area, use the no form of this command.
area area_id nssa [no-redistribution] [default-information-originate [metric-type {1 | 2}] [metric value]] [no-summary]
no area area_id nssa [no-redistribution] [default-information-originate [metric-type {1 | 2}] [metric value]] [no-summary]
Syntax Description
Defaults
The defaults are as follows:
•
•
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
If the specified area has not been previously defined using the area command, this command creates the area with the specified parameters.
If you configure one option for an area, and later specify another option, both options are set. For example, entering the following two command separately results in a single command with both options set in the configuration:
area 1 nssa no-redistributionarea area_id nssa default-information-originateExamples
The following example shows how setting two options separately results in a single command in the configuration:
hostname(config-router)# area 1 nssa no-redistributionhostname(config-router)# area 1 nssa default-information-originatehostname(config-router)# exithostname(config-router)# show running-config router ospf 1router ospf 1area 1 nssa no-redistribution default-information-originateRelated Commands
area stub
Defines the area as a stub area.
router ospf
Enters router configuration mode.
show running-config router
Displays the commands in the global router configuration.
area range
To consolidate and summarize routes at an area boundary, use the area range command in router configuration mode. To disable this function, use the no form of this command.
area area_id range address mask [advertise | not-advertise]
no area area_id range address mask [advertise | not-advertise]
Syntax Description
Defaults
The address range status is set to advertise.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
If the specified area has not been previously defined using the area command, this command creates the area with the specified parameters.
The area range command is used only with ABRs. It is used to consolidate or summarize routes for an area. The result is that a single summary route is advertised to other areas by the ABR. Routing information is condensed at area boundaries. External to the area, a single route is advertised for each address range. This behavior is called route summarization. You can configure multiple area range commands for an area. Thus, OSPF can summarize addresses for many different sets of address ranges.
The no area area_id range ip_address netmask not-advertise command removes only the not-advertise optional keyword.
Examples
The following example specifies one summary route to be advertised by the ABR to other areas for all subnets on network 10.0.0.0 and for all hosts on network 192.168.110.0:
hostname(config-router)# area 10.0.0.0 range 10.0.0.0 255.0.0.0hostname(config-router)# area 0 range 192.168.110.0 255.255.255.0hostname(config-router)#Related Commands
router ospf
Enters router configuration mode.
show running-config router
Displays the commands in the global router configuration.
area stub
To define an area as a stub area, use the area stub command in router configuration mode. To remove the stub area function, use the no form of this command.
area area_id [no-summary]
no area area_id [no-summary]
Syntax Description
Defaults
The default behaviors are as follows:
•
•
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
The command is used only on an ABR attached to a stub or NSSA.
There are two stub area router configuration commands: the area stub and area default-cost commands. In all routers and access servers attached to the stub area, the area should be configured as a stub area using the area stub command. Use the area default-cost command only on an ABR attached to the stub area. The area default-cost command provides the metric for the summary default route generated by the ABR into the stub area.
Examples
The following example configures the specified area as a stub area:
hostname(config-router)# area 1 stubhostname(config-router)#Related Commands
area virtual-link
To define an OSPF virtual link, use the area virtual-link command in router configuration mode. To reset the options or remove the virtual link, use the no form of this command.
area area_id virtual-link router_id [authentication [message-digest | null]] [hello-interval seconds] [retransmit-interval seconds] [transmit-delay seconds] [dead-interval seconds [[authentication-key key] | [message-digest-key key_id md5 key]]
no area area_id virtual-link router_id [authentication [message-digest | null]] [hello-interval seconds] [retransmit-interval seconds] [transmit-delay seconds] [dead-interval seconds [[authentication-key key] | [message-digest-key key_id md5 key]]
Syntax Description
Defaults
The defaults are as follows:
•
•
•
•
•
•
•
•
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
In OSPF, all areas must be connected to a backbone area. If the connection to the backbone is lost, it can be repaired by establishing a virtual link.
The smaller the hello interval, the faster topological changes are detected, but more routing traffic ensues.
The setting of the retransmit interval should be conservative, or needless retransmissions occur. The value should be larger for serial lines and virtual links.
The transmit delay value should take into account the transmission and propagation delays for the interface.
The specified authentication key is used only when authentication is enabled for the backbone with the area area_id authentication command.
The two authentication schemes, simple text and MD5 authentication, are mutually exclusive. You can specify one or the other or neither. Any keywords and arguments you specify after authentication-key key or message-digest-key key_id md5 key are ignored. Therefore, specify any optional arguments before such a keyword-argument combination.
If the authentication type is not specified for an interface, the interface uses the authentication type specified for the area. If no authentication type has been specified for the area, the area default is null authentication.
Note
To remove an option from a virtual link, use the no form of the command with the option that you want removed. To remove the virtual link, use the no area area_id virtual-link command.
Examples
The following example establishes a virtual link with MD5 authentication:
hostname(config-router)# area 10.0.0.0 virtual-link 10.3.4.5 message-digest-key 3 md5 sa5721bk47Related Commands
arp
To add a static ARP entry to the ARP table, use the arp command in global configuration mode. To remove the static entry, use the no form of this command.
arp interface_name ip_address mac_address [alias]
no arp interface_name ip_address mac_address
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
A static ARP entry maps a MAC address to an IP address and identifies the interface through which the host is reached. Static ARP entries do not time out, and might help you solve a networking problem. In transparent firewall mode, the static ARP table is used with ARP inspection (see the arp-inspection command).
Although hosts identify a packet destination by an IP address, the actual delivery of the packet on Ethernet relies on the Ethernet MAC address. When a router or host wants to deliver a packet on a directly connected network, it sends an ARP request asking for the MAC address associated with the IP address, and then delivers the packet to the MAC address according to the ARP response. The host or router keeps an ARP table so it does not have to send ARP requests for every packet it needs to deliver. The ARP table is dynamically updated whenever ARP responses are sent on the network, and if an entry is not used for a period of time, it times out. If an entry is incorrect (for example, the MAC address changes for a given IP address), the entry times out before it can be updated.
Note
Examples
The following example creates a static ARP entry for 10.1.1.1 with the MAC address 0009.7cbe.2100 on the outside interface:
hostname(config)# arp outside 10.1.1.1 0009.7cbe.2100Related Commands
arp timeout
To set the time before the FWSM rebuilds the ARP table, use the arp timeout command in global configuration mode. To restore the default timeout, use the no form of this command.
arp timeout seconds
no arp timeout seconds
Syntax Description
Defaults
The default value is 14,400 seconds (4 hours).
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
Rebuilding the ARP table automatically updates new host information and removes old host information. You might want to reduce the timeout because the host information changes frequently.
Examples
The following example changes the ARP timeout to 5000 seconds:
hostname(config)# arp timeout 5000Related Commands
arp-inspection
To enable ARP inspection for transparent firewall mode, use the arp-inspection command in global configuration mode. To disable ARP inspection, use the no form of this command.
arp-inspection interface_name enable [flood | no-flood]
no arp-inspection interface_name enable
Syntax Description
Defaults
By default, ARP inspection is disabled on all interfaces; all ARP packets are allowed through the FWSM. When you enable ARP inspection, the default is to flood non-matching ARP packets.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
—
•
•
•
—
Command History
Usage Guidelines
ARP inspection checks all ARP packets against static ARP entries (see the arp command) and blocks mismatched packets. This feature prevents ARP spoofing.
Configure static ARP entries using the arp command before you enable ARP inspection.
When you enable ARP inspection, the FWSM compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions:
•
•
•
ARP inspection prevents malicious users from impersonating other hosts or routers (known as ARP spoofing). ARP spoofing can enable a "man-in-the-middle" attack. For example, a host sends an ARP request to the gateway router; the gateway router responds with the gateway router MAC address. The attacker, however, sends another ARP response to the host with the attacker MAC address instead of the router MAC address. The attacker can now intercept all the host traffic before forwarding it on to the router.
ARP inspection ensures that an attacker cannot send an ARP response with the attacker MAC address, so long as the correct MAC address and the associated IP address are in the static ARP table.
Note
Examples
The following example enables ARP inspection on the outside interface and sets the FWSM to drop any ARP packets that do not match the static ARP entry:
hostname(config)# arp outside 209.165.200.225 0009.7cbe.2100hostname(config)# arp-inspection outside enable no-floodRelated Commands
asdm disconnect
To terminate an active ASDM session, use the asdm disconnect command in privileged EXEC mode.
asdm disconnect session
Syntax Description
session
The session ID of the active ASDM session to be terminated. You can display the session IDs of all active ASDM sessions using the show asdm sessions command.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
1.1(1)
This command was introduced (as the pdm disconnect command).
3.1(1)
This command was changed from the pdm disconnect command to the asdm disconnect command.
Usage Guidelines
Use the show asdm sessions command to display a list of active ASDM sessions and their associated session IDs. Use the asdm disconnect command to terminate a specific session.
When you terminate an ASDM session, any remaining active ASDM sessions keep their associated session ID. For example, if there are three active ASDM sessions with the session IDs of 0, 1, and 2, and you terminate session 1, the remaining active ASDM sessions keep the session IDs 0 and 2. The next new ASDM session in this example would be assigned a session ID of 1, and any new sessions after that would begin with the session ID 3.
Examples
The following example terminates an ASDM session with a session ID of 0. The show asdm sessions commands display the active ASDM sessions before and after the asdm disconnect command is entered.
hostname# show asdm sessions0 192.168.1.11 192.168.1.2hostname# asdm disconnect 0hostname# show asdm sessions1 192.168.1.2Related Commands
show asdm sessions
Displays a list of active ASDM sessions and their associated session ID.
asdm disconnect log_session
To terminate an active ASDM logging session, use the asdm disconnect log_session command in privileged EXEC mode.
asdm disconnect log_session session
Syntax Description
session
The session ID of the active ASDM logging session to be terminated. You can display the session IDs of all active ASDM sessions using the show asdm log_sessions command.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
Use the show asdm log_sessions command to display a list of active ASDM logging sessions and their associated session IDs. Use the asdm disconnect log_session command to terminate a specific logging session.
Each active ASDM session has one or more associated ASDM logging sessions. ASDM uses the logging session to retrieve syslog messages from FWSM. Terminating a log session may have an adverse effect on the active ASDM session. To terminate an unwanted ASDM session, and the associated log sessions, use the asdm disconnect command.
Note
When you terminate an ASDM logging session, any remaining active ASDM logging sessions keep their associated session ID. For example, if there are three active ASDM logging sessions with the session IDs of 0, 1, and 2, and you terminate session 1, the remaining active ASDM logging sessions keep the session IDs 0 and 2. The next new ASDM logging session in this example would be assigned a session ID of 1, and any new logging sessions after that would begin with the session ID 3.
Examples
The following example terminates an ASDM session with a session ID of 0. The show asdm log_sessions commands display the active ASDM sessions before and after the asdm disconnect log_sessions command is entered.
hostname# show asdm log_sessions0 192.168.1.11 192.168.1.2hostname# asdm disconnect 0hostname# show asdm log_sessions1 192.168.1.2Related Commands
show asdm log_sessions
Displays a list of active ASDM logging sessions and their associated session ID.
asdm group
Caution
asdm group real_grp_name real_if_name
asdm group ref_grp_name ref_if_name reference real_grp_name
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
1.1(1)
This command was introduced (as the pdm group command).
3.1(1)
This command was changed from the pdm group command to the asdm group command.
Usage Guidelines
Do not manually configure or remove this command.
asdm history enable
To enable ASDM history tracking, use the asdm history enable command in global configuration mode. To disable ASDM history tracking, use the no form of this command.
asdm history enable
no asdm history enable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
•
Command History
1.1(1)
This command was introduced (as the pdm history enable command).
3.1(1)
This command was changed from the pdm history enable command to the asdm history enable command.
Usage Guidelines
The information obtained by enabling ASDM history tracking is stored in the ASDM history buffer. You can view this information using the show asdm history command. The history information is used by ASDM for device monitoring.
Examples
The following example enables ASDM history tracking:
hostname(config)# asdm history enablehostname(config)#Related Commands
asdm location
Caution
asdm location ip_addr netmask if_name
asdm location ipv6_addr/prefix if_name
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
1.1(1)
This command was introduced (as the pdm location command).
3.1(1)
This command was changed from the pdm location command to the asdm location command.
Usage Guidelines
Do not manually configure or remove this command.
asr-group
To specify an asymmetrical routing interface group ID, use the asr-group command in interface configuration mode. To remove the ID, use the no form of this command.
asr-group group_id
no asr-group group_id
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Interface configuration
•
•
•
•
—
Command History
Usage Guidelines
In some situations, return traffic for a session may be routed through a different interface than it originated from. In failover configurations, return traffic for a connection that originated on one unit may return through the peer unit. This most commonly occurs when two interfaces on a single FWSM, or two FWSMs in a failover pair, are connected to different service providers and the outbound connection does not use a NAT address. By default, FWSM drops the return traffic because there is no connection information for the traffic.
You can prevent the return traffic from being dropped using the asr-group command on interfaces where this is likely to occur. When an interface configured with the asr-group command receives a packet for which it has no session information, it checks the session information for the other interfaces that are in the same group.
Note
If it does not find a match, the packet is dropped. If it finds a match, then one of the following actions occurs:
•
•
Tip
Caution
You can view ASR statistics using the show interface detail command. These statistics include the number of ASR packets sent, received, and dropped on an interface.
Examples
The following example assigns the selected interfaces to the asymmetric routing group 1:
Context ctx1 configuration:
hostname/ctx1(config)# interface Vlan101hostname/ctx1(config-if)# nameif outsidehostname/ctx1(config-if)# ip address 192.168.1.11 255.255.255.0 standby 192.168.1.21hostname/ctx1(config-if)# asr-group 1Context ctx2 configuration:
hostname/ctx2(config)# interface Vlan102hostname/ctx2(config-if)# nameif outsidehostname/ctx2(config-if)# ip address 192.168.1.31 255.255.255.0 standby 192.168.1.41hostname/ctx2(config-if)# asr-group 1Related Commands
interface
Enters interface configuration mode.
show interface
Displays interface statistics.
authentication key eigrp
To enable authentication of EIGRP packets and specify the authentication key, use the authentication key eigrp command in interface configuration mode. To disable EIGRP authentication, use the no form of this command.
authentication key eigrp as-number key key-id key-id
no authentication key eigrp as-number
Syntax Description
Defaults
EIGRP authentication is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Interface configuration
•
—
•
—
—
Command History
Usage Guidelines
You must configure both the authentication mode eigrp and the authentication key eigrp commands on an interface to enable EIGRP message authentication. Use the show running-config interface command to view the authentication commands configured on an interface.
Examples
The following examples shows EIGRP authentication configured on interface vlan10:
hostname(config)# interface vlan10hostname(config-if)# authentication mode eigrp md5hostname(config-if)# authentication key eigrp 100 thisismykey key_id 5Related Commands
authentication mode eigrp
Specifies the type of authentication used for EIGRP authentication.
authentication mode eigrp
To specify the type of authentication used for EIGRP authentication, use the authentication mode eigrp command in interface configuration mode. To restore the default authentication method, use the no form of this command.
authentication mode eigrp as-num md5
no authentication mode eigrp as-num md5
Syntax Description
as-num
The autonomous system number of the EIGRP routing process.
md5
Uses MD5 for EIGRP message authentication.
Defaults
No authentication is provided by default.
Command Modes
The following table shows the modes in which you can enter the command:
Interface configuration
•
—
•
—
—
Command History
Usage Guidelines
You must configure both the authentication mode eigrp and the authentication key eigrp commands on an interface to enable EIGRP message authentication. Use the show running-config interface command to view the authentication commands configured on an interface.
Examples
The following examples shows EIGRP authentication configured on interface vlan10:
hostname(config)# interface vlan10hostname(config-if)# authentication mode eigrp 100 md5hostname(config-if)# authentication key eigrp 100 thisismykey key_id 5Related Commands
authentication key eigrp
Enables authentication of EIGRP packets and specifies the authentication key.
authentication-port
To specify the port number used for RADIUS authentication for this host, use the authentication-port command in aaa-server host configuration mode. To remove the authentication port specification, use the no form of this command. This command specifies the destination TCP/UDP port number of the remote RADIUS server hosts to which you want to assign authentication functions.
authentication-port port
no authentication-port
Syntax Description
Defaults
By default, the device listens for RADIUS on port 1645 (in compliance with RFC 2058). If the port is not specified, the RADIUS authentication default port number (1645) is used.
Command Modes
The following table shows the modes in which you can enter the command:
aaa-server host configuration
•
•
•
•
—
Command History
3.1(1)
This command was introduced, replacing the aaa-server radius-authport command.
Usage Guidelines
If your RADIUS authentication server uses a port other than 1645, you must configure the FWSM for the appropriate port prior to starting the RADIUS service with the aaa-server command.
Tip
This command is valid only for server groups that are configured for RADIUS.
Examples
The following example configures a RADIUS AAA server named "svrgrp1" on host "209.165. 200.225", sets a timeout of 9 seconds, sets a retry-interval of 7 seconds, and configures authentication port 1650.
hostname(config)#aaa-server svrgrp1 protocol radiushostname(config-aaa-server-group)#aaa-server svrgrp1 host 209.165.200.225hostname(config-aaa-server-host)#timeout 9hostname(config-aaa-server-host)#retry-interval 7hostname(config-aaa-server-host)#authentication-port 1650Related Commands
authentication-server-group
To specify the aaa-server group to use for user authentication, use the authentication-server-group command in tunnel-group general-attributes mode. To return this command to the default, use the no form of this command.
authentication-server-group [(interface name)] server group [LOCAL | NONE]
no authentication-server-group [(interface name)] server group
Syntax Description
Defaults
The default setting for this command is LOCAL.
Command Modes
The following table shows the modes in which you can enter the command:
Tunnel-group general attributes configuration
•
—
•
—
—
Command History
Usage Guidelines
You can apply this attribute to the IPSec remote access tunnel-group type only:
Examples
The following example entered in config-general configuration mode, configures an authentication server group named aaa-server456 for an IPSec remote-access tunnel group named remotegrp:
hostname(config)# tunnel-group remotegrp type ipsec_rahostname(config)# tunnel-group remotegrp generalhostname(config-general)# authentication-server-group aaa-server456hostname(config-general)#Related Commands
authorization-dn-attributes
To specify what part of the subject DN field to use as the username for authorization, use the authorization-dn-attributes command in tunnel-group ipsec-attributes configuration mode. To return this command to the default, use the no form of this command.
[no] authorization-dn-attributes {primary-attr [secondary-attr] | use-entire-name}
Syntax Description
Defaults
The default value for the primary attribute is Common Name.
The default value for the secondary attribute is Organization Unit.
Command Modes
The following table shows the modes in which you can enter the command:
Tunnel-group ipsec-attributes configuration
•
•
•
•
—
Command History
Usage Guidelines
You can apply this attribute to IPSec remote access tunnel type only.
Primary and secondary attributes include the following:
Examples
The following example entered in config-ipsec configuration mode, creates a remote access tunnel group (ipsec_ra) named remotegrp, specifies IPSec group attributes and defines the Common Name to be used as the username for authorization:
hostname(config)# tunnel-group remotegrp type ipsec_rahostname(config)# tunnel-group remotegrp ipsec-attributeshostname(config-ipsec)# authorization-dn-attributes CNhostname(config-ipsec)#Related Commands
authorization-required
To require users to authorize successfully to connect, use the authorization-required command in tunnel-group ipsec-attributes configuration mode. To return this command to the default, use the no form of this command.
[no] authorization-required
Defaults
The default setting of this command is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Tunnel-group general attributes configuration
•
•
•
•
—
Syntax Description
This command has no arguments or keywords.
Command History
Usage Guidelines
You can apply this attribute to IPSec remote-access tunnel-group type only.
Examples
The following example entered in config-ipsec configuration mode, requires authorization based on the complete DN for users connecting through a remote-access tunnel group named remotegrp. The first command configures the tunnel-group type as ipsec_ra (IPSec remote access) for the remote group named remotegrp. The second command enters ipsec-attributes mode for the specified tunnel group, and the last command specifies authorization required for the named tunnel group:
hostname(config)# tunnel-group remotegrp type ipsec_rahostname(config)# tunnel-group remotegrp ipsec-attributeshostname(config-ipsec)# authorization-requiredhostname(config-ipsec)#Related Commands
authorization-server-group
To specify the aaa-server group for user authorization, use the authorization-server-group command in tunnel-group general-attributes configuration mode. To return this command to the default, use the no form of this command.
authorization-server-group server group
no authorization-server-group
Syntax Description
Defaults
The default setting for this command is no authorization-server-group.
Command Modes
The following table shows the modes in which you can enter the command:
Tunnel-group general-attributes configuration
•
•
•
•
—
Command History
Usage Guidelines
You can apply this attribute only to IPSec remote access tunnel-group types.
When VPN Authorization is defined as LOCAL, the attributes configured in the default group policy DfltGrpPolicy are enforced.
Examples
The following example entered in config-general configuration mode, configures an authorization server group named "aaa-server78" for an IPSec remote-access tunnel group named "remotegrp":
hostname(config)# tunnel-group remotegrp type ipsec-rahostname(config)# tunnel-group remotegrp generalhostname(config-general)# authorization-server-group aaa-server78hostname(config-general)#Related Commands
auth-prompt
To specify or change the AAA challenge text for through-the-FWSM user sessions, use the auth-prompt command in global configuration mode. To remove the authentication challenge text, use the no form of this command.
auth-prompt {prompt | accept | reject [invalid-credentials | expired-pwd]} string
no auth-prompt {prompt | accept | reject [invalid-credentials | expired-pwd]}
Syntax Description
Defaults
If you do not specify an authentication prompt, the prompt users see when they log in depends on the protocol they use:
•
0xe02888da 0x4ba7bed6 0xf1c123ae 0xffd8624e.•
hostname(config)#.•
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
1.1(1)
This command was introduced.
3.2(1)
The expired-pwd and invalid-credentials keywords were added.
Usage Guidelines
The auth-prompt command lets you specify the AAA challenge text for HTTP, HTTPS, FTP, and Telnet access through the FWSM when requiring user authentication from TACACS+ or RADIUS servers. This text is primarily for cosmetic purposes and displays above the username and password prompts that users view when logging in (the prompt keyword), or after the user enters the username and password (the accept and reject keywords).
Note
Microsoft Internet Explorer displays up to 37 characters in an authentication prompt. Netscape Navigator displays up to 120 characters, and Telnet and FTP display up to 235 characters in an authentication prompt.
Examples
The following example sets the authentication prompt to the string "Please enter your username and password.":
hostname(config)# auth-prompt prompt Please enter your username and passwordAfter this string is added to the configuration, users see the following:
Please enter your username and passwordUser Name:Password:You can also provide separate messages to display when the FWSM accepts or rejects the authentication attempt; for example:
hostname(config)# auth-prompt reject Authentication failed. Try again.hostname(config)# auth-prompt accept Authentication succeeded.To set rejection messages for invalid credentials, expired password, and for unknown rejection reasons, enter the following commands:
hostname(config)# auth-prompt reject Authentication failed. Try again.hostname(config)# auth-prompt reject invalid-credentials Incorrect username or passwordhostname(config)# auth-prompt reject expired-pwd Your password is expired. Reset your password and try again.Related Commands
auto-summary
To enable the automatic summarization of subnet routes into network-level routes, use the auto-summary command in router configuration mode. To disable route summarization, use the no form of this command.
auto-summary
no auto-summary
Syntax Description
This command has no arguments or keywords.
Defaults
Route summarization is enabled for EIGRP.
Command Modes
The following table shows the modes in which you can enter the command:
Router configuration
•
—
•
—
—
Command History
Usage Guidelines
Route summarization reduces the amount of routing information in the routing tables.
EIGRP summary routes are given an administrative distance value of 5. You cannot configure this value.
Only the no form of this command appears in the running configuration.
Examples
The following example disables automatic EIGRP route summarization:
hostname(config)# router eigrp 100hostname(config-router)# network 10.0.0.0hostname(config-router)# no auto-summaryRelated Commands
auto-update device-id
To configure the FWSM device ID for use with an Auto Update Server, use the auto-update device-id command in global configuration mode. To remove the device ID, use the no form of this command.
auto-update device-id [hardware-serial | hostname | ipaddress [if_name] | mac-address [if_name] | string text]
no auto-update device-id [hardware-serial | hostname | ipaddress [if_name] | mac-address [if_name] | string text]
Syntax Description
Defaults
The default ID is the hostname.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Examples
The following example sets the device ID to the serial number:
hostname(config)# auto-update device-id hardware-serialRelated Commands
auto-update poll-period
To configure how often the FWSM checks for updates from an Auto Update Server, use the auto-update poll-period command in global configuration mode. To reset the parameters to the defaults, use the no form of this command.
auto-update poll-period poll_period [retry_count [retry_period]]
no auto-update poll-period poll_period [retry_count [retry_period]]
Syntax Description
Defaults
The default poll period is 720 minutes (12 hours).
The default number of times to try reconnecting to the Auto Update Server if the first attempt fails is 0.
The default period to wait between connection attempts is 5 minutes.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Examples
The following example sets the poll period to 360 minutes, the retries to 1, and the retry period to 3 minutes:
hostname(config)# auto-update poll-period 360 1 3Related Commands
auto-update server
To identify the Auto Update Server, use the auto-update server command in global configuration mode. To remove the server, use the no form of this command. The FWSM periodically contacts the Auto Update Server for any configuration, operating system, and ASDM updates.
auto-update server url [verify-certificate]
no auto-update server url [verify-certificate]
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
Only one server can be configured.
Examples
The following example sets the Auto Update Server URL:
hostname(config)# auto-update server http://10.1.1.1:1741/Related Commands
auto-update timeout
To set a timeout period in which to contact the Auto Update Server, use the auto-update timeout command in global configuration mode. If the Auto Update Server has not been contacted for the timeout period, the FWSM stops all traffic through the FWSM. Set a timeout to ensure that the FWSM has the most recent image and configuration. To remove the timeout, use the no form of this command.
auto-update timeout period
no auto-update timeout [period]
Syntax Description
Defaults
The default timeout is 0, which sets the FWSM to never time out.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
—
—
Command History
Usage Guidelines
A timeout condition is reported with system log message 201008.
Examples
The following example sets the timeout to 24 hours:
hostname(config)# auto-update timeout 1440
Related Commands
