Match the command with the device mode at which the command is entered Not all options are used

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.

WAE# configure

WAE(config)#

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:

WAE(config)# exit

WAE#

(config) aaa accounting

To configure AAA accounting on a WAAS device, use the aaa accounting command in global configuration mode.

aaa accounting {commands {0 | 15} default {start-stop | stop-only | wait-start} tacacs | exec default {start-stop | stop-only | wait-start} tacacs | system default {start-stop | stop-only} tacacs}

Syntax Description

Defaults

AAA accounting is disabled by default.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The AAA accounting feature enables you to track the activities of an administrative user, services that users access, and the amount of network resources they consume (for example, connection time or the bytes transferred). You can use the AAA accounting feature to track user activity for billing, auditing, reporting, or security purposes. WAAS uses TACACS+ to implement AAA accounting; RADIUS is not currently supported. When AAA accounting is enabled, the WAAS device reports user activity to the TACACS+ security server in the form of accounting records. This data can then be analyzed for network management, client billing, and auditing.

You can activate accounting for the following types of events:

•

WeekDay#Month#Day#Time#Year#CEaddress#username#terminal#RemoteHost#Event#

EventTime#TaskId#Timezone#Service

•

WeekDay#Month#Day#Time#Year#CEaddress#username#terminal#RemoteHost#Event#

EventTime#TaskId#Timezone#Service#PrivilegeLevel#CLICommand

•

WeekDay#Month#Day#Time#Year#CEaddress#username#terminal#RemoteHost#Event#

EventTime#TaskId#Timezone#SystemService#SystemAccountingEvent#EventReason

WAAS software supports only the default accounting list.

Caution

Before using the wait-start option, make sure that the WAAS device is configured with the TACACS+ server and is able to successfully contact the server. If the WAAS device cannot contact a configured TACACS+ server, it might become unresponsive.

The WAAS software displays the following warning message if the wait-start option is configured:

Warning: The device may become non-responsive if it cannot contact a configured TACACS+ server.

The administrator is asked to confirm the configuration in an indefinite loop until the administrator enters "yes" to the following prompt:

Are you sure you want to proceed? [yes]

Examples

The following example configures TACACS+ on the WAAS device and also specifies 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 the requested user process should begin regardless of whether the start accounting notice was received by the accounting server:

WAE(config)# tacacs key abc

WAE(config)# tacacs server 192.168.50.1 primary

WAE(config)# aaa accounting system default start-stop tacacs

WAE# show aaa accounting 

Accounting Type   Record event(s)  Protocol

----------------------------------------------------------------

Exec shell         unknown            unknown

Command level  0   unknown            unknown

Command level 15   unknown            unknown

System             start-stop         TACACS+

In the following example, 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.

WAE(config)# aaa accounting exec default stop-only tacacs

In the following example, 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.

WAE(config)# aaa accounting commands 0 default stop-only tacacs

In the following example, 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.

WAE(config)# aaa accounting commands 15 default wait-start tacacs

The following are some examples of the EXEC shell accounting report that is available on the TACACS+ server:

Wed Apr 14 11:19:19 2004 172.16.0.0 super10 pts/0 172.31.0.0 start

start_time=1081919558 task_id=3028 timezone=PST service=shell

Wed Apr 14 11:19:23 2004 172.16.0.0 super10 pts/0 172.31.0.0

stop stop_time=1081919562 task_id=3028 timezone=PST service=shell

Wed Apr 14 11:22:13 2004 172.16.0.0 normal20 pts/0 via5.abc.com start

start_time=1081919732 task_id=3048 timezone=PST service=shell

Wed Apr 14 11:22:16 2004 172.16.0.0 normal20 pts/0 via5.abc.com stop

stop_time=1081919735 task_id=3048 timezone=PST service=shell

Wed Apr 14 11:25:29 2004 172.16.0.0 admin ftp via5.abc.com start start_time=1081919928

task_id=3069 timezone=PST service=shell

Wed Apr 14 11:25:33 2004 172.16.0.0 admin ftp via5.abc.com stop stop_time=1081919931

task_id=3069 timezone=PST service=shell

The following are some examples of the system accounting report that is available on the TACACS+ server:

Wed Apr 14 08:37:14 2004 172.16.0.0 unknown unknown 0.0.0.0 start start_time=1081909831

task_id=2725 timezone=PST service=system event=sys_acct reason=reload

Wed Apr 14 10:19:18 2004 172.16.0.0 admin ttyS0 0.0.0.0 stop stop_time=1081915955

task_id=5358 timezone=PST service=system event=sys_acct reason=shutdown

The following are some examples of 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

debug

show aaa accounting

(config) adapter

To enable the EndPoint Mapper (EPM) service, use the adapter global configuration command. To disable the EPM service, use the no form of the command.

adapter epm enable

Syntax Description

Defaults

The EPM service is enabled by default when you upgrade to WAAS software release 4.0.3 and later releases. The EPM service is disabled by default on new WAE appliances or when you restore the factory default settings.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the adapter epm enable command to enable EPM service when the Microsoft PortMapper adapter is installed.

Examples

The following example enables the EPM service:

WAE(config)# adapter epm enable

Related Commands

show adapter

show statistics epm

(config) alarm overload-detect

To detect alarm overload situations, use the alarm overload-detect global configuration command.

alarm overload-detect {clear1-999 [raise10-1000] | enable | raise10-1000 [clear1-999]}

Syntax Description

clear	Specifies the threshold at which the alarm overload state on the WAAS device is cleared. When the alarm drops below this threshold, the alarm is cleared and the SNMP traps and alarm notifications are again sent to your NMS. Note The alarm overload-detect clear value must be less than the alarm overload-detect raise value.
1-999	Number of alarms per second that ends an alarm overload condition.
raise	(Optional) Specifies the threshold at which the WAAS device enters an alarm overload state and SNMP traps and alarm notifications to your network management station (NMS) are suspended.
enable	Enables the detection of alarm overload situations.
10-1000	Number of alarms per second that triggers an alarm overload.

Defaults

clear: 1 alarm per second

raise: 10 alarms per second

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

When multiple applications running on a WAAS device experience problems at the same time, numerous alarms are set off simultaneously, and the WAAS device may stop responding. You can use the alarm overload-detect global configuration command to set an overload limit for the incoming alarms from the node health manager. If the number of alarms exceeds the maximum number of alarms allowed, the WAAS device enters an alarm overload state until the number of alarms drops down to the number defined in the clear option.

When the WAAS device is in the alarm overload state, the following events occur:

•

•

•

•

Note

Examples

The following example enables detection of alarm overload:

WAE(config)# alarm overload-detect enable

The following example sets the threshold for triggering the alarm overload at 100 alarms per second:

WAE(config)# alarm overload-detect raise 100

The following example sets the level for clearing the alarm overload at 10 alarms per second:

WAE(config)# alarm overload-detect clear 10

Related Commands

show alarms

(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.

asset tag name

Syntax Description

Defaults

No default behaviors or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to configure a tag name for the asset tag string on a WAAS device:

WAE(config)# asset tag entitymib

(config) authentication

To specify administrative login authentication and authorization methods for a WAAS device, use the authentication 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] | fail-over server-unreachable | login {local | radius | tacacs | windows-domain} enable [primary | secondary | tertiary| quaternary] | content-request windows-domain disconnected-mode enable}

Syntax Description

configuration	Sets the administrative login authorization (configuration) parameters for the WAAS device.
local	Selects the local database method as a login authorization (configuration) method for the WAAS device.
radius	Selects the RADIUS method as a login authorization (configuration) method for the WAAS device.
tacacs	Selects the TACACS+ method as a login authorization (configuration) method for the WAAS device.
windows-domain	Selects the Windows domain controller method as a login authorization (configuration) method for the WAAS device.
enable	Enables the specified administrative login authorization methods for the WAAS device.
primary	(Optional) Specifies the first method the WAAS device should use for administrative login authorization.
secondary	(Optional) Specifies the second method the WAAS device should use for administrative login authorization if the primary method fails.
tertiary	(Optional) Specifies the third method the WAAS device should use for administrative login authorization if the primary and secondary methods fail.
quaternary	(Optional) Specifies the fourth method the WAAS device should use for administrative login authorization if the primary, secondary, and tertiary methods all fail.
fail-over server-unreachable	Specifies that the WAAS device is to query the secondary authentication database if the primary authentication server is unreachable.
login	Sets the administrative login authentication parameters for the WAAS device.
local	Selects the local database method as an administrative login authentication method for the WAAS device.
radius	Selects the RADIUS method as an administrative login authentication method for the WAAS device.
tacacs	Selects the TACACS+ method as an administrative login authentication method for the WAAS device.
windows-domain	Selects the Windows domain controller method as an administrative login authentication method for the WAAS device.
enable	Enables the selected administrative login authentication methods for the WAAS device.
primary	(Optional) Specifies the first method the WAAS device should use for administrative login authentication.
secondary	(Optional) Specifies the second method the WAAS device should use for administrative login authentication if the primary method fails.
tertiary	(Optional) Specifies the second method the WAAS device should use for administrative login authentication if the primary method fails.
quaternary	(Optional) Specifies the fourth method the WAAS device should use for administrative login authentication if the primary, secondary, and tertiary methods all fail.
content-request	Authenticates a request for content. Note This option is available in the application-accelerator device mode only.
windows-domain	Selects a Windows domain controller for domain server authentication.
disconnected-mode	Authenticates in the disconnected mode.
enable	Enables authentication in the disconnected mode.

