Cisco Wide Area Application Services Quick Configuration Guide (Software Version 6.1.1)

Network Configuration Example

The example WAAS network configuration shown in Figure 1 contains one WAAS Central Manager device and two WAEs that will be centrally managed through the WAAS Central Manager device. The WAEs contain Cisco Interface Modules or Cisco WAE Inline Network Adapter cards and are deployed inline between the WAN routers and the clients or servers. Alternately, you can use WCCP interception and position the WAEs off-path.

Figure 1 WAAS Inline Network Configuration

 

---

Note Position the WAEs directly in the traffic path between the router and the clients or file servers. The WAEs intercept traffic directly through the inline interfaces and redirection is not needed.

When you install any inline device, you must follow the cabling requirements described in the hardware installation guide for your WAVE or WAE device.

---

Note We strongly recommend that you do not use half-duplex connections on the WAE or on routers, switches, or other devices. Use of half duplex impedes the system’s ability to improve performance and should not be used. Check each Cisco WAE interface and the port configuration on the adjacent device (router, switch, firewall, WAE) to verify that full duplex is configured.

The WAAS Central Manager must run on a dedicated appliance. You should install the WAAS Central Manager on a dedicated appliance that is located in your data center so that the WAAS Central Manager device is in the same physical location as your data center’s web, file, and application servers.

---

Note You cannot configure the device mode as Central Manager on a WAE network module (NME-WAE) device.

Summary of the Configuration Process

The following steps summarize the tasks that are required to perform a basic configuration of a WAAS network:

1. Configure the basic network settings and define the primary interface and device mode for each of the WAEs by using the setup utility and the WAAS CLI, beginning with the WAAS Central Manager. You are given the choice to run diagnostics in the setup utility to verify the success of your configuration once all settings have been applied. See the “Configuring the WAAS Network” section.

The setup utility includes choosing and enabling an interception method: WCCP or inline. We recommend inline interception for the easiest set up. If you choose WCCP, the setup utility prompts you for a list of intercepting routers and enables TCP promiscuous mode on the WAEs.

2. (Optional) If you are using WCCP interception, configure WCCP Version 2 on the routers as described in the “Configuring WCCP” section. This step is not required if you are using inline mode and WAEs with the Cisco Interface Module or Cisco WAE Inline Network Adapter installed.

3. Access the WAAS Central Manager GUI to manage and monitor your WAAS network. See the “Accessing the WAAS Central Manager GUI” section.

4. Verify that the WAAS application acceleration is working properly. See the “Verifying Application Acceleration” section.

5. Change the password for the predefined superuser account. See the “Changing the Administrator Password” section.

For detailed command syntax information for any of the CLI commands that are mentioned in this document, see the Cisco Wide Area Application Services Command Reference.

Checklist for Configuring a WAAS Network

This section contains the following topics for configuring your WAAS network:

• Network System Parameters
• Setup Utility

Network System Parameters

Table 1 specifies the different parameters and data needed to set up and configure the WAAS network. For your convenience, you can enter your values in the table and refer back to it when configuring the WAAS network.

 

Setup Utility

From release 6.x and later, the setup utility will accept IPv6 address for Interface, Central Manager, Domain Name Server entry and Network Time Protocol settings. You can configure IPv4 only, IPv6 only or dual stack network using the setup utility.

The following restrictions, recommendations, and requirements apply to the WAAS setup utility:

