Table Of Contents
quit through router-id Commands
quit
radius-common-pw
radius-with-expiry
reactivation-mode
redistribute
reload
remote-access threshold session-threshold-exceeded
rename
replication http
request-command deny
request-method
request-queue
resource acl-partition
retry-interval
re-xauth
rip
rmdir
route
route-map
router ospf
router-id
quit through router-id Commands
quit
To exit the current configuration mode, or to log out from privileged or user EXEC modes, use the quit command.
quit
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
|
1.1(1)
|
This command was introduced.
|
Usage Guidelines
You can also use the key sequence Ctrl Z to exit global configuration (and higher) modes. This key sequence does not work with privileged or user EXEC modes.
When you enter the quit command in privileged or user EXEC modes, you log out from the FWSM. Use the disable command to return to user EXEC mode from privileged EXEC mode.
Examples
The following example shows how to use the quit command to exit global configuration mode, and then logout from the session:
The following example shows how to use the quit command to exit global configuration mode, and then use the disable command to exit privileged EXEC mode:
Related Commands
Command
|
Description
|
exit
|
Exits a configuration mode or logs out from privileged or user EXEC modes.
|
radius-common-pw
To specify a common password to be used for all users whose VPN access is authorized by a RADIUS authorization server, use the radius-common-pw command in AAA-server host mode. To remove this specification, use the no form of this command:
radius-common-pw password
no radius-common-pw
Syntax Description
password
|
A case-sensitive, alphanumeric keyword of up to 127 characters to be used as a common password for all authorization transactions with the RADIUS server specified with the aaa-server host command.
|
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
|
Aaa-server host
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Usage Guidelines
This command is valid only for RADIUS authorization servers.
The RADIUS authorization server requires a password and username for each connecting user. The FWSM provides the username automatically. You enter the password here. The RADIUS server administrator must configure the RADIUS server to associate this password with each user authorizing to the server via this FWSM. Be sure to provide this information to your RADIUS server administrator.
If you do not specify a common user password, each user password is the username of the user. For example, the default RADIUS authorization for a user with the username "jsmith" is "jsmith". If you are using usernames for the common user passwords, as a security precaution do not use this RADIUS server for authorization anywhere else on your network.
Note
The password field is required by the RADIUS protocol and the RADIUS server requires it; however, users do not need to know it.
Examples
The following example configures a RADIUS AAA server group named "svrgrp1" on host "1.2.3.4", sets the timeout interval to 9 seconds, sets the retry interval to 7 seconds, and configures the RADIUS commnon password as "allauthpw".
hostname(config)# aaa-server svrgrp1 protocol radius
hostname(config-aaa-server-group)# aaa-server svrgrp1 host 1.2.3.4
hostname(config-aaa-server-host)# timeout 9
hostname(config-aaa-server-host)# retry 7
hostname(config-aaa-server-host)# radius-common-pw allauthpw
Related Commands
Command
|
Description
|
aaa-server host
|
Enter AAA server host configuration mode so that you can configure AAA server parameters that are host-specific.
|
clear configure aaa-server
|
Remove all AAA command statements from the configuration.
|
show running-config aaa-server
|
Displays AAA server statistics for all AAA servers, for a particular server group, for a particular server within a particular group, or for a particular protocol
|
radius-with-expiry
To have the FWSM use MS-CHAPv2 to negotiate a password update with the user during authentication, use the radius-with-expiry command in tunnel-group ipsec-attributes configuration mode. The FWSM ignores this command if RADIUS authentication has not been configured.
To return to the default value, use the no form of this command.
radius-with-expiry
no radius-with-expiry
Syntax Description
This command has no arguments or keywords.
Defaults
The default setting for this command is disabled.
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
|
Tunnel-group ipsec-attributes configuration
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
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, configures Radius with Expiry for the remote-access tunnel group named remotegrp:
hostname(config)# tunnel-group remotegrp type ipsec_ra
hostname(config)# tunnel-group remotegrp ipsec-attributes
hostname(config-ipsec)# radius-with-expiry
Related Commands
Command
|
Description
|
clear configure tunnel-group
|
Clears all configured tunnel groups.
|
show running-config tunnel-group
|
Shows the indicated certificate map entry.
|
tunnel-group-map default-group
|
Associates the certificate map entries created using the crypto ca certificate map command with tunnel groups.
|
reactivation-mode
To specify the method (reactivation policy) by which failed servers in a group are reactivated, use the reactivation-mode command in AAA-server group mode. To remove this specification, use the no form of this command:
reactivation-mode depletion [deadtime minutes]
reactivation-mode timed
no reactivation-mode
Syntax Description
deadtime minutes
|
(Optional) Specifies the amount of time that elapses between the disabling of the last server in the group and the subsequent reenabling of all servers.
|
depletion
|
Reactivates failed servers only after all of the servers in the group are inactive.
|
timed
|
Reactivates failed servers after 30 seconds of down time.
|
Defaults
The default reactivation mode is depletion, and the default deadtime value is 10. The supported range of values for deadtime is 0-1440 minutes.
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
|
Aaa-server group
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Usage Guidelines
Each server group has an attribute that specifies the reactivation policy for its servers.
In depletion mode, when a server is deactivated, it remains inactive until all other servers in the group are inactive. When and if this occurs, all servers in the group are reactivated. This approach minimizes the occurrence of connection delays due to failed servers. When depletion mode is in use, you can also specify the deadtime parameter. The deadtime parameter specifies the amount of time (in minutes) that will elapse between the disabling of the last server in the group and the subsequent re-enabling of all servers. This parameter is meaningful only when the server group is being used in conjunction with the local fallback feature.
In timed mode, failed servers are reactivated after 30 seconds of down time. This is useful when customers use the first server in a server list as the primary server and prefer that it is online whenever possible. This policy breaks down in the case of UDP servers. Because UDP is a connectionless protocol, the FWSM cannot determine if the server is present; therefore, UDP servers are put back on line blindly. This could lead to slowed connection times or connection failures if a server list contains multiple servers that are not reachable.
Accounting server groups that have simultaneous accounting enabled are forced to use the timed mode. This implies that all servers in a given list are equivalent.
Examples
The following example configures a TACACS+ AAA server named "svrgrp1" to use the depletion reactivation mode, with a deadtime of 15 minutes:
hostname(config)# aaa-server svrgrp1 protocol tacacs+
hostname(config-aaa-sersver-group)# reactivation-mode depletion deadtime 15
The following example configures a TACACS+ AAA server named "svrgrp1" to use timed reactivation mode:
hostname(config)# aaa-server svrgrp2 protocol tacacs+
hostname(config-aaa-server)# reactivation-mode timed
Related Commands
accounting-mode
|
Indicates whether accounting messages are sent to a single server (single mode) or sent to all servers in the group (simultaneous mode).
|
aaa-server protocol
|
Enters AAA server group configuration mode so that you can configure AAA server parameters that are group-specific and common to all hosts in the group.
|
max-failed-attempts
|
Specifies the number of failures that will be tolerated for any given server in the server group before that server is deactivated.
|
clear configure aaa-server
|
Removes all AAA server configuration.
|
show running-config aaa-server
|
Displays AAA server statistics for all AAA servers, for a particular server group, for a particular server within a particular group, or for a particular protocol
|
redistribute
To redistribute routes from one routing domain into another routing domain, use the redistribute command in router configuration mode. To remove the redistribution, use the no form of this command.
redistribute {{ospf pid [match {internal | external [1 | 2] | nssa-external [1 | 2]}]} | static |
connected} [metric metric_value] [metric-type metric_type] [route-map map_name] [tag
tag_value] [subnets]
no redistribute {{ospf pid [match {internal | external [1 | 2] | nssa-external [1 | 2]}]} | static |
connected} [metric metric_value] [metric-type metric_type] [route-map map_name] [tag
tag_value] [subnets]
Syntax Description
connected
|
Specifies redistributing a network connected to an interface into an OSPF routing process.
|
external type
|
Specifies the OSPF metric routes that are external to a specified autonomous system; valid values are 1 or 2.
|
internal type
|
Specifies OSPF metric routes that are internal to a specified autonomous system.
|
match
|
(Optional) Specifies the conditions for redistributing routes from one routing protocol into another.
|
metric metric_value
|
(Optional) Specifies the OSPF default metric value from 0 to 16777214.
|
metric-type metric_type
|
(Optional) The external link type associated with the default route advertised into the OSPF routing domain. It can be either of the following two values: 1 (Type 1 external route) or 2 (Type 2 external route).
|
nssa-external type
|
Specifies the OSPF metric type for routes that are external to a not-so-stubby area (NSSA); valid values are 1 or 2.
|
ospf pid
|
Used to redistribute an OSPF routing process into the current OSPF routing process. The pid specifies the internally used identification parameter for an OSPF routing process; valid values are from 1 to 65535.
|
route-map map_name
|
(Optional) Name of the route map to apply.
|
static
|
Used to redistribute a static route into an OSPF process.
|
subnets
|
(Optional) For redistributing routes into OSPF, scopes the redistribution for the specified protocol. If not used, only classful routes are redistributed.
|
tag tag_value
|
(Optional) A 32-bit decimal value attached to each external route. This value is not used by OSPF itself. It may be used to communicate information between ASBRs. If none is specified, then the remote autonomous system number is used for routes from BGP and EGP; for other protocols, zero (0) is used. Valid 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:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Router configuration
|
•
|
—
|
•
|
—
|
—
|
Command History
Release
|
Modification
|
1.1(1)
|
This command was introduced.
|
Examples
This example shows how to redistribute static routes into the current OSPF process:
hostname(config-router)# redistribute ospf static
Related Commands
Command
|
Description
|
router ospf
|
Enters router configuration mode.
|
show running-config router
|
Displays the commands in the global router configuration.
|
reload
To reboot and reload the configuration, use the reload command in privileged EXEC mode.
reload [at hh:mm [month day | day month]] [cancel] [in [hh:]mm] [max-hold-time [hh:]mm]
[noconfirm] [quick] [reason text] [save-config]
Syntax Description
at hh:mm
|
(Optional) Schedules a reload of the software to take place at the specified time (using a 24-hour clock). If you do not specify the month and day, the reload occurs at the specified time on the current day (if the specified time is later than the current time), or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The reload must take place within 24 hours.
|
cancel
|
(Optional) Cancels a scheduled reload.
|
day
|
(Optional) Number of the day in the range from 1 to 31.
|
in [hh:]mm]
|
(Optional) Schedules a reload of the software to take effect in the specified minutes or hours and minutes. The reload must occur within 24 hours.
|
max-hold-time [hh:]mm
|
(Optional) Specifies the maximum hold time the FWSM waits to notify other subsystems before a shutdown or reboot. After this time elapses, a quick (forced) shutdown/reboot occurs.
|
month
|
(Optional) Specifies the name of the month. Enter enough characters to create a unique string for the name of the month. For example, "Ju" is not unique because it could represent June or July, but "Jul" is unique because no other month beginning with those exact three letters.
|
noconfirm
|
(Optional) Permits the FWSM to reload without user confirmation.
|
quick
|
(Optional) Forces a quick reload, without notifying or properly shutting down all the subsystems.
|
reason text
|
(Optional) Specifies the reason for the reload, 1 to 255 characters. The reason text is sent to all open IPSec VPN client, terminal, console, telnet, SSH, and ASDM connections/sessions.
Note Some applications, like isakmp, require additional configuration to send the reason text to IPSec VPN Clients. Refer to the appropriate section in the software configuration documentation for more information.
|
save-config
|
(Optional) Saves the running configuration to memory before shutting down. If you do not enter the save-config keyword, any configuration changes that have not been saved will be lost after the reload.
|
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
|
3.1(1)
|
This command was modified to add the following new arguments and keywords: day, hh, mm, month, quick, save-config, and text.
|
Usage Guidelines
The command lets you reboot the FWSM and reload the configuration from Flash.
By default, the reload command is interactive. The FWSM first checks whether the configuration has been modified but not saved. If so, the FWSM prompts you to save the configuration. In multiple context mode, the FWSM prompts for each context with an unsaved configuration. If you specify the save-config parameter, the configuration is saved without prompting you. The FWSM then prompts you to confirm that you really want to reload the system. Only a response of y or pressing the Enter key causes a reload. Upon confirmation, the FWSM starts or schedules the reload process, depending upon whether you have specified a delay parameter (in or at).
By default, the reload process operates in "graceful" (also known as "nice") mode. All registered subsystems are notified when a reboot is about to occur, allowing these subsystems to shut down properly before the reboot. To avoid waiting until for such a shutdown to occur, specify the max-hold-time parameter to specify a maximum time to wait. Alternatively, you can use the quick parameter to force the reload process to begin abruptly, without notifying the affected subsystems or waiting for a graceful shutdown.
You can force the reload command to operate noninteractively by specifying the noconfirm parameter. In this case, the FWSM does not check for an unsaved configuration unless you have specified the save-config parameter. The FWSM does not prompt the user for confirmation before rebooting the system. It starts or schedules the reload process immediately, unless you have specified a delay parameter, although you can specify the max-hold-time or quick parameters to control the behavior or the reload process.
Use reload cancel to cancel a scheduled reload. You cannot cancel a reload that is already in progress.
Note
Configuration changes that are not written to the Flash partition are lost after a reload. Before rebooting, enter the write memory command to store the current configuration in the Flash partition.
Examples
This example shows how to reboot and reload the configuration:
Proceed with ? [confirm] y
Related Commands
Command
|
Description
|
show reload
|
Displays the reload status of the FWSM.
|
remote-access threshold session-threshold-exceeded
To set threshold values, use the remote-access threshold session-threshold-exceeded command in global configuration mode. To remove threshold values, use the no version of this command. This command specifies the number of remote access sessions that need to be active for the FWSM to send traps.
remote-access threshold session-threshold-exceeded {threshold-value}
no remote-access threshold session-threshold-exceeded
Syntax Description
threshold-value
|
Specifies an integer less than or equal to the session limit the FWSM supports.
|
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Command Mode
|
Firewall Mode
|
Security Context
|
Routed
|
Transparent
|
Single
|
Multiple
|
Context
|
System
|
Global configuration
|
•
|
•
|
—
|
—
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Examples
The following example shows how to set a threshold value of 1500:
hostname# remote-access threshold session-threshold-exceeded 1500
Related Commands
Command
|
Description
|
snmp-server enable trap remote-access
|
Enables threshold trapping.
|
rename
To rename a file or a directory from the source filename to the destination filename, use the rename command in privileged EXEC mode.
rename [/noconfirm] [flash:] source-path [flash:] destination-path
Syntax Description
/noconfirm
|
(Optional) Suppresses the confirmation prompt.
|
destination-path
|
Specifies the path of the destination file.
|
flash:
|
(Optional) Specifies the internal flash memory, followed by a colon.
|
source-path
|
Specifies the path of the source file.
|
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
|
3.1(1)
|
Support for this command was introduced.
|
Usage Guidelines
The rename flash: flash: command prompts you to enter a source and destination filename.
You cannot rename a file or directory across file systems.
For example:
hostname# rename flash: disk1:
Source filename []? new-config
Destination filename []? old-config
%Cannot rename between filesystems
Examples
The following example shows how to rename a file named "test" to "test1":
hostname# rename flash: flash:
Source filename [running-config]? test
Destination filename [n]? test1
Related Commands
Command
|
Description
|
mkdir
|
Creates a new directory.
|
rmdir
|
Removes a directory.
|
show file
|
Displays information about the file system.
|
replication http
To enable HTTP connection replication for the failover group, use the replication http command in failover group configuration mode. To disable HTTP connection replication, use the no form of this command.
replication http
no replication http
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
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
|
Failover group configuration
|
•
|
•
|
—
|
—
|
•
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Usage Guidelines
By default, the FWSM does not replicate HTTP session information when Stateful Failover is enabled. Because HTTP sessions are typically short-lived, and because HTTP clients typically retry failed connection attempts, not replicating HTTP sessions increases system performance without causing serious data or connection loss. The replication http command enables the stateful replication of HTTP sessions in a Stateful Failover environment, but could have a negative effect on system performance.
This command is available for Active/Active failover only. It provides the same functionality as the failover replication http command for Active/Standby failover, except for failover groups in Active/Active failover configurations.
Examples
The following example shows a possible configuration for a failover group:
hostname(config)# failover group 1
hostname(config-fover-group)# primary
hostname(config-fover-group)# preempt 100
hostname(config-fover-group)# replication http
hostname(config-fover-group)# exit
Related Commands
Command
|
Description
|
failover group
|
Defines a failover group for Active/Active failover.
|
failover replication http
|
Configures Stateful Failover to replicate HTTP connections.
|
request-command deny
To disallow specific commands within FTP requests, use the request-command deny command in FTP map configuration mode, which is accessible by using the ftp-map command. To remove the configuration, use the no form of this command.
request-command deny { appe | cdup | dele | get | help | mkd | put | rmd | rnfr | rnto | site | stou }
no request-command deny { appe | cdup | help | retr | rnfr | rnto | site | stor | stou }
Syntax Description
appe
|
Disallows the command that appends to a file.
|
cdup
|
Disallows the command that changes to the parent directory of the current working directory.
|
dele
|
Disallows the command that deletes a file on the server.
|
get
|
Disallows the client command for retrieving a file from the server.
|
help
|
Disallows the command that provides help information.
|
mkd
|
Disallows the command that makes a directory on the server.
|
put
|
Disallows the client command for sending a file to the server.
|
rmd
|
Disallows the command that deletes a directory on the server.
|
rnfr
|
Disallows the command that specifies rename-from filename.
|
rnto
|
Disallows the command that specifies rename-to filename.
|
site
|
Disallows the command that are specific to the server system. Usually used for remote administration.
|
stou
|
Disallows the command that stores a file using a unique filename.
|
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
|
FTP map configuration
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Usage Guidelines
This command is used for controlling the commands allowed within FTP requests traversing the FWSM when using strict FTP inspection.
Examples
The following example causes the FWSM to drop FTP requests containing stor, stou, or appe commands:
hostname(config)# ftp-map inbound_ftp
hostname(config-ftp-map)# request-command deny put stou appe
Related Commands
Commands
|
Description
|
class-map
|
Defines the traffic class to which to apply security actions.
|
ftp-map
|
Defines an FTP map and enables FTP map configuration mode.
|
inspect ftp
|
Applies a specific FTP map to use for application inspection.
|
mask-syst-reply
|
Hides the FTP server response from clients.
|
policy-map
|
Associates a class map with specific security actions.
|
request-method
To restrict HTTP traffic based on the HTTP request method, use the request-method command in HTTP map configuration mode, which is accessible using the http-map command. To disable this feature, use the no form of the command.
request-method {{ ext ext_methods | default} | { rfc rfc_methods | default}} action {allow | reset
| drop} [log]
no request-method { ext ext_methods | rfc rfc_methods } action {allow | reset | drop} [log]
Syntax Description
action
|
Identifies the action taken when a message fails this command inspection.
|
allow
|
Allows the message.
|
default
|
Specifies the default action taken by the FWSM when the traffic contains a supported request method that is not on a configured list.
|
drop
|
Closes the connection.
|
ext
|
Specifies extension methods.
|
ext-methods
|
Identifies one of the extended methods you want to allow to pass through the FWSM.
|
log
|
(Optional) Generates a syslog.
|
reset
|
Sends a TCP reset message to client and server.
|
rfc
|
Specifies RFC 2616 supported methods.
|
rfc-methods
|
Identifies one of the RFC methods you want to allow to pass through the FWSM (see Table 23-1).
|
Defaults
This command is disabled by default. When the command is enabled and a supported request method is not specified, the default action is to allow the connection without logging. To change the default action, use the default keyword and specify a different default action.
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
|
HTTP map configuration
|
•
|
•
|
•
|
•
|
—
|
Command History
Release
|
Modification
|
3.1(1)
|
This command was introduced.
|
Usage Guidelines
When you enable the request-method command, the FWSM applies the specified action to HTTP connections for each supported and configured request method.
The FWSM applies the default action to all traffic that does not match the request methods on the configured list. The default action is to allow connections without logging. Given this preconfigured default action, if you specify one or more request methods with the action of drop and log, the FWSM drops connections containing the configured request methods, logs each connection, and allows all connections containing other supported request methods.
If you want to configure a more restrictive policy, change the default action to drop (or reset) and log (if you want to log the event). Then configure each permitted method with the allow action.
Enter the request-method command once for each setting you wish to apply. You use one instance of the request-method command to change the default action or to add a single request method to the list of configured methods.
When you use the no form of the command to remove a request method from the list of configured methods, any characters in the command line after the request method keyword are ignored.
Table 23-1 lists the methods defined in RFC 2616 that you can add to the list of configured methods:
Table 23-1 RFC 2616 Methods
Method
|
Description
|
connect
|
Used with a proxy that can dynamically switch to being a tunnel (for example SSL tunneling).
|
delete
|
Requests that the origin server delete the resource identified by the Request-URI.
|
get
|
Retrieves whatever information or object is identified by the Request-URI.
|
head
|
Identical to GET except that the server does not return a message-body in the response.
|
options
|
Represents a request for information about the communication options available on server identified by the Request-URI.
|
post
|
Request that the origin server accept the object enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line.
|
put
|
Requests that the enclosed object be stored under the supplied Request-URI.
|
trace
|
Invokes a remote, application-layer loop-back of the request message.
|
Examples
The following example provides a permissive policy, using the preconfigured default, which allows all supported request methods that are not specifically prohibited.
hostname(config)# http-map inbound_http
hostname(config-http-map)# request-method rfc options drop log
hostname(config-http-map)# request-method rfc post drop log
In this example, only the options and post request methods are dropped and the events are logged.
The following example provides a restrictive policy, with the default action changed to reset the connection and log the event for any request method that is not specifically allowed.
hostname(config)# http-map inbound_http
hostname(config-http-map)# request-method rfc default action reset log
hostname(config-http-map)# request-method rfc get allow
hostname(config-http-map)# request-method rfc put allow
In this case, the get and put request methods are allowed. When traffic is detected that uses any other methods, the FWSM resets the connection and creates a syslog entry.
Related Commands
Commands
|
Description
|
class-map
|
Defines the traffic class to which to apply security actions.
|
debug appfw
|
Displays detailed information about traffic associated with enhanced HTTP inspection.
|
http-map
|
Defines an HTTP map for configuring enhanced HTTP inspection.
|
|