Defaults

The local authentication method is enabled by default.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The authentication command configures both the authentication and authorization methods that govern login and configuration access to the WAAS device.

Note

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 commandsuse a remote TACACS+ server to determine the level of user access. 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 commandsuse 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, local 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 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 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.

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.)

Server Redundancy

Authentication servers can be specified with the tacacs host or radius-server host global configurationcommands. 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.

Specifying Windows Domain Login Authentication

You can enable 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 using the windows-domain wins-server global configuration command. (See the "(config) windows-domain" command.)

We recommend that you use the WAAS Central Manager GUI instead of the WAAS CLI to configure Windows domain controller settings. See Chapter 6 of the Cisco Wide Area Application Services Configuration Guide.

Examples

To query the secondary authentication database if the primary authentication server is unreachable, enter the following command. This feature is referred to as the fail-over server-unreachable feature.

WAE(config)# authentication fail-over server-unreachable

If you enable the fail-over server-unreachable feature on the WAAS device, only two login authentication scheme (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 fail-over server-unreachable feature is not enabled on the WAAS device.

WAE(config)# authentication login radius enable primary

WAE(config)# authentication login tacacs enable secondary

WAE(config)# authentication login windows-domain enable tertiary

WAE(config)# authentication login local enable quaternary

Note

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

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.

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 authorization (configuration) methods are specified because the fail-over server-unreachable feature is not enabled on the WAAS device.

WAE(config)# authentication configuration radius enable primary

WAE(config)# authentication configuration tacacs enable secondary

WAE(config)# authentication configuration windows-domain enable tertiary

WAE(config)# authentication configuration local enable quaternary

Note

The following example shows the resulting output of the show authentication command:

WAE# show authentication user

Login Authentication:         Console/Telnet/Ftp/SSH Session

----------------------------- ------------------------------

local                         enabled (primary)

Windows domain 							 enabled

Radius                        disabled

Tacacs+                       disabled

Configuration Authentication: Console/Telnet/Ftp/SSH Session

----------------------------- ------------------------------

local                         enabled (primary)

Radius                        disabled

Tacacs+                       disabled

Related Commands

(config) radius-server

show authentication

show statistics radius

show statistics tacacs

(config) tacacs

windows-domain

(config) windows-domain

(config) auto-register

To enable discovery of a Fast Ethernet or Gigabit Ethernet WAE and its automatic registration with the WAAS Central Manager through 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 [FastEthernetslot/port | GigabitEthernetslot/port]

Syntax Description

Defaults

Automatic registration using DHCP is enabled on a WAE by default.

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Autoregistration automatically configures network settings and registers WAEs with the WAAS Central Manager. On bootup, devices running WAAS software (with the exception of the WAAS Central Manager itself) automatically discover the WAAS Central Manager and register with it. The administrator does not have to do any manual configuration on the device. Once the WAE is registered, the administrator approves the device and configures it remotely using the WAAS Central Manager GUI.

The auto-register enable command allows a Fast Ethernet or Gigabit Ethernet 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.

To assign a static IP address using the interface GigabitEthernet slot/port command, the automatic registration of devices through DHCP must be disabled by using the no auto-register enable command, because automatic registration through DHCP is enabled by default.

For autoregistration to work, you must have a DHCP server that is configured with the hostname of the WAAS Central Manager and that is capable of handling vendor class option 43.

Note

The DHCP server needs to send the vendor class option (option 43) information to the WAAS device in the format for encapsulated vendor-specific options as provided in RFC 2132. The relevant section of RFC 2132, Section 8.4, is reproduced here as follows:

You should encode the encapsulated vendor-specific options field as a sequence of code/length/value fields of syntax identical to that of the DHCP options field with the following exceptions:

1.

2.

3.

In accordance with the RFC standard, the DHCP server needs to send the WAAS Central Manager hostname information in code/length/value format. (Code and length are single octets.) The code for the WAAS Central Manager hostname is 0x01. DHCP server management and configuration are not within the scope of the autoregistration feature.

The WAAS device sends CISCOCDN as the vendor class identifier in option 60 to facilitate device groupings by customers.

Autoregistration DHCP also requires that the following options be present in the DHCP server's offer to be considered valid:

•

•

•

•

•

Interface-level DHCP requires only subnet-mask (option 1) and routers (option 3) for an offer to be considered valid; domain-name (option 15), domain-name-servers (option 6), and host-name (option 12) are optional. All of the above options, with the exception of domain-name-servers (option 6), replace the existing configuration on the system. The domain-name-servers option is added to the existing list of name servers with the restriction of a maximum of eight name servers.

Autoregistration is enabled by default on the first interface of the device. The first interface depends on the WAE model as follows:

•

If you do not have a DHCP server, the device is unable to complete autoregistration and eventually times out. You can disable autoregistration at any time after the device has booted and proceed with manual setup and registration.

Examples

The following example enables autoregistration on GigabitEthernet port 2/0:

WAE(config)# auto-register enable GigabitEthernet 2/0

The following example disables autoregistration on all configured interfaces on the WAE:

WAE(config)# no auto-register enable

Related Commands

show auto-register

show running-config

show startup-config

(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]}

Syntax Description

Defaults

Banner support is disabled by default

Command Modes

global configuration

Usage Guidelines

You can configure the following three types of banners in any device mode:

•

•

•

Note

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

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.

Note

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.

WAE(config)# banner exec

Please type your MOTD messages below and end it with '.' at beginning of line:

(plain text only, no longer than 980 bytes including newline)

This is the EXEC banner.\nUse your WAAS username and password to log in to this WAE.\n

.

Message has 99 characters.

WAE(config)#

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.

Use your password to login.

Cisco Wide Area Application Services Engine

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.

Use your WAAS username and password to log in to this WAE.

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

show banner

(config) bypass

To configure static bypass lists on a WAE, use the bypass global configuration command. To disable the bypass feature (clear the static bypass lists), use the no form of this command.

bypass static {clientip | any-client} {serverip |any-server}

Syntax Description

Defaults

No default behaviors or values

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Using a static bypass allows traffic flows between a configurable set of clients and file servers to bypass handling by the WAE. By configuring static bypass entries on the Edge WAE, you can control traffic interception without modifying the router configuration. Separately, if so desired, IP access lists may be configured on the router to bypass traffic without first redirecting it to the Edge WAE. Typically, the WCCP accept list defines the group of file servers that are cached (and the file servers that are not). Static bypass can be used in rare cases when you want to prevent WAAS from caching a connection from a certain client to a certain file server (or from a certain client to all file servers).

The bypass static command permits traffic from specified sources to bypass the WAE. Wildcards in either the client or server IP addresses are not supported.

Note

Examples

The following example forces traffic from a specified client to a specified server to bypass the WAE:

WAE(config)# bypass static 10.1.17.1 172.16.7.52

The following example forces all traffic destined to a specified server to bypass the WAE:

WAE(config)# bypass static any-client 172.16.7.52

The following example forces all traffic from a specified client to any file server to bypass the WAE:

WAE(config)# bypass static 10.1.17.1 any-server

A static list of source and destination addresses helps to isolate instances of problem-causing clients and servers. To display static configuration list items, use the show bypass list command as follows:

WAE# show bypass list

Client              Server          Entry type

------              ------          ----------

10.1.17.1:0         172.16.7.52:0   static-config

any-client:0        172.16.7.52:0   static-config

10.1.17.2:0         any-server:0    static-config 

Related Commands

show bypass

(config) cdp

To configure the Cisco Discovery Protocol (CDP) options globally on all WAAS device interfaces, use the cdp command in global configuration mode.

cdp{enable | holdtime seconds|timer seconds}

Syntax Description

Defaults

holdtime: 180 seconds

timer: 60 seconds

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

When enabled with the cdp enable command, CDP obtains protocol addresses of neighboring devices and discovers the platform of those devices. It also shows information about the interfaces used by your device. CDP is media- and protocol-independent and runs on Cisco-manufactured equipment.

Use of SNMP with the CDP MIB allows network management applications to learn the device type and the SNMP agent address of neighboring devices and to send SNMP queries to those devices. Cisco Discovery Protocol uses the CISCO-CDP-MIB.

Each device configured for CDP sends periodic messages, known as advertisements, to a multicast address. The cdp timer seconds command specifies the rate at which CDP packets are sent. Each device advertises at least one address at which it can receive SNMP messages. The advertisements also contain Time-To-Live or hold-time information. To set the hold time, use the cdp holdtime seconds command to specify the period of time in seconds that a receiver is to keep CDP packets. Each device also listens to the periodic CDP messages sent by others to learn about neighboring devices.

Examples

In the following example, 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:

WAE(config)# cdp enable

WAE(config)# cdp holdtime 10

WAE(config)# cdp timer 15

Related Commands

(config-if) cdp

clear

show cdp

(config) central-manager

To specify the WAAS Central Manager's 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} | uiport port-num}

Syntax Description

Note

Defaults

The WAAS Central Manager GUI is preconfigured to use port 8443.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The central-manager address global configuration command associates a WAE device with the WAAS Central Manager so that the device can be approved as a part of the WAAS network. After the device is configured with the WAAS Central Manager IP address, it presents a self-signed security certificate and other essential information, such as its IP address or hostname, disk space allocation, and so forth, to the WAAS Central Manager.

