- Preface
- Using the WAAS Command-Line Interface
- Cisco WAAS Software Command Summary
- CLI Commands
- EXEC Mode Commands
- Global Configuration Mode Commands
- Interface Configuration Mode Commands
- Standard ACL Configuration Mode Commands
- Extended ACL Configuration Mode Commands
- Preposition Configuration Mode Commands
- PKI Certification Authority Configuration Mode Commands
- PKI Global Settings Configuration Mode Commands
- SSL Accelerated Service Configuration Mode Commands
- SSL Cipher List Configuration Mode Commands
- SSL Global Service Configuration Mode Commands
- SSL Host Peering Service Configuration Mode Commands
- SSL Management Service Configuration Mode Commands
- WCCP Configuration Mode Commands
- Service Context Configuration Mode Commands
- Service Node Group Configuration Mode Commands
- Service Node Configuration Mode Commands
- Service Context Configuration Mode Commands
- Class Map Configuration Mode Commands
- Policy Map Configuration Mode Commands
- Policy Map Class Configuration Mode Commands
- Acronyms and Abbreviations
- Command Summary by Mode
- (config) aaa accounting
- (config) aaa authorization commands
- (config) accelerator epm
- (config) accelerator http
- (config) accelerator http object-cache enable
- (config) accelerator http object-cache transparent enable
- (config) accelerator http object-cache transparent basic
- (config) accelerator http object-cache transparent standard
- (config) accelerator http object-cache transparent advanced
- (config) accelerator http object-cache transparent bypass
- (config) accelerator http object-cache ott enable
- (config) accelerator http object-cache connected enable
- (config) accelerator http object-cache cws-check enable
- (config) accelerator http object-cache validate-address bypass
- (config) accelerator http object-cache validate-address enable
- (config) accelerator http preposition proxy server
- (config) accelerator ica
- (config) accelerator mapi
- (config) accelerator smb
- (config) accelerator smb preposition
- (config) accelerator smb preposition dre
- (config) accelerator ssl
- (config) alarm overload-detect
- (config) asset
- (config) authentication configuration
- (config)authentication enable
- (config) authentication content-request
- (config) authentication fail-over
- (config) authentication login
- (config) authentication strict-password-policy
- (config) auto-discovery
- (config) auto-register
- (config) banner
- (config) bridge
- (config) cdp
- (config) central-manager
- (config) class-map
- (config) clock
- (config) cms
- (config) crypto encryption-servic e
- (config) crypto pki
- (config) crypto ssl
- (config) device mode
- (config) disk disk-name
- (config) disk cache
- (config) disk encrypt
- (config) disk error-handling
- (config) disk logical shutdown
- (config) disk object-cache extend
- (config) dre
- (config) end
- (config) exec-timeout
- (config) exit
- (config) flow exporter
- (config) flow record
- (config) flow monitor
- (config) help
- (config) hostname
- (config) inetd
- (config) inline
- (config) inline vlan-id-connection-check
- (config) interception
- (config) interception-method
- (config) interface GigabitEthernet
- (config) interface InlineGroup
- (config) interface PortChannel
- (config) interface standby
- (config) interface TenGigabitEthernet
- (config) interface virtual
- (config) ip
- (config) ip access-list
- (config) ip icmp rate-limit unreachable
- (config) ip unreachables df
- (config) ip v6
- (config) kerberos
- (config) kernel kdb
- (config) kernel kdump enable
- (config) line
- (config) logging console
- (config) logging disk
- (config) logging facility
- (config) logging host
- (config) ntp
- (config) peer
- (config) policy-map
- (config) port-channel
- (config) primary-interface
- (config) radius-server
- (config) service-insertion
- (config) service-policy
- (config) smb-conf
- (config) snmp-server access-list
- (config) snmp-server community
- (config) snmp-server contact
- (config) snmp-server enable traps
- (config) snmp-server group
- (config) snmp-server host
- (config) snmp-server location
- (config) snmp-server mib
- (config) snmp-server monitor user
- (config) snmp-server notify inform
- (config) snmp-server trap-source
- (config) snmp-server trigger
- (config) snmp-server user
- (config) snmp-server view
- (config) sshd
- (config) ssh-key-generate
- (config) stats-collector logging
- (config) system jumbomtu
- (config) tacacs
- (config) tcp
- (config) telnet enable
- (config) tfo exception
- (config) tfo optimize
- (config) tfo tcp adaptive-buffer-sizing
- (config) tfo tcp keepalive
- (config) tfo tcp optimized-mss
- (config) tfo tcp optimized-receive-buffer
- (config) tfo tcp optimized-send-buffer
- (config) tfo tcp original-mss
- (config) tfo tcp original-receive-buffer
- (config) tfo tcp original-send-buffer
- (config) threshold-monitor
- (config) username
- (config) vn-service vpath
- (config) wccp access-list
- (config) wccp flow-redirect
- (config) wccp router-list
- (config) wccp shutdown
- (config) wccp tcp-promiscuous service-pair
- (config) windows-domain
Global Configuration Mode Commands
Use global configuration mode for setting, viewing, and testing configuration of WAAS software features for the entire device. To enter this mode, enter the configure command from privileged EXEC mode. The prompt for global configuration mode consists of the hostname of the WAE followed by (config) and the pound sign (#). You must be in global configuration mode to enter global configuration commands.
Commands entered in global configuration mode update the running configuration file as soon as they are entered. These changes are not saved into the startup configuration file until you enter the copy running-config startup-config EXEC mode command. Once the configuration is saved, it is maintained across WAE reboots.
You also can use global configuration mode to enter specific configuration modes. From global configuration mode you can enter the interface configuration mode, standard ACL configuration mode, or the extended ACL configuration mode.
To exit global configuration mode and return to privileged-level EXEC mode, use either the exit or end global configuration command:
(config) aaa accounting
To configure AAA accounting on a WAAS device, use the aaa accounting global configuration command. To unconfigure AAA, use the no form of this command.
aaa accounting cms enable tacacs+
no aaa accounting cms enable tacacs+
aaa accounting commands { 0 | 15 } default { start-stop | stop-only | wait-start } tacacs
no aaa accounting commands { 0 | 15 } default { start-stop | stop-only | wait-start } tacacs
aaa accounting exec default { start-stop | stop-only | wait-start } tacacs
no aaa accounting exec default { start-stop | stop-only | wait-start } tacacs
aaa accounting system default { start-stop | stop-only } tacacs
no aaa accounting system default { start-stop | stop-only } tacacs
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to configure TACACS+ on the WAAS device, specify that a start accounting notice should be sent at the beginning of the process and a stop accounting notice at the end of the process, and request that the user process should begin regardless of whether the start accounting notice was received by the accounting server:
The following example shows that the WAAS device is set to record all user EXEC sessions. The command also specifies that a stop accounting notice should be sent to the TACACS+ server at the end of the session.
The following example shows that the WAAS device is set to record all CLI commands executed by a normal user. The command also specifies that a stop accounting notice should be sent to the TACACS+ server at the end of each CLI command executed by a normal user.
The following example shows that the WAAS device is set to record all CLI commands executed by an administrative user. The command also specifies that a start accounting notice should be sent to the TACACS+ server at the beginning of the process and a stop accounting notice at the end of the process. The CLI command executed by the administrative user does not proceed until the start accounting notice has been acknowledged.
The following example shows the EXEC shell accounting report that is available on the TACACS+ server:
The following example shows the system accounting report that is available on the TACACS+ server:
The following example shows the command accounting report that is available on the TACACS+ server:
Wed Apr 14 12:35:38 2004 172.16.0.0 admin ttyS0 0.0.0.0 start start_time=1081924137
task_id=3511 timezone=PST service=shell -lvl=0 cmd=logging console enable
Wed Apr 14 12:35:39 2004 172.16.0.0 admin ttyS0 0.0.0.0 stop stop_time=1081924137
task_id=3511 timezone=PST service=shell priv-lvl=0 cmd=logging console enable
In addition to command accounting, the WAAS device records any executed CLI command in the system log ( syslog.txt). The message format is as follows:
ce_syslog(LOG_INFO, CESM_PARSER, PARSER_ALL, CESM_350232,
"CLI_LOG %s: %s \n", __FUNCTION__, pd->command_line);
Related Commands
(config) aaa authorization commands
To authorize commands issued through the CLI by a user on a WAAS device, use the aaa authorization commands global configuration command. To disable command authorization, use the no form of this command.
aaa authorization commands level default tacacs+
no aaa authorization commands level default tacacs+
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Command authorization enforces authorization through an external AAA server for each command executed by the user. All commands executed by a CLI user are authorized before they are executed.
When command authorization is configured for level 0, only EXEC commands are authorized, regardless of user level (normal or super).
When command authorization is configured for level 15, EXEC and global configuration commands are authorized, regardless of user level (normal or super).
Once it is configured, command authorization configuration is displayed in the running config. When the running config is copied to the startup config, command authorization is configured as the last config so that during the reload, the startup config need not be authorized.
Only commands executed through the CLI interface are subject to command authorization.
Examples
The following example shows how to configure command authorization for level 15 (authorization for both EXEC and global configuration commands) on the WAAS device:
Related Commands
(config) accelerator epm
To enable the Endpoint Mapper (EPM) application accelerator, use the accelerator epm global configuration command. To disable the EPM application accelerator, use the no form of this command.
accelerator epm {enable | exception {coredump | debug | no-coredump }}
no accelerator epm {enable | exception {coredump | debug | no-coredump }}
Syntax Description
(Optional) Configures the action to be taken if an exception occurs. |
|
Defaults
The EPM accelerator is enabled by default and will start automatically if the Enterprise license is installed. The default exception action is coredump.
Command Modes
Device Modes
Usage Guidelines
Use the accelerator epm enable command to enable the acceleration of EPM traffic. The EPM accelerator must be enabled for the MAPI accelerator to operate.
Examples
The following example shows how to enable the EPM application accelerator:
Related Commands
(config) accelerator http
To enable the HTTP application accelerator, use the accelerator http global configuration command. To disable the HTTP application accelerator, use the no form of this command.
accelerator http { enable | dre-hints { access-list acl | enable } | exception { coredump | debug | no-coredump } | metadatacache { access-list acl | enable | conditional-response enable | filter-extension extension-list | redirect-response enable | request-ignore-no-cache enable | response-ignore-no-cache enable | unauthorized-response enable | max-age seconds | min-age seconds | filter-extension extension-list | https { access-list acl | enable }} | sharepoint-opt prefetch enable | suppress-server-encoding { access-list acl | enable }}
no accelerator http { enable | dre-hints { access-list acl | enable}| exception { coredump | debug | no-coredump } | metadatacache { access-list acl | enable | conditional-response enable | filter-extension extension-list | redirect-response enable | request-ignore-no-cache enable | response-ignore-no-cache enable | unauthorized-response enable | max-age seconds | min-age seconds | filter-extension extension-list | https { access-list acl | enable }} | sharepoint-opt prefetch enable | suppress-server-encoding { access-list acl | enable }}
Syntax Description
Configures the HTTP AO feature subnet to associate an access list to an HTTP AO feature. acl refers to an ACL that can be created by the ip access-list CLI. See (config) ip access-list. |
|
(Optional) Configures the action to be taken if an exception occurs. |
|
Configures the metadata cache to ignore cache-control on requests. |
|
Configures the metadata cache to ignore cache-control on responses. |
|
(Optional) Specifies the maximum number of seconds to retain HTTP header information in the cache. The default is 86400 seconds (24 hours). Valid time periods range from 5–2592000 seconds (30 days). |
|
(Optional) Specifies the minimum number of seconds to retain HTTP header information in the cache. The default is 60 seconds. Valid time periods range from 5–86400 seconds (24 hours). |
|
(Optional) String containing a comma-separated list of file extensions to which metadata caching is to be applied. Do not include the dot at the beginning of the file extension. You can specify a maximum of 20 file extensions. |
|
(Optional) Enables data to be prefetched from the SharePoint server and serve it from the cache to the client. |
|
(Optional) Enables suppression of Accept-Encoding compress, gzip, and deflate request-headers between the client and the server for HTTP and HTTPS. |
Defaults
The HTTP accelerator is enabled by default and will start automatically if the Enterprise license is installed. The default exception action is coredump.
The metadata caching feature is disabled by default for all response types. The default max-age is 86400 seconds (24 hours), the default min-age is 60 seconds, and the default filter extension list is empty (meaning that metadata caching is applied to all extension types).
The SharePoint optimization feature is disabled by default.
When suppress-server-encoding is enabled, it suppresses the server compression for both HTTP and HTTPS requests. The suppress server encoding feature is disabled by default.
The DRE hints feature applies to both HTTP and HTTPS requests. It is disabled by default.
The subnet feature is enabled after the subnet configuration is added.
Command Modes
Device Modes
Usage Guidelines
Use the accelerator http enable command to enable the acceleration of HTTP traffic.
You can enable or disable each of three metadata caches (conditional-response, redirect-response, and unauthorized-response) separately. By default they are all enabled when you enable HTTP metadata caching. If you disable the HTTP accelerator, metadata caching is also disabled.
When you enable the suppress-server-encoding feature, the WAE removes the Accept-Encoding header from HTTP requests, preventing the web server from compressing HTTP data that it sends to the client. This allows the WAE to apply its own compression to the HTTP data, typically resulting in much better compression than the web server.
Use the SharePoint optimization feature when you need to access Microsoft Office documents stored on a SharePoint server 2010, using a web browser. Enabling this feature will prefetch the data from the server and serve it from the cache, which reduces latency and improves the user experience.
The DRE hint feature improves DRE performance. This feature is not automatically enabled when metadata caching or the suppress server encoding feature is enabled.
The options request-ignore-no-cache and response-ignore-no-cache are disabled by default. Because the HTTP accelerator is conservative in caching client request metadata and server response metadata, deployments may want to test with these settings enabled to improve the HTTP metadata cache hit ratio to achieve less latency.
If an existing subnet configuration gets modified or removed, the new configuration applies to new connections only, and does not impact the existing HTTP sessions. The change takes effect only after the change is updated in the kernel. Only one ACL is associated with each feature and a new subnet configuration replaces the old one. Use the no command to remove the subnet configuration. If the HTTP AO feature is globally disabled, the feature is not applied to any session. If the HTTP AO feature is globally enabled, and if the acl lookup result for this session is permit, the feature applies to the session; otherwise, it does not apply. HTTP AO bypass-list takes precedence over this feature.
Examples
The following example shows how to enable the HTTP application accelerator:
The following example shows how to enable and configure the metadata cache to operate only on specific file types:
Related Commands
(config) accelerator http object-cache enable
To turn on the CE (cache engine) for the WAE, use the accelerator http object-cache enable global configuration command. To disable the CE on the WAE, use the no form of this command.
accelerator http object-cache enable
no accelerator http object-cache enable
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
When accelerator http object cache is enabled, it turns on the CE.
Note Turning on the CE with accelerator http object-cache enable starts Transparent caching in Basic mode. After using this command, you can also specify the type of caching you want the CE to perform: transparent, transparent standard, transparent advanced, bypass, or OTT (Over the Top caching). Each of these is listed below in Related Commands.
Examples
The following example shows how to enable HTTP object cache:
DT-HTTP-AO-DC-W594-52-18(config)# accelerator http object-cache enable
Related Commands
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache transparent bypass
(config) accelerator http object-cache connected enable
(config) accelerator http object-cache transparent enable
To enable transparent basic caching mode on the CE, use the accelerator http object-cache transparent enable global configuration command. To disable transparent basic caching mode on the CE, use the no form of this command.
accelerator http object-cache transparent enable
no accelerator http object-cache transparent enable
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
When transparent basic caching mode is enabled on the CE, the CE caches only responses marked explicitly as cacheable.
Examples
The following example shows how to enable transparent caching on the CE.
WAAS(config)# accelerator http object-cache transparent enable
Related Commands
(config) accelerator http object-cache enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache transparent bypass
(config) accelerator http object-cache transparent basic
To enable transparent basic caching mode on the CE, use the accelerator http object-cache transparent standard global configuration command. To disable transparent basic caching mode on the CE, use the no form of this command.
accelerator http object-cache transparent basic
no accelerator http object-cache transparent basic
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
In transparent basic caching mode (which follows the standards set in RFC-2616), the CE:
- caches responses marked explicitly as cacheable (as in transparent caching mode)
- caches objects with no explicit cache marker with a last- modified date
- ignores “reload” headers from clients
Use the sub-mode facility (prompt “>”) to set transparent standard mode for all sites, or for a specified IPv4 address or hostname (domain):
- no - Turns off the command or resets it to its defaults.
- default - Sets the transparent basic cache mode as the default for all sites.
- exit - Exits the sub-mode options menu.
- server parameter - Specifies a particular server for transparent basic caching, either in octet format (“A.B.C.D.”), or with the server name in FQDN format (with a maximum of 255 total characters based on RFC-1035, and a maximum of 63 characters per label/segment).
A maximum of 512 host entries is supported for transparent basic caching mode.
Examples
The following example shows how to configure transparent basic as the default caching mode for a specified site:
Related Commands
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache transparent bypass
(config) accelerator http object-cache transparent standard
To enable transparent standard caching mode on the CE, use the accelerator http object-cache transparent standard global configuration command. To disable transparent standard caching mode on the CE, use the no form of this command.
accelerator http object-cache transparent standard
no accelerator http object-cache transparent standard
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
In transparent standard caching mode, the CE:
- caches responses marked explicitly as cacheable (for transparent caching mode)
- caches objects with no explicit cache marker and with a last- modified date
- ignores “reload” headers from clients
Use the sub-mode facility (prompt “>”) to set transparent standard mode for all sites, or for a specified IPv4 address or hostname (domain):
- no - Turns off the command or resets it to its defaults.
- default - Sets the transparent standard cache mode as the default for all sites.
- exit - Exits the sub-mode options menu.
- server parameter - Specifies a particular server for transparent standard caching, either in octet format (“A.B.C.D.”), or with the server name in FQDN format (with a maximum of 255 total characters based on RFC-1035, and a maximum of 63 characters per label/segment).
A maximum of 512 host entries is supported for transparent standard caching mode.
Examples
The following example shows how to configure transparent standard as the default caching mode for a specified site:
Related Commands
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache transparent bypass
(config) accelerator http object-cache transparent advanced
To enable transparent advanced caching mode on the CE, use the accelerator http object-cache transparent advanced global configuration command. To disable transparent advanced caching mode on the CE, use the no form of this command.
accelerator http object-cache transparent advanced
no accelerator http object-cache transparent advanced
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
In transparent advanced mode, the CE caches media files by MIME type, more aggressively, and caches all objects for longer times (when there is no specified expiration time).
Use the sub-mode facility (prompt “>”) to set transparent advanced mode for all sites, or for a specified IPv4 address or hostname (domain):
- no - Turns off the command or resets it to its defaults.
- default - Sets the transparent advanced cache mode as the default for all sites.
- exit - Exits the sub-mode options menu.
- server parameter - Specifies a particular server for transparent standard caching, either in octet format (“A.B.C.D.”), or with the server name in FQDN format (with a maximum of 255 total characters based on RFC-1035, and a maximum of 63 characters per label/segment).
A maximum of 512 host entries is supported for transparent advanced caching mode.
Examples Guidelines
The following example shows how to configure transparent advanced caching as the default caching mode for all sites:
Related Commands
(config) accelerator http object-cache enable
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent bypass
(config) accelerator http object-cache transparent bypass
To turn off caching for a configured site, use the accelerator http object-cache transparent bypass global configuration command. To turn on caching for a configured site, use the no form of this command.
accelerator http object-cache transparent bypass
no accelerator http object-cache transparent bypass
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
Use this command to turn off caching for all configured sites or for a specific site.
Enables the transparent bypass mode of the CE for all sites or for a specific site. In this mode, caching is turned off for all sites or for a specified site(s). Transparent bypass mode suppresses all caching so that individual hostname rules are successfully applied.
Use the sub-mode facility (prompt “>”) to set transparent bypass mode for all configured sites or for a specified IPv4 address or hostname (domain):
- no - Turns off the command or resets it to its defaults.
- default - Sets the transparent bypass mode as the default for all sites.
- exit - Exits the sub-mode options menu.
- server parameter - Specifies a particular server for transparent advanced caching, either in octet format (“A.B.C.D.”), or with the server name in FQDN format (with a maximum of 255 total characters based on RFC-1035, and a maximum of 63 characters per label/segment).
Note When you configure Bypass mode as the site-specific transparent caching policy, you must specify a complete server name or complete (FQDN) domain name. If you use a wildcard to specify sites for Bypass mode, the sites will still be optimized via Akamai Cache.
Examples
The following is an example of how to set transparent bypass mode for a specified site:
Related Commands
(config) accelerator http object-cache enable
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache ott enable
In OTT (Over the Top caching) caching mode, the CE caches content of third-party websites, using a predefined set of rules. Use the accelerator http object-cache ott enable global configuration command to turn on OTT caching mode. To turn off OTT caching, use the no form of this command.
accelerator http object-cache ott enable
no accelerator http object-cache ott enable
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
OTT (Over the Top) Caching caches dynamic content by examining the URL related to a session and a site to determine if the object is identical to one previously stored in the CE cache.
OTT is used for streamed content, particularly video content, and for sites that use dynamic URLs based on session or authentication methods. Currently, the CE only uses OTT for one site, www.youtube.com.
Examples
The following example shows how to enable OTT caching:
Related Commands
(config) accelerator http object-cache enable
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache connected enable
To enable the CE to retrieve content from Akamai’s CDNs (Content Data Networks), use the accelerator http object-cache connected enable global configuration command. This enables Connected Cache mode. To turn off Connected Cache mode, use the no form of this command.
accelerator http object-cache connected enable
no accelerator http object-cache connected enable
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
The Connected Cache (CC) feature allows the CE to cache content that is delivered by an Edge server on the Akamai Intelligent Platform. Object caching is done on the client side WAAS device only. Prepositioning may be leveraged to cache HTTP websites delivered via the Akamai Intelligent Platform.
Examples
The following example shows how to enable the Connected Cache.
Related Commands
(config) accelerator http object-cache enable
(config) accelerator http object-cache transparent enable
(config) accelerator http object-cache transparent basic
(config) accelerator http object-cache transparent standard
(config) accelerator http object-cache transparent advanced
(config) accelerator http object-cache cws-check enable
To enable the Cisco Cloud Web Security feature, use the accelerator http object-cache cws-check enable global configuration command. To turn off the Cisco Cloud Web Security feature, use the no form of this command.
accelerator http object-cache cws-check enable
no accelerator http object-cache cws-check enable
Syntax Description
Command Default
Command Modes
Device Modes Default
Usage Guidelines
The Cisco Cloud Web Security feature provides content scanning of HTTP and secure HTTP/S traffic and malware protection service to web traffic. Cisco Cloud Web Security servers scan the web traffic content and either allow or block the traffic based on the configured policies. Servers use credentials such as private IP addresses, usernames, and user groups to identify and authenticate users and redirect the traffic for content scanning.
This command enables the same feature that is displayed on the WAAS Central Manager Advanced Cache Settings screen, as the Cisco Cloud Web Security present check box.
Examples
The following example shows how to enable the Cisco Cloud Web Security feature.
Related Commands
(config) accelerator http object-cache validate-address bypass
To add bypass server IP addresses to a whitelist for Server Address Validation, use the accelerator http object-cache validate-address bypass global configuration command. To remove a bypass server IP address from a whitelist for Server Address Validation, use no form of this command and the specified server IP address.
accelerator http object-cache validate-address bypass
no accelerator http object-cache validate-address bypass
Note For the server address validation feature to work properly, your system must have a valid DNS configuration. For how to configure DNS for your WAAS system, see the Chapter “Configuring Network Settings,” section “Configuring the DNS Server” in the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
Command Default
Command Modes
Device Modes Default
Usage Guidelines
After you have enabled Server Address Validation with the (config) accelerator http object-cache validate-address enable command, use the accelerator http object-cache validate-address bypass command to add bypass server addresses to a server whitelist.
There are three commands used with the bypass submode of the accelerator http object-cache validate-address bypass command:
Examples
The following example shows how to add a bypass server IP address to a whitelist:
The following example shows how to add a bypass server netmask to a whitelist:
Related Commands
(config) accelerator http object-cache validate-address enable
(config) accelerator http object-cache validate-address enable
To validate the server IP address configuration, use the accelerator http object-cache validate-address global configuration command. To disable the server IP address validation, use the no form of this command.
accelerator http object-cache validate-address enable
no accelerator http object-cache validate-address enable
Note For the server address validation feature to work properly, your system must have a valid DNS configuration. For how to configure DNS for your WAAS system, For how to configure DNS for your WAAS system, see the Chapter “Configuring Network Settings,” section “Configuring the DNS Server” in the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
Command Default
Command Modes
Device Modes Default
Usage Guidelines
Server Address Validation prevents malicious content from infecting the Akamai Connect cache, in situations like the one described here:
- The server IP address to which a DNS name resolves might be an IP address of a server that contains malicious content, rather than that of an expected and trusted server.
- The resulting response would get cached, and the Akamai cache would then contain malicious content.
- After the cache is “poisoned” with this malicious content, other clients accessing the same content would also get served with this malicious data.
To prevent such situations, the (config) accelerator http object-cache validate-address enable command:
- Performs DNS lookups on the name in the HTTP host header.
- Compares the lookup result with that connection’s forward IP address.
- If there is a mismatch, the transaction is allowed to pass through the cache, however—no content is allowed to be cached.
For the Server Address Validation feature to work properly, consider the following operating guidelines:
- Your system must have a valid DNS configuration. If you do not have a valid DNS configuration, the following warning message is displayed:
Please have a valid DNS configuration for this feature to work propertly.
For how to configure DNS for your WAAS system, see the Chapter “Configuring Network Settings,” section “Configuring the DNS Server” in the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
Interposer-SSL is in disabled state. Enable Interposer-SSL for HTTP Object Cache Server Validation feature to use SNI extension. Peformance for HTTPS connections, when this feature is enabled, might get affected in the absence of SNI.
For more information on Interposer-SSL, see the chapter “Configuring Application Acceleration,” section “Enabling and Disabling the Global Optimization Features” in the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
Note To configure IP server addresses to bypass server address validation, see the (config) accelerator http object-cache validate-address bypass global configuration command.
Examples
The following example shows how to enable Server Address Validation:
Note For the server address validation feature to work properly, your system must have a valid DNS configuration. If you do not have a valid DNS configuration, the following warning message will be displayed:
Please have a valid DNS configuration for this feature to work propertly.
For how to configure DNS for your WAAS system, see the Chapter “Configuring Network Settings,” section “Configuring the DNS Server” in the Cisco Virtual Wide Area Application Services Installation and Configuration Guide.
The following example shows how to disable Server Address Validation:
Related Commands
(config) accelerator http object-cache validate-address bypass
(config) accelerator http preposition proxy server
To configure a proxy that can be used by any HTTP/S preposition task, use the accelerator http preposition proxy server global configuration command. To disable command authorization, use the no form of this command.
accelerator http preposition proxy server ip address port port
no accelerator http preposition proxy server ip address port port
Syntax Description
The specified server address, in FQDN format, for the proxy server. |
|
The specified server port number to connect to the proxy server. The port number is from 1 to 65535. |
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the accelerator http preposition proxy server command to configure a proxy server that can be used by an HTTP/S preposition task.
Related Commands
(config-preposition) accelerator http preposition task task-name
(config) accelerator ica
To enable the ICA application accelerator, use the accelerator ica global configuration command. To disable the ICA application accelerator, use the no form of this command.
accelerator ica { enable | exception { coredump | debug | no-coredump } | wansecure-mode | session-limit limit { always | none }}
accelerator ica { enable | exception { coredump | debug | no-coredump } | wansecure-mode | session-limit limit { always | none }}
Syntax Description
Sets the session limit for the ICA AO. The maximum value that can be set is the device TFO (Transport Flow Optimization) limit. |
|
Defaults
The ICA accelerator is enabled by default. The default exception action is coredump. The default WAN Secure mode state is none.
Command Modes
Device Modes
Usage Guidelines
Use the accelerator ica enable command to enable the acceleration of ICA (Independent Computing Architecture) traffic with the transparent ICA accelerator. The ICA application accelerator provides WAN optimization on a WAAS device for ICAtraffic which is used to access a virtual desktop infrastructure (VDI). This is done through a process that is both automatic and transparent to the client and server.
Use the accelerator ica session-limit limit command to limit the number of session for the ICA AO (application accelerator).
Warning Make sure you have accurately measured the per ICA user bandwidth before changing the accelerator ica session-limit limit parameter. Failure to do so could lead to undesired overload scenarios.
Here are guidelines and limitations for the accelerator session-limit limit command:
- You must enter this command when the ICA AO is running.
- The new value takes effect only after the ICA AO is restarted.
Before an ICA AO restart, the show statistics accelerator output includes old and pending values for session limits counters; after an ICA AO restart, the output includes only new session limit values. Here is how the session limit counters are displayed for show statistics accelerator for each scenario:
– Before ICA AO restart—After you have entered a new session limit value, but before an ICA AO restart, the Connection Limit and Effective Limit counters will still show the old ICA session limit values. Another counter, New ICA Session Limit, shows the new (pending) value.
– After ICA AO restart—After you have entered a new session limit value, and after an ICA AO restart, the Connection Limit and Effective Limit counters will show the new ICA session limit value. The New ICA Session Limit counter is no longer needed, and is not included in the output.
- The maximum value that can be set is the device TFO limit.
- After you have saved the entered value to the startup configuration, the value is persistent across device reboots.
Use the accelerator ica wansecure-mode always command to enable WAN Secure mode for ICA. The WAN Secure mode configuration in both of the peer WAEs must match in order for the ICA accelerator to optimize connections.
WAN Secure mode requires that the SSL application accelerator is enabled. Use the accelerator ssl enable global configuration command to enable the SSL accelerator.
Examples
The following example shows how to enable the ICA application accelerator:
The following example shows how to set a session limit for the ICA application accelerator:
Related Commands
(config) accelerator mapi
To enable the MAPI application accelerator, use the accelerator mapi global configuration command. To disable the MAPI application accelerator, or one of its options, use the no form of this command.
accelerator mapi { enable | encryption | read-opt | write-opt | reserved-pool-size maximum-percent max_percent | wansecure-mode { always | auto | none } |
exception { coredump | debug | no-coredump }}
no accelerator mapi { enable | encryption | read-opt | write-opt | reserved-pool-size maximum-percent max_percent | wansecure-mode { always | auto | none } |
exception { coredump | debug | no-coredump }}
Syntax Description
Defaults
The MAPI accelerator is enabled by default and will start automatically if the Enterprise license is installed. Encrypted MAPI traffic acceleration is not enabled by default. The read optimization (read-opt) and write optimization (write-opt) features are enabled by default when the MAPI accelerator is enabled. The default maximum reserved connection pool percent is 15. The default WAN secure mode is auto. The default exception action is coredump.
Command Modes
Device Modes
Usage Guidelines
Use the accelerator mapi enable command to enable MAPI acceleration. This feature supports Microsoft Outlook 2000–2007 clients. Secure connections that use message authentication (signing) or encryption are not accelerated and MAPI over HTTP is not accelerated.
You must enable the EPM accelerator before the MAPI accelerator can operate.
Use the reserved-pool-size keyword to restrict the maximum number of connections reserved for MAPI optimization during TFO overload. It is specified as a percent of the TFO connection limit of the platform. Valid percent ranges from 5%-50%. The default is 15% which would reserve approximately 0.5 connection for each client-server Association Group (AG) optimized by MAPI accelerator.
The client maintains at least one AG per server it connects to with an average of about 3 connections per AG. For deployments that observe a greater average number of connections per AG, or where TFO overload is a frequent occurrence, a higher value for the reserved pool size maximum percent is recommended.
Reserved connections would remain unused when the device is not under TFO overload. Reserved connections are released when the AG terminates.
Examples
The following example shows how to enable the MAPI application accelerator:
Related Commands
(config) accelerator smb
To enable the SMB application accelerator, use the accelerator smb global configuration command. To disable the SMB application accelerator, use the no form of this command.
accelerator smb {{ alarm digital-signing enable | metadata-cache-max-limit enable } | batch-close-opt enable | change-notif size size | dir-opt {enable | aging seconds } | dre-hints dre enable | dynamic-share name | enable } exception {coredump | debug | no-coredump} | highest-dialect { ntlm0-12 | smb2-002 | smb2-1 } exceed-action { handoff | mute } | invalid-fid-opt enable | iobuf size mb | load-bypass enable | max-pkt-size size kb | metadata-opt { enable | cache-size mb [ force ]} | namedpipe-opt { enable | cache-size kb | resp-cache lifetime seconds | sess-cache lifetime seconds } | nf-cache { enable | aging seconds | bypass-patterns regex | size mb } | object-cache enable | oplock-opt {client-patterns name | enable } | office-opt enable | optimization bypass-pattern regex | print-opt enable | read-ahead { enable | buffer-size mb [ force ] | exhaust-distance kb | extended-window kb | hit-threshold percentage | init-window kb | max-active div | wait-distance kb } | signing { enable | unwrap} | smb2-read-caching enable | smb2-write-opt {enable | smb2-quota-aging seconds | smb2-quota-threshold mb } | wansecure-mode {always | none} | write-opt { enable | quota-aging seconds | quota-threshold mb }}
no accelerator smb { alarm digital-signing enable | batch-close-opt enable | change-notif size size | dir-opt {enable | aging seconds } | dre-hints dre enable | dynamic-share name | enable } exception {coredump | debug | no-coredump} | highest-dialect { ntlm0-12 | smb2-002 | smb2-1 } exceed-action { handoff | mute } | invalid-fid-opt enable | iobuf size mb | load-bypass enable | max-pkt-size size kb | metadata-opt { enable | cache-size mb [ force ]} | namedpipe-opt { enable | cache-size kb | resp-cache lifetime seconds | sess-cache lifetime seconds } | nf-cache { enable | aging seconds | bypass-patterns regex | size mb } | object-cache enable | oplock-opt {client-patterns name | enable } | office-opt enable | optimization bypass-pattern regex | print-opt enable | read-ahead { enable | buffer-size mb [ force ] | exhaust-distance kb | extended-window kb | hit-threshold percentage | init-window kb | max-active div | wait-distance kb } | signing { enable | unwrap} | smb2-read-caching enable | smb2-write-opt {enable | smb2-quota-aging seconds | smb2-quota-threshold mb } | | write-opt { enable | quota-aging seconds | quota-threshold mb }}
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
The enterprise license is required to start the SMB accelerator.
The EXEC mode command show running-config displays non-default settings only. Therefore, the command no accelerator smb enable does not show up in the running configuration if the SMB accelerator is disabled, while the accelerator smb enable command does display if the SMB accelerator is enabled.
Use the accelerator smb signing unwrap enable command to verify signature of the signed request packets at the Edge WAE. This checks whether the packet is modified/tampered while coming over the LAN. However, since the packet usually travels in the LAN from the Client to the Edge WAE, chances of man-in-middle attacks are less likely and you may choose to disable Edge side signature verification for request packets.
Use the accelerator smb wansecure-mode always command to enable WAN Secure mode for optimizing signed SMBv2 traffic. The default is “always”. The WAN Secure mode configuration for both the EDGE WAE and Core WAEs must match (be set at “always”) in order for the SMB accelerator to optimize signed SMBv2 connections. Even if one side has “none” set, then the signed connections would be handed over for generic optimization.
Use the accelerator smb wansecure-mode none to disable the wansecure -mode.
WAN Secure mode requires that the SSL application accelerator is enabled. Use the accelerator ssl enable global configuration command to enable the SSL accelerator.
Examples
The following example shows how to enable the SMB application accelerator:
The following example shows how to configure a case-insensitive regular expression that matches filenames to be bypassed for all optimizations:
This configuration would bypass files that contain.pst,.accdb,.accde,.accdt, and.accdr (Outlook PST files, and MS Access files).
Related Commands
(config) accelerator smb preposition
To create a smb preposition directive, use the accelerator smb preposition global configuration command. To disable the SSL application accelerator, use the no form of this command.
accelerator smb preposition task-id { credentials | duration<min> | enable | exit | max-cache <percentage> | max-file-size <max-file-size> | min-file-size<min-file-size> | name <directive name> | no | pattern {contains | ends-with | equals | starts with } | recursive | signing {kerberos | ntlm } | root <full path>| schedule {daily | date | monthly | now | weekly}| server <server name> }
no accelerator smb preposition task { enable | exception { coredump | debug | no-coredump }}
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the following guidelines when you create a smb preposition directive.
Special characters like ; | && || : * ? < > “ ` ! [ ] + =, are not allowed for top level shares. Additionally, when you create subdirectories inside the shares, the following special characters are not allowed: ; | && || : * ? < > “ ` !
Do not use the special character “;“ in files and directory names, else it will throw up errors. Additionally, we do not support extended Unicode characters in files and directories for release 6.2.1 and any such files or directories would be skipped and not prepositioned.
Do not use a space or the following special characters when defining patterns:
The following characters are not allowed to be used as username ; | && || : \ / * ? < > + =, [ ] “ ` !.
The following characters are not allowed to be used in server names ; | && ||, ~ : ! ` @ # $ % ^ & ‘ { } ()_“
The following characters are not allowed to be used as domain names ; | && || : \ / * ? < > “ ` !.
Examples
The following example shows how to configure the accelerator SMB preposition directive:
Related Commands
(config) accelerator smb preposition dre
To enable DRE for smb preposition tasks, use the accelerator smb preposition dre global configuration command. Use the no form of the command to disable it.
accelerator smb preposition dre enable
no accelerator smb preposition dre enable
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the accelerator smb preposition dre command if you want to cache files in both Object Cache and DRE cache. If you do not enable this, files are cached only in Object Cache.
Examples
The following example shows how to enable dre for the SMB preposition task:
Related Commands
(config) accelerator ssl
To enable the SSL application accelerator, use the accelerator ssl global configuration command. To disable the SSL application accelerator, use the no form of this command.
accelerator ssl { enable | exception { coredump | debug | no-coredump }}
no accelerator ssl { enable | exception { coredump | debug | no-coredump }}
Syntax Description
(Optional) Configures the action to be taken if an exception occurs. |
|
Defaults
The SSL accelerator is enabled by default and will start automatically if the Enterprise license is installed. The default exception action is coredump.
Command Modes
Device Modes
Usage Guidelines
Use the accelerator ssl enable command to enable the acceleration of SSL traffic. To undo this command, for example to disable SSL acceleration after you have enabled it, use the no version of this command.
Examples
The following example shows how to enable the SSL application accelerator:
Related Commands
(config) alarm overload-detect
To detect alarm overload situations, use the alarm overload-detect global configuration command. To unconfigure alarm parameters, use the no form of this command.
alarm overload-detect { clear 1-999 [ raise 10-1000 ] | enable | raise 10-1000 [ clear 1-999 ]}
no alarm overload-detect { clear 1-999 [ raise 10-1000 ] | enable | raise 10-1000 [ clear 1-999 ]}
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
In the alarm overload state, applications continue to raise alarms and these alarms are recorded within the WAAS device. Use the show alarms and show alarms history EXEC commands to display all the alarms in the alarm overload state.
Examples
The following example shows how to enable detection of alarm overload:
The following example shows how to set the threshold for triggering the alarm overload at 100 alarms per second:
The following example shows how to set the level for clearing the alarm overload at 10 alarms per second:
Related Commands
(config) asset
To set the tag name for the asset tag string, use the asset global configuration command. To remove the asset tag name, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to configure a tag name for the asset tag string on a WAAS device:
(config) authentication configuration
To specify administrative login authorization parameters for a WAAS device, use the authentication configuration global configuration mode command. To selectively disable options, use the no form of this command.
authentication { configuration { local | radius | tacacs | windows-domain }
enable [ primary | secondary | tertiary | quaternary ]
no authentication { configuration { local | radius | tacacs | windows-domain }
enable [ primary | secondary | tertiary | quaternary ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
The authentication command configures both the authentication and authorization methods that govern login and configuration access to the WAAS device.
Note We strongly recommend that you use the WAAS Central Manager GUI instead of the WAAS CLI to configure administrative login authentication and authorization for your WAAS devices, if possible. For information about how to use the WAAS Central Manager GUI to centrally configure administrative login authentication and authorization on a single WAE or group of WAEs, which are registered with a WAAS Central Manager, see the Cisco Wide Area Application Services Configuration Guide.
The authentication login command determines whether the user has any level of permission to access the WAAS device. The authentication configuration command authorizes the user with privileged access (configuration access) to the WAAS device.
The authentication login local and the authentication configuration local commands use a local database for authentication and authorization.
The authentication login tacacs and authentication configuration tacacs commands use a remote TACACS+ server to determine the level of user access. The WAAS software supports only TACACS+ and not TACACS or Extended TACACS.
To configure TACACS+, use the authentication and tacacs commands. To enable TACACS+, use the tacacs enable command. For more information on TACACS+ authentication, see the (config) tacacs command.
The authentication login radius and authentication configuration radius commands use a remote RADIUS server to determine the level of user access.
By default, the local method is enabled, with TACACS+ and RADIUS both disabled for login and configuration. Whenever TACACS+ and RADIUS are disabled the local method is automatically enabled. TACACS+, RADIUS, and local methods can be enabled at the same time.
The primary option specifies the first method to attempt for both login and configuration; the secondary option specifies the method to use if the primary method fails. The tertiary option specifies the method to use if both primary and secondary methods fail. The quaternary option specifies the method to use if the primary, secondary, and tertiary methods fail. If all methods of an authentication login or authentication configuration command are configured as primary, or all as secondary or tertiary, local is attempted first, then TACACS+, and then RADIUS.
Enforcing Authentication with the Primary Method
The authentication fail-over server-unreachable global configuration command allows you to specify that a failover to the secondary authentication method should occur only if the primary authentication server is unreachable. This feature ensures that users gain access to the WAAS device using the local database only when remote authentication servers (TACACS+ or RADIUS) are unreachable. For example, when a TACACS+ server is enabled for authentication with a user authentication failover configured and the user tries to log in to the WAAS device using an account defined in the local database, login fails. Login succeeds only when the TACACS+ server is unreachable.
You can configure multiple TACACS+ or RADIUS servers; authentication is attempted on the primary server first. If the primary server is unreachable, then authentication is attempted on the other servers in the TACACS+ or RADIUS farm, in order. If authentication fails for any reason other than a server is unreachable, authentication is not attempted on the other servers in the farm. This process applies regardless of the setting of the authentication fail-over server-unreachable command.
Login Authentication and Authorization Through the Local Database
Local authentication and authorization uses locally configured login and passwords to authenticate administrative login attempts. The login and passwords are local to each WAAS device and are not mapped to individual usernames.
By default, local login authentication is enabled first. You can disable local login authentication only after enabling one or more of the other administrative login authentication methods. However, when local login authentication is disabled, if you disable all other administrative login authentication methods, local login authentication is reenabled automatically.
Specifying RADIUS Authentication and Authorization Settings
To configure RADIUS authentication on a WAAS device, you must first configure a set of RADIUS authentication server settings on the WAAS device by using the radius-server global configuration command. (See the (config) radius-server command.)
Use the authentication login radius global configuration command to enable RADIUS authentication for normal login mode.
Use the authentication configuration radius global configuration command to enable RADIUS authorization.
To disable RADIUS authentication and authorization on a WAAS device, use the no form of the authentication global configuration command (for example, use the no authentication login radius enable command to disable RADIUS authentication).
Specifying TACACS+ Authentication and Authorization Settings
To configure TACACS+ authentication on WAAS devices, you must configure a set of TACACS+ authentication settings on the WAAS device by using the tacacs global configuration command. (See the (config) tacacs command.)
Authentication servers can be specified with the tacacs host or radius-server host global configuration commands. In the case of TACACS+ servers, the tacacs host hostname command can be used to configure additional servers. These additional servers provide authentication redundancy and improved throughput, especially when WAAS device load-balancing schemes distribute the requests evenly between the servers. If the WAAS device cannot connect to any of the authentication servers, no authentication takes place and users who have not been previously authenticated are denied access. Secondary authentication servers are queried in order only if the primary server is unreachable. If authentication fails for any other reason, alternate servers are not queried.
Specifying the Windows Domain Login Authentication
You can enable the Windows domain as an administrative login authentication and authorization method for a device or device group. Before you enable Windows authentication, you must first configure the Windows domain controller by using the windows-domain wins-server global configuration command. (See the (config) windows-domain command.)
Note WAAS supports authentication by a Windows domain controller running only on Windows Server 2000 or Windows Server 2003.
Examples
The following example shows how to query the secondary authentication database if the primary authentication server is unreachable. This feature is referred to as the failover server-unreachable feature.
If you enable the failover server-unreachable feature on the WAAS device, only two login authentication schemes (a primary and secondary scheme) can be configured on the WAAS device. The WAAS device fails over from the primary authentication scheme to the secondary authentication scheme only if the specified authentication server is unreachable.
To enable authentication privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authentication, use the authentication login global configuration command. In the following example, RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authentication methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authentication, and specify local as the secondary scheme for authentication.
To enable authorization privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authorization (configuration), use the authentication configuration global configuration command.
Note Authorization privileges apply to console and Telnet connection attempts, secure FTP (SFTP) sessions, and Secure Shell (SSH Version 2) sessions.
We strongly recommend that you set the administrative login authentication and authorization methods in the same order. For example, configure the WAAS device to use RADIUS as the primary login method, TACACS+ as the secondary login method, Windows as the tertiary method, and the local method as the quaternary method for both administrative login authentication and authorization.
The following example shows that RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authorization (configuration) methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authorization (configuration), and specify local as the secondary scheme for authorization (configuration).
The following example shows the resulting output of the show authentication command:
Related Commands
(config)authentication enable
To configure “enable authentication” to use local "admin" user account password instead of using external authentication servers, use the authentication enable global configuration mode command. To disable this, use the no form of the command.
no authentication enable local
Syntax Description
Selects the local admin user account password to enable authentication information for the WAAS device. |
Defaults
When this command is configured, the local admin user account password is used for enable authentication by default.
Command Modes
Device Modes
Usage Guidelines
When a user who does not have privileged EXEC level types "enable" at the WAE>prompt, the request for enable access is not sent to the external authentication servers, but is processed on the WAE, using only the local admin user account password to verify the given password and provide access.
Note Critical commands (e.g. configuration and management) require that the user be at the privileged EXEC level. To change to the privileged EXEC level, type "enable" at the WAE> prompt.
Examples
The following example shows how to configure enable authentication by using local admin user account password.
Related Commands
(config) authentication content-request
To authenticate a request for content, use the authentication content-request global configuration mode command. To selectively disable options, use the no form of this command.
authentication content-request windows-domain-ctrl disconnected-mode enable
no authentication content-request windows-domain-ctrl disconnected-mode enable
Syntax Description
Selects a Windows domain controller for domain server authentication. |
|
Defaults
Command Modes
Device Modes
Usage Guidelines
The authentication command configures both the authentication and authorization methods that govern login and configuration access to the WAAS device.
Note We strongly recommend that you use the WAAS Central Manager GUI instead of the WAAS CLI to configure administrative login authentication and authorization for your WAAS devices, if possible. For information about how to use the WAAS Central Manager GUI to centrally configure administrative login authentication and authorization on a single WAE or group of WAEs, which are registered with a WAAS Central Manager, see the Cisco Wide Area Application Services Configuration Guide.
The authentication login command determines whether the user has any level of permission to access the WAAS device. The authentication configuration command authorizes the user with privileged access (configuration access) to the WAAS device.
The authentication login local and the authentication configuration local commands use a local database for authentication and authorization.
The authentication login tacacs and authentication configuration tacacs commands use a remote TACACS+ server to determine the level of user access. The WAAS software supports only TACACS+ and not TACACS or Extended TACACS.
To configure TACACS+, use the authentication and tacacs commands. To enable TACACS+, use the tacacs enable command. For more information on TACACS+ authentication, see the (config) tacacs command.
The authentication login radius and authentication configuration radius commands use a remote RADIUS server to determine the level of user access.
By default, the local method is enabled, with TACACS+ and RADIUS both disabled for login and configuration. Whenever TACACS+ and RADIUS are disabled the local method is automatically enabled. TACACS+, RADIUS, and local methods can be enabled at the same time.
The primary option specifies the first method to attempt for both login and configuration; the secondary option specifies the method to use if the primary method fails. The tertiary option specifies the method to use if both primary and secondary methods fail. The quaternary option specifies the method to use if the primary, secondary, and tertiary methods fail. If all methods of an authentication login or authentication configuration command are configured as primary, or all as secondary or tertiary, local is attempted first, then TACACS+, and then RADIUS.
Enforcing Authentication with the Primary Method
The authentication fail-over server-unreachable global configuration command allows you to specify that a failover to the secondary authentication method should occur only if the primary authentication server is unreachable. This feature ensures that users gain access to the WAAS device using the local database only when remote authentication servers (TACACS+ or RADIUS) are unreachable. For example, when a TACACS+ server is enabled for authentication with a user authentication failover configured and the user tries to log in to the WAAS device using an account defined in the local database, login fails. Login succeeds only when the TACACS+ server is unreachable.
You can configure multiple TACACS+ or RADIUS servers; authentication is attempted on the primary server first. If the primary server is unreachable, then authentication is attempted on the other servers in the TACACS+ or RADIUS farm, in order. If authentication fails for any reason other than a server is unreachable, authentication is not attempted on the other servers in the farm. This process applies regardless of the setting of the authentication fail-over server-unreachable command.
Login Authentication and Authorization Through the Local Database
Local authentication and authorization uses locally configured login and passwords to authenticate administrative login attempts. The login and passwords are local to each WAAS device and are not mapped to individual usernames.
By default, local login authentication is enabled first. You can disable local login authentication only after enabling one or more of the other administrative login authentication methods. However, when local login authentication is disabled, if you disable all other administrative login authentication methods, local login authentication is reenabled automatically.
Specifying RADIUS Authentication and Authorization Settings
To configure RADIUS authentication on a WAAS device, you must first configure a set of RADIUS authentication server settings on the WAAS device by using the radius-server global configuration command. (See the (config) radius-server command.)
Use the authentication login radius global configuration command to enable RADIUS authentication for normal login mode.
Use the authentication configuration radius global configuration command to enable RADIUS authorization.
To disable RADIUS authentication and authorization on a WAAS device, use the no form of the authentication global configuration command (for example, use the no authentication login radius enable command to disable RADIUS authentication).
Specifying TACACS+ Authentication and Authorization Settings
To configure TACACS+ authentication on WAAS devices, you must configure a set of TACACS+ authentication settings on the WAAS device by using the tacacs global configuration command. (See the (config) tacacs command.)
Authentication servers can be specified with the tacacs host or radius-server host global configuration commands. In the case of TACACS+ servers, the tacacs host hostname command can be used to configure additional servers. These additional servers provide authentication redundancy and improved throughput, especially when WAAS device load-balancing schemes distribute the requests evenly between the servers. If the WAAS device cannot connect to any of the authentication servers, no authentication takes place and users who have not been previously authenticated are denied access. Secondary authentication servers are queried in order only if the primary server is unreachable. If authentication fails for any other reason, alternate servers are not queried.
Specifying the Windows Domain Login Authentication
You can enable the Windows domain as an administrative login authentication and authorization method for a device or device group. Before you enable Windows authentication, you must first configure the Windows domain controller by using the windows-domain wins-server global configuration command. (See the (config) windows-domain command.)
Note WAAS supports authentication by a Windows domain controller running only on Windows Server 2000 or Windows Server 2003.
Examples
The following example shows how to query the secondary authentication database if the primary authentication server is unreachable. This feature is referred to as the failover server-unreachable feature.
If you enable the failover server-unreachable feature on the WAAS device, only two login authentication schemes (a primary and secondary scheme) can be configured on the WAAS device. The WAAS device fails over from the primary authentication scheme to the secondary authentication scheme only if the specified authentication server is unreachable.
To enable authentication privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authentication, use the authentication login global configuration command. In the following example, RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authentication methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authentication, and specify local as the secondary scheme for authentication.
To enable authorization privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authorization (configuration), use the authentication configuration global configuration command.
Note Authorization privileges apply to console and Telnet connection attempts, secure FTP (SFTP) sessions, and Secure Shell (SSH Version 2) sessions.
We strongly recommend that you set the administrative login authentication and authorization methods in the same order. For example, configure the WAAS device to use RADIUS as the primary login method, TACACS+ as the secondary login method, Windows as the tertiary method, and the local method as the quaternary method for both administrative login authentication and authorization.
The following example shows that RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authorization (configuration) methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authorization (configuration), and specify local as the secondary scheme for authorization (configuration).
The following example shows the resulting output of the show authentication command:
Related Commands
(config) authentication fail-over
To specify authentication failover if the primary authentication server is unreachable, use the authentication fail-over global configuration mode command. To disable this feature, use the no form of this command.
authentication fail-over server-unreachable
no authentication fail-over server-unreachable
Syntax Description
Specifies that the WAAS device is to query the secondary authentication database only if the primary authentication server is unreachable. |
Defaults
This feature is disabled by default. This means that the WAAS device tries the other authentication methods if the primary method fails for any reason, not just if the server is unreachable.
Command Modes
Device Modes
Usage Guidelines
The authentication command configures both the authentication and authorization methods that govern login and configuration access to the WAAS device.
Note We strongly recommend that you use the WAAS Central Manager GUI instead of the WAAS CLI to configure administrative login authentication and authorization for your WAAS devices, if possible. For information about how to use the WAAS Central Manager GUI to centrally configure administrative login authentication and authorization on a single WAE or group of WAEs, which are registered with a WAAS Central Manager, see the Cisco Wide Area Application Services Configuration Guide.
The authentication fail-over server-unreachable global configuration command allows you to specify that a failover to the secondary authentication method should occur only if the primary authentication server is unreachable. This feature ensures that users gain access to the WAAS device using the local database only when remote authentication servers (TACACS+ or RADIUS) are unreachable. For example, when a TACACS+ server is enabled for authentication with a user authentication failover configured and the user tries to log in to the WAAS device using an account defined in the local database, login fails. Login succeeds only when the TACACS+ server is unreachable.
You can configure multiple TACACS+ or RADIUS servers; authentication is attempted on the primary server first. If the primary server is unreachable, then authentication is attempted on the other servers in the TACACS+ or RADIUS farm, in order. If authentication fails for any reason other than a server is unreachable, authentication is not attempted on the other servers in the farm. This process applies regardless of the setting of the authentication fail-over server-unreachable command.
Examples
The following example shows how to query the secondary authentication database if the primary authentication server is unreachable. This feature is referred to as the failover server-unreachable feature.
If you enable the failover server-unreachable feature on the WAAS device, only two login authentication schemes (a primary and secondary scheme) can be configured on the WAAS device. The WAAS device fails over from the primary authentication scheme to the secondary authentication scheme only if the specified authentication server is unreachable.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authentication, and specify local as the secondary scheme for authentication.
Related Commands
(config) authentication login
To set the administrative login authentication parameters for a WAAS device, use the authentication login global configuration mode command. To selectively disable options, use the no form of this command.
authentication login { local | radius | tacacs | windows-domain }
enable [ primary | secondary | tertiary | quaternary ]
no authentication login { local | radius | tacacs | windows-domain }
enable [ primary | secondary | tertiary | quaternary ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
The authentication command configures both the authentication and authorization methods that govern login and configuration access to the WAAS device.
Note We strongly recommend that you use the WAAS Central Manager GUI instead of the WAAS CLI to configure administrative login authentication and authorization for your WAAS devices, if possible. For information about how to use the WAAS Central Manager GUI to centrally configure administrative login authentication and authorization on a single WAE or group of WAEs, which are registered with a WAAS Central Manager, see the Cisco Wide Area Application Services Configuration Guide.
The authentication login command determines whether the user has any level of permission to access the WAAS device. The authentication configuration command authorizes the user with privileged access (configuration access) to the WAAS device.
The authentication login local and the authentication configuration local commands use a local database for authentication and authorization.
The authentication login tacacs and authentication configuration tacacs commands use a remote TACACS+ server to determine the level of user access. The WAAS software supports only TACACS+ and not TACACS or Extended TACACS.
To configure TACACS+, use the authentication and tacacs commands. To enable TACACS+, use the tacacs enable command. For more information on TACACS+ authentication, see the (config) tacacs command.
The authentication login radius and authentication configuration radius commands use a remote RADIUS server to determine the level of user access.
By default, the local method is enabled, with TACACS+ and RADIUS both disabled for login and configuration. Whenever TACACS+ and RADIUS are disabled the local method is automatically enabled. TACACS+, RADIUS, and local methods can be enabled at the same time.
The primary option specifies the first method to attempt for both login and configuration; the secondary option specifies the method to use if the primary method fails. The tertiary option specifies the method to use if both primary and secondary methods fail. The quaternary option specifies the method to use if the primary, secondary, and tertiary methods fail. If all methods of an authentication login or authentication configuration command are configured as primary, or all as secondary or tertiary, local is attempted first, then TACACS+, and then RADIUS.
Enforcing Authentication with the Primary Method
The authentication fail-over server-unreachable global configuration command allows you to specify that a failover to the secondary authentication method should occur only if the primary authentication server is unreachable. This feature ensures that users gain access to the WAAS device using the local database only when remote authentication servers (TACACS+ or RADIUS) are unreachable. For example, when a TACACS+ server is enabled for authentication with a user authentication failover configured and the user tries to log in to the WAAS device using an account defined in the local database, login fails. Login succeeds only when the TACACS+ server is unreachable.
You can configure multiple TACACS+ or RADIUS servers; authentication is attempted on the primary server first. If the primary server is unreachable, then authentication is attempted on the other servers in the TACACS+ or RADIUS farm, in order. If authentication fails for any reason other than a server is unreachable, authentication is not attempted on the other servers in the farm. This process applies regardless of the setting of the authentication fail-over server-unreachable command.
Login Authentication and Authorization Through the Local Database
Local authentication and authorization uses locally configured login and passwords to authenticate administrative login attempts. The login and passwords are local to each WAAS device and are not mapped to individual usernames.
By default, local login authentication is enabled first. You can disable local login authentication only after enabling one or more of the other administrative login authentication methods. However, when local login authentication is disabled, if you disable all other administrative login authentication methods, local login authentication is reenabled automatically.
Specifying RADIUS Authentication and Authorization Settings
To configure RADIUS authentication on a WAAS device, you must first configure a set of RADIUS authentication server settings on the WAAS device by using the radius-server global configuration command. (See the (config) radius-server command.)
Use the authentication login radius global configuration command to enable RADIUS authentication for normal login mode.
Use the authentication configuration radius global configuration command to enable RADIUS authorization.
To disable RADIUS authentication and authorization on a WAAS device, use the no form of the authentication global configuration command (for example, use the no authentication login radius enable command to disable RADIUS authentication).
Specifying TACACS+ Authentication and Authorization Settings
To configure TACACS+ authentication on WAAS devices, you must configure a set of TACACS+ authentication settings on the WAAS device by using the tacacs global configuration command. (See the (config) tacacs command.)
Authentication servers can be specified with the tacacs host or radius-server host global configuration commands. In the case of TACACS+ servers, the tacacs host hostname command can be used to configure additional servers. These additional servers provide authentication redundancy and improved throughput, especially when WAAS device load-balancing schemes distribute the requests evenly between the servers. If the WAAS device cannot connect to any of the authentication servers, no authentication takes place and users who have not been previously authenticated are denied access. Secondary authentication servers are queried in order only if the primary server is unreachable. If authentication fails for any other reason, alternate servers are not queried.
Specifying the Windows Domain Login Authentication
You can enable the Windows domain as an administrative login authentication and authorization method for a device or device group. Before you enable Windows authentication, you must first configure the Windows domain controller by using the windows-domain wins-server global configuration command. (See the (config) windows-domain command.)
Note WAAS supports authentication by a Windows domain controller running only on Windows Server 2000 or Windows Server 2003.
Examples
The following example shows how to query the secondary authentication database if the primary authentication server is unreachable. This feature is referred to as the failover server-unreachable feature.
If you enable the failover server-unreachable feature on the WAAS device, only two login authentication schemes (a primary and secondary scheme) can be configured on the WAAS device. The WAAS device fails over from the primary authentication scheme to the secondary authentication scheme only if the specified authentication server is unreachable.
To enable authentication privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authentication, use the authentication login global configuration command. In the following example, RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authentication methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authentication, and specify local as the secondary scheme for authentication.
To enable authorization privileges using the local, TACACS+, RADIUS, or Windows databases, and to specify the order of the administrative login authorization (configuration), use the authentication configuration global configuration command.
Note Authorization privileges apply to console and Telnet connection attempts, secure FTP (SFTP) sessions, and Secure Shell (SSH Version 2) sessions.
We strongly recommend that you set the administrative login authentication and authorization methods in the same order. For example, configure the WAAS device to use RADIUS as the primary login method, TACACS+ as the secondary login method, Windows as the tertiary method, and the local method as the quaternary method for both administrative login authentication and authorization.
The following example shows that RADIUS is specified as the primary method, TACACS+ as the secondary method, Windows as the third method, and the local database as the fourth method. In this example, four login authorization (configuration) methods are specified because the failover server-unreachable feature is not enabled on the WAAS device.
Note If you enable the failover server unreachable feature on the WAAS device, make sure that you specify either TACACS+ or RADIUS as the primary scheme for authorization (configuration), and specify local as the secondary scheme for authorization (configuration).
The following example shows the resulting output of the show authentication command:
Related Commands
(config) authentication strict-password-policy
To activate the strong password policy on a WAAS device, use the authentication strict-password-policy global configuration command. To deactivate the strong password policy and use the standard password policy on a WAAS device, use the no form of this command.
authentication strict-password-policy [ max-retry-attempts number ]
no authentication strict-password-policy [ max-retry-attempts number ]
Syntax Description
(Optional) Specifies the maximum number of failed login attempts allowed before the user is locked out. The range is 1–25; the default is 3. |
Defaults
Command Modes
Device Modes
Usage Guidelines
When you enable the strong password policy, your user passwords must meet the following requirements:
- The password must be 8 to 31 characters long. However, the minimum password length can vary depending on the following conditions:
– The minimum password length must be 10 characters if all characters are the same type of characters: all lowercase letters. all uppercase letters, all numbers, or all special characters
– The minimum password length must be 9 characters if you use any two different types of characters.
– The minimum password length must be 8 characters if you use any three different types of characters.
– The minimum password length must be 7 if you use any four different types of characters.
- The password can include both uppercase and lowercase letters (A-Z and a-z), numbers (0 to 9), and special characters including ~,`,!,@,#,$,%,^,&,*,(,),_,+,-,=,[,],\,{,},;,:,,,<,/,>.
- The password cannot contain the characters ' ? | (apostrophe, double quote, or pipe) or any control characters.
- The password cannot contain all the same characters (for example, 99999).
- The password cannot contain consecutive characters (for example, 12345).
- The password cannot be the same as the username.
- Each new password must be different from the previous 12 passwords. User passwords expire within 90 days.
- The password cannot contain dictionary words.
When you disable the strong password policy, user passwords must meet the following requirements:
- The password must have 1 to 31 characters.
- The password can include both uppercase and lowercase letters (A–Z and a–z), and numbers (0–9).
- The password cannot contain the characters
' " |
(apostrophe, double quote, or pipe) or any control characters.
Note When you enable the strong password policy, existing standard-policy passwords will still work. However, these passwords are subject to expiration under the strong password policy.
Examples
The following example shows how to enable the strong password policy:
The following example shows how to enable the strong password policy and set the maximum retry attempts to 5:
The following example shows how to disable the strong password policy:
Related Commands
(config) auto-discovery
To configure a WAE to automatically discover origin servers (such as those servers behind firewalls) that cannot receive TCP packets with setup options and add these server IP addresses to a blacklist for a specified number of minutes, use the auto-discovery global configuration command. To disable auto-discovery, use the no form of this command.
auto-discovery blacklist { enable itps | hold-time minutes }
no auto-discovery blacklist { enable itps | hold-time minutes }
Syntax Description
Defaults
The default auto-discovery blacklist hold time is 60 minutes.
Command Modes
Device Modes
Usage Guidelines
Use the auto-discovery blacklist hold-time command to adjust the blacklist hold time for the TFO auto-discovery feature. With auto-discovery, the WAE keeps track of origin servers (such as those servers behind firewalls) that cannot receive TCP packets with options and learns not to send out TCP packets with options to these blacklisted servers. When a server IP address is added to the blacklist, it remains on the blacklist for the configured number of minutes. After the hold time expires, subsequent connection attempts will again include TCP options so that the WAE can redetermine if the server can receive them. Resending TCP options periodically is useful because network packet loss could cause a server to be blacklisted erroneously.
Use the auto-discovery blacklist enable itps command to configure the interposer-ssl blacklist operation. Once enabled, depending on the nature of the error, the server or client ip is blacklisted.If blacklisted, any request sent to this particular server cannot use the SMART-SSL optimization for the next 60 minutes. Optimization requests to this server will be treated as pass through connections.
Similarly, if the client IP is blacklisted due to some error, the SMART-SSL accelerator will not accept any new connection requests from this client for the next 20 seconds. Optimization requests from this particular client will be treated as pass-through connections.
Examples
The following example shows how to enable TFO auto-discovery blacklist using the auto-discovery command:
Related Commands
(config) auto-register
To enable the discovery of a WAE and its automatic registration with the WAAS Central Manager through the Dynamic Host Configuration Protocol (DHCP), use the auto-register global configuration command. To disable the autoregistration feature on a WAE, use the no form of this command.
auto-register enable [ FastEthernet slot/port | GigabitEthernet slot/port | TenGigabitEthernet slot/port ]
no auto-register enable [ FastEthernet slot/port | GigabitEthernet slot/port | TenGigabitEthernet slot/port ] [ preserve-ip ]
Syntax Description
Defaults
Automatic registration using DHCP is enabled on a WAE by default.
Command Modes
Device Modes
Usage Guidelines
Autoregistration automatically configures network settings and registers WAEs with the WAAS Central Manager. On bootup, devices that run the WAAS software (with the exception of the WAAS Central Manager) automatically discover the WAAS Central Manager and register with it. You do not have to do any manual configuration on the device. Once the WAE is registered, you can approve the device and configure it remotely using the WAAS Central Manager GUI.
You can use the auto-register enable command to allow a WAE to discover the hostname of the WAAS Central Manager through DHCP and to automatically register the device with the WAAS Central Manager. Discovery and registration occur at bootup.
Note You must disable autoregistration when both device interfaces are configured as port-channel interfaces.
Note The DHCP that is used for autoregistration is not the same as the interface-level DHCP that is configurable through the ip address dhcp interface configuration command.
To assign a static IP address using the interface command, you must first disable the automatic registration of devices through DHCP by using the no auto-register enable command. If you want to keep the dynamic IP address that had been assigned to the interface, use the preserve-ip option to convert it to a static IP address.
After the WAE configures its network settings from DHCP, it needs to know the Central Manager hostname so it can register with the Central Manager.
The WAE queries the DNS server to obtain the Central Manager hostname. For autoregistration to work, you must configure the DNS server with the Central Manager hostname by configuring a DNS SRV (Service Location) record. For more information about autoregistration and how to configure the DNS SRV record, see the section on autoregistration in the “Planning Your WAAS Network” chapter of the Cisco Wide Area Application Services Configuration Guide.
Examples
The following example shows how to enable autoregistration on GigabitEthernet port 1/0:
The following example shows how to disable autoregistration on all configured interfaces on the WAE without losing any IP addresses assigned by autoregistration DHCP:
Related Commands
(config) banner
To configure the EXEC, login, and message-of-the-day (MOTD) banners, use the banner global configuration command. To disable the banner feature, use the no form of this command.
banner { enable | {{ exec | login | motd } [ message text ]}}
no banner { enable | {{ exec | login | motd } [ message text ]}}
Syntax Description
Defaults
Command Modes
Usage Guidelines
The message keyword is optional. If you enter a carriage return without specifying the message keyword, you will be prompted to enter your message text. For message text on one or more lines, press the Return key or enter delimiting characters (\n) to specify a message to appear on a new line. You can enter up to a maximum of 980 characters, including new-line characters (\n). Enter a period (.) at the beginning of a new line to save the message and return to the prompt for the global configuration mode.
Note The EXEC banner content is obtained from the command-line input that you enter when prompted for the input.
After you configure the banners, enter the banner enable global configuration command to enable banner support on the appliance. Enter the show banner EXEC command to display information about the configured banners.
Examples
The following example shows how to use the banner motd message global configuration command to configure the MOTD banner. In this example, the MOTD message consists of a single line of text.
WAE(config)#
banner motd message This is a WAAS 4.0.7 device
The following example shows how to use the banner motd message global command to configure a MOTD message that is longer than a single line. In this case, the WAE translates the \n portion of the message to a new line when the MOTD message is displayed to the user.
WAE(config)#
banner motd message "This is the motd message.\nThis is a WAAS 4.0.7 device\n"
The following example shows how to use the banner login message global configuration command to configure a login message that is longer than a single line. In this case, WAE A translates the \n portion of the message to a new line in the login message that is displayed to the user.
WAE(config)#
banner login message "This is login banner.\nUse your password to login\n"
The following example shows how to enable banner support:
WAE(config)#
banner enable
The following example shows how to use the banner exec global configuration command to configure an interactive banner. The banner exec command is similar to the banner motd message commands except that for the banner exec command, the banner content is obtained from the command-line input that the user enters after being prompted for the input.
Assume that a WAE has been configured with the MOTD, login, and EXEC banners as shown in the previous examples. When a user uses an SSH session to log in to the WAE, the user will see a login session that includes a MOTD banner and a login banner that asks the user to enter a login password as follows:
This is the motd banner.
This is a WAAS 4.0.7 device
This is login banner.
admin@wae's password:
After the user enters a valid login password, the EXEC banner is displayed, and the user is asked to enter the WAAS username and password as follows:
Last login: Fri Oct 1 14:54:03 2004 from client
System Initialization Finished.
This is the EXEC banner.
After the user enters a valid WAAS username and password, the WAE CLI is displayed. The CLI prompt varies depending on the privilege level of the login account. In the following example, because the user entered a username and password that had administrative privileges (privilege level of 15), the EXEC mode CLI prompt is displayed:
WAE#
Related Commands
(config) bridge
To configure a bridge group for use by an inline interfaces on an AppNav Controller Interface Module, use the bridge global configuration command. To unconfigure the bridge group, use the no form of this command.
bridge bridge-id { protocol { interception }| description description | intercept vlan { add | except | remove } { all | native | list }| propagate-link-state }
no bridge bridge-id { protocol { ieee | interception }| description description | intercept vlan { add | except | remove } { all | native | list }| propagate-link-state }
Syntax Description
Defaults
For an inline bridge group, all VLANS are intercepted and link state propagation is enabled.
Command Modes
Device Modes
Usage Guidelines
Use this command to create a bridge group for bridging two inline interfaces for interception on an AppNav Controller Interface Module in an AppNav deployment, by using the protocol interception option. The two member interfaces of this kind of bridge group do not need to be similar. For example, one could be a physical interface and one could be a port-channel interface. A standby interface is not allowed in a bridge group for inline interception on an AppNav Controller Interface Module.
Examples
The following example shows how to create and configure a bridge group for inline interfaces on an AppNav Controller Interface Module:
WAE#
configure
WAE(config)#
interface GigabitEthernet 1/10 bridge-group 5
WAE(config)#
interface GigabitEthernet 1/11 bridge-group 5
Related Commands
(config) cdp
To configure the Cisco Discovery Protocol (CDP) options globally on all WAAS device interfaces, use the cdp global configuration command. To disable CDP, use the no form of this command.
cdp { enable | holdtime seconds | timer seconds }
no cdp { enable | holdtime seconds | timer seconds }
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows that when CDP is first enabled, the hold time is set to 10 seconds for keeping CDP packets, and then the rate at which CDP packets are sent (15 seconds) is set:
Related Commands
(config) central-manager
To specify the WAAS Central Manager role and port number, use the central-manager global configuration command in central-manager device mode. To specify the IP address or hostname of the WAAS Central Manager with which a WAE is to register, use the central-manager global configuration command in application-accelerator device mode. To negate these actions, use the no form of this command.
central-manager {address { hostname | ip-address } | role { primary | standby } | ui port port-num }
no central-manager {address { hostname | ip-address } | role { primary | standby } | ui port port-num }
Syntax Description
Note The address option works in the application-accelerator device mode only. The role and ui port options work in the central-manager device mode only.
Defaults
The WAAS Central Manager GUI is preconfigured to use port 8443.
Command Modes
Device Modes
Examples
The following example shows how to specify that the WAAS device named waas-cm is to function as the primary WAAS Central Manager for the WAAS network:
The following example shows how to specify that the WAE should register with the WAAS Central Manager that has an IP address of 10.1.1.1. This command associates the WAE with the primary WAAS Central Manager so that the WAE can be approved as a part of the WAAS network.
The following example shows how to configure a new GUI port to access the WAAS Central Manager GUI:
The following example shows how to configure the WAAS Central Manager as the standby WAAS Central Manager:
(config) class-map
To configure an AppNav or optimization class map, use the class-map global configuration command. To unconfigure settings, use the no form of this command.
class-map type { appnav | waas } [ match-all | match-any ] classmap-name [ rename new-name ]
no class-map type { appnav | waas } [ match-all | match-any ] classmap-name
Syntax Description
Defaults
For AppNav class maps, match-all is the default when multiple match criteria exist.
Command Modes
Device Modes
Usage Guidelines
Use the class-map command to add or modify class maps and match conditions to identify specific types of traffic for use in policies. This command invokes the Class Map configuration mode, which is indicated by a different prompt (config-cmap). For more information on Class Map configuration mode commands, see the “ Class Map Configuration Mode Commands ” section. To return to global configuration mode, enter the exit command.
You can delete a class map by using the no form of this command. You cannot delete a class map if any policies are using it.
When creating a new class map, you must add at least one condition. If any of the conditions specified match an already existing condition in the class-map, no action is taken.
Note You cannot have more than 512 different class maps and 1024 total match conditions.
The WAAS software comes with many class maps and policy rules that help your WAAS system classify and optimize some of the most common traffic on your network. Before you create a new class map or policy rule, we recommend that you review the default class map and policy rules and modify them as appropriate. It is usually easier to modify an existing class map or policy rule than to create a new one. For a list of the default applications, class maps, and policy rules, see the Cisco Wide Area Application Services Configuration Guide.
Note We strongly recommend that you use the WAAS Central Manager GUI to centrally configure class maps for your WAAS devices. For more information, see the Cisco Wide Area Application Services Configuration Guide.
There is one exception tp this recommendation. Use the CLI to create an AppNav class map with type Application or Custom, and whose source or destination address has one of the following: an IP address ending in “0.0.0” or a non-Class A IP address ending in “0.0”.
Examples
The following example shows how to configure a WAAS optimization class map:
The following example shows how to configure an AppNav class map:
The following example shows how to modify a WAAS optimization class map for Citrix to enable ICA over SOCKS proxy server. In this example, the SOCKS server would be listening on port 2000.
Related Commands
(config) clock
To set the summer daylight saving time and time zone for display purposes, use the clock global configuration command. To disable this function, use the no form of this command.
clock { timezone timezone hoursoffset [minutesoffset] } |
summertime timezone { date startday startmonth startyear starthour endday endmonth endyear offset | recurring { 1-4 startweekday startmonth starthour endweekday endmonth endhour offset | first startweekday startmonth starthour endweekday endmonth endhour
offset | last startweekday startmonth starthour endweekday endmonth endhour offset }}
no clock { timezone timezone hoursoffset [minutesoffset] } |
summertime timezone { date startday startmonth startyear starthour endday endmonth endyear offset | recurring { 1-4 startweekday startmonth starthour endweekday endmonth endhour offset | first startweekday startmonth starthour endweekday endmonth endhour
offset | last startweekday startmonth starthour endweekday endmonth endhour offset }}
Syntax Description
Configures the name of the standard time zone and hours offset from UTC (–23 to +23). See Table 3-1 in the “Usage Guidelines” section. |
|
(Optional) Minutes offset (see Table 3-1 in the “Usage Guidelines” section) from UTC (0–59). |
|
Configures the name of the summer or daylight saving time zone. |
|
Minutes offset from UTC (0–1439). The summer time offset specifies the number of minutes that the system clock moves forward at the specified start time and backward at the end time. |
|
Configures the summer time to recur beginning the first week of the month. |
|
Configures the summer time to recur beginning the last week of the month. |
Defaults
Command Modes
Device Modes
Usage Guidelines
To set and display the local and UTC current time of day without an NTP server, use the clock timezone command with the clock set command. The clock timezone parameter specifies the difference between UTC and local time, which is set with the clock set EXEC command. The UTC and local time are displayed with the show clock detail EXEC command.
Note Unexpected time changes can result in unexpected system behavior. We recommend reloading the system after changing the system clock.
Use the clock timezone offset command to specify a time zone, where timezone is the desired time zone entry listed in the table below and 0 0 is the offset (ahead or behind) UTC is in hours and minutes. (UTC was formerly known as Greenwich mean time [GMT]).
Note The time zone entry is case sensitive and must be specified in the exact notation listed in Table 3-1. When you use a time zone entry from the time zone table, the system is automatically adjusted for daylight saving time.
|
|
---|---|
Examples
The following example shows how to specify the local time zone as Pacific Standard Time with an offset of 8 hours behind UTC:
The following example shows how to negate the time zone setting on the WAAS device:
The following example shows how to configure daylight saving time:
Related Commands
(config) cms
To schedule maintenance and enable the Centralized Management System (CMS) on a WAAS device, use the cms global configuration command. To negate these actions, use the no form of this command.
cms { database maintenance { full { enable | schedule weekday at time }} |
regular { enable | schedule weekday at time }} | enable
no cms { database maintenance { full { enable | schedule weekday at time }} |
regular { enable | schedule weekday at time }} | enable
cms rpc timeout { connection 5-1800 | incoming-wait 10-600 | transfer 10-7200 }
no cms rpc timeout { connection 5-1800 | incoming-wait 10-600 | transfer 10-7200 }
Syntax Description
Defaults
database maintenance regular : enabled
database maintenance full : enabled
connection: 30 seconds for WAAS Central Manager; 180 seconds for a WAE
Command Modes
Device Modes
Usage Guidelines
Use the cms database maintenance global configuration command to schedule routine full maintenance cleaning (vacuuming) or a regular maintenance reindexing of the embedded database. The full maintenance routine runs only when the disk is more than 90 percent full and only runs once a week. Cleaning the tables returns reusable space to the database system.
The cms enable global configuration command automatically registers the node in the database management tables and enables the CMS process. The no cms enable global configuration command only stops the management services on the WAAS device. Use the cms deregister EXEC command to de-register (remove) a WAAS device from the WAAS network.
Tip If you are trying to register a device that had previously been registered with a WAAS Central Manager and the cms enable global configuration command fails, use the cms deregister force command. If you get an error saying that the management service is not enabled when you use the cms deregister force command, delete the device from the WAAS Central Manager.
Examples
The following example shows how to schedule a regular (reindexing) maintenance routine to start every Friday at 11:00 p.m on the WAAS device:
The following example shows how to enable the CMS process on a WAAS device:
Related Commands
(config) crypto encryption-service
To configure encryption services on a WAAS device, use the crypto encryption service global configuration command. To disable a crypto encryption-service, use the no form of the command.
crypto encryption-service enable
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the command to enable the encryption service and to configure the interposer.
Examples
The following example shows how to enable an encrypted service on a WAAS device.
Related Commands
(config) crypto pki
To configure public key infrastructure (PKI) encryption parameters on a WAAS device, use the crypto pki global configuration command. To negate these actions, use the no form of this command.
crypto pki { ca certificate-authority-name}
crypto pki global-settings [ocsp url url | revocation-check {ocsp-cert-url [none] | ocsp-url [none] }]
Syntax Description
Configures encryption certificate authority information. Using this command enables certificate authority configuration mode. See PKI Certificate Authority Configuration Mode Commands. |
|
Configures PKI encryption global settings. Using this command enables PKI global settings configuration mode. See PKI Certificate Authority Configuration Mode Commands. |
|
(Optional) Specifies a null method that returns revocation success. |
|
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the crypto pki global configuration command to enter CA configuration mode or PKI global settings configuration mode.
Examples
The following example puts WAAS into CA configuration mode, editing the “my-ca” certification authority. The mode change is indicated by the system prompt:
Related Commands
(config) crypto ssl
To configure secure sockets layer (SSL) encryption parameters on a WAAS device, use the crypto ssl global configuration command. To negate these actions, use the no form of this command.
crypto ssl { cipher-list cipher-list-name | management-service |
services {accelerated-service service-name | global-settings | host-service peering} }
no crypto ssl { cipher-list cipher-list-name | management-service |
services {accelerated-service service-name | global-settings | host-service peering} }
Syntax Description
Configures the SSL cipher suite list. Using this command enables SSL cipher list configuration mode. See the SSL Cipher List Configuration Mode Commands chapter. |
|
Configures SSL management services. Using this command enables SSL management service configuration mode. See the SSL Management Service Configuration Mode Commands chapter. |
|
Configures other SSL services (accelerated, global, and host peering). |
|
Configures SSL accelerated services. Using this command enables SSL accelerated service configuration mode. See the SSL Accelerated Service Configuration Mode Commands chapter. |
|
Configures SSL service global settings. Using this command enables SSL service global configuration mode. See the SSL Global Service Configuration Mode Commands chapter. |
|
Configures SSL host peering services. Using this command enables SSL host peering service configuration mode. See the SSL Host Peering Service Configuration Mode Commands chapter. |
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the crypto ssl global configuration command to enter SSL cipher list configuration mode, SSL management service configuration mode, SSL accelerated service configuration mode, SSL service global configuration mode, or SSL host peering service configuration mode.
Examples
The following example puts the WAAS device into SSL cipher list configuration mode, editing the mylist cipher suite list. The mode change is indicated by the system prompt:
The following example puts the WAAS device into SSL management service configuration mode. The mode change is indicated by the system prompt:
The following example puts the WAAS device into SSL accelerated service configuration mode, editing the myservice accelerated service. The mode change is indicated by the system prompt:
The following example puts the WAAS device into SSL global service configuration mode. The mode change is indicated by the system prompt:
The following example puts the WAAS device into SSL host peering service configuration mode. The mode change is indicated by the system prompt:
Related Commands
(config) device mode
To configure the device mode for the WAAS device, use the device mode global configuration command. To reset the mode of operation on your WAAS device, use the no form of this command.
device mode { application-accelerator | application-accelerator profile branch | central-manager | appnav-controller }
no device mode { application-accelerator | application-accelerator profile branch | central-manager | appnav-controller |}
Syntax Description
Defaults
The default device operation mode is application-accelerator.
Command Modes
Device Modes
Usage Guidelines
If the WAAS device is operating with an Accelerator only image, you will not be able to convert it to central-manager mode until after you update it with a Full image and reboot. You can use the show version EXEC command to check the type of software image the WAE is running.
Examples
The following example shows how to specify central manager as the device mode of a WAAS device:
The following example shows how to specify application accelerator as the device mode of a WAAS device:
To change the device mode from central-manager to application-accelerator or appnav-controller, you must first use the cms deregister command in EXEC mode to disable the Centralized Management System on the Central Manager. Then use the device mode command in global configuration mode, as shown in the following example:
Related Commands
(config) disk disk-name
To disable the disk for online removal, use the disk disk-name global configuration command. To reenable the disk, use the no form of this command.
disk disk-name diskxx shutdown [ force ]
no disk disk-name diskxx shutdown [ force ]
Syntax Description
(Optional) Forces a disk to be reenabled when used with the no form of this command. |
Defaults
Command Modes
Device Modes
Usage Guidelines
You can replace a failed disk or perform a scheduled disk maintenance on the WAE-612. Use the disk disk-name diskxx shutdown global configuration command to manually shut down a disk for a scheduled disk maintenance. (For the schedule disk maintenance procedure, see the Cisco Wide Area Application Services Configuration Guide, Chapter 14.)
Examples
The following example shows how to disable disk00 for online removal using the disk disk-name command:
Related Commands
(config) disk cache
To configure Akamai cache and Object cache partitions, use the disk cache global configuration command. If disk configuration is not required, use the default option or use the restore factory-default preserve basic-config EXEC command.
disk cache { default | Akamai-OC-equal | Akamai-weight1 | OC-weight1 | Akamai-weight2 | OC-weight2}{force}
Syntax Description
Command Default
The “default” configuration for disk cache management sets the available partition to predefined values for Akamai cache and Object cache.
Command Modes
Device Modes
Usage Guidelines
When you upgrade to software version 6.1.1, and configure the device/s for data cache management for the first time and perform a reload, all the data-cache is lost on reload.
Upgrading vWAAS/ISR-WAAS/SM-SRE:
When you upgrade to software version 6.1.1, and configure the device/s for data cache management for the first time and perform a reload, both data and system partitions are re-created. Logs and Data Cache are cleaned up, but software version and CM registration information is preserved.
Fresh deployment in all models:
When you do a fresh deployment of 6.1.1, and configure the device/s for data cache management for the first time and perform a reload, only Akamai and object-cache data is lost.
Second/Subsequent configuration in all models:
Configuring DCM for second/subsequent times cleans only the Akamai and object cache partitions. All other partitions are retained.
The status of data cache can be displayed using the show disk cache-details EXEC mode command. If data-cache is enabled, the show running configuration will display the config.
Data Cache Management is not supported on the following hardware platforms.
Examples
The following example shows how to set the available partition size equally among Akamai cache and Object cache:
Related Commands
(config) disk encrypt
To enable disk encryption, use the disk encrypt global configuration command. To disable disk encryption, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
To view the encryption status details, use the show disks details EXEC command. While the file system is initializing, you will see the following message: “ System initialization is not finished, please wait...
” You may also view the disk encryption status to check whether a disk is enabled or disabled in the Central Manager GUI, Device Home window.
Note If you are using a No Payload Encryption (NPE) image, the disk encryption feature has been disabled for use in countries where disk encryption is not permitted.
Examples
The following example shows how to enable disk encryption using the disk encrypt command:
Related Commands
(config) disk error-handling
To configure how disk errors are handled on a WAAS device, use the disk error-handling global configuration command. To disable automatic remapping of disk errors, use the no form of this command.
Syntax Description
Sets the disk to attempt to remap disk errors automatically. |
Defaults
Command Modes
Device Modes
Examples
The following example shows how to disable automatic remapping of disk errors:
WAE(config)#
no disk error-handling remap
Related Commands
(config) disk logical shutdown
To shut down the RAID-5 logical disk drive, use the disk logical shutdown global configuration command. To reenable the RAID-5 logical disk drive, use the no form of this command.
no disk logical shutdown [ force ]
Syntax Description
(Optional) Forces RAID Logical drive to be reenabled when used with the no form of this command. |
Defaults
Command Modes
Device Modes
Usage Guidelines
This command is supported on WAE-7541, WAE-7571, and WAE-8541 models only.
Use this command to operate the WAE in diskless mode. In diskless mode, the partitions and disks are not mounted and cannot be used.
You must reload the device for this command to take effect.
After a multiple disk failure or RAID controller failure, and after the drives are replaced and the RAID disk is rebuilt, the logical disk may remain in the error state. To reenable the disk, use the no disk logical shutdown force command, then reload the WAE.
Examples
The following example shows how shutdown the RAID-5 logical disk drive using the disk logical shutdown command:
Related Commands
(config) disk object-cache extend
To enable extended object cache, use the disk object-cache extend global configuration command. To disable this feature, use the no form of this command.
Syntax Description
Command Default
Command Modes
Device Modes
Usage Guidelines
Extended Object Cache is supported only on 674-4G, 674-8G and 694 models.
When extended object cache is enabled, the object cache space is increased only after saving the configuration and performing a reload.
The status of extended object cache can be displayed using the show disk details EXEC mode command. The output of this command states whether extended object cache is enabled or disabled.
This feature is supported only on WAE-674-4G, and WAE-674-8G models.
When a device is changed to AppNav mode, a warning message tells the user that changing the Device mode to AppNav Controller, will forcefully disable disk object-cache extend.The new configuration will take effect after a reload. If the user confirms, the system proceeds with reloading the system configuration and the extended object cache is disabled.
Examples
The following example shows how to enable extended object cache:
Related Commands
(config) dre
To enable and configure DRE (Data Redundancy Elimination) auto bypass and load monitor settings, use the dre global configuration command. To disable DRE settings, use the no form of this command.
dre {auto-bypass {cache-percent [percent_no] | comp-threshold [comp_threshold] | enable} | load-monitor {report | disk-max-latency [disk-mask-latency] | threshold [threshold] }}
no dre {auto-bypass {cache-percent | comp-threshold | enable} | load-monitor {report | | disk-max-latency | threshold}}
Syntax Description
Sets the cache size percent threshold for bypass trigger (1-99). |
|
Sets the DRE compression ratio threshold for bypass trigger (1-50). |
|
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the dre auto-bypass global configuration command to generate an alarm and automatically DRE bypass application traffic.
Examples
The following example shows how to enable DRE auto bypass using the dre command:
Related Commands
(config) end
To exit global configuration mode, use the end global configuration command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the end command to exit global configuration mode after completing any changes to the running configuration. To save new configurations to NVRAM, use the write command.
In addition, you can press Ctrl-Z to exit global configuration mode.
Examples
The following example shows how to exit global configuration mode on a WAAS device:
Related Commands
(config) exec-timeout
To configure the length of time that an inactive Telnet or SSH session remains open on a WAAS device, use the exec-timeout global configuration command. To revert to the default value, use the no form of this command.
Syntax Description
Timeout in minutes (0–44640). A value of 0 sets the logout timeout to infinite. |
Defaults
Command Modes
Device Modes
Usage Guidelines
A Telnet session or Secure Shell (SSH) session with the WAAS device can remain open and inactive for the interval of time specified by the exec-timeout command. When the exec-timeout interval elapses, the WAAS device automatically closes the Telnet or SSH session.
Examples
The following example shows how to configure a timeout of 100 minutes:
The following example shows how to negate the configured timeout of 100 minutes and revert to the default value of 15 minutes:
Related Commands
(config) exit
To terminate global configuration mode and return to the privileged-level EXEC mode, use the exit command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
This command is equivalent to pressing Ctrl-Z or entering the end command.
Examples
The following example shows how to terminate global configuration mode and return to the privileged-level EXEC mode:
Related Commands
(config) flow exporter
To configure the collector server destination for the exported information, use the flow exporter global configuration command.
flow exporter exporter name { description | destination ip_address| exit | export-protocol { ipfix | netflowv9} | no | rename | transport }
Syntax Description
Specifies the export protocol for the flow records - IPFIX or Netflow-v9 (default). |
|
Specifies the transport protocol for the flow records. The default port is 2055. |
|
Defaults
Command Modes
Device Modes
Usage Guidelines
When you configure a flow exporter, the exporter name can be a maximum of 16 characters. For more information about how to configure flow monitoring on the WAE, see the Cisco Wide Area Application Services Configuration Guide, Chapter 15.
Examples
The following example shows how to enable flow monitoring using the flow exporter command:
Related Commands
(config) flow record
To configure basic DNA-specific or WAAS-specific flow information to be sent to the collector, use the flow record global configuration command. To remove the fields from the template, use the no form of this command.
flow record Record name { collect
{dna-lite {all | application name | class-name | collection mode | destination-asn | destination-mask | dre | end-time | flow-direction | input-interface | lz | next-hop | opt-segment-id | output-interface | passthrough-reason | protocol | source-asn| source-mask | start-time | tcp-flags | types-of-service} |
waas {application name | bytes | class-name | connection-mode | dre | lz | packets | passthrough-reason} | rename | exit }}}
no flow record Record name collect dna-lite application name
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
For information about how to configure a flow record for flow monitoring on the WAE, see the Cisco Wide Area Application Services Configuration Guide, Chapter 15.
Examples
The following example shows how to create a flow record using the flow record command:
Related Commands
(config) flow monitor
To enable network traffic flow monitoring and to register the WAE with the tcpstat-v1 collector for traffic analysis (in case of NetQoS), use the flow monitor global configuration command. To disable the network traffic flow configuration, use the no form of this command.
flow monitor tcpstat-v1 { enable | host ip_address }
no flow monitor tcpstat-v1 { enable | host ip_address }
flow monitor monitor name { description | enable | exporter | record | rename }
Syntax Description
Defaults
The default configuration has no host address configured and the feature is disabled.
Command Modes
Device Modes
Usage Guidelines
For information about how to configure flow monitoring on the WAE, see the Cisco Wide Area Application Services Configuration Guide, Chapter 15. A maximum of 15 characters is allowed for the flow monitor name.
Examples
The following example shows how to enable flow monitoring (for NetQos) using the flow monitor command :
For Netflowv9, the following example shows how to specify which flow record should go to which flow exporter using the flow monitor command :
Related Commands
(config) help
To obtain online help for the command-line interface, use the help global configuration command. To disable help, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
You can obtain help at any point in a command by entering a question mark (?). If nothing matches, the help list will be empty, and you must use the backspace key until entering a ? shows the available options.
Examples
The following example shows the output of the help global configuration command:
The following example shows how to use full help to see what WCCP command arguments are available:
WAE(config)#
wccp ?
access-list Configure an IP access-list for inbound WCCP encapsulate
traffic
flow-redirect Redirect moved flows
router-list Router List for use in WCCP services
shutdown Wccp Shutdown parameters
tcp-promiscuous TCP promiscuous mode service
The following example shows how to use partial help to determine the syntax of a WCCP argument:
Related Commands
(config) hostname
To configure the network hostname on a WAAS device, use the hostname global configuration command. To reset the hostname to the default setting, use the no form of this command.
Syntax Description
New hostname for the WAAS device; the name is case sensitive. The name may be from 1 to 30 alphanumeric characters. |
Defaults
The default hostname is the model number of the WAAS device (for example WAE-612).
Command Modes
Device Modes
Usage Guidelines
Use this command to configure the hostname for the WAAS device. The hostname is used for the command prompts and default configuration filenames. This name is also used for routing, so it conforms to the following rules:
Examples
The following example shows how to change the hostname of the WAAS device to sandbox :
The following example shows how to remove the hostname:
Related Commands
(config) inetd
To enable FTP and RCP, and TFTP services on a WAAS device, use the inetd enable global configuration command. To disable these same services, use the no form of this command.
inetd enable { ftp | rcp | tftp }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Inetd (an Internet daemon) is a program that listens for connection requests or messages for certain ports and starts server programs to perform the services associated with those ports. Use the inetd enable command with the ftp and rcp, and tftp keywords to enable and disable services on the WAAS device. To disable the service, enter the no form of the inetd enable command. Use the show inetd EXEC command to see whether current inetd sessions are enabled or disabled.
Examples
The following example shows how to enable an FTP service session on the WAAS device:
The following example shows how to disable FTP services:
Related Commands
(config) inline
To configure the failover timeout of inline interfaces on a Cisco Interface Module, use the inline global configuration command. To unconfigure the failover timeout, use the no form of this command.
inline failover timeout { 1 | 5 | 25 }
no inline failover timeout { 1 | 5 | 25 }
Syntax Description
Sets the failover timeout for the inline interfaces. Valid values are 1, 5, or 25 seconds. The default is 1. |
Defaults
Command Modes
Device Modes
Usage Guidelines
This command applies only to the following WAAS devices that use a Cisco Interface Module: WAVE-294, WAVE-594, WAVE-694, WAVE-7541, WAVE-7571, and WAVE-8541. This command does not apply to the TenGigabitEthernet module, which cannot be used in inline mode, or to interfaces on the Cisco AppNav Controller Interface Module.
The inline failover timeout command sets the number of seconds the interface should wait before going into bypass mode, after a device or power failure.
Examples
The following example shows how to configure the inline failover timeout for 5 seconds:
Related Commands
(config) interface InlineGroup
(config) inline vlan-id-connection-check
To enable VLAN ID checking on intercepted traffic, use the inline vlan-id-connection-check global configuration command. To disable VLAN ID checking, use the no form of this command.
inline vlan-id-connection-check
no inline vlan-id-connection-check
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to enable VLAN ID checking of the intercepted traffic on the WAAS device:
The following example shows how to disable VLAN ID checking:
Related Commands
(config) interface InlineGroup
(config) interface GigabitEthernet
(config) interception
To configure traffic interception with an access list, use the interception global configuration command. To disable the interception access list, use the no form of this command.
interception [ appnav-controller ] access-list { acl-num | acl_name }
no interception [ appnav-controller ] access-list { acl-num | acl_name }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the interception command to apply an access list (ACL) to traffic interception. Packets permitted by the ACL are intercepted for WAAS optimization (on an application accelerator device) or for distribution (on an ANC). Packets denied by the ACL are passed through by WAAS. You can define ACLs by using the ip access-list standard or ip access-list extended configuration commands.
Note On an ANC the tcp... established
extended ACL rule type is not supported.
You can configure only one interception ACL, except if the device is an ANC that is also acting as a WN. In this situation, you can configure one interception appnav-controller access-list for the ANC and one interception access-list for the WN. The ANC ACL could permit a flow that is subsequently denied by the WN ACL.
If you specify an interception ACL that is not defined, it is considered to be a “permit any” ACL and all traffic is intercepted.
An interception ACL works both with WCCP and inline interception modes.
When used with interface ACLs and WCCP ACLs, the interface ACL is applied first, the WCCP ACL is applied second, and then the interception ACL is applied last.
Examples
The following example shows how to define and apply an ACL that intercepts all traffic except WWW traffic from a particular client:
The following example uses the same ACL for an ANC:
Related Commands
(config) interception-method
To configure the traffic interception method, use the interception-method global configuration command. To disable the interception method, use the no form of this command.
interception-method { inline | | appnav-controller | wccp vn-service }[ force ]
no interception-method { inline | | appnav-controller | wccp vn-service }[ force ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
You must use the interception-method command to enable a traffic interception method before configuring other traffic interception settings. Other settings that are specific to a particular traffic interception method are not available until after you use this command to enable the method.
When you are changing the traffic interception method, all configuration settings for the current method are removed before the new method is enabled. You are prompted to confirm before the command proceeds.
Examples
The following example shows how to enable WCCP interception:
Related Commands
(config) interface InlineGroup
(config) interface GigabitEthernet
To configure a Gigabit Ethernet interface, use the interface global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface GigabitEthernet slot/port [ autosense | bandwidth { 10 | 100 | 1000 } | cdp enable | channel-group index | description text | full-duplex | half-duplex |
ip { access-group { acl-num | acl_name } { in | out } |
address { ip_address netmask [ secondary ] | dhcp [ client-id id ][ hostname name ]}} |
ipv6 {address [autoconfig | dhcp | use-link-local-only | ip_address] | nd [ dad-transmits range]} |
load-interval seconds | mtu mtusize | shutdown | standby group-index [ primary ] | bridge-group bridge-id ]
no interface GigabitEthernet slot/port [ autosense | bandwidth { 10 | 100 | 1000 } | cdp enable | channel-group index | description text | full-duplex | half-duplex |
ip { access-group { acl-num | acl_name } { in | out } |
address { ip_address netmask [ secondary ] | dhcp [ client-id id ][ hostname name ]}} |
ipv6 {address [autoconfig| dhcp | use-link-local-only| ip_address] | nd [ secondary]} |
load-interval seconds | mtu mtusize | shutdown | standby group-index [ primary ] | bridge-group bridge-id ]
Syntax Description
Defaults
The first attached interface in a standby group is defined as the active interface. There are no other default behaviors or values.
Command Modes
Device Modes
Usage Guidelines
Although the CLI contains the no interface option, you cannot apply the no command to an interface. The software displays the following error message: Removing of physical interface is not permitted.
To configure an interface bandwidth on a WAAS device, use the bandwidth interface configuration command. The bandwidth is specified in megabits per second (Mbps). Using this option automatically enables autosense on the interface.
Note Changing the interface bandwidth, duplex mode, or MTU can cause network disruption for up to 30 seconds. The best practice is to make such changes when traffic interception is disabled or at an off-peak time when traffic disruption is acceptable.
Using the cdp enable command in global configuration mode enables CDP globally on all the interfaces. If you want to control CDP behavior per interface, use the cdp enable command in interface configuration mode. The interface level control overrides the global control.
To display the interface identifiers (for example, interface GigabitEthernet 1/0), use the show running-config or show startup-config commands. The autosense, bandwidth, full-duplex, half-duplex, ip, and shutdown commands are listed separately in this command reference.
Note When you use the ip address command to change the IP address of an interface that has been shut down, it automatically brings up that interface by default.
Configuring Multiple Secondary IP Addresses on a Single Physical Interface
Use the interface secondary global configuration command to configure more than one IP address on the same interface. By configuring multiple IP addresses on a single interface, the WAAS device can be present in more than one subnet. This configuration allows you to optimize the response time because the content goes directly from the WAAS device to the requesting client without being redirected through a router. The WAAS device becomes visible to the client because they are configured on the same subnet.
You can assign up to four secondary addresses to an interface. These addresses become active only after you configure the primary address. No two interfaces can have the same IP address in the same subnetwork. To set these secondary IP addresses, use the ip address command.
If a WAAS device has one physical interface that has multiple secondary IP addresses assigned to it, the egress traffic uses the source IP address that is chosen by IP routing. If the secondary IP addresses of a WAAS device in the same subnet as the primary IP address, then the egress traffic uses the primary IP address only. If the secondary IP addresses are in a different subnet than the primary IP address, then the destination IP address determines which IP address on the WAAS device is used for the egress traffic.
Configuring Interfaces for DHCP
When you configure a WAAS device initially, you can configure a static IP address or use interface-level DHCP to dynamically assign IP addresses to the interfaces on the WAAS device.
If you do not enable interface-level DHCP on the WAAS device, you must manually specify a static IP address and network mask for the WAAS device. If the WAAS device moves to another location in another part of the network, you must manually enter a new static IP address and network mask for this WAAS device.
You can enable an interface for DHCP using the ip address dhcp client-id id hostname name interface configuration command. The client identifier is an ASCII value. The WAAS device sends its configured client identifier and hostname to the DHCP server when requesting network information. You can configure DHCP servers to identify the client identifier and the hostname that the WAAS device is sending and then send the specific network settings that are assigned to the WAAS device.
Note You must disable autoregistration before you can manually configure an interface for DHCP. Autoregistration is enabled by default on the first interface of the device.
Defining Interface Descriptions
You can specify a one-line description for a specific interface on a WAAS device. Use the description text interface configuration command to enter the description for the specific interface. The maximum length of the description text is 240 characters. This feature is supported for the Gigabit Ethernet, 10 Gigabit Ethernet, port-channel and standby bridge virtual interfaces.
After you define the description for an interface, use the show EXEC commands to display the defined interface descriptions. Enter the show interface interface type slot/port EXEC command to display the defined description for a specific interface on the WAE.
You can associate an interface with a standby group by using the standby group-index interface configuration command. To make an interface the active interface in a standby group, use the standby group-index primary interface configuration command. If you have already associated an interface with a standby group but have not made it the primary interface, you cannot specify the command again to add the primary designation. First, remove the interface from the standby group, then reassign it, specifying the primary option at the same time.
A physical interface can be a member of a standby group or a port channel, but not both.
If a device has only two interfaces, you cannot assign an IP address to both a standby group and a port channel. On such a device, only one virtual interface can be configured with an IP address.
Examples
The following example shows how to configure an attribute of an interface with a single CLI command:
The following example shows that an interface can be configured in a sequence of CLI commands:
The following example shows how to enable a shut down interface:
The following example shows how to add an interface to a channel group:
WAE#
configure
WAE(config)#
interface GigabitEthernet 1/0
WAE(config-if)#
channel-group 1
WAE(config-if)#
exit
The following example shows how to remove an interface from a channel group:
WAE(config)#
interface GigabitEthernet 1/0
WAE(config-if)#
no channel-group 1
WAE(config-if)#
exit
The following example shows how to assign a secondary IP address on a Gigabit Ethernet interface on a WAAS device:
WAE#
configure
WAE(config)#
interface GigabitEthernet 1/0
WAE(config-if)#
ip address 10.10.10.10 255.0.0.0 secondary
The following example shows how to configure a description for a Gigabit Ethernet interface:
WAE(config)#
interface GigabitEthernet 1/0
WAE(config-if)#
description This is a GigabitEthernet interface.
Related Commands
(config) interface InlineGroup
(config) interface PortChannel
(config) interface InlineGroup
To configure an InlineGroup interface, use the interface global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface InlineGroup slot / grpnumber [ autosense | bandwidth { 10 | 100 | 1000 } | cdp enable | encapsulation dot1q VLAN | failover timeout { 1 | 3 | 5 | 10 } | full-duplex | half-duplex | inline [ vlan { all | native | vlan_list }] | ip { access-group { acl-num | acl_name } { in | out } | load-interval seconds | shutdown ]
no interface InlineGroup slot / grpnumber [ autosense | bandwidth { 10 | 100 | 1000 } | cdp enable | encapsulation dot1q VLAN | failover timeout { 1 | 3 | 5 | 10 } | full-duplex | half-duplex | inline [ vlan { all | native | vlan_list }] | ip { access-group { acl-num | acl_name } { in | out } | load-interval seconds | shutdown ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
An InlineGroup interface is a logical grouping of a pair of Ethernet ports that are physically contained on the optional Cisco WAE Inline Network Adapter or Cisco Interface Module. This command does not apply to the Cisco AppNav Controller Interface Module; use the (config) bridge command to configure an inline bridge on that platform.
You can have multiple InlineGroup interfaces, which allows for multiple bypass-enabled paths for traffic to pass through the WAE appliance, making multiple-router deployments possible. The InlineGroup interfaces provide failover capability and can be assigned to any set of VLANs. (For examples of InlineGroup interface configurations, see the (config-if) inline command.)
You can configure the InlineGroup interface for link speed (bandwidth or autosense) and mode of operation (half-duplex or full-duplex).
The failover timeout set by this command applies only to interfaces on the Cisco WAE Inline Network Adapter. To set the failover timeout for all interfaces together on the Cisco Interface Module, use the (config) inline command.
Note If the VLAN ID that you set with the encapsulation dot1q option does not match the VLAN ID expected by the router subinterface, you may not be able to connect to the inline interface IP address.
The inline adapter supports only a single VLAN ID for each inline group interface. If you have configured a secondary address from a different subnet on an inline interface, you must have the same secondary address assigned on the router subinterface for the VLAN.
Note We strongly recommend that you do not use half duplex on the WAE, routers, switches, or other devices. Use of half-duplex impedes system ability to improve performance and should not be used. Double-check each Cisco WAE interface as well as the port configuration on the adjacent device (router, switch, firewall, WAE) to verify that full duplex is configured.
Related Commands
(config) interface GigabitEthernet
(config) interface PortChannel
(config) interface PortChannel
To configure a port-channel interface, use the interface PortChannel global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface PortChannel index [ description text | ip { access-group { acl-num | acl_name } { in | out } | address ip-address netmask } | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | shutdown | standby index | bridge-group bridge-id ]
no interface PortChannel index [ description text | ip { access-group { acl-num | acl_name } { in | out } | address ip-address netmask } | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | shutdown | standby index | bridge-group bridge-id ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Port channels (EtherChannels) for the WAAS software support the grouping of multiple same-speed network interfaces into one virtual interface. This configuration allows you to set or remove a virtual interface that consists of up to four physical interfaces (eight on an AppNav Controller Interface Module). Port channels also provide interoperability with Cisco routers, switches, and other networking devices or hosts that support port channels, load balancing, and automatic failure detection and recovery based on the current link status of each interface. You must configure port channels on the switch or router if you configure it on the WAE.
You cannot add an interface that already has a configured IP address, or is configured as primary or secondary, to a port channel.
You cannot remove a port-channel interface that is configured as the primary interface on a WAE.
Note You cannot use the inline Ethernet interfaces that are located on the Cisco WAE Inline Network Adapter to form a port-channel interface. However, you can use the interfaces on a Cisco Interface Module to form a port-channel interface.
Note No two interfaces can have IP addresses in the same subnet.
Examples
The following example shows how to create a port-channel interface. The port channel is port channel 1 and is assigned an IP address of 10.10.10.10 and a netmask of 255.0.0.0:
WAE#
configure
WAE(config)#
interface PortChannel 1
WAE(config-if)#
ip address 10.10.10.10 255.0.0.0
WAE(config-if)#
exit
The following example shows how to remove a port-channel interface:
WAE(config)#
interface PortChannel 1
WAE(config-if)#
no ip address 10.10.10.10 255.0.0.0
WAE(config-if)#
exit
WAE(config)#
no interface PortChannel 1
Related Commands
(config) interface GigabitEthernet
(config) interface InlineGroup
(config) interface standby
To configure a standby interface, use the interface standby global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface standby group-index { description text | ip address ip_address netmask | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | shutdown | bridge-group bridge-id }
no interface standby group-index { description text | ip address ip_address netmask | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | shutdown | bridge-group bridge-id }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
WAVE-294/594/694/7541/7571/8541 devices support up to two standby groups. All devices with the AppNav Controller Interface Module support up to three standby interfaces.
A standby group cannot be removed if it is configured as the system primary interface.
A standby group can have up to two member interfaces.
Note No two interfaces can have IP addresses in the same subnet.
Related Commands
(config) interface GigabitEthernet
(config) interface InlineGroup
(config) interface PortChannel
(config) interface TenGigabitEthernet
To configure a TenGigabitEthernet interface, use the interface global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface TenGigabitEthernet slot/port [ cdp enable | channel-group index | description text |
ip { access-group { acl-num | acl_name } { in | out } |
address { ip_address netmask [ secondary ] | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | dhcp [ client-id id ][ hostname name ]}} |
load-interval seconds | mtu mtusize | shutdown | standby group-index [ primary ] | bridge-group bridge-id ]
no interface TenGigabitEthernet slot/port [ cdp enable | channel-group index | description text | ip { access-group { acl-num | acl_name } { in | out } |
address { ip_address netmask [ secondary ] | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | dhcp [ client-id id ][ hostname name ]}} |
load-interval seconds | mtu mtusize | shutdown | standby group-index [ primary ] | bridge-group bridge-id ]
Syntax Description
Defaults
The first attached interface in a standby group is defined as the active interface. There are no other default behaviors or values.
Command Modes
Device Modes
Usage Guidelines
Although the CLI contains the no interface option, you cannot apply the no command to an interface. The software displays the following error message: Removing of physical interface is not permitted.
Note Changing the MTU can cause network disruption for up to 30 seconds. The best practice is to make such changes when traffic interception is disabled or at an off-peak time when traffic disruption is acceptable.
Using the cdp enable command in global configuration mode enables CDP globally on all the interfaces. If you want to control CDP behavior per interface, use the cdp enable command in interface configuration mode. The interface level control overrides the global control.
To display the interface identifiers (for example, interface TenGigabitEthernet 1/0), use the show running-config or show startup-config commands. The ip and shutdown commands are listed separately in this command reference.
Note When you use the ip address command to change the IP address of an interface that has been shut down, it automatically brings up that interface by default.
Configuring Multiple Secondary IP Addresses on a Single Physical Interface
Use the interface secondary global configuration command to configure more than one IP address on the same interface. By configuring multiple IP addresses on a single interface, the WAAS device can be present in more than one subnet. This configuration allows you to optimize the response time because the content goes directly from the WAAS device to the requesting client without being redirected through a router. The WAAS device becomes visible to the client because they are configured on the same subnet.
You can assign up to four secondary addresses to an interface. These addresses become active only after you configure the primary address. No two interfaces can have the same IP address in the same subnetwork. To set these secondary IP addresses, use the ip address command.
If a WAAS device has one physical interface that has multiple secondary IP addresses assigned to it, the egress traffic uses the source IP address that is chosen by IP routing. If the secondary IP addresses of a WAAS device in the same subnet as the primary IP address, then the egress traffic uses the primary IP address only. If the secondary IP addresses are in a different subnet than the primary IP address, then the destination IP address determines which IP address on the WAAS device is used for the egress traffic.
Configuring Interfaces for DHCP
When you configure a WAAS device initially, you can configure a static IP address or use interface-level DHCP to dynamically assign IP addresses to the interfaces on the WAAS device.
If you do not enable interface-level DHCP on the WAAS device, you must manually specify a static IP address and network mask for the WAAS device. If the WAAS device moves to another location in another part of the network, you must manually enter a new static IP address and network mask for this WAAS device.
You can enable an interface for DHCP using the ip address dhcp client-id id hostname name interface configuration command. The client identifier is an ASCII value. The WAAS device sends its configured client identifier and hostname to the DHCP server when requesting network information. You can configure DHCP servers to identify the client identifier and the hostname that the WAAS device is sending and then send the specific network settings that are assigned to the WAAS device.
Note You must disable autoregistration before you can manually configure an interface for DHCP. Autoregistration is enabled by default on the first interface of the device.
Defining Interface Descriptions
You can specify a one-line description for a specific interface on a WAAS device. Use the description text interface configuration command to enter the description for the specific interface. The maximum length of the description text is 240 characters. This feature is supported for the Gigabit Ethernet, 10 Gigabit Ethernet, port-channel and standby bridge virtual interfaces.
After you define the description for an interface, use the show EXEC commands to display the defined interface descriptions. Enter the show interface interface type slot/port EXEC command to display the defined description for a specific interface on the WAE.
You can associate an interface with a standby group by using the standby group-index interface configuration command. To make an interface the active interface in a standby group, use the standby group-index primary interface configuration command. If you have already associated an interface with a standby group but have not made it the primary interface, you cannot specify the command again to add the primary designation. First, remove the interface from the standby group, and then reassign it, specifying the primary option at the same time.
A physical interface can be a member of a standby group or a port channel, but not both.
If a device has only two interfaces, you cannot assign an IP address to both a standby group and a port channel. On such a device, only one virtual interface can be configured with an IP address.
Examples
The following example shows how to configure an attribute of an interface with a single CLI command:
The following example shows that an interface can be configured in a sequence of CLI commands:
The following example shows how to enable a shut down interface:
The following example shows how to add an interface to a channel group:
WAE#
configure
WAE(config)#
interface TenGigabitEthernet 1/0
WAE(config-if)#
channel-group 1
WAE(config-if)#
exit
The following example shows how to remove an interface from a channel group:
WAE(config)#
interface TenGigabitEthernet 1/0
WAE(config-if)#
no channel-group 1
WAE(config-if)#
exit
The following example shows how to assign a secondary IP address on a TenGigabitEthernet interface:
WAE#
configure
WAE(config)#
interface TenGigabitEthernet 1/0
WAE(config-if)#
ip address 10.10.10.10 255.0.0.0 secondary
The following example shows how to configure a description for a TenGigabitEthernet interface:
WAE(config)#
interface TenGigabitEthernet 1/0
WAE(config-if)#
description This is a TenGigabitEthernet interface.
Related Commands
(config) interface GigabitEthernet
(config) interface InlineGroup
(config) interface virtual
To configure a virtual interface, use the interface virtual global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.
interface virtual slot/port { cdp enable | description text |
ip { access-group { acl-num | acl_name } { in | out } | address { ip_address netmask [ secondary ] | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | dhcp [ client-id id ][ hostname name ]}| mtu mtusize | shutdown }
no interface virtual slot/port ( cdp enable | description text |
ip { access-group { acl-num | acl_name } { in | out } | address { ip_address netmask [ secondary ] | ipv6 {address {autoconfig | use-link-local only | ipv6 address} | nd dad-tansmits range} | load-interval seconds | dhcp [ client-id id ][ hostname name ]}| mtu mtusize | shutdown }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Using the cdp enable command in global configuration mode enables CDP globally on all the interfaces. If you want to control CDP behavior per interface, use the cdp enable command in interface configuration mode. The interface level control overrides the global control.
To display the interface identifiers (for example, interface virtual 1/0), use the show running-config or show startup-config commands.
Note When you use the ip address command to change the IP address of an interface that has been shut down, it automatically brings up that interface by default.
Configuring Interfaces for DHCP
When you configure a WAAS device initially, you can configure a static IP address or use interface-level DHCP to dynamically assign IP addresses to the interfaces on the WAAS device.
If you do not enable interface-level DHCP on the WAAS device, you must manually specify a static IP address and network mask for the WAAS device. If the WAAS device moves to another location in another part of the network, you must manually enter a new static IP address and network mask for this WAAS device.
You can enable an interface for DHCP using the ip address dhcp client-id id hostname name interface configuration command. The client identifier is an ASCII value. The WAAS device sends its configured client identifier and hostname to the DHCP server when requesting network information. You can configure DHCP servers to identify the client identifier and the hostname that the WAAS device is sending and then send the specific network settings that are assigned to the WAAS device.
Note You must disable autoregistration before you can manually configure an interface for DHCP. Autoregistration is enabled by default on the first interface of the device.
Defining Interface Descriptions
You can specify a one-line description for a specific interface on a WAAS device. Use the description text interface configuration command to enter the description for the specific interface. The maximum length of the description text is 240 characters.
After you define the description for an interface, use the show EXEC commands to display the defined interface descriptions. Enter the show interface virtual EXEC command to display the defined description for a virtual interface on the WAE.
Examples
The following example shows how to assign a secondary IP address on a virtual interface on a vWAAS device:
WAE#
configure
WAE(config)#
interface virtual 1/0
WAE(config-if)#
ip address 10.10.10.10 255.0.0.0 secondary
The following example shows how to configure a description for a virtual interface:
WAE(config)#
interface virtual 1/0
WAE(config-if)#
description This is a virtual interface.
Related Commands
(config) interface GigabitEthernet
(config) interface InlineGroup
(config) interface PortChannel
(config) ip
To change the initial network device configuration settings, use the ip global configuration command. To delete or disable these settings, use the no form of this command.
ip {access list |default-gateway [ management ] ip-address | domain-name name1 name2 name3 |
ftp management | host hostname ip-address | icmp | name-server {interface | ip-addresses }| ntp | radius management | tacacs management | path-mtu-discovery enable | route [ management ] dest_addrs net_addrs gateway_addrs | tftp management | unreachable }
no ip {default-gateway [ management ] ip-address | domain-name name1 name2 name3 |
ftp management | host hostname ip-address | name-server ip-addresses | radius management | tacacs management | path-mtu-discovery enable | route [ management ] dest_addrs net_addrs [gateway_addrs] | tftp management }
Syntax Description
Defaults
Command Modes
Device Modes
appnav-controller. (Management interface commands are not available when device is on central manager mode)
Usage Guidelines
To define a default gateway, use the ip default-gateway command. If you have designated a management interface, you can configure a different default gateway for the management interface by using the management keyword. To remove the IP default gateway, use the no form of this command. The WAAS device uses the default gateway to route IP packets when there is no specific route found to the destination.
To define a default domain name, use the ip domain-name command. To remove the IP default domain name, use the no form of this command. You can enter up to three domain names. If a request arrives without a domain name appended in its hostname, the proxy tries to resolve the hostname by appending name1, name2, and name3 in that order until one of these names succeeds.
To add an entry to the /etc/hosts file on the device, mapping a hostname to an IP address, use the ip host command. A given hostname can be mapped only to a single IP address, while an IP address can have multiple hostnames mapped to it, each one through a separate issuance of this command. To remove the entry from the /etc/hosts file, use the no form of this command. You can use the show hosts EXEC command to display the contents of the /etc/hosts file.
To specify the address of one or more name servers to use for name and address resolution, use the ip name-server ip-addresses command. To disable IP name servers, use the no form of this command. For proper resolution of the hostname to the IP address or the IP address to the hostname, the WAAS device uses DNS servers. Use the ip name-server command to point the WAAS device to a specific DNS server. You can configure up to three servers.
Path MTU autodiscovery discovers the MTU and automatically sets the correct value. Use the ip path-mtu-discovery enable command to start this autodiscovery utility. By default, this feature is disabled because the WAE does not receive ICMP packets. When this feature is disabled, the sending device uses a packet size that is smaller than 576 bytes and the next hop MTU. Existing connections are not affected when this feature is turned on or off.
Use the ip route command to add a specific static route for a network or host. Any IP packet designated for the specified destination uses the configured route.
To configure static IP routing, use the ip route command. To remove the route, use the no form of this command. Do not use the ip route 0.0.0.0 0.0.0.0 command to configure the default gateway; use the ip default-gateway command instead.
Examples
The following example shows how to configure a default gateway for the WAAS device:
The following example shows how to configure a default gateway for the management interface on the WAAS device, if it is different from the standard default gateway:
The following example shows how to configure a static IP route for the WAAS device:
The following example shows how to configure a default domain name for the WAAS device:
The following example shows how to add an entry to the /etc/hosts file on the WAAS device:
The following example shows how to configure a name server for the WAAS device:
Related Commands
(config) ip access-list
To create and modify access lists on a WAAS device for controlling access to interfaces or applications, and to define subnets, use the ip access-list global configuration command. To disable an access list, use the no form of this command.
ip access-list { standard { acl-name | acl- num } | extended { acl-name | acl- num } | logging}
no ip access-list { standard { acl-name | acl- num } | extended { acl-name | acl- num } | logging}
Syntax Description
Enables standard ACL configuration mode. The CLI enters the standard ACL configuration mode in which all subsequent commands apply to the current standard access list. The (config-std-nacl) prompt appears: See the “Standard ACL Configuration Mode Commands” section for details about working with entries in a standard access list and the commands available from the standard ACL configuration mode (config-std-nacl)#. |
|
Enables extended ACL configuration mode. The CLI enters the extended ACL configuration mode in which all subsequent commands apply to the current extended access list. The (config-ext-nacl) prompt appears: See the “Extended ACL Configuration Mode Commands” section for details about working with entries in an extended access list and the commands available from the extended ACL configuration mode (config-ext-nacl)#. |
|
Access list to which all commands entered from ACL configuration mode apply, using an alphanumeric string of up to 30 characters, beginning with a letter. |
|
Access list to which all commands entered from access list configuration mode apply, using a numeric identifier. For standard access lists, the valid range is 1 to 99; for extended access lists, the valid range is 100 to 199. |
|
Defaults
An access list drops all packets unless you configure at least one permit entry.
Command Modes
Device Modes
Usage Guidelines
Within ACL configuration mode, you can use the editing commands (list, delete, and move) to display the current condition entries, to delete a specific entry, or to change the order in which the entries will be evaluated. To return to global configuration mode, use the exit command at the ACL configuration mode prompt.
To create an entry, use a the deny or permit keyword and specify the type of packets that you want the WAAS device to drop or to accept for further processing. By default, an access list denies everything because the list is terminated by an implicit deny any entry. You must include at least one permit entry to create a valid access list.
Note IP ACLs that are defined on a router take precedence over the IP ACLs that are defined on the WAE. IP ACLs that are defined on a WAE take precedence over the WAAS application definition policies that are defined on the WAE.
After creating an access list, you can include the access list in an access group using the access-group command, which determines how the access list is applied. You can also apply the access list to a specific application using the appropriate command. A reference to an access list that does not exist is the equivalent of a permit any condition statement.
To work with access lists, enter either the ip access-list standard or ip access-list extended global configuration command. Identify the new or existing access list with a name up to 30 characters long beginning with a letter, or with a number. If you use a number to identify a standard access list, it must be between 1 and 99; for an extended access list, use a number from 100 to 199. You must use a standard access list for providing access to the SNMP server or to the TFTP gateway/server. However, you can use either a standard access list or an extended access list for providing access to the WCCP application.
After you identify the access list, the CLI enters the appropriate configuration mode and all subsequent commands apply to the specified access list. The prompt for each configuration mode is shown in the following examples.
To define a subnet, use either a standard or an extended ACL. In an HTTP AO subnet configuration, the access-list option must have at least one condition statement in it for it to exist. The list is terminated by an implicit deny any (standard access list) or deny ip any any (extended access list) condition statement. This statement applies to HTTP AO optimizations unless the ACL has an explicit permit all statement in it. If an acl name or acl number does not exist (if no condition statements exist in the access list), it is considered as an implicit permit any (standard access list) or permit ip any any (extended access list) condition statement. We recommend that you explicitly add permit any or deny any at the end of the ACL to make all the conditions clear for the subnet feature.
Use the ip access-list logging command to log denied packets.
Examples
The following example shows how to create an access list on the WAAS device. You create this access list to allow the WAAS device to accept all web traffic that is redirected to it but limit host administrative access using SSH:
The following example shows how to activate the access list for an interface:
The following example shows how this configuration appears when you enter the show running-configuration command:
The following example shows how to configure an ACL to define a subnet:
(config) ip icmp rate-limit unreachable
To limit the rate at which Internet Control Message Protocol (ICMP) destination unreachable messages are generated, use the ip icmp rate-limit unreachable command in global configuration mode. To remove the rate limit, use the no form of this command.
ip icmp rate-limit unreachable df microseconds
no ip icmp rate-limit unreachable df microseconds
Syntax Description
Defaults
The default value is one ICMP destination unreachable message per 500 microseconds.
Command Modes
Device Modes
Usage Guidelines
This feature is enabled by default. The no ip icmp rate-limit unreachable df command turns off the previously configured rate limit.
The software maintains two timers: one for general destination unreachable messages and one for DF destination unreachable messages. Both share the same time limits and defaults. If the df option is not configured, the ip icmp rate-limit unreachable command sets the time values for DF destination unreachable messages. If the df option is configured, its time values remain independent from those of general destination unreachable messages.
Examples
The following example sets the rate of the ICMP destination unreachable message to one message every 10 microseconds:
The following example turns off the previously configured rate limit:
Related Commands
(config) ip unreachables df
To enable the generation of Internet Control Message Protocol (ICMP) unreachable messages, use the ip unreachables df command in global configuration mode. To disable this function, use the no form of this command.
Syntax Description
Defaults
The default value is one ICMP destination unreachable message per 500 microseconds.
Command Modes
Device Modes
Usage Guidelines
If the software receives a nonbroadcast packet destined for itself that uses an unknown protocol, it sends an ICMP protocol unreachable message back to the source. Similarly, if the software receives a packet that it is unable to deliver to the ultimate destination because it knows of no route to the destination address, it sends an ICMP host unreachable message to the source. This feature is enabled by default.
ExamplesExamples
The following example enables the generation of ICMP unreachable messages, as appropriate, on an interface:
Related Commands
(config) ipv6
To change the initial network device configuration settings, use the ip v6 global configuration command. To delete or disable these settings, use the no form of this command.
ipv6 {default-gateway [ management ] ip-v6 address | route [ management ] ip-v6 address}
no ipv6 {default-gateway [ management ] ip-v6 address | route [ management ] ip-v6 address}
Syntax Description
Specifies the IPv6 address of the default gateway, in the X:X:X:X format. |
|
Specifies that the default gateway or net route is for the management interface. |
Defaults
Command Modes
Device Modes
Usage Guidelines
To define a default gateway, use the ip default-gateway command.If you have designated a management interface, you can configure a different default gateway for the management interface by using the management keyword. The WAAS device uses the default gateway to route IP packets when there is no specific route found to the destination. To remove the IP default gateway, use the no form of this command.
Use the ip route command to add a specific static route for a network or host. Any IP packet designated for the specified destination uses the configured route.If you have designated a management interface, you can configure a different ip route for the management interface by using the management keyword.
To configure static IP routing, use the ip route command. To remove the route, use the no form of this command.
Examples
The following example shows how to configure a default gateway for the WAAS device:
The following example shows how to configure a default gateway for the management interface on the WAAS device, if it is different from the standard default gateway:
The following example shows how to configure a static IP route for the WAAS device:
Related Commands
(config) kerberos
To authenticate a user that is defined in the Kerberos database, use the kerberos global configuration command. To disable authentication, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
All Windows 2000 domains are also Kerberos realms. Because the Windows 2000 domain name is also a DNS domain name, the Kerberos realm name for the Windows 2000 domain name is always in uppercase letters. This capitalization follows the recommendation for using DNS names as realm names in the Kerberos Version 5 protocol document (RFC-1510) and affects only interoperability with other Kerberos-based environments.
Note Your Windows domain server must have a Reverse DNS Zone configured for this command to execute successfully.
The KDC server and all hosts with Kerberos authentication configured must interact within a 5-minute window or authentication will fail. All hosts, especially the KDC, should be running NTP. For information about configuring NTP, see the (config) ntp command.
The KDC server and Admin server must have the same IP address. The default port number for both servers is port 88.
Examples
The following example shows how to configure the WAAS device to authenticate with a specified KDC in a specified Kerberos realm. The configuration is then verified.
Related Commands
(config) kernel kdb
To enable access to the kernel debugger (kdb), use the kernel kdb global configuration command. To disable access to the kernel debugger, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Once enabled, kdb is automatically activated if kernel problems occur, or you can manually activate it from the local console for the WAAS device. Once activated, all normal functioning of the WAAS device is suspended until kdb is manually deactivated. The kdb prompt looks like this:
To deactivate kdb, enter the go command at the kdb prompt. If kdb was automatically activated because of kernel problems, the system generates a core dump and restarts. If you activated kdb manually for diagnostic purposes, the system resumes normal functioning in whatever state it was when you activated kdb. In either case, if you enter the reboot command, the system restarts and normal operation resumes.
kdb is disabled by default and you must enter the kernel kdb command in global configuration mode to enable it. If kdb has been previously enabled, you can enter the no kernel kdb global configuration command to disable it. When kdb is enabled, you can activate it manually from the local console by pressing Ctrl-_ followed by Ctrl-B. On a vWAAS device, kdb can be enabled by pressing the Esc key and typing kdb.
The WAAS device is often unattended at many sites, and it is desirable for the WAAS device to automatically reboot after generating a core dump instead of requiring user intervention. Disabling the kernel debugger allows automatic recovery.
Examples
The following example shows how to enable, and then disable, access to the kernel debugger:
Related Commands
(config) kernel kdump enable
To enable the kernel crash dump mechanism, use the kernel kdump enable global configuration command. To disable the kernel crash dump mechanism, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
A kernal crash dump file is stored in the following disk location:
/local/local1/crash/ timestamp /vmcore
The analysis of the kernal crash dump file is stored in the following file:
/local/local1/crash/ timestamp /analysis.txt
Examples
The following example shows how to enable, and then disable, the kernel crash dump mechanism:
Related Commands
(config) line
To specify terminal line settings, use the line global configuration command. To configure the WAAS device to not check for the carrier detect signal, use the no form of this command.
no line console carrier-detect
Syntax Description
Sets the device to check the carrier detect signal before writing to the console. |
Defaults
Command Modes
Device Modes
Examples
The following example shows how to set the WAAS device to check for the carrier detect signal:
(config) logging console
To set system logging to console, use the logging console global configuration command. To disable logging functions, use the no form of this command.
logging console { enable | priority loglevel }
no logging console { enable | priority loglevel }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the logging command to set specific parameters of the system log file.
You can configure logging to send various levels of messages to the console using the logging console priority option.
Examples
The following example shows how to send messages that have a priority code of “error” (Level 3) to the console:
The following example shows how to disable sending of messages that have a priority code of “error” (level 3) to the console:
Related Commands
(config) logging disk
To system logging to a disk file, use the logging disk global configuration command. To disable logging functions, use the no form of this command.
logging disk { enable | filename filename | priority loglevel | recycle size }
no logging disk { enable | filename filename | priority loglevel | recycle size }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the logging command to set specific parameters of the system log file.
The no logging disk recycle size command sets the file size to the default value. Whenever the current log file size surpasses the recycle size, the log file is rotated. The log file cycles through at most five rotations, and they are saved as [ log file name ]. [ 1-5 ] under the same directory as the original log. The rotated log file is the one configured using the logging disk filename command.
Examples
The following example shows how to send messages that have a priority code of “error” (level 3) to a file:
WAE(config)#
logging disk priority error
Related Commands
(config) logging facility
To set the facility parameter for system logging, use the logging facility global configuration command. To disable logging functions, use the no form of this command.
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to set the facility parameter to authorization system for syslog messages:
Related Commands
(config) logging host
To configure system logging to a remote host, use the logging host global configuration command. To disable logging functions, use the no form of this command.
logging host { hostname | ip-address } [ port port_num | priority loglevel | rate-limit message_rate ]
no logging host { hostname | ip-address } [ port port_num | priority loglevel | rate-limit message_rate ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the logging command to set specific parameters of the system log file.
To configure the WAAS device to send varying levels of event messages to an external syslog host, use the logging host option.
You can configure a WAAS device to send varying levels of messages to up to four remote syslog hosts using the logging host hostname command.
Examples
The following example shows how to send messages that have a priority code of “error” (level 3) to the remote syslog host that has an IP address of 172.31.2.160:
WAE(config)#
logging host 172.31.2.160 priority error
Related Commands
(config) ntp
To configure the NTP server and to allow the system clock to be synchronized by a time server, use the ntp global configuration command. To disable this function, use the no form of this command.
ntp [authenticate | authentication-key key-num [md5 authentication-key] |
server {ip-address | hostname} [ip-addresses | hostnames] |
server-with-authentication {ip-address | hostname} key key-num]
ntp [ authenticate | authentication-key authentication-key [ md5 encryption-type ] |
server { ip-address | hostname } [ ip-addresses | hostnames ] |
server-with-authentication { ip-address | hostname } key authentication-key ]
no ntp [authenticate | authentication-key key-num [md5 authentication-key] |
server {ip-address | hostname} [ip-addresses | hostnames] |
server-with-authentication {ip-address | hostname} key key-num]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Note Unexpected time changes can result in unexpected system behavior. We recommend reloading the system after enabling an NTP server.
Note When you use the ntp ip-address command, it is important to verify that you have specified the correct IP address and IP address format. The system displays an error message if you enter an incorrect IP address for this command; however, when the IP address with 2 or 3 octant is configured, the system considers the IP format as valid, as per the global IP standard.
Examples
The following example shows how to specify the NTP server IP address as the time source for a WAAS device. It also removes this configuration.
(config) peer
To enable peer optimization, use the peer global configuration command. To disable peer optimization, use the no form of this command.
peer device-id deviceid [ description description ] optimization enable
no peer device-id deviceid [ description description ] optimization enable
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the no peer command to disable optimization between peer devices in a serial cluster.
Use the peer command to reenable optimization between peer devices if it has been disabled previously.
The deviceid is a hexadecimal string (for example, d4:65:01:40:40:8a) that you can obtain with the show device-id or show hardware EXEC commands.
You can configure optimization for only one peer device with this command.
Examples
The following example shows how to disable optimization with a serial peer device:
Related Commands
(config) policy-map
To configure an AppNav or optimization policy map, use the policy-map global configuration command. To unconfigure settings, use the no form of this command.
policy-map type { appnav | waas } policymap-name [ rename new-name ]
no policy-map type { appnav | waas } policymap-name
Syntax Description
Policy map name (up to 40 alpha-numeric characters and hyphen, beginning with a letter). |
|
(Optional) Renames the policy map with the specified new name. |
Defaults
Command Modes
Device Modes
Usage Guidelines
Use the policy-map command to add or modify policy maps that associate policy actions with class maps. This command invokes the Policy Map configuration mode, which is indicated by a different prompt (config-pmap). For more information on Policy Class Map configuration mode commands, see the “ Policy Map Configuration Mode Commands ” section. To return to global configuration mode, enter the exit command.
You can delete a policy map by using the no form of this command.
The WAAS software comes with many class maps and policy rules that help your WAAS system classify and optimize some of the most common traffic on your network. Before you create a new class map or policy rule, we recommend that you review the default class map and policy rules and modify them as appropriate. It is usually easier to modify an existing class map or policy rule than to create a new one. For a list of the default applications, class maps, and policy rules, see the Cisco Wide Area Application Services Configuration Guide.
Note We strongly recommend that you use the WAAS Central Manager GUI to centrally configure policy maps for your WAAS devices. For more information, see the Cisco Wide Area Application Services Configuration Guide.
Examples
The following example shows how to configure a WAAS optimization policy map:
The following example shows how to configure an AppNav policy map:
Related Commands
(config) port-channel
To configure port channel load-balancing on a WAAS device, use the port-channel global configuration command. To set load balancing on the port channel to its default method, use the no form of this command.
port-channel load-balance { src-dst-ip | src-dst-ip-port }
no port-channel load-balance { src-dst-ip | src-dst-ip-port }
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to configure src-dst-ip load balancing on a port channel and then disable it:
Related Commands
(config) primary-interface
To configure the primary interface for a WAAS device, use the primary-interface global configuration command. To remove the configured primary interface, use the no form of this command.
primary-interface { BVI bridge-id | GigabitEthernet slot / port | PortChannel index | Standby group-index | TenGigabitEthernet slot / port } {IPv4 | IPv6}[ management ]
no primary-interface { BVI bridge-id | GigabitEthernet slot / port | PortChannel index | Standby group-index | TenGigabitEthernet slot / port } {IPv4 | IPv6}[ management ]
primary-interface virtual slot/port {IPv4 | IPv6}[ management ]
no primary-interface virtual slot/port {IPv4 | IPv6}[ management ]
Syntax Description
Defaults
The default primary interface is the Gigabit Ethernet 0/0 or 1/0 interface, depending on the hardware platform. If this interface is not configured, then the first operational interface on which a link beat is detected becomes the default primary interface. Interfaces with lower number IDs are polled first (for example, Gigabit Ethernet 1/0 is checked before 2/0). The Gigabit Ethernet interfaces are polled before the port-channel interfaces.
Command Modes
Device Modes
Usage Guidelines
You can change the primary interface without disabling the WAAS device. To change the primary interface, reenter the command string and specify a different interface.
Note If you use the restore factory-default preserve basic-config command, the configuration for the primary interface is not preserved. If you want to reenable the WAAS device after using the restore factory-default preserve basic-config command, make sure to reconfigure the primary interface after the factory defaults are restored.
Setting the primary interface to be a Standby group does not imply that Standby functionality is available. You must configure Standby interfaces using the interface standby global configuration command.
Examples
The following example shows how to specify the Gigabit Ethernet slot 1, port 0 as the primary interface, for IPv6 traffic, on a WAAS device:
WAE(config)# primary-interface GigabitEthernet 1/0 IPv6
The following example shows how to specify the Gigabit Ethernet slot 2, port 0 as the primary interface on a WAAS device:
The following example shows how to specify port channel interface 1 as the primary interface on a WAAS device:
The following example shows how to specify the Gigabit Ethernet slot 1, port 0 as the primary interface, for IPv6 traffic, on a WAAS device and designate it to be used for management trafffic:
To configure a primary interface to be used as a management interface, you should have configured it with an ip and default-gateway address.
Related Commands
(config) radius-server
To configure a set of RADIUS authentication server settings on the WAAS device, use the radius-server global configuration command. To disable RADIUS authentication server settings, use the no form of this command.
radius-server { host hostname | ip-addr | ipv6 {ipv6-address} [primary] | key keyword | retransmit retries | timeout seconds }
no radius-server { host hostname | hostipaddr | ipv6 {ipv6-address} [primary] | key keyword | retransmit retries | timeout seconds }
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
RADIUS authentication is disabled by default. You can enable RADIUS authentication and other authentication methods at the same time. You can also specify which method to use first. (See the (config) authentication configuration command.)
You can configure multiple RADIUS servers; authentication is attempted on the primary server first. If the primary server is unreachable, then authentication is attempted on the other servers in the RADIUS farm, in the order in which they were configured. If authentication fails for any reason other than a server is unreachable, authentication is not attempted on the other servers in the farm. This process applies regardless of the setting of the authentication fail-over server-unreachable command.
Examples
The following example shows how to specify a RADIUS server, specify the RADIUS key, and accept retransmit defaults. You can verify the configuration using the show radius-server command.
Related Commands
(config) service-insertion
To configure WNs, WNGs, ANCs, an ANCG, and a service context that are part of an AppNav Cluster, use the service-insertion global configuration command. To unconfigure settings, use the no form of this command.
service-insertion { pass-through offload enable { all | [ config ] [ intermediate ] [ no-peer ]} | service-context contextname [ rename newname ]| appnav-controller distribute enable | appnav-controller-group ancgroupname | service-node | service-node-group sngroupname | swap src-ip }
no service-insertion { pass-through offload enable { all | [ config ] [ intermediate ] [ no-peer ]} | service-context contextname | appnav-controller distribute enable | appnav-controller-group ancgroupname | service-node | service-node-group sngroupname | swap src-ip }
Syntax Description
Defaults
Distribution is enabled on an ANC. Pass-through offload is enabled for config, intermediate, and no-peer reasons.
Command Modes
Device Modes
Usage Guidelines
Use the service-insertion command to configure the entities (WNs, WNGs, ANCs, an ANCG, and a service context) that are part of an AppNav Cluster.
Note We recommend that you use only the WAAS Central Manager to create, modify, or delete an AppNav cluster. Using the service-insertion command to perform any of these operations will cause the device to go out of sync with the WAAS Central Manager, which will also cause the Central Manager to display incorrect cluster configuration information.
For how to create, modify, or delete an AppNav cluster in the WAAS Central Manager, see the “Configuring AppNav” chapter of the Cisco Wide Area Application Services Configuration Guide.
Some options of this command initiate configuration submodes, which are indicated by a different prompt (for example, config-scg). For more information on the configuration submode commands, see the following sections:
- service-context —“ Service Context Configuration Mode Commands ”
- appnav-controller-group —“ AppNav Controller Group Configuration Mode Commands ”
- service-node —“ Service Node Configuration Mode Commands ”
- service-node-group —“ Service Node Group Configuration Mode Commands ”
Within configuration submodes, you can use the various commands to define the settings of the entity. To return to global configuration mode, enter the exit command.
Note For the no service-insertion service-context contextname command to take effect, you must first disable the specified cluster before you execute this command. If you execute this command while the service cluster is enabled, the following error message will be displayed: Error! Cannot remove Service Context (contextname) while it is enabled.
Each WN (and ANC acting as a WN) in the AppNav Cluster must be configured with WN settings by the service-insertion service-node command.
Each ANC in the AppNav Cluster must be configured with the following:
- ANCG settings by the service-insertion appnav-controller-group command
- WNG settings by the service-insertion service-node-group command
- Service context settings by the service-insertion service-context command
You can put an ANC into monitoring mode with the no service-insertion appnav-controller distribute enable command. This command stops the ANC from distributing any traffic to WNs for optimization. Instead, all traffic is passed through. This mode can be used for traffic monitoring for deployment sizing or troubleshooting purposes. If one ANC in an AppNav Cluster has this setting, all ANCs operate in monitor mode. You can reenable distribution with the service-insertion appnav-controller distribute enable command.
You can use the service-insertion pass-through offload enable command on a WN to prevent the ANCs from sending pass-through traffic to that WN. You can use this command on an ANC to prevent the ANC from sending pass-through traffic to any WN. The options allow you to specify what kind of pass-through traffic is to be off loaded by the ANC.
You may want to use the swap src-ip option if you are using a port channel for the cluster interface or there is a load balancing device between the ANC and WN. This option may improve the load balancing of traffic that the ANC distributes to WNs for optimization because it load balances based on the client IP address rather than the ANC IP address. (For traffic from the server to the client, it swaps the server IP address with the ANC IP address.) The Central Manager enables this feature automatically if any existing ANCs or WNs have port channel cluster interfaces that you configure with the Central Manager.
Examples
The following example shows how to configure and enable a WN:
The following example shows how to configure and enable two WNGs, each having two WNs, on an ANC:
The following example shows how to configure and enable an ANCG with two ANC members, on an ANC:
The following example shows how to configure and enable a service context:
The following example shows how to enable pass-through offloading of traffic for all reasons:
The following example shows how to enable the source IP address swapping feature:
Related Commands
(config) service-policy
To configure AppNav and optimization service policy, use the service-policy global configuration command. To unconfigure settings, use the no form of this command.
service-policy { optimize policy-map-name | type { appnav config { remove-all | restore-predefined }| waas { config { remove-all | restore-predefined }| set ip dscp dscp-marking }}
no service-policy { optimize policy-map-name | type { appnav config { remove-all | restore-predefined }| waas { config { remove-all | restore-predefined }| set ip dscp dscp-marking }}
Syntax Description
Replaces all class map and policy map configurations with factory default configurations. |
|
Specifies the default DSCP marking value, as shown in Table 3-2 . |
Defaults
Command Modes
Device Modes
Usage Guidelines
The DSCP field in an IP packet enables different levels of service to be assigned to network traffic. Levels of service are assigned by marking each packet on the network with a DSCP code. DSCP is the combination of IP Precedence and Type of Service (ToS) fields. For more information, see RFC 2474.
A DSCP value is assigned in a policy rule and applies to all traffic associated with a class map. If a DSCP value is not assigned or defined, the default DSCP value is applied to traffic. The global default DSCP value is copy, which copies the DSCP value from the incoming packet and uses it for the outgoing packet.
Table 3-2 lists the valid DSCP marking values that you can specify.
|
|
---|---|
Copies the DSCP value from the incoming packet to the outgoing packet. (default) |
|
Examples
The following example shows how to set the default DSCP marking value to copy:
The following example shows how to restore optimization policies:
The following example shows how to remove all AppNav policies:
Related Commands
(config) smb-conf
To manually configure the parameters for a WAAS device Samba configuration file, smb.conf, use the smb-conf global configuration command. To return a parameter to its default value, use the no form of this command.
smb-conf section { global } name attr-name value attr-value
no smb-conf section { global } name attr-name value attr-value
Syntax Description
Specifies the name of the parameter in the specified section that you want to manually configure (up to 80 characters). |
|
Specifies the value of the parameter (up to 255 characters). |
See Table 3-3 for a description of the parameters for the global, print$, and printers, including the names and default values.
Defaults
Command Modes
Device Modes
Usage Guidelines
Legacy print services are no longer supported in WAAS 4.4.x and later.
The smb.conf file contains a variety of samba Configuration parameters. Global parameters apply to the server. Service level parameters, which define default settings for all other sections and shares, allow you to avoid the need to set the same value repeatedly. You can override these globally set share settings and specify other values for each individual section or share.
Examples
The following example shows how to change the maximum size of the Samba error log file from the default of 50 errors to 75 errors:
The following example shows how to change the realm from the default of CISCO to MYCOMPANYNAME:
The following example shows how to enable LDAP server signing:
Related Commands
(config) snmp-server access-list
To configure a standard access control list on a WAAS device to allow access through an SNMP agent, use the snmp-server access-list global configuration command. To remove a standard access control list, use the no form of this command.
snmp-server access-list { num | name }
no snmp-server access-list { num | name }
Syntax Description
Standard access list name. You can use a maximum of 30 characters. |
Defaults
Command Modes
Device Modes
Usage Guidelines
If you are using an SNMP server ACL, you must permit the loopback interface.
Examples
The following example shows how to allow the SNMP agent to check against access control list 12 before accepting or dropping packets:
Note You must first create access list 12 using the ip access-list standard global configuration command.
Related Commands
(config) snmp-server community
To enable the SNMP agent on a WAAS device and to set up the community access string to permit access to the SNMP agent, use the snmp-server community global configuration command. To disable the SNMP agent and remove the previously configured community string, use the no form of this command.
snmp-server community string [ group groupname | rw ]
no snmp-server community string [ group groupname | rw ]
Syntax Description
Defaults
The SNMP agent is disabled and a community string is not configured. When configured, an SNMP community string by default permits read-only access to all objects.
Command Modes
Device Modes
Examples
The following example shows how to enable the SNMP agent and assign the community string comaccess to SNMP:
The following example shows how to disable the SNMP agent and remove the previously defined community string:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server contact
To set the system server contact string on a WAAS device, use the snmp-server contact global configuration command. To remove the system contact information, use the no form of this command.
Syntax Description
Specifies the text for MIB-II object sysContact. This is the identification of the contact person for this managed node. |
Defaults
Command Modes
Device Modes
Usage Guidelines
The system contact string is the value stored in the MIB-II system group sysContact object.
Examples
The following example shows how to set a system contact string and then remove it:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server enable traps
To enable the WAAS device to send SNMP traps, use the snmp-server enable traps global configuration command. To disable all SNMP traps or only SNMP authentication traps, use the no form of this command.
snmp-server enable traps [ alarm [ clear-critical | clear-major | clear-minor | raise-critical | raise-major | raise-minor ]
snmp-server enable traps config | entity | event
snmp-server enable traps content-engine [ disk-fail | disk-read | disk-write | overload-bypass | transaction-log ]
snmp-server enable traps snmp [ authentication | cold-start | linkdown | linkup ]
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
In the WAAS software the following six generic alarm traps are available in the CISCO-CONTENT-ENGINE-MIB:
|
|
|
---|---|---|
Note By default, these six general alarm traps are disabled.
These six general alarm traps provide SNMP and Node Health Manager integration. You can enable or disable each of these six alarm traps through the WAAS CLI.
To configure traps, you must enter the snmp-server enable traps command. If you do not enter the snmp-server enable traps command, no traps are sent.
The snmp-server enable traps command is used with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP traps. To send traps, you must configure at least one host using the snmp-server host command.
To allow a host to receive a trap, you must enable both the snmp-server enable traps command and the snmp-server host command for that host.
You must enable SNMP with the snmp-server community command.
To disable the sending of the MIB-II SNMP authentication trap, you must enter the command no snmp-server enable traps snmp authentication.
Examples
The following example shows how to enable the WAAS device to send all traps to the host 172.31.2.160 using the community string public:
The following example shows how to disable all traps:
Related Commands
(config) snmp-server community
(config) snmp-server group
To define a user security model group for a WAAS device, use the snmp-server group global configuration command. To remove the specified group, use the no form of this command.
snmp-server group name { v1 [ notify name ] [ read name ] [ write name ] |
v2c [ notify name ] [ read name ] [ write name ] |
v3 { auth [ notify name ] [ read name ] [ write name ] |
noauth [ notify name ] [ read name ] [ write name ] |
priv [ notify name ] [ read name ] [ write name ]}}
no snmp-server group name { v1 [ notify name ] [ read name ] [ write name ] |
v2c [ notify name ] [ read name ] [ write name ] |
v3 { auth [ notify name ] [ read name ] [ write name ] |
noauth [ notify name ] [ read name ] [ write name ] |
priv [ notify name ] [ read name ] [ write name ]}}
Syntax Description
Defaults
The default is that no user security model group is defined.
Command Modes
Device Modes
Usage Guidelines
The maximum number of SNMP groups that can be created is 10.
Select one of three SNMP security model groups: Version 1 (v1) Security Model, Version 2c (v2c) Security Model, or the User Security Model (v3 or SNMPv3). Optionally, you then specify a notify, read, or write view for the group for the particular security model chosen. The v3 option allows you to specify the group using one of three security levels: auth (AuthNoPriv Security Level), noauth (noAuthNoPriv Security Level), or priv (AuthPriv Security Level).
Examples
The following example shows how to define a user security model group named acme that uses the SNMP version 1 security model and a view name of mymib for notifications:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server host
To specify the recipient of a host SNMP trap operation, use the snmp-server host global configuration command. To remove the specified host, use the no form of this command.
snmp-server host { hostname | ipv-4address/ ipv6-address } communitystring
[ v2c [ retry number ] [ timeout seconds ] |
[ v3 { auth [ retry number ] [ timeout seconds ] |
noauth [ retry number ] [ timeout seconds ] |
priv [ retry number ] [ timeout seconds ]}]
no snmp-server host { hostname | ip-address } communitystring
[ v2c [ retry number ] [ timeout seconds ] |
[ v3 { auth [ retry number ] [ timeout seconds ] |
noauth [ retry number ] [ timeout seconds ] |
priv [ retry number ] [ timeout seconds ]}]
Syntax Description
Defaults
This command is disabled by default. No traps are sent. If enabled, the default version of the SNMP protocol used to send the traps is SNMP Version 1.
Command Modes
Device Modes
Usage Guidelines
If you do not enter an snmp-server host command, no traps are sent. To configure the WAAS device to send SNMP traps, you must enter at least one snmp-server host command. To enable multiple hosts, you must enter a separate snmp-server host command for each host. The maximum number of snmp-server host commands is four.
When multiple snmp-server host commands are given for the same host, the community string in the last command is used.
The snmp-server host command is used with the snmp-server enable traps command to enable SNMP traps.
You must enable SNMP with the snmp-server community command.
Examples
The following example shows how to send the SNMP traps defined in RFC 1157 to the host specified by the IP address 172.16.2.160. The community string is comaccess:
The following example shows how to remove the host 172.16.2.160 from the SNMP trap recipient list:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server location
To set the SNMP system location string on a WAAS device, use the snmp-server location global configuration command. To remove the location string, use the no form of this command.
Syntax Description
Specifies the text for MIB-II object sysLocation. This string describes the physical location of this node. |
Defaults
Command Modes
Device Modes
Usage Guidelines
The system location string is the value stored in the MIB-II system group system location object. You can see the system location string with the show snmp EXEC command.
Examples
The following example shows how configure a system location string:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server mib
To configure persistence for the SNMP Event MIB, use the snmp-server mib global configuration command. To disable the Event MIB, use the no form of this command.
no snmp-server mib persist event
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
The Event MIB can set the threshold on any MIB variables supported by the WAAS software and store the threshold permanently on the disk.
The WAAS software implementation of SNMP supports the following MIBs:
- ACTONA-ACTASTORE-MIB
- CISCO-CONFIG-MAN-MIB
- CISCO-CDP-MIB
- CISCO-CONTENT-ENGINE-MIB (partial)
- CISCO-ENTITY-ASSET-MIB
- CISCO-SMI
- CISCO-TC
- ENTITY-MIB
- EVENT-MIB
- HOST-RESOURCES-MIB
- MIB-II
- SNMP-COMMUNITY-MIB
- SNMP-FRAMEWORK-MIB
- SNMP-NOTIFICATION-MIB
- SNMP-TARGET-MIB
- SNMP-USM-MIB
- SNMPv2
- SNMP-VACM-MIB
Note The WAAS software supports six generic alarm traps in the CISCO-CONTENT-ENGINE-MIB for SNMP and Node Health Manager integration.
Examples
The following example shows how to set persistence for the Event MIB:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server monitor user
To specify the user to be used for active monitoring of triggers, use the snmp-server monitor-user global configuration command. To disable the user from monitoring, use the no form of this command.
snmp-server monitor-user existing snmpv3 user
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Using the snmp-server monitor-user global configuration command, you can specify the user that will be used for active monitoring of triggers. Any SNMP V3 user can be configured as a Monitor User. This user should have sufficient permission to run a query on the objects specified in triggers. No priv key should be associated with this user, because this user monitors triggers internally.
Examples
The following example shows how to specify the user that is to be used for active monitoring of triggers:
Related Commands
(config) snmp-server notify inform
To configure the SNMP notify inform request on a WAAS device, use the snmp-server notify inform global configuration command. To return the setting to the default value, use the no form of this command.
Syntax Description
Defaults
If you do not enter the snmp-server notify inform command, the default is an SNMP trap request.
Command Modes
Device Modes
Examples
The following example shows how to configure an SNMP notify inform request versus the default SNMP trap:
Related Commands
(config) snmp-server community
(config) snmp-server trap-source
To set the source interface from which SNMP traps are sent on a WAAS device, use the snmp-server trap-source global configuration command. To remove the trap source configuration, use the no form of this command.
snmp-server trap-source { GigabitEthernet slot / port | PortChannel index | Standby grpnumber | TenGigabitEthernet slot / port }
no snmp-server trap-source { GigabitEthernet slot / port | PortChannel index | Standby grpnumber | TenGigabitEthernet slot / port | bvi bridge-id }
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to configure gigabit Ethernet interface 1/0 as the trap source:
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server trigger
To configure thresholds for a user-selected MIB object for monitoring purposes on a WAAS device, use the snmp-server trigger global configuration command. To remove access, use the no form of this command.
snmp-server trigger {trigger name | mib varname [ wildcard ] | wait-time
[absent [ LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
equal [absolute threshold value | delta threshold value] |
greater-than [absolute threshold value | delta threshold value] |
less-than [absolute threshold value | delta threshold value] |
on- change [LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
present [ LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
threshold lower threshold value |
]}
no snmp-server trigger {trigger name | mib varname [ wildcard ] | wait-time
[absent [ LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
equal [absolute threshold value | delta threshold value] |
greater-than [absolute threshold value | delta threshold value] |
less-than [absolute threshold value | delta threshold value] |
on- change [LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
present [ LINE | mibvar1 mibvar1 ] [ LINE | mibvar2 mibvar2 ] [ LINE | mibvar3 mibvar3 ]
[ LINE ] |
threshold lower threshold value |
]}
Syntax Description
Defaults
Command Modes
Device Modes
Usage Guidelines
Using the snmp-server trigger global configuration command, you can define additional SNMP traps for other MIB objects of interest to your particular configuration. You can select any MIB object from any of the support MIBs for your trap. The trap can be triggered based on a variety of tests:
- absent—A specified MIB object that was present at the last sampling is no longer present as of the current sampling.
- equal—The value of the specified MIB object is equal to the specified threshold.
- greater-than—The value of the specified MIB object is greater than the specified threshold value.
- less-than—The value of the specified MIB object is less than the specified threshold value.
- on-change—The value of the specified MIB object has changed since the last sampling.
- present—A specified MIB object is present as of the current sampling that was not present at the previous sampling.
- threshold- Min value and Max values specifying the lower and upper thresholds.
The threshold value can be based on an absolute sample type or on a delta sample type. An absolute sample type is one in which the test is evaluated against a fixed integer value between zero and 4294967295. A delta sample type is one in which the test is evaluated against the change in the MIB object value between the current sampling and the previous sampling.
After you configure SNMP traps, you must use the snmp-server enable traps event global configuration command for the event traps you just created to be generated. To save the MIB data using the write mib-data EXEC command.
Note You can create valid triggers only on read-write and read-only MIB objects. If you try to create a trigger on a read-create MIB object, you receive an error message.
Examples
The following example shows how to create a threshold for the MIB object esConTabIsConnected so that a trap is sent when the connection from the Edge WAE to the Core WAE is lost:
"Lost the connection with the core server."
Once you have configured the WAE to send SNMP traps, you can view the results of these newly created traps using the show snmp events EXEC command.
You can also delete user-created SNMP traps. The following example shows how to delete the trap set for esConTabIsConnected that we created in the previous example.
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server user
To define a user who can access the SNMP server, use the snmp-server user global configuration command. To remove access, use the no form of this command.
snmp-server user name group
[ auth { md5 password [ priv password ] |
sha password [ priv password ]} |
remote octetstring [ auth { md5 password [ priv password ] |
sha password [ priv password ]}]]
no nmp-server user name group
[ auth { md5 password [ priv password ] |
sha password [ priv password ]} |
remote octetstring [ auth { md5 password [ priv password ] |
sha password [ priv password ]}]]
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to create an SNMPv3 user account on the WAAS device. The SNMPv3 user is named acme and belongs to the group named admin. Because this SNMP user account has been set up with no authentication password, the SNMP agent on the WAAS device does not perform authentication on SNMP requests from this user.
WAE(config)#
snmp-server user acme admin
Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server notify inform
(config) snmp-server view
To define an SNMPv2 MIB view on a WAAS device, use the snmp-server view global configuration command. To remove the MIB view definition, use the no form of this command.
snmp-server view viewname MIBfamily { excluded | included }
no snmp-server view viewname MIBfamily { excluded | included }
Syntax Description
Name of this family of view subtrees and a subtree of the MIB. You can enter a maximum of 64 characters. |
|
Defaults
Command Modes
Device Modes
Examples
The following example shows how to define an SNMPv2 MIB view:
Related Commands
(config) snmp-server community