• Designed for basic WAE configuration on new installations only (otherwise the running configuration of the existing system is not reflected in the tool).
• Requires a minimum 25 row x 80 column terminal window for proper display (terminal length, if configured, must be 24).
• For hyper terminal, the emulation should be set to vt100 so that all lines show up properly (input translation should be set to Shift-JIS on the File > Properties menu.
• Console logging should be disabled when executing the setup utility from the CLI to avoid system message flooding on the screen.
• After a restore factory-default, you are encouraged to run the setup utility (and are prompted with the option to do so).

---

Configuring the WAAS Central Manager

To install and configure the WAAS Central Manager device, follow these steps:

---

Step 1 In the data center, unpack and connect the first WAAS device that you want to configure as the WAAS Central Manager device. You must set the port to which the WAE is connected to full duplex. For hardware installation instructions, see the hardware installation guide for your WAVE or WAE device.

Step 2 Power up the first WAAS device in the data center and open a console connection to configure the basic device network settings (see Table 1 ) for the WAE.

---

Note If you are connecting to the WAAS device using a PC as the console, the PC must have terminal emulation software installed. The terminal emulation software should be configured with the following parameters: 9600 baud, 8 data bits, no parity bits, and 1 stop bit.

You must use a console connection rather than a Telnet session for the initial configuration of these basic device network settings on the WAE. Once you have used a console connection to define the device network settings, you can use a Telnet session for subsequent CLI sessions. By default, the Telnet service is enabled on a WAAS device.

Step 3 When a WAAS device starts up, you are prompted to run the first-time setup utility, which you use to set up the basic configuration for the device. When prompted, press Enter and then enter the administrator password, which is default.

The configuration prompt waits several seconds before proceeding with the WAE setup sequence.

If you want to quit the setup utility, you can press Esc at any time. For help, enter the ? key.

---

Note If you do not press Enter in time to enter the basic configuration, you will need to log into the WAAS device through the terminal console and run the setup EXEC CLI command to manually invoke the setup utility. When you log in, the username is admin and the password is default.

Step 4 The default values for the basic configuration of the device are listed. Enter n at the first prompt to change the default settings or, to change a specific parameter, select the index number. You must change the defaults to configure a WAAS Central Manager.

Step 5 Select the Device Mode as prompted. For example, choose central-manager as the device mode that you want to configure on the WAAS device.

---

Note The AppNav Controller device mode option is shown only on WAVE-294/594/694/7541/7571/8541 models and is not applicable for Central Manager configuration.

Step 6 Enter the Time Zone of the device. The number of hours offset from UTC (rounded down to the nearest whole number), and the number of minutes of any partial hour of offset. For example, if your time zone offset is -3:30, then you would set -3 for the hours offset and 30 for the minutes offset.

 

Step 7 Select the Management Interface of the device.

You can accept the default choice (shown in brackets) at a prompt by pressing Enter.

Step 8 Configure Autosense for Management Interface.

---

Note Configuring Autosense is not required if the management interface is a TenGigabitEthernet interface.

Step 9 If you have Dynamic Host Control Protocol enabled in your network, enable DHCP on the WAAS device interface.

---

Note Enabling DHCP is not required if the management interface is a TenGigabitEthernet interface.

Step 10 Select the Management Interface Speed.

---

Note This option is available only if management interface Autosense is disabled. Management interface speed is not applicable if the interface is a TenGigabitEthernet interface.

Step 11 Enter the Management Interface IP Address.

Step 12 Enter the Management Interface IP Mask.

Step 13 Enter the Default Gateway IP Address.

Step 14 Enter the Domain Name Server IP Address.

Step 15 Enter the Domain Names.

Step 16 Enter the Host Name.

Step 17 For the Network Time Protocol (NTP) server, we recommend that you enter the IP address of an NTP server, because clock synchronization between the WAEs in a WAAS network is important.

Step 18 Select the licenses that you purchased.

Step 19 Write down the IP address of the WAAS Central Manager for future reference. You will need it to launch the WAAS Central Manager GUI, which you will use later in the “Accessing the WAAS Central Manager GUI” section.

Press F2 to see all of the configuration, enter d to toggle the defaults display, or enter a number to change a specific parameter.

Figure 2 Central Manager Config

 

 

 

 

Step 20 Enter y when you are ready to accept the final configuration. The device is then visible on the network and it can be pinged.

Step 21 Save the configuration changes to the startup configuration file and reload the system to apply the final configuration.

The system reboots. The WAAS Central Manager configuration that you just configured is loaded on the WAAS device, which is now designated as a WAAS Central Manager.

Step 22 When prompted, enter the administrator username (admin) and password (default) and press Enter.

 

The initial configuration of the WAAS Central Manager is completed. The next step is to initially configure and register the other two WAAS devices (the data center WAE and the branch WAE) with this WAAS Central Manager. See the “Configuring the WAEs for Inline Interception” section for details.

Running Diagnostics

Once your configuration has been applied, you are given the choice to run the diagnostic utility to verify connectivity. The option to run the diagnostic utility appears only if the setup utility was executed using the EXEC CLI command. (See Figure 3.)

---

Note If diagnostics fail because of transient configurations, such as before a DHCP server has completed learning, you can run diagnostics manually using the test self-diagnostics all EXEC CLI command.

Figure 3 Configuration Diagnostics

 

The diagnostic utility tests configuration properties including basic configuration, connectivity, interface link properties, and TFO configuration. (See Figure 4.)

---

Note Invalid IP addresses (Central Manager or WCCP router list) can lead to long delays when testing connectivity.

Figure 4 Diagnostics

 

Configuring the WAEs for Inline Interception

This section describes configuring WAEs that have the Cisco Interface Module or Cisco WAE Inline Network Adapter installed. If you are using WAEs (or WAE network modules) that are using WCCP interception, see the “Configuring WCCP” section.

To install and configure the WAAS WAE devices, and register them with the WAAS Central Manager, follow these steps:

---

Step 1 In the data center, unpack and connect the second WAAS device that you want to configure as the data center WAE in the WAAS network. You must set the port to which the WAE is connected to full duplex. For hardware installation instructions, see the hardware installation guide for the WAE.

---

Note We strongly recommend that you do not use half-duplex connections on the WAE or on routers, switches, or other devices. Use of half duplex impedes the system’s ability to improve performance and should not be used. Check each Cisco WAE interface and the port configuration on the adjacent device (router, switch, firewall, WAE) to verify that full duplex is configured.

Step 2 Power up the designated data center WAE and open a console connection.

Step 3 When a WAAS device starts up, you are prompted to run the first-time setup utility, which you use to set up the basic configuration for the device. When prompted, press Enter and then enter the administrator password, which is default.

The configuration prompt waits several seconds before proceeding with the WAE setup sequence.

If you want to quit the setup utility, you can press Esc at any time.

---

Note If you do not press Enter in time to enter the basic configuration, you will need to log into the WAAS device through the terminal console and run the setup EXEC CLI command to manually invoke the setup utility. When you log in, the username is admin and the password is default.

Step 4 The first step of the setup utility displays a default configuration and allows you to enter ‘y’ to accept the default values, ‘n’ to configure all, or enter a number to change a specific parameter.

If you use the default settings, the setup utility skips configuration of the parameters in the following steps.

Step 5 Enter the required information as prompted by the setup utility (see Table 1 ). For example, choose application-accelerator as the device mode that you want to configure on the WAAS device. You can accept the default choice (shown in brackets) at a prompt by pressing Enter.

---

Note If you want to use AppNav Controller device mode, see the “Configuring an AppNav Controller” section.

Step 6 Choose the interception method. The default method is normally the correct one to choose because it is automatically set to inline if a Cisco WAE Inline Network Adapter is installed, otherwise it is set to WCCP. The AppNav Controller interception method is for WAEs that are operating as WAAS nodes in an AppNav deployment; other AppNav-specific settings must be configured using the Central Manager. Choose other if you want to use PBR interception or redirection from a Cisco Application Control Engine (ACE) or Catalyst 6500 series Content Switching Module (CSM). PBR interception is not supported on an AppNav Controller.

---

Note When using inline interception, we recommend configuring a routable IP address on the Cisco WAE Inline Network Adapter interface. Though it is possible to configure no IP address on the Cisco WAE Inline Network Adapter interface, directed mode operation will not work without an IP address. For more information on using directed mode, see the section “Configuring Directed Mode” in the Cisco Wide Area Application Services Configuration Guide.

Step 7 Choose the interface to configure as the management interface, for communicating with the WAAS Central Manager. With the Cisco WAE Inline Network Adapter, you can choose to share one of the inline interfaces for management traffic or you can use one of the built-in Gigabit Ethernet interfaces (out-of-band management).

When you are prompted for the IP address of the interface, the IP address that you enter is used for the management interface that you chose in this step.

Step 8 If you chose inline as the interception method, when you are prompted to enter the VLAN ID, enter a VLAN ID between 1 and 4094, or if you are not using VLAN tagging, enter none.

If the WAE with the Cisco WAE Inline Network Adapter is present in an 802.1Q VLAN trunk line between a switch and a router, and you are configuring an inline interface with an IP address, you must set the VLAN ID that is to be assigned to traffic that leaves the WAE. The VLAN ID should be set to match the VLAN ID expected by the router.

Continue to answer the questions displayed in the setup utility.

Step 9 If the management interface is a GigabitEthernet interface, then you are prompted to select an inline group to be used for interception, choose the inline group.

Step 10 When you are prompted to choose a license, choose the licenses that you have purchased for use on your WAE. Activating the appropriate licenses is required for various acceleration features to operate. All licenses are not supported on all WAE models.

Step 11 If you chose WCCP as the interception method, the setup utility displays a set of example router configurations for your convenience. These configurations are the same configurations that are described in the “Configuring WCCP on the Routers” section. Press Enter to continue.

Step 12 When finished, the configuration is displayed. Enter d to toggle the defaults display, or enter a number to change a specific parameter. (See Figure 5.)

Figure 5 WAE Config—Inline

 

Enter y to select the configuration. If you choose not to accept the configuration, you have the option to go through the setup questions again and reenter the values. Your previous values are used as the defaults.

Step 13 Once you apply the changes, the configuration is saved automatically and you are given the option to reload the system so that the new configuration will take effect. The option to reload the system appears only when the device mode is changed using the Setup wizard.

---

Note If a Central Manager address has been configured, cms enable is automatically configured by the system (node manager) within 5 minutes after the reboot.

The system reboots and the device is then visible on the network and it can be pinged.

 

If you want to check the current running configuration on the WAE, you can use the show running-config EXEC command.

The initial configuration of the data center WAE is completed. The next step is to initially configure and register the designated branch WAE with the WAAS Central Manager device. Repeat the procedure in this section with the WAE in the branch office; the configuration is identical.

If you are using inline mode for the WAEs, you are finished with network configuration and you can proceed with the “Accessing the WAAS Central Manager GUI” section.

If you are using WCCP interception, the next step is to configure WCCP. For details, see the “Configuring WCCP” section.

Configuring an AppNav Controller

This section describes how to configure a WAAS device as an AppNav Controller.

---

Note AppNav Controller device mode is supported only on WAVE-294/594/694/7541/7571/8541 models. Advanced AppNav configuration is not supported using the setup utility and must be configured using the Central Manager. For more information on Cisco WAAS AppNav, see the “Configuring AppNav” chapter in the Cisco Wide Area Application Services Configuration Guide.

---

Step 1 When prompted by the setup utility for the device mode that you want to configure on the WAAS device, enter 3 to choose AppNav Controller.

Step 2 Reboot the device as prompted by entering y and then y again at the confirmation prompt.

The device restarts. Continue after the device finishes restarting.

Step 3 Rerun the setup utility.

Step 4 The first step of the setup utility again displays a default configuration and allows you to enter ‘y’ to accept the default values, ‘n’ to configure all, or enter a number to change a specific parameter.

If you use the default settings, the setup utility skips configuration of the parameters in the following steps.

Step 5 Choose AppNav Controller as the device mode.

Step 6 Choose the interception method. The default method is normally the correct one to choose. Choose other if you want to use redirection from a Cisco Application Control Engine (ACE) or Catalyst 6500 series Content Switching Module (CSM).

Step 7 Choose the interface to configure as the management interface, for communicating with the WAAS Central Manager. With the Cisco AppNav Controller Interface Module, you can choose to share one of the inline interfaces for management traffic or you can use one of the built-in Gigabit Ethernet interfaces (out-of-band management).

---

Note In AppNav Controller device mode, the last port of the AppNav Controller Interface Module is the default. When an AppNav Controller Interface Module port is chosen, DHCP and Autosense are supported only on 12xGE Copper or Fiber AppNav Controller Interface Modules.

When you are prompted for the IP address of the interface, the IP address that you enter is used for the management interface that you chose in this step.

Continue to answer the questions displayed in the setup utility.

Step 8 When finished, the configuration is displayed. Enter d to toggle the defaults display, or enter a number to change a specific parameter.

Enter y to select the configuration. If you choose not to accept the configuration, you have the option to go through the setup questions again and reenter the values. Your previous values are used as the defaults.

---

Note Advanced AppNav cluster configuration is not supported using the setup utility and must be configured using the Central Manager. For more information on Cisco WAAS AppNav, see the “Configuring AppNav” chapter in the Cisco Wide Area Application Services Configuration Guide.

Step 9 Finish the setup process and save the configuration by pressing Enter.

Step 10 Exit the setup utility by pressing Enter. You are prompted to run the diagnostics. Press y to run the diagnostics or n to exit the setup utility.

The device is visible on the network and it can be pinged.

 

If you want to check the current running configuration on the WAE, you can use the show running-config EXEC command.

The initial configuration of the data center WAE is completed. The next step is to initially configure and register the designated branch WAE with the WAAS Central Manager device. On the WAE in the branch office, repeat the procedure in the “Configuring the WAEs for Inline Interception” section.

If you are using inline mode for the WAEs, you are finished with network configuration and you can proceed with the “Accessing the WAAS Central Manager GUI” section.

If you are using WCCP interception, see the next section for details.

Configuring WCCP

---

Note Do not configure WCCP if you are using inline mode and a WAE with the Cisco WAE Inline Network Adapter installed. With inline mode, traffic is directly intercepted and redirection is unnecessary. Skip to the “Accessing the WAAS Central Manager GUI” section.

If your network configuration is using WCCP instead of inline interception, WCCP provides the method to transparently redirect client requests to a WAE for processing. Figure 6 shows an example WAAS network configuration using WCCP.

Figure 6 Example WCCP Network Configuration

 

To configure basic WCCP, you must enable the WCCP service on at least one router in your network and on your WAEs. It is not necessary to configure all of the available WCCP features or services to get your WAEs up and running.

In this configuration example, because there is a data center WAE and a branch WAE in the WAAS network, you must configure WCCP Version 2 on four devices, as follows:

• Data Center WAE—To configure WCCP on the data center WAE, see the “Configuring WCCP on the WAEs” section.
• Branch WAE—To configure WCCP on the branch WAE, see the “Configuring WCCP on the WAEs” section.
• Data Center Router—To configure WCCP on the data center router, see the “Configuring WCCP on the Routers” section.
• Branch Router—To configure WCCP on the branch router, see the “Configuring WCCP on the Routers” section.

---

Note You must configure these devices to use WCCP Version 2 instead of WCCP Version 1 because WCCP Version 1 supports web traffic (port 80) only. For more information on WCCP configuration, see the Cisco Wide Area Application Services Configuration Guide.

The following WCCP procedures are included in this section:

• Configuring WCCP on the WAEs
• Configuring WCCP on WAAS Network Modules
• Configuring WCCP on the Routers

Configuring WCCP on the WAEs

This section describes configuring WAEs that are using WCCP. If you are using WAEs that have the Cisco WAE Inline Network Adapter installed, see the section “Configuring the WAEs for Inline Interception” section.

---

Note If one of the WAE devices that you are configuring is a network module (NME-WAE) installed in a Cisco access router, you must configure its basic network settings using the access router CLI, not by using the WAAS CLI as described in this section. For details, see the document Configuring Cisco WAAS Network Modules for Cisco Access Routers. For SM-SRE modules, see the document Cisco SRE Service Module Configuration and Installation Guide.

After you configure basic network settings, and open a session to the network module, you can use the procedures in this section to configure other basic settings. The setup utility skips the questions on device mode (only application accelerator can be used) and basic network configuration, which is provided by the router configuration. For basic WCCP configuration, see the section “Configuring WCCP on WAAS Network Modules” section.

To install and configure the WAAS WAE devices with WCCP, and register them with the WAAS Central Manager, follow these steps:

---

Step 1 In the data center, unpack and connect the second WAAS device that you want to configure as the data center WAE in the WAAS network. You must set the port to which the WAE is connected to full duplex. For hardware installation instructions, see the hardware installation guide for the WAE.

---

Note We strongly recommend that you do not use half-duplex connections on the WAE or on routers, switches, or other devices. Use of half duplex impedes the system’s ability to improve performance and should not be used. Check each Cisco WAE interface and the port configuration on the adjacent device (router, switch, firewall, WAE) to verify that full duplex is configured.

Step 2 Power up the designated data center WAE and open a console connection.

Step 3 When a WAAS device starts up, you are prompted to run the first-time setup utility, which you use to set up the basic configuration for the device. When prompted, press Enter and then enter the administrator password, which is default.

The configuration prompt waits several seconds before proceeding with the WAE setup sequence.

If you want to quit the setup utility, you can press Esc at any time.

---

Note If you do not press Enter in time to enter the basic configuration, you will need to log into the WAAS device through the terminal console and run the setup EXEC CLI command to manually invoke the setup utility. When you log in, the username is admin and the password is default.

Step 4 The first step of the setup utility displays a default configuration and allows you to enter ‘y’ to accept the default values, ‘n’ to configure all, or enter a number to change a specific parameter.

If you use the default settings, the setup utility skips the configuration of some of the parameters in the following steps.

Step 5 Enter the required information as prompted by the setup utility (see Table 1 ). For example, choose application-accelerator as the device mode that you want to configure on the WAAS device. You can accept the default choice (shown in brackets) at a prompt by pressing Enter.

---

Note If you want to use AppNav Controller device mode, see the “Configuring an AppNav Controller” section.

Step 6 Choose the interception method. The default method is normally the correct one to choose.

Step 7 Enter the Time Zone of the device. The number of hours offset from UTC (rounded down to the nearest whole number), and the number of minutes of any partial hour of offset. For example, if your time zone offset is -3:30, then you would set -3 for the hours offset and 30 for the minutes offset.

Step 8 Choose the interface to configure as the management interface, for communicating with the WAAS Central Manager. With the Cisco WAE Inline Network Adapter, you can choose to share one of the inline interfaces for management traffic or you can use one of the built-in Gigabit Ethernet interfaces (out-of-band management).

Continue to answer the questions displayed in the setup utility.

When you are prompted for the IP address of the interface, the IP address that you enter is used for the management interface that you chose in this step.

Step 9 Configure Autosense for Management Interface. Autosense is disabled by default.

---

Note Autosense is not supported on the 4x10GE SFP+ fiber AppNav Controller Interface Module.

Step 10 If you have Dynamic Host Control Protocol enabled in your network, enable DHCP on the WAAS device interface.

---

Note If an interface on the AppNav Controller Interface Module is selected as the management interface, DHCP is disabled and cannot be enabled.

Step 11 Enter the Central Manager IP Address.

Step 12 Enter the Host Name.

Step 13 For the Network Time Protocol (NTP) server, we recommend that you enter the IP address of an NTP server, because clock synchronization between the WAEs in a WAAS network is important.

Step 14 When you are prompted to enter the WCCP router list, enter the IP addresses of 1-4 routers separated by spaces. The easiest configuration is to accept the default, which is the router you configured as the default gateway. To accept the default, press Enter.

Step 15 When you are prompted to choose a license, choose the licenses that you have purchased for use on your WAE. Activating the appropriate licenses is required for various acceleration features to operate. All licenses are not supported on all WAE models.

Step 16 The setup utility displays a set of example router configurations for your convenience. These configurations are the same configurations that are described in the “Configuring WCCP on the Routers” section. Press Enter to continue.

Step 17 When finished, the configuration is displayed. Enter d to toggle the defaults display, or enter a number to change a specific parameter. (See Figure 7.)

Figure 7 WAE Config—WCCP

 

Enter y to select the configuration. If you choose not to accept the configuration, you have the option to go through the setup questions again and reenter the values. Your previous values are used as the defaults.

Step 18 Once you apply the changes, the configuration is saved automatically and you are given the option to reload the system so that the new configuration will take effect.The option to reload the system appears only when the device mode is changed using the Setup wizard.

---

Note If a CM address has been configured, cms enable is automatically configured by the system (node manager) within 5 minutes after the reboot.

 

If you want to check the current running configuration on the WAE, you can use the show running-config EXEC command.

The initial configuration of the data center WAE is completed. The next step is to initially configure and register the designated branch WAE with the WAAS Central Manager device. Repeat the procedure in this section with the WAE in the branch office; the configuration is identical.

After you are finished configuring both WAEs with WCCP, proceed with the “Configuring WCCP on the Routers” section.

Configuring WCCP on WAAS Network Modules

If one of the WAE devices that you are configuring is a network module (NME-WAE) installed in a Cisco access router, you can configure basic WCCP settings using the setup utility.

---

Note If an external interface is used as the primary interface, router WCCP configuration is not recommended. If configured, however, the default gateway must point to the router hosting the network module, and the interface must be either directly connected back to the router, or through a trusted network. Otherwise, there could be a security risk.

To configure basic WCCP settings on a network module, perform the following steps in the setup utility after initial configuration:

---

Step 1 Once you have entered y to select the final basic network module configuration, enter y to configure WCCP on the router.

(See Figure 8.)

Figure 8 WAAS Network Module Config—Basic Config

 

Step 2 Enter and confirm router login password.

If TACACS or RADIUS server authentication is configured on the router, that password takes precedence over the local password.

The router user ID should have the privilege level set to 15 for a successful configuration. The following message displays:

Enter y if the privilege level is set to 15. Else, enter n and set the privilege level to 15 and then proceed with the configuration.

Step 3 Choose a WCCP configuration (LAN redirection or WAN redirection). (See Figure 9.)

Figure 9 WAAS Network Module Config—WCCP Config

 

The following WCCP configuration is applied:

• LAN—ip wccp service 61 is configured as IN
• WAN—ip wccp service 62 is configured as IN
• NME-WAE interface of the router—ip wccp redirect exclude in is configured

In addition, a WAAS WCCP pilot redirect list of ACLs will are configured by default on the router. When you have completed the configuration, you can display the CLI using the ! key to view the WAAS WCCP pilot redirect list of ACLs, and the rest of the configuration.

Step 4 Enter the ! key to display the CLI.

Step 5 Hit any key to continue and apply the configuration. Once you apply the changes, the configuration is saved automatically and you are given the option to reload the system so that the new configuration will take effect. The option to reload the system appears only when the device mode is changed using the Setup wizard.

---

Note If a CM address has been configured and the device mode has changed from the current running device mode (show device-mode running), cms enable is automatically configured by the system (node manager) within 5 minutes after the reboot.

The system reboots and the device is then visible on the network and it can be pinged.

 

Configuring WCCP on the Routers

To complete a basic WCCP configuration on the routers in the data center (Core-Router1) and in the branch office (Edge-Router1), follow these steps on each router:

---

Step 1 Log on to Core-Router1 and enter global configuration mode.

Step 2 Enable WCCP Version 2 and WCCP services 61 and 62 (TCP promiscuous mode) on Core-Router1.

Step 3 On Core-Router1, configure the LAN interface for redirection. This interface is where traffic will be intercepted from when leaving the data center network toward the WAN. This interface must be a Layer 3 interface (routed port or switch virtual interface [SVI]).

Step 4 Enable WCCP service 61 on the inbound direction of fa1/0.40.

Step 5 Configure the WAN interface for redirection. This interface is where traffic will be intercepted from when entering the data center network from the WAN. This interface must be a Layer 3 interface (routed port or switch virtual interface [SVI]).

Step 6 Enable WCCP service 62 on the inbound direction of serial0.

Step 7 To avoid redirection loops, configure the subinterface where Core-WAE1 will connect to Core-Router1. To avoid a routing loop, Core-WAE1 must not be attached to the same segment (subnet) as the interface on Core-Router1 that is performing the redirection. Make sure that you have a tertiary interface (a separate physical interface) or a subinterface (off the router’s LAN port) from which Core-WAE1 connects. In the following example, a subinterface is being used:

---

Note If you plan to use the WCCP GRE return or generic GRE egress methods, you can place the WAE on the same VLAN or subnet as the clients and servers. When using these egress methods, it is important not to enable WCCP on the router until after these egress methods are configured on the WAEs, which can only be done after the setup utility has completed. For more information on configuring these egress methods, see the section “Configuring Egress Methods for WCCP Intercepted Connections” in the Cisco Wide Area Application Services Configuration Guide.

Step 8 After you create the subinterface, enter the ip wccp redirect exclude in command to specify that Core-Router1 should not repeatedly redirect the same traffic to the local WAE, Core-WAE1.

Step 9 Exit subinterface configuration mode.

Step 10 Enable Cisco Express Forwarding (CEF) on Core-Router1.

---

Note CEF is not required but it is recommended for improved performance. WCCP can use IP CEF if CEF is enabled on the router.

Step 11 Save the configuration changes that you just made by writing the running configuration to nonvolatile memory.

Step 12 Verify the new configuration for Core-Router1.

 

The configuration of WCCP on the data center router is completed. The next step is to configure WCCP on the branch router. Repeat the procedure in this section on the branch office router; the configuration is identical.

Accessing the WAAS Central Manager GUI

After the WAE designated as the WAAS Central Manager has been deployed, you can use the WAAS Central Manager GUI to complete the basic configuration of the WAAS network. You can also use the WAAS Central Manager GUI to centrally manage and monitor the geographically dispersed WAEs in the WAAS network.

To access the WAAS Central Manager GUI and complete the initial configuration of the WAAS network, follow these steps:

---

Step 1 Enter the following URL in your web browser:

https:// IP_address_of_WAAS Central_Manager :8443

For example:

https://10.10.10.10:8443

or

https:// hostname_of_WAAS_Central_Manager :8443

For example:

https://waas-cm:8443

---

Note When you access the WAAS Central Manager GUI, make sure that you use HTTPS instead of HTTP to ensure that data is securely transmitted from the WAAS Central Manager to your web browser.

Step 2 After the Security Alert window appears, click Yes to accept the security certificate.

Step 3 After the Login window appears, enter the default username (admin) and the default password (default) for the predefined superuser account and click the Login button.

The Dashboard window of the WAAS Central Manager GUI appears in your browser.

 

The initial configuration of the WAAS network is completed. The next step is to verify that application acceleration is working correctly. See the next section for details.

The WAAS software comes with a set of predefined application policies that help your WAEs classify and optimize some of the most common application traffic with DRE, TFO, and LZ optimizations. This set of default application policies are for applications that use well-known port numbers. For a list of the predefined application definition policies, see the Cisco Wide Area Application Services Configuration Guide.

You can use the WAAS Central Manager GUI to modify these predefined application policies, create new ones, and then distribute these policies to one or more devices in the WAAS network. You can also modify the predefined set of application policies or create new ones through the WAAS CLI. However, we strongly recommend that you use the WAAS Central Manager GUI to perform this task in order to significantly reduce the complexity of this task and to increase the level of consistency. (For CLI command syntax information, see the Cisco Wide Area Application Services Command Reference.)

The WAAS software also comes with most application accelerators enabled. Enabled accelerators include the following: CIFS, EPM, HTTP, ICA, MAPI, NFS, SSL, and video. Enabled accelerators operate only if the proper license is installed. The Enterprise license is required for all accelerators and the video license is additionally required for the video accelerator.

Verifying Application Acceleration

Verify that WAAS optimization and application acceleration is working properly by following these steps:

---

Step 1 Log into the WAAS Central Manager as described in the previous section.

Step 2 From the WAAS Central Manager menu, choose Devices > All Devices.

The WAAS Central Manager displays the Devices list, as shown in Figure 10. You will see the WAAS Central Manager (CM in the Services column) and the two WAEs (Application Accelerator in the Services column).

Step 3 Verify that each of the three WAAS devices show a Management Status of Online and the Device Status has a green light.

Figure 10 WAAS Central Manager Devices Window

 

Step 4 Generate some traffic through the WAAS network for an application that WAAS optimizes.

Step 5 From the WAAS Central Manager menu, choose Home.

Step 6 Verify that your WAAS network is intercepting, optimizing, and compressing data by viewing the charts in the System Dashboard window. The Traffic Volume and Reduction chart should show an amount of optimized traffic that is lower than original traffic. The Compression Summary chart should show a percentage of reduction for the type of application traffic that traversed the network.

 

For more information on monitoring WAAS performance, see the Cisco Wide Area Application Services Monitoring Guide and the chapter, “Monitoring and Troubleshooting Your WAAS Network” in the Cisco Wide Area Application Services Configuration Guide. For troubleshooting information, see the Cisco WAAS Troubleshooting Guide on Cisco DocWiki.

Changing the Administrator Password

After you have initially configured your WAAS devices, we strongly recommend that you immediately change the password for the predefined superuser account (the predefined username is admin, the password is default, and the privilege level is superuser, privilege level 15) on each WAAS device.

To change the password for the superuser account across all WAAS devices registered to the Central Manager, follow these steps:

---

Step 1 Log in to the WAAS Central Manager GUI with the admin account, if you are not already logged in.

Step 2 From the WAAS Central Manager menu, choose Admin > Security > Password.

The Changing Password for User Account window appears.

Step 3 In the New Password field, enter the new password. Passwords are case sensitive, must be 1 to 31 characters in length, and cannot contain the characters ‘ “ | (apostrophe, double quote, or pipe) or any control characters.

Step 4 In the Confirm New Password field, reenter the password for confirmation.

Step 5 Click Submit.

The message “Changes Submitted” appears at the bottom of the window confirming that your password has been changed.

 

Clock synchronization between the WAEs in a WAAS network is important. On each WAE, be sure to set up a Network Time Protocol (NTP) server to keep the clocks synchronized. The setup utility asks you to configure a NTP server, and you should configure one and your time zone when prompted. For information on setting up an NTP server, see the chapter, “Configuring Other System Settings” in the Cisco Wide Area Application Services Configuration Guide.

To set the clock manually, use the clock EXEC CLI command on each WAE. For details, see the Cisco Wide Area Application Services Command Reference.

After you initially configure your WAAS network for application acceleration, you can perform other WAAS administrative tasks. For details, see the Cisco Wide Area Application Services Configuration Guide.

 

 

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2015 Cisco Systems, Inc. All rights reserved.