If you change the WAAS Central Manager GUI port number, the Centralized Management System (CMS) service is automatically restarted on the WAAS Central Manager if the cms service has been enabled on the WAAS Central Manager by entering the cms enable global configuration command on the WAAS Central Manager.

Configuring Devices Inside a NAT

In a WAAS network, there are two methods for a WAAS device that is registered with the WAAS Central Manager (WAEs or a standby WAAS Central Manager) to obtain configuration information from the primary WAAS Central Manager. The primary method is for the device to periodically poll the primary WAAS Central Manager on port 443 to request a configuration update. You cannot configure this port number. The backup method is when the WAAS Central Manager pushes configuration updates to a registered device as soon as possible by issuing a notification to the registered device on port 443. This method allows changes to take effect in a timelier manner. You cannot configure this port number even when the backup method is being used. WAAS networks do not work reliably if devices registered with the WAAS Central Manager are unable to poll the WAAS Central Manager for configuration updates.

All of the above methods become complex in the presence of Network Address Translation (NAT) firewalls. When a WAAS device (WAEs at the edge of the network and the primary or standby WAAS Central Managers) is inside a NAT firewall, those devices that are inside the same NAT use one IP address (the inside local IP address) to access the device, and those devices that are outside the NAT use a different IP address (the inside global IP address) to access the device. A centrally managed device advertises only its inside local IP address to the WAAS Central Manager. All other devices inside the NAT use the inside local IP address to contact the centrally managed device that resides inside the NAT. A device that is not inside the same NAT as the centrally managed device is not able to contact it without special configuration.

If the primary WAAS Central Manager is inside a NAT, you can allow a device outside the NAT to poll it for getUpdate requests by configuring a static translation (inside global IP address) for the WAAS Central Manager's inside local IP address on its NAT, and using this address, rather than the WAAS Central Manager's inside local IP address, in the central-manager addressip-address global configuration command when you register the device to the WAAS Central Manager. If a WAAS device is inside a NAT and the WAAS Central Manager is outside the NAT, you can allow the WAAS device to poll for getUpdate requests by configuring a static translation (inside global IP address) for the WAAS device's inside local address on its NAT and specifying this address in the Use IP Address field under the NAT Configuration heading in the Device Activation window.

Note

Standby WAAS Central Managers

The Cisco WAAS software implements a standby WAAS Central Manager. This process allows you to maintain a copy of the WAAS network configuration. If the primary WAAS Central Manager fails, the standby can be used to replace the primary.

For interoperability, when a standby WAAS Central Manager is used, it must be at the same software version as the primary WAAS Central Manager to maintain the full WAAS Central Manager configuration. Otherwise, the standby WAAS Central Manager detects this status and does not process any configuration updates that it receives from the primary WAAS Central Manager until the problem is corrected.

Note

Switching a WAAS Central Manager from Warm Standby to Primary

If your primary WAAS Central Manager becomes inoperable, you can manually reconfigure one of your warm standby WAAS Central Managers to be the primary WAAS Central Manager. Configure the new role by using the global configuration central-manager role primary command as follows:

WAE# configure

WAE(config)# central-manager role primary

This command changes the role from standby to primary and restarts the management service to recognize the change.

Caution

If you switch a warm standby WAAS Central Manager to primary while your primary WAAS Central Manager is still online and active, both WAAS Central Managers detect each other, automatically shut themselves down, and disable management services. The WAAS Central Managers are switched to halted, which is automatically saved in flash memory. For information about how to return halted WAAS Central Managers to an online status, see the Cisco Wide Area Application Services Configuration Guide.

Caution

When you switch a WAAS Central Manager from primary to standby, the configuration on the Central Manager is erased. The Central Manager, after becoming a standby, will begin replicating its configuration information from whichever Central Manager is now the primary. If standby and primary units are not synchronized before switching roles, important configuration information can be lost. Before you use this command, see the Cisco Wide Area Application Services Configuration Guide.

Examples

The following example specifies that the WAAS device named waas-cm is to function as the primary WAAS Central Manager for the WAAS network:

waas-cm(config)# central-manager role primary

The following example specifies 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.

WAE(config)# central-manager address 10.1.1.1

The following example configures a new GUI port to access the WAAS Central Manager GUI:

WAE(config)# central-manager ui port 8550

The following example configures the WAAS Central Manager as the standby WAAS Central Manager:

WAE(config)# central-manager role standby

Switching CDM to standby will cause  all configuration settings made on this CDM to be 
lost.

Please confirm you want to continue  [no]?yes

Restarting CMS services

(config) clock

To set the summer daylight savings time and time zone for display purposes, use the clockglobal configuration command. To disable this function, use the no form of this command.

clock {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}} | timezone {timezone hoursoffset minutesoffset}}

Syntax Description

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

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 clockset EXEC command. The UTC and local time are displayed with the show clock detail EXEC command.

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]).

WAE(config)# clock timezone timezone 0 0

Note

Examples

The following example specifies the local time zone as Pacific Standard Time with an offset of 8 hours behind UTC:

WAE(config)# clock timezone US/Pacific -8 0

The following example negates the time zone setting on the WAAS device:

WAE(config)# no clock timezone

The following example configures daylight saving time:

WAE(config)# clock summertime US/Pacific date 10 October 2005 23:59 29 April 2006 23:59 60

Related Commands

clock

show clock

