-
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Command Reference, 3.1
-
About This Guide
-
Using the Command Line Interface
-
aaa accounting through accounting-server-group
-
activation-key through auto-update timeout
-
backup-servers through bridge-group
-
cache-time through clear capture
-
clear configure through clear configure virtual
-
clear conn through clear xlate
-
client-access-rule through crl-configure
-
crypto ca authenticate through crypto map set trustpoint
-
debug aaa through debug xdmcp
-
default through drop
-
email through ftp-map
-
gateway through http-map
-
icmp through ignore lsa mospf
-
inspect ctiqbe through inspect xdmcp
-
interface through issuer-name
-
join-failover-group through kill
-
ldap-base-dn through log-adj-changes
-
logging asdm through logout
-
mac-address-table aging-time through multicast-routing
-
name through ospf transmit-delay
-
pager through pwd
-
quit through router-id
-
same-security-traffic through show asdm sessions
-
show asp drop through show curpriv
-
show debug through show ipv6 traffic
-
show isakmp sa through show route
-
show running-config through show running-config isakmp
-
show running-config logging through show running-config vpn-sessiondb
-
show service-policy through show xlate
-
shun through sysopt uauth allow-http-cache
-
telnet through tunnel-limit
-
upgrade-mp through write terminal
-
Feedback
Table Of Contents
cache-time through clear capture Commands
clear aaa local user fail-attempts
cache-time through clear capture Commands
cache-time
To specify in minutes how long to allow a CRL to remain in the cache before considering it stale, use the cache-time command in ca-crl configuration mode. To return to the default value, use the no form of this command.
cache-time refresh-time
no cache-time
Syntax Description
refresh-time
Specifies the number of minutes to allow a CRL to remain in the cache. The range is 1 - 1440 minutes. If the NextUpdate field is not present in the CRL, the CRL is not cached.
Defaults
The default setting is 60 minutes.
Command Modes
The following table shows the modes in which you can enter the command:
Ca-crl configuration
•
•
•
•
—
Command History
Examples
The following example enters ca-crl configuration mode, and specifies a cache time refresh value of 10 minutes for trustpoint central:
hostname(configure)# crypto ca trustpoint centralhostname(ca-trustpoint)# crl configurehostname(ca-crl)# cache-time 10hostname(ca-crl)#Related Commands
call-agent
To specify a group of call agents, use the call-agent command in MGCP map configuration mode, which is accessible by using the mgcp-map command. To remove the configuration, use the no form of this command.
call-agent ip_address group_id
no call-agent ip_address group_id
Syntax Description
ip_address
The IP address of the gateway.
group_id
The ID of the call agent group, from 0 to 2147483647.
Defaults
This command is disabled by default.
Command Modes
The following table shows the modes in which you can enter the command:
MGCP map configuration
•
•
•
•
—
Command History
Usage Guidelines
Use the call-agent command to specify a group of call agents that can manage one or more gateways. The call agent group information is used to open connections for the call agents in the group (other than the one a gateway sends a command to) so that any of the call agents can send the response. Call agents with the same group_id belong to the same group. A call agent may belong to more than one group. The group_id option is a number from 0 to 4294967295. The ip_address option specifies the IP address of the call agent.
Examples
The following example allows call agents 10.10.11.5 and 10.10.11.6 to control gateway 10.10.10.115, and allows call agents 10.10.11.7 and 10.10.11.8 to control both gateways 10.10.10.116 and 10.10.10.117:
hostname(config)# mgcp-map mgcp_inboundhostname(config-mgcp-map)# call-agent 10.10.11.5 101hostname(config-mgcp-map)# call-agent 10.10.11.6 101hostname(config-mgcp-map)# call-agent 10.10.11.7 102hostname(config-mgcp-map)# call-agent 10.10.11.8 102hostname(config-mgcp-map)# gateway 10.10.10.115 101hostname(config-mgcp-map)# gateway 10.10.10.116 102hostname(config-mgcp-map)# gateway 10.10.10.117 102Related Commands
capture
To enable packet capture capabilities for packet sniffing and network fault isolation, use the capture command. To disable packet capture capabilities, use the no form of this command.
capture capture_name [type {asp-drop [drop-code] | raw-data }] access-list access_list_name interface interface_name [buffer buf_size] [ethernet-type type] [packet-length bytes] [circular-buffer]
no capture capture-name [type {asp-drop [drop-code] | raw-data }] [access-list access_list_name] [interface interface_name]
Note
Syntax Description
Defaults
The defaults are as follows:
•
•
•
•
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
•
Command History
1.1(1)
This command was introduced.
3.1(1)
Added the capability to capture all traffic, not just traffic that passes through the general-purpose processor.
Usage Guidelines
Capturing packets is useful when troubleshooting connectivity problems or monitoring suspicious activity. You can create multiple captures. To view the packet capture, use the show capture name command. To save the capture to a file, use the copy capture command.
The FWSM is capable of tracking all IP traffic that flows across it. It is also capable of capturing all the IP traffic that is destined to the FWSM, including all the management traffic (such as SSH and Telnet traffic) to the FWSM.
Enter the no capture command with the access-list and interface keywords to stop the capture without deleting the capture buffer. To stop the capture and delete the buffer, enter no capture name without additional keywords.
Note
Examples
This example shows that the traffic is captured from an outside host at 171.71.69.234 to an inside HTTP server:
hostname(config)# access-list http permit tcp host 10.120.56.15 eq http host 171.71.69.234hostname(config)# access-list http permit tcp host 171.71.69.234 host 10.120.56.15 eq httphostname(config)# capture captest access-list http packet-length 74 interface insideOn a web browser, the capture contents for a capture named "captest" can be viewed at the following location, depending on firewall mode and version:
Before version 3.1(7) and 3.2(2):
https://171.69.38.95/capture/captestAfter version 3.1(7) or 3.2(2) and in single context mode:
https://171.69.38.95/capture/single_vf/captestAfter version 3.1(7) or 3.2(2) and in multiple context mode:
https://171.69.38.95/capture/context_name/captestWhere context_name is the actual name of the context where the capture was configured. To download the binary capture file from the FWSM, append "/pcap" to the end of the URL. For example:
https://171.69.38.95/capture/single_vf/captest/pcapRelated Commands
clear capture
Clears the capture buffer.
copy capture
Copies a capture file to a server.
show capture
Displays the capture configuration when no options are specified.
cd
To change the current working directory to the one specified, use the cd command in privileged EXEC mode.
cd [flash:] [path]
Syntax Description
flash:
Specifies the internal Flash memory, followed by a colon.
path
(Optional) The absolute path of the directory to change to.
Defaults
If you do not specify a directory, the directory is changed to the root directory.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
•
Command History
Examples
This example shows how to change to the "config" directory:
hostname# cd flash:/config/Related Commands
certificate
To add the indicated certificate, use the certificate command in crypto ca certificate chain mode. When you use this command, the FWSM interprets the data included with it as the certificate in hexadecimal format. A quit string indicates the end of the certificate.
To delete the certificate, use the no form of the command.
certificate {ca | ra-encrypt | ra-sign | ra-general} certificate-serial-number
no certificate certificate-serial-number
Syntax Description
Syntax DescriptionSyntax Description
Defaults
This command has no default values.
Command Modes
The following table shows the modes in which you can enter the command:
Crypto ca certificate chain configuration
•
•
•
•
—
Command History
Usage Guidelines
A certificate authority is an authority in a network that issues and manages security credentials and public key for message encryption. As part of a public key infrastructure, a CA checks with a registration authority to verify information provided by the requestor of a digital certificate. If the RA verifies the requestor's information, the CA can then issue a certificate.
Examples
This example enters ca trustpoint mode for a trustpoint named central, then enters crypto ca certificate chain mode for central, and adds a CA certificate with a serial number 29573D5FF010FE25B45:
hostname(config)# crypto ca trustpoint centralhostname(ca-trustpoint)# crypto ca certificate chain centralhostname(ca-cert-chain)# certificate ca 29573D5FF010FE25B4530820345 308202EF A0030201 02021029 572A3FF2 96EF854F D0D6732F E25B45300D06092A 864886F7 0D010105 05003081 8F311630 1406092A 864886F7 0D01090116076140 622E636F 6D310B30 09060355 04061302 55533116 30140603 550408130D6D6173 73616368 75736574 74733111 300F0603 55040713 08667261 6E6B6C696E310E30 0C060355 040A1305 63697363 6F310F30 0D060355 040B1306 726F6F746F75311C 301A0603 55040313 136D732D 726F6F74 2D736861 2D30362D 32303031301E170D 30313036 32363134 31313430 5A170D32 32303630 34313430 3133305A30818F31 16301406 092A8648 86F70D01 09011607 6140622E 636F6D31 0B30090603550406 13025553 31163014 06035504 08130D6D 61737361 63687573 657474733111300F 06035504 07130866 72616E6B 6C696E31 0E300C06 0355040A 1305636973636F31 0F300D06 0355040B 1306726F 6F746F75 311C301A 06035504 0313136D732D726F 6F742D73 68612D30 362D3230 3031305C 300D0609 2A864886 F70D010101050003 4B003048 024100AA 3EB9859B 8670A6FB 5E7D2223 5C11BCFE 48E6D3A8181643ED CF7E75EE E77D83DF 26E51876 97D8281E 9F58E4B0 353FDA41 29FC791B1E14219C 847D19F4 A51B7B02 03010001 A3820123 3082011F 300B0603 551D0F0404030201 C6300F06 03551D13 0101FF04 05300301 01FF301D 0603551D 0E04160414E0D412 3ACC96C2 FBF651F3 3F66C0CE A62AB63B 323081CD 0603551D 1F0481C53081C230 3EA03CA0 3A86386C 6461703A 2F2F7732 6B616476 616E6365 647372762F436572 74456E72 6F6C6C2F 6D732D72 6F6F742D 7368612D 30362D32 3030312E63726C30 3EA03CA0 3A863868 7474703A 2F2F7732 6B616476 616E6365 647372762F436572 74456E72 6F6C6C2F 6D732D72 6F6F742D 7368612D 30362D32 3030312E63726C30 40A03EA0 3C863A66 696C653A 2F2F5C5C 77326B61 6476616E 6365647372765C43 65727445 6E726F6C 6C5C6D73 2D726F6F 742D7368 612D3036 2D323030312E6372 6C301006 092B0601 04018237 15010403 02010130 0D06092A 864886F70D010105 05000341 0056221E 03F377B9 E6900BF7 BCB3568E ADBA146F 3B8A71F3DF9EB96C BB1873B2 B6268B7C 0229D8D0 FFB40433 C8B3CB41 0E4D212B 2AEECD77BEA3C1FE 5EE2AB6D 91quitRelated Commands
chain
To enable sending of a certificate chain, use the chain command in tunnel-group ipsec-attributes configuration mode. This action includes the root certificate and any subordinate CA certificates in the transmission. To return this command to the default, use the no form of this command.
chain
no chain
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:
Tunnel-group ipsec attributes configuration
•
•
•
•
—
Command History
Usage Guidelines
You can apply this attribute to all tunnel-group types.
Examples
The following example entered in config-ipsec configuration mode, enables sending a chain for an IPSec LAN-to-LAN tunnel group with the IP address of 209.165.200.225, which includes the root certificate and any subordinate CA certificates:
hostname(config)# tunnel-group 209.165.200.225 type IPSec_L2Lhostname(config)# tunnel-group 209.165.200.225 ipsec-attributeshostname(config-ipsec)# chainhostname(config-ipsec)#Related Commands
changeto
To change between security contexts and the system, use the changeto command in privileged EXEC mode.
changeto {system | context name}
Syntax Description
context name
Changes to the context with the specified name.
system
Changes to the system execution space.
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
If you log in to the system execution space or the admin context, you can change between contexts and perform configuration and monitoring tasks within each context. The "running" configuration that you edit in configuration mode, or that is used in the copy or write commands, depends on which execution space you are in. When you are in the system execution space, the running configuration consists only of the system configuration; when you are in a context execution space, the running configuration consists only of that context. For example, you cannot view all running configurations (system plus all contexts) by entering the show running-config command. Only the current configuration appears.
Examples
The following example changes between contexts and the system in privileged EXEC mode:
hostname/admin# changeto systemhostname# changeto context customerAhostname/customerA#The following example changes between the system and the admin context in interface configuration mode. When you change between execution spaces, and you are in a configuration mode, the mode changes to the global configuration mode in the new execution space.
hostname(config-if)# changeto context adminhostname/admin(config)#Related Commands
checkheaps
To configure checkheaps verification intervals, use the checkheaps command in global configuration mode. To set the value to the default, use the no form of this command. Checkheaps is a periodic process that verifies the sanity of the heap memory buffers (dynamic memory is allocated from the system heap memory region) and the integrity of the code region.
checkheaps {check-interval | validate-checksum} seconds
no checkheaps {check-interval | validate-checksum} [seconds]
Syntax Description
Defaults
The default intervals are 60 seconds each.
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 buffer allocation interval to 200 seconds and the code space checksum interval to 500 seconds:
hostname(config)# checkheaps check-interval 200hostname(config)# checkheaps validate-checksum 500Related Commands
check-retransmission
To prevent against TCP retransmission attacks, use the check-retransmission command in tcp-map configuration mode. To remove this specification, use the no form of this command.
check-retransmission
no check-retransmission
Syntax Description
This command has no arguments or keywords.
Defaults
The default is disabled.
Command Modes
The following table shows the modes in which you can enter the command:
Tcp-map configuration
•
•
•
•
—
Command History
Usage Guidelines
The tcp-map command is used along with the Modular Policy Framework infrastructure. Define the class of traffic using the class-map command and customize the TCP inspection with tcp-map commands. Apply the new TCP map using the policy-map command. Activate TCP inspection with service-policy commands.
Use the tcp-map command to enter tcp-map configuration mode. To prevent against TCP retransmission style attacks that arise from end-system interpretation of inconsistent retransmissions, use the check-retransmission command in tcp-map configuration mode.
Examples
The following example enables the TCP check-retransmission feature on all TCP flows:
hostname(config)# access-list TCP extended permit tcp any anyhostname(config)# tcp-map tmaphostname(config-tcp-map)# check-retransmissionhostname(config-tcp-map)# class-map cmaphostname(config-cmap)# match access-list TCPhostname(config-cmap)# policy-map pmaphostname(config-pmap)# class cmaphostname(config-pmap)# set connection advanced-options tmaphostname(config-pmap)# service-policy pmap globalRelated Commands
class
To create a resource class to which to assign a security context, use the class command in global configuration mode. To remove a class, use the no form of this command.
class name
no class name
Syntax Description
name
Specifies the name as a string up to 20 characters long. To set the limits for the default class, enter default for the name.
Defaults
No default behavior or values.
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
By default, all security contexts have unlimited access to the resources of the FWSM, except where maximum limits per context are enforced. However, if you find that one or more contexts use too many resources, and they cause other contexts to be denied connections, for example, then you can configure resource management to limit the use of resources per context.
The FWSM manages resources by assigning contexts to resource classes. Each context uses the resource limits set by the class.
Note
When you create a class, the FWSM does not set aside a portion of the resources for each context assigned to the class; rather, the FWSM sets the maximum limit for a context. If you oversubscribe resources, or allow some resources to be unlimited, a few contexts can "use up" those resources, potentially affecting service to other contexts. See the limit-resource command to set the resources for the class.
All contexts belong to the default class if they are not assigned to another class; you do not have to actively assign a context to the default class.
If a context belongs to a class other than the default class, those class settings always override the default class settings. However, if the other class has any settings that are not defined, then the member context uses the default class for those limits. For example, if you create a class with a 2 percent limit for all concurrent connections, but no other limits, then all other limits are inherited from the default class. Conversely, if you create a class with a 2 percent limit for all resources, the class uses no settings from the default class.
By default, the default class provides unlimited access to resources for all contexts, except for the following limits, which are by default set to the maximum allowed per context:
•
•
•
•
Examples
The following example sets the default class limit for conns to 10 percent instead of unlimited:
hostname(config)# class defaulthostname(config-class)# limit-resource conns 10%All other resources remain at unlimited.
To add a class called gold with all resources set to 5 percent, except for fixups, with a setting of 10 percent, enter the following commands:
hostname(config)# class goldhostname(config-class)# limit-resource all 5%hostname(config-class)# limit-resource fixups 10%To add a class called silver with all resources set to 3 percent, except for system log messages, with a setting of 500 per second, enter the following commands:
hostname(config)# class silverhostname(config-class)# limit-resource all 3%hostname(config-class)# limit-resource rate syslogs 500Related Commands
class (policy-map)
To assign a class-map to a policy for traffic classification, use the class command in policy-map mode. To remove a class-map specification for a policy map, use the no form of this command.
class classmap-name
no class classmap-name
Syntax Description
Defaults
By default, "class class-default" always exists at the end of a policy map.
Command Modes
The following table shows the modes in which you can enter the command:
Policy-map
•
•
•
•
—
Command History
Usage Guidelines
Including the class-default, up to 63 class commands can be configured in a policy map.
The name "class-default" is a reserved name for default class, and it always exists; that is, you can include it in your configuration, but you cannot reconfigure or remove it using CLI. See the description of the class-map command for more information.
Use the class command to enter class mode, in which you can enter the following commands:
•
•
•
See the individual command descriptions for detailed information.
Examples
The following is an example of a policy-map command, with its class commands, for a connection policy that limits connections to an HTTP server to a maximum of 256:
hostname(config)# access-list myhttp permit tcp any host 10.1.1.1hostname(config)# class-map myhttphostname(config-cmap)# match access-list myhttphostname(config-cmap)# exithostname(config)# policy-map global-policyhostname(config-pmap)# description This policy map defines a policy concerning connection to http server.hostname(config-pmap)# class myhttphostname(config-pmap-c)# set connection conn-max 256Related Commands
class-map
When using the Modular Policy Framework, identify Layer 3 or 4 traffic to which you want to apply actions by using the class-map command in global configuration mode. To delete a class map, use the no form of this command.
class-map class_map_name
no class-map class_map_name
Syntax Description
Defaults
No default behaviors or values.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
A Layer 3/4 class map identifies Layer 3 and 4 traffic to which you want to apply actions. You can create multiple Layer 3/4 class maps for each Layer 3/4 policy map.
Default Class Maps
The configuration includes a default Layer 3/4 class map that the FWSM uses in the default global policy. It is called inspection_default and matches the default inspection traffic:
class-map inspection_defaultmatch default-inspection-trafficAnother class map that exists in the default configuration is called class-default, and it matches all traffic:
class-map class-defaultmatch anyThis class map appears at the end of all Layer 3/4 policy maps and essentially tells the FWSM to not perform any actions on all other traffic. You can use the class-default class map if desired, rather than making your own match any class map.
Maximum Class Maps
The maximum number of class maps of all types is 255 in single mode or per context in multiple mode. This limit also includes default class maps of all types.
Configuration Overview
Configuring Modular Policy Framework consists of four tasks:
1.
2.
3.
Use the class-map command to enter class-map configuration mode. From class-map configuration mode, you can define the traffic to include in the class using the match command. A Layer 3/4 class map contains, at most, one match command (with the exception of the match default-inspection-traffic commands) that identifies the traffic included in the class map.
Examples
The following example creates four Layer 3/4 class maps:
hostname(config)# access-list udp permit udp any anyhostname(config)# access-list tcp permit tcp any anyhostname(config)# access-list host_foo permit ip any 10.1.1.1 255.255.255.255hostname(config)# class-map all_udphostname(config-cmap)# description "This class-map matches all UDP traffic"hostname(config-cmap)# match access-list udphostname(config-cmap)# class-map all_tcphostname(config-cmap)# description "This class-map matches all TCP traffic"hostname(config-cmap)# match access-list tcphostname(config-cmap)# class-map all_httphostname(config-cmap)# description "This class-map matches all HTTP traffic"hostname(config-cmap)# match port tcp eq httphostname(config-cmap)# class-map to_serverhostname(config-cmap)# description "This class-map matches all traffic to server 10.1.1.1"hostname(config-cmap)# match access-list host_fooRelated Commands
clear aaa local user fail-attempts
To reset the number of failed user authentication attempts to zero without modifying a user locked-out status, use the clear aaa local user fail-attempts command in privileged EXEC mode.
clear aaa local user authentication fail-attempts {username name | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
Use this command when a user fails authentication a few times, but you want to reset to counter to zero, for example, when the configuration has recently been modified.
After the configured number of failed authentication attempts, the user is locked out of the system and cannot successfully log in until either a system administrator unlocks the username or the system reboots.
The number of failed attempts resets to zero and the lockout status resets to No when the user successfully authenticates or when the FWSM reboots.
Locking or unlocking a username results in a syslog message.
A system administrator with a privilege level of 15 cannot be locked out.
Examples
The following example shows use of the clear aaa local user authentication fail-attempts command to reset the failed-attempts counter to 0 for the username anyuser:
hostname(config)# clear aaa local user authentication fail-attempts username anyuserhostname(config)#The following example shows use of the clear aaa local user authentication fail-attempts command to reset the failed-attempts counter to 0 for all users:
hostname(config)# clear aaa local user authentication fail-attempts allhostname(config)#Related Commands
clear aaa local user lockout
To clear the lockout status of the specified users and set their failed-attempts counter to 0, use the clear aaa local user lockout command in privileged EXEC mode.
clear aaa local user lockout {username name | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Usage Guidelines
You can specify a single user by using the username option or all users with the all option.
This command affects only the status of users that are locked out.
The administrator cannot be locked out of the device.
Locking or unlocking a username results in a syslog message.
Examples
The following example shows use of the clear aaa local user lockout command to clear the lockout condition and reset the failed-attempts counter to 0 for the username anyuser:
hostname(config)# clear aaa local user lockout username anyuserhostname(config)#Related Commands
clear aaa-server statistics
To reset the statistics for AAA servers, use the clear aaa-server statistics command in privilged EXEC mode.
clear aaa-server statistics [LOCAL | groupname [host hostname] | protocol protocol]
Syntax Description
Defaults
Remove all AAA-server statistics across all groups.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
—
Command History
Examples
The following command shows how to reset the AAA statistics for a specific server in a group:
hostname(config)# clear aaa-server statistics svrgrp1 host 1.2.3.4The following command shows how to reset the AAA statistics for an entire server group:
hostname(config)# clear aaa-server statistics svrgrp1The following command shows how to reset the AAA statistics for all server groups:
hostname(config)# clear aaa-server statisticsThe following command shows how to reset the AAA statistics for a particular protocol (in this case, TACACS+):
hostname(config)# clear aaa-server statistics protocol tacacs+Related Commands
clear access-list
To clear access-list counters, use the clear access-list command in global configuration mode.
clear access-list [id counters]
Syntax Description
Defaults
All the access list counters are cleared.
Command Modes
The following table shows the modes in which you can enter the command:
Global configuration
•
•
•
•
—
Command History
Usage Guidelines
When you enter the clear access-list command, all the access list counters are cleared if you do not specify an id.
Examples
The following example shows how to clear a specific access list counter:
hostname# clear access-list inbound countersRelated Commands
clear arp
To clear dynamic ARP entries or ARP statistics, use the clear arp command in privileged EXEC mode.
clear arp [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:
Privileged EXEC
•
•
•
•
—
Command History
Examples
The following example clears all ARP statistics:
hostname# clear arp statisticsRelated Commands
clear asp drop
To clear accelerated security path drop statistics, use the clear asp drop command in privileged EXEC mode.
clear asp drop [flow type | frame type]
Syntax Description
Defaults
By default, this command clears all drop statistics.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
•
•
Command History
Usage Guidelines
Process types include the following:
acl-dropaudit-failureclosed-by-inspectionconn-limit-exceededfin-timeoutflow-reclaimedfo-primary-closedfo-standbyfo_rep_errhost-removedinspect-failips-fail-closeips-requestipsec-spoof-detectloopbackmcast-entry-removedmcast-intrf-removedmgmt-lockdownnat-failednat-rpf-failedneed-ikeno-ipv6-ipsecnon_tcp_synout-of-memoryparent-closedpinhole-timeoutrecursereinject-puntreset-by-ipsreset-inreset-ooutshunnedsyn-timeouttcp-finstcp-intecept-no-responsetcp-intercept-killtcp-intercept-unexpectedtcpnorm-invalid-syntcpnorm-rexmit-badtcpnorm-win-variationtimeouttunnel-pendingtunnel-torn-downxlate-removedExamples
The following example clears all drop statistics:
hostname# clear asp dropRelated Commands
clear blocks
To reset the packet buffer counters such as the low watermark and history information, use the clear blocks command in privileged EXEC mode.
clear blocks
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
The following table shows the modes in which you can enter the command:
Privileged EXEC
•
•
•
—
•
Command History
Usage Guidelines
Resets the low watermark counters to the current available blocks in each pool. Also clears the history information stored during the last buffer allocation failure.
Examples
The following example clears the blocks:
hostname# clear blocksRelated Commands
blocks
Increases the memory assigned to block diagnostics
show blocks
Shows the system buffer utilization.
clear capture
To clear the capture buffer, use the clear capture capture_name command.
clear capture capture_name
Syntax Description
Defaults
This command has no default settings.
Command Modes
The following table shows the modes in which you can enter the command:
Priveleged Mode
•
•
•
•
•
Command History
Usage Guidelines
The shortened form of the clear capture (for example, cl cap or clear cap) is not supported to prevent accidental destruction of all the packet captures.
Examples
This example shows how to clear the capture buffer for the capture buffer "trudy":
hostname(config)# clear capture trudyRelated Commands
capture
Enables packet capture capabilities for packet sniffing and network fault isolation.
show capture
Displays the capture configuration when no options are specified.