(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 {databasemaintenance {full {enable | scheduleweekdayattime} | regular {enable | scheduleweekdayattime}} | enable | rpc timeout {connection5-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

incoming wait: 30 seconds

transfer: 300 seconds

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

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.

Examples

The following example schedules a regular (reindexing) maintenance routine to start every Friday at 11:00 p.m on the WAAS device:

WAE(config)# cms database maintenance regular schedule Fri at 23:00

The following example shows how to enable the CMS process on a WAAS device:

WAE(config)# cms enable

Generating new RPC certificate/key pair

Restarting RPC services

Creating database backup file emerg-debug-db-01-25-2006-15-31.dump

Registering Wide Area Central Manager...

Registration complete.

Please preserve running configuration using 'copy running-config startup-config'.

Otherwise management service will not be started on reload and node will be shown

'offline' in Wide Area Central Manager UI.

management services enabled

Related Commands

cms

show cms

(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 | central-manager}

Syntax Description

Defaults

The default device operation mode is application-accelerator.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

You must deploy the WAAS Central Manager on a dedicated appliance. In the WAAS 4.0 software release, the device mode feature was added, which allows you to deploy a WAAS device as either a WAAS Central Manager or a WAE. Because you must deploy a WAAS Central Manager on a dedicated appliance, a WAAS device can operate in one device mode only: either in central-manager mode or application-accelerator mode. The set of WAAS CLI commands that are available vary based on the device mode of the WAAS device.

Note

By default, a WAAS device uses the application-accelerator mode, which makes it operate as a Wide Area Application Engine (WAE). Before you configure network settings for your WAAS Central Managers using the WAAS CLI, you must change the device mode to central-manager.

After you have changed the device mode to central-manager, use the cms enable global configuration command to enable WAAS network-related applications and services. Use the no form of this command to disable the WAAS network.

You cannot configure the WAE network module (any of the NME-WAE family of devices) as a Central Manger.

You can configure an inline WAE as a Central Manager, but the functionality of the inline feature will not be available.

Examples

To specify central manager as the device mode of a WAAS device, enter the following command from global configuration mode:

WAE(config)# device mode central-manager

To specify application accelerator as the device mode of a WAAS device, enter the following command from global configuration mode:

WAE(config)# device mode application-accelerator

To change the device mode from central-manager to application-accelerator, you must first use the cms deregister force command in EXEC mode to disable the Centralized Management System on the Central Manager, and then use the device mode command in global configuration mode, as shown in the following example:

WAE# cms deregister force

WAE(config)# device mode application-accelerator

WAE# copy running-config startup-config

Related Commands

show device-mode

(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 diskxxshutdown [force]

Syntax Description

Defaults

Disks enabled

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

This command replaces the disk mark EXEC mode command.

This command is not available on the WAE-7341 and WAE-7371 models. Instead, use the disk disk-name diskxx replace EXEC mode command.

Logical Disk Handling with RAID-1

RAID-1 is implemented in WAAS as a software feature. A RAID-1 WAAS device can use two disk drives to increase reliability. RAID-1 provides disk mirroring (data is written redundantly to two or more drives). The goal is higher reliability through redundancy. With RAID-1, file system write performance may be affected because each disk write must be executed against two disk drives. RAID-1 (mirroring) is used for all file systems on the RAID-1 device. This setup ensures reliable execution of the software in all cases.

Note

Hot Swap for WAE-612, WAE-7326, WAE-7341, and WAE-7371 Disk Drives

This release of WAAS supports hot swap functionality for both failed disk replacement and scheduled disk maintenance. On the WAE-612 and WAE-7326, use the disk disk-name diskxx shutdown global configuration command to manually shut down a disk for scheduled disk maintenance. On the WAE-7341 and WAE-7371, use the disk disk-name diskxx replace EXEC command to manually shut down a disk for scheduled disk maintenance. (For the schedule disk maintenance procedure, see the Cisco Wide Area Application Services Configuration Guide, Chapter 14.)

You must wait for the disk to be completely shut down before you physically remove the disk from the WAE. When the RAID removal process is complete, WAAS generates a disk failure alarm and trap. In addition, a syslog ERROR message is logged.

If the software removes a failed disk during the RAID rebuild process, a RAID rebuild failure alarm is generated. If you administratively shut down the disk during the RAID rebuild process, a RAID rebuild abort alarm is generated instead.

If the removal event occurs while the RAID is in the rebuild process, the RAID removal process may take up to one minute before it is successful. The exact duration of this process depends on the size of the disk.

Automatic Failed Disk Handling for RAID-1

The disk hot swap functionality automatically disables a failed disk if the system detects one critical disk alarm. The software will remove the failed disk automatically regardless of the setting for disk error-handling.

Replacing a Failed Disk

To administratively disable disks for removal, use the disk disk-name command in global configuration mode. To administratively reenable disks after replacement, use the no form of this command.

When a disk is manually shutdown, it remains shutdown until you enter the no disk disk-name diskxx shutdown command.

For RAID-1 devices, you may replace a disk that was previously identified as a bad disk by using the disk disk-name diskxx shutdown force command in global configuration mode to manually override the bad status.

Disk Information

To identify which disks have been identified as failed or bad, use the show disks failed-disk-id EXEC command. Do not reinsert any disk with a serial number shown in this list.

Note

Related Commands

(config) disk error-handling

(config) disk logical shutdown

disk

show disks

(config) disk encrypt

To enable disk encryption, use the disk encrypt enable global configuration command. To disable disk encryption, use the no form of this command.

disk encryptenable

Syntax Description

Defaults

Disk encryption is disabled by default.

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

The disk encryption feature addresses the need to securely protect sensitive information that flows through deployed WAAS systems and that is stored in WAAS persistent storage. Disk encryption includes two aspects: the actual data encryption on the WAE disk and the encryption key storage and management.

When you enable disk encryption, all data in WAAS persistent storage will be encrypted. The encryption key for unlocking the encrypted data is stored on the Central Manager, and key management is handled by the Central Manager. When you reboot the WAE after configuring disk encryption, the WAE retrieves the key from the Central Manager, allowing normal access to the data that is stored in WAAS persistent storage.

Disk encryption requirements are as follows:

•

•

•

•

After you reboot your WAE, the encryption partitions are created using the new key, and any previously existing data is removed from the partition.

Any change to the disk encryption configuration, whether to enable or disable encryption, causes the disk to clear its cache. This feature protects sensitive customer data from being decrypted and accessed should the WAE ever be stolen.

If you enable disk encryption and then downgrade to a software version that does not support this feature, you cannot use the disk partitions. In such cases, you must delete the disk partitions after you downgrade.

To enable or disable disk encryption, use the disk encrypt global configuration command. When you enable or disable disk encryption, the file system is reinitialized during the first subsequent reboot. Reinitialization may take from ten minutes to several hours, depending on the size of the disk partitions. During this time, the WAE is accessible, but it does not provide any services.

If you change the Central Manager IP address, or if you relocate the Central Manager, or replace one Central Manager with another Central Manager that has not copied over all the information from the original Central Manager, and you reload the WAE when disk encryption is enabled, the WAE file system cannot complete the reinitialization process or obtain the encryption key from the Central Manager.

If the WAE fails to obtain the encryption key, disable disk encryption by using the disk encrypt disable global configuration command from the CLI, and reload the WAE. Ensure connectivity to the Central Manager before you enable disk encryption and reload the WAE. This process clears the disk cache.

To view the encryption status details, use the show disks details EXEC command. While the file system is initializing, show disks details displays the following message: "System initialization is not finished, please wait..." You may also view the disk encryption status, whether it is enabled or disabled, in the Central Manager GUI, Device Home window.

Related Commands

disk

show disks

(config) disk error-handling

To configure how disk errors are handled and to define a disk error-handling threshold on a WAAS device, use the disk global configuration command. Use the no form of this command to return to the default error-handling threshold.

disk error-handling {reload | remap | thresholdnumber}

Syntax Description

Defaults

error-handling threshold number: 10

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

If you have a two-drive system, the RAID software protects the SYSFS from single-drive failures and prevents applications from seeing I/O errors. With this configuration, error handling need not be specified. For all other configurations, error handling should be specified.

To operate properly, the WAAS device must have a disk drive named disk00. The WAAS device must also contain a disk drive that contains the first SYSFS (system file system) partition. The SYSFS partition is used to store log files, including system logs and internal debugging logs. It may also be used to store image files and configuration files on a WAAS device. Disk00 always contains the SYSFS partition. When software RAID is applied, the SYSFS partitions are contained on both disk00 and disk01. In either case, the disk00 disk and the disk that contains the first SYSFS partition are called critical drives and are required for proper operation of the WAAS device.

When a WAE is booted and a critical disk drive is not detected at system startup time, the WAAS device runs at a degraded state. If one of the critical disk drives becomes inoperable at run time, the WAAS device can exhibit symptoms such as the applications malfunctioning or failing, or the WAAS device can stop responding. You must monitor the critical disk drives on a WAAS device and report any disk drive errors to Cisco TAC.

With a WAAS device, a disk device error is defined as any of the following events:

•

•

•

The disk status is recorded in Flash memory (nonvolatile storage). When an error occurs on the disk drive of a WAAS device, a message is written to the system log (syslog) if the SYSFS partition is still intact, and an SNMP trap is generated if SNMP is configured on the WAAS device.

Specifying the Disk Error-Handling Threshold

You can define a disk device error-handling threshold on the WAAS device. If the number of disk device errors reaches the specified threshold, the corresponding disk device is automatically marked as bad. By default, this threshold is set to 10. The device does not stop using the bad disk device immediately; it stops using the bad disk drive after the next reboot.

To change the default threshold, use the disk error-handling threshold global configuration command. Specify 0 if you never want the disk drive to be marked as bad.

If the specified threshold is exceeded, the WAAS device either records this event or reboots. If the bad disk drive is a critical disk drive, and the automatic reload feature (disk error-handling reload command) is enabled, then the WAAS software marks the disk drive as bad, and the WAAS device is automatically reloaded. After the WAAS device is reloaded, a syslog message and an SNMP trap are generated.

By default, the automatic reload feature is disabled on a WAAS device. To enable the automatic reload feature, use the disk error-handling reload global configuration command. After enabling the automatic reload feature, use the no disk error-handling reload global configuration command to disable it.

Examples

In the following example, an administrator configures five disk drive errors for a particular disk drive (for example, disk00) as the maximum number of errors allowed before the disk drive is automatically marked as bad:

WAE(config)# disk error-handling threshold 5

Related Commands

disk

show disks

(config) disk logical shutdown

To shutdown 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.

disk logical shutdown

Syntax Description

Defaults

The RAID-5 array is configured by default.

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

This command is supported on WAE-7341 and WAE-7371 models only.

Use this command to operate the WAE-7341 or WAE-7371 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.

(config) egress-method

To configure the egress method for intercepted connections, use the egress-method global configuration command.

egress-method {ip-forwarding | negotiated-return} intercept-method wccp

Syntax Description

Defaults

The default egress method is IP forwarding.

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

WCCP interception mode supports two egress configuration options: IP forwarding and negotiated return. Negotiated return supports WCCP GRE as the WCCP egress method.

WCCP GRE packet return allows you to place WAEs on the same VLAN or subnet as clients and servers, a topology that is not allowed when using the IP forwarding egress method. For optimized flows, WCCP GRE packet return also provides "best effort" support for redundant routers and router load balancing.

When you configure WCCP GRE as the egress method, WAAS makes a best effort to maintain the original router selection when router load balancing is used in the network. WAAS applies the following logic in its router selection for WCCP GRE:

•

•

Negotiated return supports WCCP GRE as the only WCCP egress method. When WCCP negotiates WCCP L2 return, the WAE defaults to using IP forwarding as the egress method. You do not receive any notification if the negotiated egress method defaults to IP forwarding; however, a syslog message is generated if such a case occurs.

The default egress method is IP forwarding. If you do not configure the negotiated-return option, IP forwarding is used.

WCCP bypass flows, however, use the WCCP negotiated return method and not IP forwarding, regardless of the CLI configuration.

Note

Examples

To configure the egress method for WCCP interception mode from the Central Manager GUI, choose Devices > Devices > Interception > Egress Methods.

To configure the interception and egress method for WCCP GRE packet return from the CLI, use the egress-method global configuration command, as follows:

WAE(config)# egress-method negotiated-return intercept-method wccp 

To configure the interception and egress method for IP forwarding from the CLI, use the egress-method global configuration command, as follows:

WAE(config)# egress-method ip-forwarding intercept-method wccp 

To view the egress method that is configured and that is being used on a particular WAE, use the show egress-methods EXEC command or the show tfo egress-methods connection EXEC command.

Related Commands

show egress-methods

show tfo egress-methods connection

(config) wccp tcp-promiscuous

(config) end

To exit global configuration mode, use the end global configuration command.

end

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the endcommand to exit global configuration mode after completing any changes to the running configuration. To save new configurations to NVRAM, use the write command.

The Ctrl-Z command also exits global configuration mode.

Examples

The following example shows how to exit global configuration mode on a WAAS device:

WAE(config)# end

WAE#

Related Commands

(config) exit

(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.

exec-timeout timeout

Syntax Description

Defaults

The default is 15 minutes.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

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 configures a timeout of 100 minutes:

WAE(config)# exec-timeout 100

The following example negates the configured timeout of 100 minutes and reverts to the default value of 15 minutes:

WAE(config)# no exec-timeout

Related Commands

(config) telnet enable

(config) exit

To terminate global configuration mode and return to the privileged-level EXEC mode, use the exit command.

exit

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

All modes

Device Modes

application-accelerator

central-manager

Usage Guidelines

This command is equivalent to the Ctrl-Z or theendcommand.

Examples

The following example terminates global configuration mode and returns to the privileged-level EXEC mode:

WAE(config)# exit

WAE#

Related Commands

(config) end

(config) external-ip

To configure up to eight external Network Address Translation (NAT) IP addresses on a WAE, use the external-ip global configuration command. To remove the NAT IP addresses, use the no form of this command.

external-ip ip-addresses

Syntax Description

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use this command to configure up to eight NAT IP addresses on a WAE to allow the router to translate up to eight internal addresses to registered unique addresses and translate external registered addresses to addresses that are unique to the private network.

In a WAAS network, there are two methods for a WAE that is registered with a WAAS Central Manager to obtain configuration information from the primary WAAS Central Manager. The primary method is for the device to periodically poll the primary WAAS Central Manager on port 443 to request a configuration update. You cannot configure this port number. The backup method is when the WAAS Central Manager pushes configuration updates to a registered device as soon as possible by issuing a notification to the registered device on port 443. This method allows changes to take effect in a more timely manner. You cannot configure this port number even when the backup method is being used. WAAS networks do not work reliably if devices registered with the WAAS Central Manager are unable to poll the WAAS Central Manager for configuration updates.

When a WAAS device (WAEs at the edge of the network and the primary or standby WAAS Central Managers) is inside a NAT firewall, those devices that are inside the same NAT use one IP address (the inside local IP address) to access the device and those devices that are outside the NAT use a different IP address (the NAT IP address or inside global IP address) to access the device. A centrally managed device advertises only its inside local IP address to the WAAS Central Manager. All other devices inside the NAT use the inside local IP address to contact the centrally managed device that resides inside the NAT. A device that is not inside the same NAT as the centrally managed device cannot contact it without a special configuration.

If the primary WAAS Central Manager is inside a NAT, you can allow a WAAS device outside the NAT to poll it for getUpdate requests by configuring a static translation (NAT IP address or inside global IP address) for the WAAS Central Manager's inside local IP address on its NAT, and using this address, rather than the WAAS Central Manager's inside local IP address in the central manager address ip-address global configuration command when you register the WAAS device to the WAAS Central Manager. If a WAAS device is inside a NAT and the WAAS Central Manager is outside the NAT, you can allow the WAAS device to poll for getUpdate requests by configuring a static translation (NAT IP address or inside global IP address) for the WAE inside local address on its NAT.

Note

Examples

The following example configures four external NAT IP addresses on a WAAS device:

WAE(config)# external-ip 192.168.43.1 192.168.43.2 192.168.43.3 192.168.43.4

Related Commands

(config) interface

(config) ip

(config-if) ip

(config) flow monitor

To enable network traffic flow monitoring and to register the WAE with the tcpstat-v1 collector for traffic analysis, 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}

Syntax Description

Defaults

The default configuration has no host address configured and the feature is disabled.

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

For procedures to configure flow monitoring on the WAE, see the Cisco Wide Area Application Services Configuration Guide, Chapter 15.

For information about using the NetQoS SuperAgent console and configuring NetQoS SuperAgent entities, go to the following website:

(config) help

To obtain online help for the command-line interface, use the help global configuration command.

help

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC and global configuration

Device Modes

application-accelerator

central-manager

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 back up until entering a ? shows the available options.

Two styles of help are provided:

•

•

Examples

The following example shows the output of the help global configuration command:

WAE# configure

WAE(config)# help

Help may be requested at any point in a command by entering a question mark '?'. If 
nothing matches, the help list will be empty and you must backup until entering a '?' 
shows the available options.

Two styles of help are provided:

1. Full help is available when you are ready to enter a command argument.

2. Partial help is provided when an abbreviated argument is entered.

The following example shows how to use full help to see what WCCP command arguments are available:

WAE# configure

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

  slow-start       accept load in slow-start mode

  tcp-promiscuous  TCP promiscuous mode service

  version          WCCP Version Number

The following example shows how to use partial help to determine the syntax of a WCCP argument:

WAE(config)# wccp tcp ?

  mask             Specify mask used for CE assignment

  router-list-num  Router list number

(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.

hostname name

Syntax Description

Defaults

The default hostname is the model number of the WAAS device (for example WAE-511, WAE-611, or WAE-7326).

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

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 changes the hostname of the WAAS device to sandbox.

WAE-511(config)# hostname sandbox

Sandbox(config)#

The following example removes the hostname.

Sandbox(config)# no hostname

WAE-511(config)#

Related Commands

dnslookup

(config) ip

(config-if) ip

show hosts

(config) inetd

To enable FTP and RCP services on a WAAS device, use theinetd enable global configuration command. To disable these same services, use the no form of this command.

inetd enable {ftp | rcp}

Syntax Description

Defaults

FTP is enabled; RCP is disabled.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Inetd (an Internet daemon pronounced eye net dee) 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 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 enables an FTP service session on the WAAS device:

WAE(config)# inetd enable ftp

The following example disables FTP services:

WAE(config)# no inetd enable ftp

Related Commands

show inetd

(config) interface

To configure a Gigabit Ethernet, InlineGroup, port-channel, orstandbyinterface, 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 {1 | 2} | description text | full-duplex | half-duplex | ip {access-group {acl-num | acl_name} {in | out} | address {ip_address netmask [secondary] | dhcp [client-ididhostnamename | hostnamenameclient-idid]}} | mtu mtusize |shutdown | standby grpnumber [priority priority]]

interface InlineGroup slot/grpnumber [autosense | bandwidth {10 | 100 | 1000} | failover timeout {1 | 3 | 5} | full-duplex | half-duplex | inline [vlan {all | native | vlan_list}] | shutdown]

interfacePortChannel {1 | 2} [description text | ip {access-group {acl-num | acl_name} {in | out} | addressip-addressnetmask} | shutdown]

interface Standby grpnumber {description text | errorsmax-error-number | ipip_address | no {description text | errorsmax-error-number | ipip_address | shutdown}| shutdown}

Syntax Description

GigabitEthernet	Selects a Gigabit Ethernet interface to configure.
slot/port	Slot and port number for the selected interface. The slot range is 0-2; the port range is 0-3. The slot number and port number are separated with a forward slash character (/).
autosense	(Optional) Sets the GigabitEthernet interface to automatically sense the interface speed.
bandwidth	(Optional) Sets the bandwidth of the specified interface.
10	Sets the bandwidth of the interface to 10 megabits per second (Mbps).
100	Sets the bandwidth of the interface to 100 Mbps.
1000	Sets the bandwidth of the interface to 1000 Mbps. This option is not available on all ports and is the same as autosense.
cdp enable	(Optional) Enables Cisco Discovery Protocol (CDP) on the specified interface.
channel-group	(Optional) Configures the EtherChannel group.
1	Assigns the interface EtherChannel to group 1.
2	Assigns the interface EtherChannel to group 2.
description	Enters a description of the interface.
text	Text describing this interface.
full-duplex	(Optional) Sets the interface to full-duplex operation.
half-duplex	(Optional) Sets the interface to half-duplex operation. Note We strongly recommend that you do not use half-duplex connections on the WAE or on routers, switches, or other devices.
ip	(Optional) Enables IP configuration commands for the interface.
access-group	Configures access control for IP packets on this interface using access control list (ACL).
acl_num	Numeric identifier that identifies the ACL to apply to the current interface. For standard ACLs, the valid range is 1-99; for extended ACLs, the valid range is 100-199.
acl_name	Alphanumeric identifier of up to 30 characters, beginning with a letter that identifies the ACL to apply to the current interface.
in	Applies the specified ACL to inbound packets on the current interface.
out	Applies the specified ACL to outbound packets on the current interface.
address	Sets the interface IP address.
ip-address	IP address of this interface.
netmask	Netmask of this interface.
secondary	(Optional) Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address.
dhcp	(Optional) Sets the IP address to that negotiated over Dynamic Host Configuration Protocol (DHCP).
client-id	(Optional) Specifies the client identifier.
id	Client identifier.
hostname	(Optional) Specifies the hostname.
name	Hostname.
mtu	(Optional) Sets the interface Maximum Transmission Unit (MTU) size.
mtusize	MTU size in bytes (88-1500).
shutdown	(Optional) Shuts down this interface.
standby	(Optional) Sets standby interface configuration commands.
grpnumber	Standby group number (1-4).
priority	(Optional) Sets the priority of an interface for the standby group.
priority	Interface priority for the standby group (0-4294967295).
InlineGroup	Sets the InlineGroup of interfaces to configure.
slot/grpnumber	Slot and inline group number for the selected interface. The group number for the inline feature is either 0 or 1 (each adapter has 2 grouped pairs).
failover	(Optional) Modifies failover parameters.
timeout	Sets the maximum time for the inline group of interfaces to transfer traffic to another port in the group after a failover event.
1	Number of seconds before failover occurs.
3	Number of seconds before failover occurs.
5	Number of seconds before failover occurs.
inline	(Optional) Enables inline interception for an InlineGroup of interfaces.
vlan	(Optional) Modifies the VLAN list parameters.
all	Applies the command to all tagged and untagged packets.
native	Specifies untagged packets.
vlan_list	Comma-separated list of VLAN IDs. Restricts the inline feature to the specified set of VLANs.
PortChannel	Selects the EtherChannel of interfaces to configure.
1	Sets the port-channel interface number to 1.
2	Sets the port-channel interface number to 2.
errors	Specifies the maximum error number.
max-error-number	Maximum number of errors.
ip	Specifies the IP address of the interface.
ip_address	IP address of the interface.

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The interface command contains an option for FibreChannel; however, the FibreChannel interface is not supported for WAAS devices. The interface FibreChannel command is not documented in this Command Reference.

To configure an interface bandwidth on a WAAS device, use the bandwidth interface configuration command. The bandwidth is specified in megabits per second (Mbps). The 1000 Mbps option is not available on all ports. Using this option automatically enables autosense on the interface. You cannot change the interface speed on a WAE-7320 model that has an optical Gigabit Ethernet interface. Gigabit Ethernet interfaces only run at 1000 Mbps for a WAE-7320. For newer models of the WAAS device (for example, the WAE-611 or WAE-7326) that have a Gigabit Ethernet interface over copper, this restriction does not apply; you can configure these Gigabit Ethernet interfaces to run at 10, 100, or 1000 Mbps. On newer WAAS models, the 1000-Mbps setting implies autosense. For example, you cannot configure the Gigabit Ethernet interface to run at 1000 Mbps and half duplex.

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, then 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.

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 both are configured on the same subnet.

Up to four secondary addresses can be assigned to an interface. These addresses become active only after the primary address is configured. 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. In contrast, 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

During the initial configuration of a WAAS device, you have the option of configuring a static IP address for the WAAS device or using 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.

An interface can be enabled for DHCP by using the ip address dhcp [client_id | hostname]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. DHCP servers can be configured to identify the client identifier information and the hostname information that the WAAS device is sending and then send back the specific network settings that are assigned to the WAAS device.

Note

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, port-channel, and Standby interfaces.

Note

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.

Port-Channel (EtherChannel) Interface

EtherChannel for the WAAS software supports the grouping of two same-speed network interfaces into one virtual interface. This grouping allows you to set or remove a virtual interface that consists of the two integrated Gigabit Ethernet interfaces. EtherChannel also provides interoperability with Cisco routers, switches, and other networking devices or hosts supporting EtherChannel, load balancing, and automatic failure detection and recovery based on each interface's current link status.

Note

InlineGroup Interface

An InlineGroup interface is a logical grouping of a pair of Ethernet ports that are physically contained in the optional 4-port inline network adapter card. The inline network adapter is supported on all WAAS appliance platforms beginning with the WAAS 4.0.7 release. You can have up to two InlineGroup interfaces, which allows for two 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 desired 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).

Note

The following example configures an attribute of an interface with a single CLI command:

WAE(config)# interface GigabitEthernet 1/0 full-duplex 

The following example shows that an interface can be configured in a sequence of CLI commands:

WAE(config)# interface GigabitEthernet 1/0

WAE(config-if)# full-duplex

WAE(config-if)# exit

WAE(config)#

The following example enables a shut down interface:

WAE(config)# no interface GigabitEthernet 1/0 shutdown

The following example creates an EtherChannel. The port channel is port channel 2 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 2 

WAE(config-if)# ip address 10.10.10.10 255.0.0.0

WAE(config-if)# exit 

The following example removes an EtherChannel:

WAE(config)# interface PortChannel 2 

WAE(config-if)# no ip address 10.10.10.10 255.0.0.0

WAE(config-if)# exit

WAE(config)# no interface PortChannel 2 

The following example adds an interface to a channel group:

WAE# configure

WAE(config)# interface GigabitEthernet 1/0

WAE(config-if)# channel-group 2

WAE(config-if)# exit

The following example removes an interface from a channel group:

WAE(config)# interface GigabitEthernet 1/0

WAE(config-if)# no channel-group 2

WAE(config-if)# exit

The following example assigns a secondary IP address on a Gigabit Ethernet interface on a WAAS device using the ip address configuration interface command:

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 configures a description for a Gigabit Ethernet interface:

WAE(config)# interface GigabitEthernet 1/0

WAE(config-if)# description This is a GigabitEthernet interface.

The following example shows a sample output of the show running-config EXEC command:

WAE# show running-config

.

.

.

interface GigabitEthernet 1/0

 description This is an interface to the WAN

 ip address dhcp

 ip address 192.168.1.200 255.255.255.0

 no autosense

 bandwidth 100

 full-duplex

 exit

.

.

.

The following example shows the sample output of the show interface command:

WAE# show interface GigabitEthernet 1/0

Description: This is the interface to the lab

type: Ethernet

.

.

.

Related Commands

show interface

show running-config

show startup-config

(config) ip

To change 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 default-gateway ip-address

ip domain-name name1 name2 name3

ip name-server ip-addresses

ip path-mtu-discovery enable

ip route dest_addrs net_addrs gateway_addrs

Syntax Description

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

To define a default gateway, use the ip default-gateway command. Only one default gateway can be configured. 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. Up to three domain names can be entered. 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.

The WAAS device appends the configured domain name to any IP hostname that does not contain a domain name. The appended name is resolved by the DNS server and then added to the host table. The WAAS device must have at least one domain name server specified for hostname resolution to work correctly.

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-servercommand to point the WAAS device to a specific DNS server. You can configure up to eight 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 enabled. 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.

The WAAS software supports IP Path MTU Discovery, as defined in RFC 1191. When enabled, Path MTU Discovery discovers the largest IP packet size allowable between the various links along the forwarding path and automatically sets the correct value for the packet size. By using the largest MTU that the links will bear, the sending device can minimize the number of packets that it must send.

Note

IP Path MTU Discovery is initiated by the sending device. If a server does not support IP Path MTU Discovery, the receiving device will have no mechanism available to avoid fragmenting datagrams generated by the server.

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 configures a default gateway for the WAAS device:

WAE(config)# ip default-gateway 192.168.7.18

The following example disables the default gateway:

WAE(config)# no ip default-gateway

The following example configures a static IP route for the WAAS device:

WAE(config)# ip route 172.16.227.128 255.255.255.0 172.16.227.250

The following example negates the static IP route:

WAE(config)# no ip route 172.16.227.128 255.255.255.0 172.16.227.250

The following example configures a default domain name for the WAAS device:

WAE(config)# ip domain-name cisco.com

The following example negates the default domain name for the WAAS device:

WAE(config)# no ip domain-name

The following example configures a name server for the WAAS device:

WAE(config)# ip name-server 10.11.12.13

The following example disables the name server for the WAAS device:

WAE(config)# no ip name-server 10.11.12.13

Related Commands

show ip routes

(config) ip access-list

To create and modify access lists on a WAAS device for controlling access to interfaces or applications, use the ip access-list global configuration commands. To disable an access list, use the no form of the command.

ip access-list {standard | extended} {acl-name | acl-num}

Syntax Description

WAE(config-ext-nacl)#

Defaults

An access list drops all packets unless you configure at least one permit entry.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use access lists to control access to specific applications or interfaces on a WAAS device. An access control list consists of one or more condition entries that specify the kind of packets that the WAAS device will drop or accept for further processing. The WAAS device applies each entry in the order in which it occurs in the access list, which by default is the order in which you configured the entry.

Note

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, enter exit at the ACL configuration mode prompt.

To create an entry, use a 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. Therefore, you must include at least one permit entry to create a valid access list.

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.

WAE(config)# ip access-list standard test

WAE(config-std-nacl)# exit

WAE(config)# ip access-list extended test2

WAE(config-ext-nacl)#

Examples

The following commands 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 limits host administrative access using SSH:

WAE(config)# ip access-list extended example

WAE(config-ext-nacl)# permit tcp any any eq www

WAE(config-ext-nacl)# permit tcp host 10.1.1.5 any eq ssh

WAE(config-ext-nacl)# exit

The following commands activate the access list for an interface:

WAE(config)# interface gigabitethernet 1/0

WAE(config-if)# ip access-group example in

WAE(config-if)# exit

The following example shows how this configuration appears when you enter the show running-configuration command:

...

!

interface GigabitEthernet 1/0

 ip address 10.1.1.50 255.255.0.0

 ip access-group example in

 exit

. . .

ip access-list extended example

 permit tcp any any eq www

 permit tcp host 10.1.1.5 any eq ssh

 exit

. . .

Related Commands

clear

(config-if) ip access-group

show ip access-list

(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 the command.

kerberos {local-realmkerberos-realm | realm{dns-domain | host} kerberos-realm | server kerberos-realm {hostname | ip-address} [port-number]}

Note

Syntax Description

local-realm	Displays the default realm for WAAS. Configures a switch to authenticate users defined in the Kerberos database.
kerberos-realm	IP address or name (in UPPERCASE letters) of the Kerberos realm. Default value is a NULL string.
realm	Maps a host name or DNS domain name to a Kerberos realm.
dns-domain	DNS domain name to map to Kerberos realm. Note The name must begin with a leading dot (.).
host	Host IP address or name to map to Kerberos host realm.
server	Specifies the Key Distribution Center (KDC) to use in a given Kerberos realm and, optionally, the port number the KDC is monitoring.
hostname	Name of the host running the KDC.
ip-address	IP address of the host running the KDC.
port-number	(Optional) Number of the port on the KDC server.

Defaults

kerberos-realm: NULL string

port-number: 88

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

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.

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.

The kerberos command modifies the krb5.conf file.

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.

WAE(config)# kerberos ?

  local-realm  Set local realm name

  realm        Add domain to realm mapping

  server       Add realm to host mapping

WAE(config)# kerberos local-realm WAE.ABC.COM

WAE(config)# kerberos realm wae.abc.com WAE.ABC.COM

WAE(config)# kerberos server wae.abc.com 10.10.192.50

WAE(config)# exit

WAE# show kerberos

  Kerberos Configuration:

  -----------------------

    Local Realm: WAE.ABC.COM

    DNS suffix: wae.abc.com

    Realm for DNS suffix: WAE.ABC.COM

    Name of host running KDC for realm:

    Master KDC: 10.10.192.50

    Port: 88

Related Commands

show kerberos

(config) kernel

To enable access to the kernel debugger (kdb), use the kernel kdb global configuration command. Once enabled, kdb is automatically activated if kernel problems occur, or you can manually activate it from the local console for the WAAS device by pressing the required key sequence. To disable access to the kernel debugger, use the no form of the command.

kernel kdb

Syntax Description

This command has no arguments or keywords.

Defaults

The kernel debugger is disabled by default.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Once enabled, kdb is automatically activated when kernel problems occur. Once activated, all normal functioning of the WAAS device is suspended until kdb is manually deactivated. The kdb prompt looks like this:

[0]kdb>

To deactivate kdb, enter go 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 reboot, 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.

The rationale for disabling the kernel debugger is as follows: 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 enables, and then disables, access to the kernel debugger:

WAE(config)# kernel kdb

WAE(config)# no kernel kdb

(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 the command.

line console carrier-detect

Syntax Description

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Examples

The following example sets the WAAS device to check for the carrier detect signal:

WAE(config)# line console carrier-detect

(config) logging

To configure system logging, use the logging global configuration command. To disable logging functions, use the no form of this command.

logging {console {enable | priority loglevel} | disk {enable | filename filename | priority loglevel | recycle size} | facility facility | host {hostname | ip-address} [port port_num | priorityloglevel | rate-limit message_rate]}

Syntax Description

console	Sets system logging to a console.
enable	Enables system logging to a console.
priority	Sets which priority level messages to send to syslog file.
loglevel	Use one of the following keywords: • alert—Immediate action needed. Priority 1. • critical—Immediate action needed. Priority 2. • debug—Debugging messages. Priority 7. • emergency—System is unusable. Priority 0. • error—Error conditions. Priority 3. • information—Informational messages. Priority 6. • notice—Normal but significant conditions. Priority 5. • warning—Warning conditions. Priority 4.
disk	Sets system logging to a disk file.
enable	Enables system logging to a disk file.
filename	Sets the name of the syslog file.
filename	Name of the syslog file.
recycle	Overwrites syslog.txt when it surpasses the recycle size.
size	Size of syslog file in bytes (1000000-50000000).
facility	Sets facility parameter for syslog messages.
facility	Use one of the following keywords: • auth—Authorization system • daemon—System daemons • kernel—Kernel • local0—Local use • local1—Local use • local2—Local use • local3—Local use • local4—Local use • local5—Local use • local6—Local use • local7—Local use • mail—Mail system • news—USENET news • syslog—Syslog itself • user—User process • uucp—UUCP system
host	Sets system logging to a remote host.
hostname	Hostname of the remote syslog host. Specify up to four remote syslog hosts. Note To specify more than one syslog host, use multiple command lines; specify one host per command.
ip-address	IP address of the remote syslog host. Specify up to four remote syslog hosts. Note To specify more than one syslog host, use multiple command lines; specify one host per command.
port	(Optional) Specifies the port to be used when logging to a host.
port_num	Port to be used when logging to a host. The default port is 514.
priority	(Optional) Sets the priority level for messages when logging messages to a host. The default priority is warning.
loglevel	Use one of the following keywords: • alert—Immediate action needed. Priority 1. • critical—Immediate action needed. Priority 2. • debug—Debugging messages. Priority 7. • emergency—System is unusable. Priority 0. • error—Error conditions. Priority 3. • information—Informational messages. Priority 6. • notice—Normal but significant conditions. Priority 5. • warning—Warning conditions. Priority 4.
rate-limit	(Optional) Sets the rate limit (in messages per second) for sending messages to a host.
message_rate	Rate limit (in messages per second) for sending messages to the host. (0-10000). Setting the rate limit to 0 disables rate limiting.

Defaults

Logging: on

Priority of message for console: warning

Priority of message for disk log file: debug

Priority of message for a host: warning

Log file: /local1/syslog.txt

Log file recycle size: 10,000,000 bytes

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the logging command to set specific parameters of the system log file. System logging is always enabled internally. By default, system logging is enabled on a WAAS device. The system log file is located on the SYSFS partition at /local1/syslog.txt. This file contains authentication entries, privilege levels, and administrative details.

WAAS supports filtering multiple syslog messages for a single failed section on SCSI disks and SATA disks.

To configure the WAAS device to send varying levels of event messages to an external syslog host, use the logging host option. Logging can be configured to send various levels of messages to the console using the logging console priority option.

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.

Configuring System Logging to Remote Syslog Hosts

You can configure a WAAS device to send varying levels of messages to up to four remote syslog hosts. Use the logging host hostname global configuration command as follows:

WAE(config)# [no] logging host hostname [priority priority-code | port port |rate-limit 
limit]

where

•

•

Note

•

•

Examples

In the following example, the WAAS device is configured to send messages that have a priority code of "error" (level 3) to the console:

WAE(config)# logging console priority error

In the following example, the WAAS device is configured to disable sending of messages that have a priority code of "error" (level 3) to the console:

WAE(config)# no logging console error

In the following example, the WAAS device is configured 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

clear

show logging

(config) no

To undo a global configuration command or set its defaults, use the no form of a global configuration command.

no command

Syntax Description

aaa	Unconfigures AAA.
alarm	Unconfigures alarm parameters.
authentication	Unconfigures login authentication and authorization.
bypass	Unconfigures bypass.
cdp	Unconfigures CDP.
clock	Unconfigures the time-of-day clock.
disk	Unconfigures disk-related parameters.
exec-timeout	Unconfigures the exec timeout.
help	Unconfigures assistance for the command-line interface.
hostname	Unconfigures the system's network name.
inetd	Unconfigures FTP, rcp, and TFTP services.
interface	Not supported. Note Although the CLI contains the no interface option, the no command cannot be applied to an interface. The software displays the following error message: Removing of physical interface is not permitted.
ip	Unconfigures IP parameters.
ip access-list	Unconfigures IP access lists.
kerberos	Unconfigures kerberos security options.
kernel	Disables access to the kernel debugger.
line	Unconfigures terminal line settings.
logging	Unconfigures system logging (syslog).
ntp	Unconfigures NTP.
port-channel	Unconfigures port channel global options.
print-services	Unconfigures the parameters for the WAAS print services.
radius-server	Unconfigures RADIUS server parameters.
smb-conf	Unconfigures the Windows domain smb.conf file.
sshd	Unconfigures the parameters for the Secure Shell (SSH) service.
ssh-key-generate	Unconfigures the SSH host key.
tacacs	Unconfigures the TACACS+ parameters.
tcp	Unconfigures the global TCP parameters.
telnet enable	Disables the Telnet service.
username	Unconfigures username authentication.
wccp	Disables WCCP.
windows-domain	Unconfigures Windows domain server parameters.

Defaults

No default behavior or values

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the no command to disable functions or negate a command. If you need to negate a specific argument in a command, such as the default gateway IP address, you must include the specific string in your command, such as no ip default-gateway ip-address.

Examples

The following example the Telnet service is disabled on the WAAS device:

WAE(config)# no telnet enable

(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 server {ip-address | hostname} [ip-addresses | hostnames]

Syntax Description

Defaults

The default NTP version number is 3.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use this command to synchronize the clock on the WAAS device with the specified NTP server. The ntp server command enables NTP servers for timekeeping purposes and is the only way to synchronize the system clock with a time server in WAAS software.

Examples

The following example specifies the NTP server IP address as the time source for a WAAS device. It also removes this configuration.

WAE(config)# ntp 172.16.22.44 

WAE(config)# no ntp 172.16.22.44 

Related Commands

clock

(config) clock

show clock

show ntp

(config) policy-engine application classifier

To create or edit an existing application classifier on a WAE, use the policy-engine application classifier global configuration command. You can use this command to add or modify rules, also known as match conditions, to identify specific types of traffic. You can also use this command to list the classifier's match conditions.

To delete an application classifier or a condition, use the no form of this command.

policy-engine application classifier classifier-name [list |
match {all | dst {host hostname | ip ip_address | port {eq port | range port1 port2}} |
src {host hostname | ip ip_address | port {eq port | range port1 port2}}}]

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Deleting a classifier fails if there are policies using it. When creating a new application classifier or adding an existing application classifier, the WAAS CLI enters into an appropriate submode allowing you to specify one or more conditions. However, if the condition specified matches an already existing condition in the classifier's conditions list, no action is taken. A condition can be deleted by using the no form of this command. When creating a new classifier, you must add at least one condition.

Note

The WAAS software comes with over 150 default application policies that help your WAAS system classify and optimize some of the most common traffic on your network. Before you create a new application policy, we recommend that you review the default policies and modify them as appropriate. It is usually easier to modify an existing policy than to create a new one. For a list of the default applications and classifiers that WAAS will either optimize or pass through based on the policies that come bundled with the system, see the Cisco Wide Area Application Services Configuration Guide.

Note

Related Commands

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map adaptor EPM

To configure the application policy with advanced policy map lists of the EndPoint Mapper (EPM) service on a WAE, use the policy-engine application map adaptor EPM global configuration command. To disable the EPM service in the application policy configuration, use the no form of this command.

policy-engine application map adaptor EPM epm-map{delete line-number| disable line-number | insert {first | last | pos line-number} name app-name{All | classifier classifier-name}{action {optimize {DRE {yes | no} compression {LZ | none}} | full}| pass-through} | disable action {optimize {DRE {yes | no} compression {LZ | none} | full} | pass-through} | list [from line-number[to line-number] | to line-number[from line-number]] | move from line-number to line-number | name app-name{All | classifier classifier-name}{action {optimize {DRE {yes | no} compression {LZ | none}} | full} | pass-through} | disable action {optimize {DRE {yes | no} compression {LZ | none} | full} | pass-through}}

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

EndPoint Mapper (EPM) is a service that dynamically allocates server ports to certain applications. Unlike most applications that always use the same port, applications that rely on the EPM service can be assigned a different port at every request.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map adaptor WAFS transport

To configure application policies with the Wide Area File Services (WAFS) transport option, use the policy-engine application map adaptor WAFS transport global configuration command. To disable the WAFS transport policy map in the application policy configuration, use the no form of this command.

policy-engine application map adaptor WAFS transport {deleteline-number | disableline-number | insert {{first | last} nameapp-name | pos line-number} | list [from line-number | to line-number] | move fromline-number | name app-name}

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

By default, when you enable WAFS, all CIFS traffic going between an Edge WAE and a core cluster is accelerated. Use this command to specify another action (such as optimize) for CIFS traffic traveling between edge and core devices.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map basic delete

To delete a specific basic (static) application policy map from the list of application policy maps on a WAE, use the policy-engine application map basic delete global configuration command.

policy-engine application map basic deletepos

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

A policy map consists of a set of application policies and the order in which they are checked. This command is ignored if the line number specified does not represent a current policy map.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map basic disable

To disable a specific basic (static) application policy map from the list of application policy maps on a WAE, use the policy-engine application map basic disable global configuration command.

policy-engine application map basic disablepos

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

This command is ignored if the line number specified does not represent a current policy map.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic insert

To insert a new basic (static) application policy map to the list of application policy maps on a WAE, use the policy-engine application map basic insert global configuration command.

policy-engine application map basic insert {first | last | pos pos} nameapp-name

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map basic insert global configuration command to insert a new basic (static) application policy map to the list of application policy maps on a WAE.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map basic list

To display a list of basic (static) application policy maps on a WAE, use the policy-engine application map basic list global configuration command.

policy-engine application map basic list [from pos [to pos] | to pos]

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map basic list global configuration command to display a list of basic application policy maps on a WAE.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map basic move

To move the application policy with the basic policy map list based on only L3 or L4 parameters on a WAE, use the policy-engine application map basic global configuration command.

policy-engine application map basic move frompos to pos

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map basic global configuration command to move the application policy with the basic policy map list based on only L3 or L4 parameters on a WAE.

Note

Examples

To move a policy map from line 10 to line 16, enter the following:

WAE(config)# policy-engine application map basic move from 10 to 16

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map basic name

To configure the application policy with the basic policy map name, use the policy-engine application map basic name global configuration command.

policy-engine application map basic name app-name classifier classifier-name {action {optimize {DRE {yescompression {LZ [accelerate {CIFS-adaptor | MS-port-mapper}] | none} | no} | full} | pass-through [accelerate {CIFS-adaptor | MS-port-mapper}]} | disable action {optimize {DRE {yes compression {LZ [accelerate {CIFS-adaptor | MS-port-mapper}] | none} | no} | full} | pass-through [accelerate {CIFS-adaptor | MS-port-mapper}]}}

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map basic name global configuration command to configure the application policy with the basic policy map name.

To view WAFS dynamic accept or deny list entries, use the show policy-engine application dynamic command.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

show policy-engine application

(config) policy-engine application map other optimize DRE

To configure the optimize DRE action on non-classified traffic on a WAE, use the policy-engine application map other optimize DRE global configuration command.

policy-engine application map other optimize DRE {yes | no} compression {LZ | none}

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map other optimize DRE global configuration command to configure the optimize DRE action on non-classified traffic on a WAE.

Note

Examples

To configure the optimize DRE action on non-classified traffic with no compression:

WAE(config)# policy-engine application map other optimize DRE yes compression none

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map other optimize full

To configure the application policy on non-classified traffic with the optimize full action, use the policy-engine application map other optimize full global configuration command.

policy-engine application map other optimize full

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map other optimize full global configuration command to configure the application policy on non-classified traffic with the optimize full action.

Note

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other pass-through

(config) policy-engine application name

(config) policy-engine application map other pass-through

To configure the application policy on nonclassified traffic with the pass-through action on a WAE, use the policy-engine application map other pass-through global configuration command.

policy-engine application map other pass-through

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use the policy-engine application map other pass-through global configuration command to configure the application policy on nonclassified traffic with the pass-through action on a WAE.

Note

Related Commands

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map basic name

(config) policy-engine application map other optimize full

(config) policy-engine application name

To create a new application definition that specifies general information about an application on a WAE, use the policy-engine application name global configuration command.To delete the application definition, use the no form of this command.

policy-engine applicationnameapp-name

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

Use this command to create a new application name that can be used later to gather statistics about an application. Deleting an application name fails if there are policies using this name. Successful deletion clears all statistics that were once associated with this application.

Note

Note

Examples

The following example shows how to create an application definition for the Payroll application:

WAE(config)# policy-engine application name Payroll

Related Commands

(config) policy-engine application classifier

(config) policy-engine application map adaptor EPM

(config) policy-engine application map adaptor WAFS transport

(config) policy-engine application map basic delete

(config) policy-engine application map basic disable

(config) policy-engine application map basic insert

(config) policy-engine application map basic list

(config) policy-engine application map basic move

(config) policy-engine application map basic name

(config) policy-engine application map basic name

(config) policy-engine application map other optimize DRE

(config) policy-engine application map other optimize full

(config) policy-engine application map other pass-through

(config) policy-engine config

To remove application policy configurations or replace application policy configurations with factory defaults on a WAE, use the policy-engine config global configuration command.

policy-engine config {remove-all | restore-predefined}

Syntax Description

Command Modes

global configuration

Device Modes

application-accelerator

Usage Guidelines

This action includes but is not limited to the following:

•

•

•

•

Note

Related Commands

show policy-engine status

(config) port-channel

To configure the port channel load-balancing options on a WAAS device, use the port-channel global configuration command. Use the no form of this command to set load balancing on the port channel to its default method.

port-channel load-balance {dst-ip | dst-mac | round-robin}

Syntax Description

Defaults

Round-robin is the default load-balancing method.

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The port-channel load-balance command configures one of three load-balancing algorithms and provides flexibility in choosing interfaces when an Ethernet frame is sent. The round-robin option allows evenly balanced usage of identical network interfaces in a channel group. Because this command takes effect globally, if two channel groups are configured, they must use the same load-balancing option.

Examples

The following example configures destination IP load balancing on a port channel and then disables it:

WAE(config)# port-channel load-balance dst-ip

WAE(config)# no port-channel load-balance

(config) primary-interface

To configure the primary interface for a WAAS device, use the primary-interface command in global configuration mode.To remove the configured primary interface, use the no form of the command.

primary-interface {GigabitEthernet1-2/port | PortChannel1-2 | Standbygroup_num}

Syntax Description

Defaults

The default primary interface is the Gigabit Ethernet 1/0 interface. If this 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

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

The primary-interface global configuration command permits the administrator to specify the primary interface for theWAAS device.

The primary interface can be changed without disabling the WAAS device. To change the primary interface, reenter the command string and specify a different interface.

Note

Setting the primary interface to be a Standby group does not imply that Standby functionality is available. You must configure relevant 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 on a WAAS device:

WAE(config)# primary-interface GigabitEthernet 1/0

The following example shows how to specify the Gigabit Ethernet slot 2 port 0 as the primary interface on a WAAS device:

WAE(config)# primary-interface GigabitEthernet 2/0

Related Commands

(config) interface

(config) print-services

To enable print services and designate a group name for administrators allowed configuration access on a WAAS device, use the print-services global configuration command. To disable print services on a WAAS device or to clear the administrative group, use the no form of this command.

print-services {enable | admin-group admin-group-name | guest-print enable}

Syntax Description

enable	Enables print services on the WAAS device.
admin-group	Configures a group of administrators with print services configuration privileges.
admin-group-name	Name of the administrative group, up to127 characters. No spaces are allowed.
guest-print enable	Enables the guest print service. Guest printing allows any user to print to the WAAS print server. Note This option is available only in the application-accelerator device mode.

Defaults

By default, print services are disabled and no administrative group is defined (admin-group-name is null).

Command Modes

global configuration

Device Modes

application-accelerator

central-manager

Usage Guidelines

WAAS print services are typically enabled on WAEs residing in branch offices. The WAE acts as a print server and services requests from multiple clients for access to multiple printers. The WAAS print services feature enables administrators to perform the following print-related tasks:

•