WAAS/SkipWare ISR Solution Configuration Note [Cisco Application Extension Platform]

Table Of Contents

WAAS/SkipWare ISR Solution Configuration Note

Traditional SCPS Networks

Cisco WAAS/SkipWare Integrated Solution

Hardware

Software

Traffic Flow

Configuring the ISR Router for the WAAS/SkipWare Solution

Configuring the WAAS Central Manager and FTP Server

Configuring the WAAS Network Module

Registering the WAAS Network Module with the WAAS Central Manager

Enabling WCCP on the ISR

Configuring the ISR to Redirect Traffic Using WCCP

Activating the WAAS Network Module

Configuring the AXP Network Module

Installing SkipWare on the AXP Network Module

Configuring SkipWare on the AXP Network Module

Configure Policy Based Routing on the ISR Router

Configuring the Remote ISR

Verifing WCCP

Verifying SkipWare is Functional

SkipWare Commands

Additional Documentation

Glossary

Obtaining Documentation, Obtaining Support, and Security Guidelines

WAAS/SkipWare ISR Solution Configuration Note

This document explains how to configure the WAAS/Skipware ISR solution. This solution combines the Global Protocols, Incorporated implementation of the Space Communications Protocol Standards (SCPS), SkipWare, and the Cisco Wide Area Application Acceleration Services (WAAS) functionality into one Cisco 3845 ISR or Cisco 3825ISR chassis. WAAS runs on a traditional network module (P/N NME-WAE-522-K9) and SkipWare runs on the Cisco Application Extension Platform (AXP) network module (P/N NME-APPRE-522-K9).

This document contains the following sections:

•Traditional SCPS Networks

•Cisco WAAS/SkipWare Integrated Solution

•Hardware

•Software

•Traffic Flow

•Configuring the ISR Router for the WAAS/SkipWare Solution

•Verifing WCCP

•Verifying SkipWare is Functional

•SkipWare Commands

•Additional Documentation

•Glossary

•Obtaining Documentation, Obtaining Support, and Security Guidelines

Traditional SCPS Networks

The Department of Defense (DoD) mandated that WAN Acceleration and Protocol Optimization devices incorporate the SCPS protocol because of the enhancements to satellite-based network links. Existing DoD satellite networks that contain SCPS-TP Performance Enhancing Proxies (PEP), such as the TurboIP SkipWare appliance, provide TCP acceleration but lack WAN acceleration and caching. Figure 1 shows a traditional SCPS network.

For more information on the Joint IP Modem specification (JIPM) from the Defense Information Systems Agency (DISA), refer to The Future of SCPS as an Acceleration Solution, by Chris Ross, at the following URL: http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/4454732/4454733/04454743.pdf?isnumber=4454733&prod=CNF&arnumber=4454743&arSt=1&ared=7&arAuthor=Ross%2C+Chris

Figure 1 Traditional SCPS Network

Cisco WAAS/SkipWare Integrated Solution

Cisco parterned with Global Protocols Incorporated to implement their SCPS SkipWare software on the Cisco AXP network module in a Cisco 3845 ISR. You can install a WAAS network module in the same Cisco 3845 ISR to have WAN windowing. This solution offers DoD customers both WAAS and SkipWare acceleration all in one Cisco 3825 or 3845 ISR to decrease the size, weight and power requirements over the traditional SCPS deployment. The Cisco WAAS network module has data redundancey elimination which provide additional caching and compression features that currently do not exist in a traditional SCPS deployment.

Figure 2 shows the integrated WAAS/SkipWare network where the WAAS optimization is on the WAAS network module and SkipWare is running on the AXP network module. Both the WAAS network module and AXP network module are physically installed into one Cisco 3825 or 3845 ISR.

Figure 2 Integrated WAAS/SkipWare Network

Hardware

The following hardware was used in the configuration and testing:

•WAE 612 Central Manager—WAAS Central Manager appliance used to configure and manage traffic optimization policy on the WAE Network Modules

•Cisco 3845 ISR with a WAAS network module (P/N NME-WAE-522-K9) and an AXP network module (P/N NME-APPRE-302-K9) with SkipWare

•Cisco 3825 ISR with a WAAS network module (P/N NME-WAE-522-K9) and an AXP network module (P/N NME-APPRE-302-K9) with SkipWare.

•2 Linkway modems, one per ISR, used to connect to the Satellite

•PC computer to serve as a remote client

•Application servers for the remote client to access.

Software

The following software was used in the configuration and testing:

•Cisco IOS 12.4(15)T on the Cisco 3845 ISR and Cisco 3825 ISR

•WAAS Central Manager & Accelerator, Release 4.0.17.14

•AXP, Release 1.0.5 including cli-plugin and AXP-PERL, Release 5.5.8

•SkipWare for the AXP network module, Release 4.8.0.2

Traffic Flow

The integrated WAAS/SkipWare solution redirects TCP traffic inside the ISR using WCCPv2 and policy-based routing (PBR). This section lists the path a packet takes through the router with the integrated WAAS/SkipWare solution.

A packet takes the following path, under normal conditions, from the LAN to the WAN (Figure 3):

1. As LAN traffic, the packet enters the ISR from the Gigabit Ethernet 0/1 interface.

2. WCCP redirects the packet to the WAAS network module on the integrated-service-engine 1/0 interface.

3. After the WAAS network module optimizes the TCP, it sends the packet to the router on the integrated-service-engine 1/0 interface.

4. A policy based route map, redirects the packet coming from the WAAS network module after optimization and sends it to integrated-service-engine 2/0.2 subinterface.

5. The packet enters the AXP network module on the integrated-service-engine 2/0.2 subinterface, and is sent to the SkipWare virtual LAN interface (ethernet 0.2) running on the AXP network module.

6. SkipWare optimizes the TCP and sends it out the integrated-service-engine 2/0.3 subinterface to the ISR.

7. The ISR routes the packet to the final destination over a WAN.

Figure 3 WAAS/SkipWare TCP Packet Flow from LAN to WAN

A packet takes the following path, under normal conditions, from the WAN to the LAN (Figure 4):

1. As WAN traffic, the packet enters the ISR from the Gigabit Ethernet 0/0 interface.

2. A policy based route map, redirects the incoming packet destined for the LAN subnet to the integrated-service-engine 2/0.3 subinterface.

3. The redirected TCP packet enters the AXP network module on the integrated-service-engine 2/0.3 subinterface and is sent to the SkipWare virtual WAN interface (Ethernet0.3) running on the AXP network module

4. The system terminates the SkipWare TCP options and then sends it out the integrated-service-engine 2/0 interface with any other remaining options (such as TFO).

5. A policy based route map reroutes the packet to the WAAS network module optimize the packet for WAAS.

6. After the WAAS network module completes optimization, the WAAS network module sends the packet back to the ISR.

7. The ISR routes the packet to the destination LAN subnet.

Figure 4 WAAS/SkipWare Packet Flow from WAN to LAN

Configuring the ISR Router for the WAAS/SkipWare Solution

This configuration uses both the Cisco WAAS network module and the Cisco AXP network module. This configuration guide focuses on the configuration changes from a standard implementation. For specific information about how to configure and install the WAAS network module, refer to the Cisco Wide Area Application Services Quick Configuration Guide at the following URL:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4019/quick/guide/waasqcg.html

For specific information on how to install and configure the AXP network module, refer to the Cisco Application eXtension Platform User Guide at the following URl:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ax/1.0/user/guide/axpusr.html

To configure the WAAS/SkipWare ISR solution, perform these tasks in the following order:

1. Configure the base configuration on the ISR.

a. Configure the WAAS Central Manager and FTP servers (page 6).

b. Perform initial configuration on the WAAS network module on the ISR (page 6).

c. Register the WAAS network module with the WAAS Central Manager (page 10)

d. Configure the ISR interface to redirect traffic to the WAAS network module using WCCP (page 10).

e. Activate the WAAS network module and specify the optimization policies using the web interface software for the WAAS Central Manager (page 11).

f. Install SkipWare on the AXP network module (page 11).

g. Configure SkipWare (page 17).

h. Define the access lists and policy-based route maps and apply the policy-based maps to the interfaces on the ISR to redirect traffic to SkipWare (page 19).

2. Repeat steps b through h on the remote ISR changing the IP addresses, access lists, and policy-based route maps to reflect the remote router.

Configuring the WAAS Central Manager and FTP Server

Before you begin configuring the WAAS/SkipWare ISR solution, you must have the following installed and configured on your network:

•A WAAS Central Manager

•An FTP server for transferring software images to the WAAS network modules and AXP network modules in the network.

Verify that you can ping the FTP server and WAAS Central Manager from the ISR.

For more information on performing the initial setup on the WAAS Central Manager, refer to the following URL: http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/quick/guide/waasqcg.html#wp1357346

Configuring the WAAS Network Module

The WAAS network module is the first device in the ISR that optimizes TCP traffic as it leaves the LAN on the local ISR. Web Cache Communication Protocol (WCCP) version 2 intercepts TCP traffic entering the LAN interface and sends it to the WAAS network module.

To configure the WAAS Network module, perform the following procedure:

Step 1 To enable and configure the internal interface on the ISR connected to the WAAS network module, enter the following commands. In the tested configuration, the WAAS network module is connected to the Integrated-Service-Engine1/0 interface.
UUTC#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface Integrated-Service-Engine1/0 
UUT3(config-if)#ip address 192.168.2.1 255.255.255.0 
UUT3(config-if)#service-module ip address 192.168.2.2 255.255.255.0 
UUT3(config-if)#service-module ip default-gateway 192.168.2.1 
UUT3(config-if)#no shutdown 
UUT3(config-if)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
Step 2 Session into the WAAS network module from the ISR router and initially configure the WAAS network module.

Note The initial password for the WAAS network module is default
UUT3#service-module integrated-Service-Engine 1/0 session 
Trying 192.168.2.1, 2066 ... Open 
Username: admin 
Password: ######
Device is configured with a (well known) default username/password 
for ease of initial configuration. This default username/password 
should be changed in order to avoid unwanted access to the device. 
System is initializing. Please wait... 
Please use 'show disks details' to monitor system status. 
NO-HOSTNAME# 
NO-HOSTNAME#setup
Please choose the device mode of the WAE 
1.central-manager 
2.application-accelerator 
3.Skip device mode configuration 
Enter your choice : 2 
Please choose the primary interface: 
1: GigabitEthernet 1/0 
2: GigabitEthernet 2/0 
Enter choice: 1 
Please enter the domain name server ip: your DNS server IP
Please enter the domain name: your domain name
Please enter the hostname: hostname you want to assign to the WAAS Network module
Would you like to configure NTP server (y/n) [y] : y
Please enter the IP address or domain name 
of the NTP server: your NTP server IP
Would you like to configure the timezone (y/n) [y] :y 
Please enter the name of the timezone : your timezone
Please enter the hours offset from UTC <-23 to +23>: your offset from UTC
Please enter the minutes offset from UTC: your minutes offset, if not applicable enter 0
 primary-interface GigabitEthernet 1/0 
       ip name-server your name server IP
       ip domain-name your domain name
       hostname your hostname for the WAAS network module
       ntp server your ntp server IP
       clock timezone your timezone and offset
Do you accept these configs (y/n) [y]: y 
Would you like to apply the configurations (y/n) [y]: y 
This may take few moments. Please wait.. 
All CLI configurations were applied successfully. 
For your reference, configuration generated 
during this setup session is available at /local1/setup_gen_config.txt. 
You can view this file with the command, "type /local1/setup_gen_config.txt". 
Press any key to continue.. 
Step 3 Enable WCCP on the WAAS network module.

1.1.1.1 is used as the defined loopback interface on the router
UUT3-WAE#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3-WAE(config)#wccp version 2 
UUT3-WAE(config)#wccp router-list 1 1.1.1.1 
UUT3-WAE(config)#wccp tcp-promiscuous router-list-num 1 
WCCP configuration for TCP Promiscuous service 61 succeeded. WCCP configuration for TCP 
Promiscuous succeeded. Please remember to configure WCCP service 61 and 62 on the 
corresponding router. 
UUT3-WAE(config)#end 
UUT3-WAE#copy running-config startup-config
Building configuration... 
[OK] 
UUT3-WAE#exit
Registering the WAAS Network Module with the WAAS Central Manager
To register the WAAS network module with the WAAS Central Manager, log into the WAAS network 
module and enter the following commands. 
Note The WAAS network module password will be default unless you changed it during the initial configuration of the WAAS network module.
UUT3#service-module integrated-Service-Engine 1/0 sess 
Trying 192.168.2.1, 2066 ... Open 
Username: admin 
Password: ######
Device is configured with a (well known) default username/password 
for ease of initial configuration. This default username/password 
should be changed in order to avoid unwanted access to the device. 
System Initialization Finished. 
UUT3-WAE#configure terminal
UUT3-WAE(config)#central-manager address IP address of your WAAS Central Manager 
UUT3-WAE(config)#cms enable 
Registering WAAS Application Engine... 
Sending device registration request to Central Manager with address 192.168.1.2 
Please wait, initializing CMS tables 
Successfully initialized CMS tables 
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 WAAS Central Manager UI. 
management services enabled 
UUT3-WAE(config)#end  
UUT3-WAE#copy running-config startup-config
Building configuration... 
[OK] 
UUT3-WAE#exit
Enabling WCCP on the ISR

To enable the WCCP on the ISR to redirect traffic to the WAAS network module, perform the following procedure:

Step 1 Enable WCCP on the ISR.
UUT3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#ip wccp version 2 
UUT3(config)#ip wccp 61
UUT3(config)#end
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
Sep  9 21:39:46.983: %SYS-5-CONFIG_I: Configured from console by console 
Sep  9 21:39:47.779: %WCCP-5-SERVICEFOUND: Service 61 acquired on WCCP client 192.168.2.2 
Step 2 Verify that WCCP is active:
UUT3#sh ip wccp 
Global WCCP information: 
    Router information: 
        Router Identifier:                   1.1.1.1 
        Protocol Version:                    2.0 
    Service Identifier: 61 
        Number of Service Group Clients:     1 
        Number of Service Group Routers:     1 
        Total Packets s/w Redirected:        0 
          Process:                           0 
          Fast:                              0 
          CEF:                               0 
        Service mode:                        Open 
        Service access-list:                 -none- 
        Total Packets Dropped Closed:        0 
        Redirect access-list:                -none- 
        Total Packets Denied Redirect:       0 
        Total Packets Unassigned:            0 
        Group access-list:                   -none- 
        Total Messages Denied to Group:      0 
        Total Authentication failures:       0 
        Total Bypassed Packets Received:     0 
Step 3 Disable Cisco Express Forwarding (CEF) because it causes problems with the route maps needed on the ISR.
UUT3#configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#no ip cef 
UUT3(config)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
UUT3#
Configuring the ISR to Redirect Traffic Using WCCP

To configure the ISR to redirect traffic using WCCP, perform the following procedure while logged into the ISR. In the tested configuration, GigabitEthernet0/1 is the LAN interface.

Step 1 Verify the interface configuration before adding WCCP to the interface:
UUT3#show running-config interface gigabitethernet0/1 
Building configuration... 
Current configuration : 143 bytes 
! 
interface GigabitEthernet0/1 
 description LAN interface 
 ip address 192.168.11.1 255.255.255.0 
 duplex full 
 speed 100 
 media-type rj45 
UUT3#
Step 2 Add WCCP 61 to the LAN interface.
UUT3#configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface gigabitethernet0/1 
UUT3(config-if)#ip wccp 61 redirect in 
UUT3(config-if)#end 
UUT3#
Step 3 Verify and save the configuration
UUT3#show running-config interface gigabitethernet0/1
Building configuration... 
Current configuration : 167 bytes 
! 
interface GigabitEthernet0/1 
 description LAN interface 
 ip address 192.168.11.1 255.255.255.0 
 ip wccp 61 redirect in 
 duplex full 
 speed 100 
 media-type rj45 
UUT3#
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
Activating the WAAS Network Module

To activate of the WAAS network module and specify the optimization policies, access the WAAS Central Manager using the web browser interface.

For more information, refer to the following URL:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v403/module/configuration/guide/wsnmecfg.html

Configuring the AXP Network Module

This configuration guide focuses on how to setup SkipWare on the Cisco AXP network module. For general information about how to install and configure the AXP network module, refer to the AXP documentation suite at the following URL: http://www.cisco.com/en/US/products/ps9701/tsd_products_support_series_home.html.

The following items are required to install SkipWare on the AXP network module:

•The ISR and AXP network module interfaces must be configured on the same IP subnet so that traffic can pass internally between the AXP network module and the ISR.

•An FTP server reachable from the AXP network module using the ISR where it is installed.

•An NTP server accessible to the AXP network module or set to act as an NTP master on the ISR.

To install SkipWare on the AXP network module, perform this procedure:

Step 1 Configure the internal interface on the ISR that connects to the AXP network module.

In the tested solution, the AXP network module is located in the Integrated-Service-Engine2/0 interface and 192.168.3.0/24 is the network, any private subnet works.
UUT3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface integrated-Service-Engine 2/0 
UUT3(config-if)# ip address 192.168.3.1 255.255.255.0 
UUT3(config-if)# service-module ip address 192.168.3.2 255.255.255.0 
UUT3(config-if)# service-module ip default-gateway 192.168.3.1 
UUT3(config-if)# ntp broadcast destination 192.168.3.2 
UUT3(config-if)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
Step 2 Configure two additional subinterfaces with VLAN tags on the ISR.

You can use any private subnet for these interfaces.
UUT3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface Integrated-Service-Engine2/0.2 
UUT3(config-subif)# encapsulation dot1Q 2 
UUT3(config-subif)# ip address 192.168.4.1 255.255.255.0 
UUT3(config-subif)#end 
UUT3#configure terminal
Sep 10 01:48:57.614: %SYS-5-CONFIG_I: Configured from console by console t 
Enter configuration commands, one per line.  End with CNTL/Z. 
UUT3(config)#interface Integrated-Service-Engine2/0.3 
UUT3(config-subif)# encapsulation dot1Q 3 
UUT3(config-subif)# ip address 192.168.5.1 255.255.255.0 
UUT3(config-subif)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
Caution The integrated-service-engine2/0.2 interface is where TCP traffic enters the AXP network module from the LAN to be optimized by SkipWare. The integrated-service-engine 2/0.3 interface is where TCP traffic enters the AXP network module on the return path from the WAN. It is imperative that the subinterfaces use VLAN 2 and VLAN 3 respectively so that SkipWare correctly acts on the TCP traffic. Do not assign any other VLANs to these subinterfaces.

Step 3 Configuring the AXP network module where Global Protocols SkipWare runs.

a. Enter the following command to session into the AXP network module:
service-module integrated-Service-Engine slot/port session
Example:
UUT3#service-module integrated-Service-Engine 2/0 session 
se-192-168-30-2.unspecified> 
b. Change the hostname to avoid any confusion when configuring devices..
se-192-168-30-2.unspecified>configure terminal
Enter configuration commands, one per line. End with CNTL/Z. 
se-192-168-30-2.unspecified(config)> hostname uut3-AXP 
uut3-AXP(config)> end 
uut3-AXP>copy running-config startup-config
Building configuration... 
[OK] 
c. Verify that the AXP version is 1.0.5.0 using the show software versions command.
uut3-AXP>show software versions 
Application eXtension Platform (AXP) version (1.0.5) 
Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2007 by Cisco 
Systems, Inc. 
If your AXP is not running version 1.0.5, refer to the instructions on upgrading the AXP module to version 1.0.5.

Installing SkipWare on the AXP Network Module

Before installing SkipWare on the AXP network module, you need to install the cli_plugin, Release 1.0.5 and AXP-PERL, release 5.5.8, packages which are included with the AXP network module image available on Cisco.com.

For more information, refer to the Cisco Application EXtension User Guide at the following URL: http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ax/1.0/user/guide/axpusr.html

To install SkipWare on your AXP network module, preform this procedure on the AXP network module:

Step 1 Install the AXP network module software packages.

If you do not have the cli_plugin and AXP-PERL software packages installed on your AXP network module, perform the following procedure:

a. Install the AXP-PERL software package from the FTP server.
uut3-AXP> software install ftp://172.18.152.88/AXP/images/axp-perl-5.8.8.nme.1.0.5.pkg 
username ftp_username password ftp_username_password
WARNING:: This command will install the necessary software to 
WARNING:: complete an add-on install. It is recommended that a backup be done 
WARNING:: before installing software. 
Downloading ftp axp-perl-5.8.8.nme.1.0.5.pkg 
Bytes downloaded : 61795 
Validating package signature ... done 
This is add on installation. 
Validating installed manifests .........complete. 
Found new Add-On subsystem SID: 2c51c608-d07f-4842-954e-11c16304fe1e Name: perl-5.8.8 
Version: 1.0.5 
Starting payload download 
File : axp-perl-5.8.8.nme.1.0.5.prt1 Bytes : 11720196 
Validating payloads match registered checksums... 
 - axp-perl-5.8.8.nme.1.0.5.prt1 ............verified 
Generating the add-on-install work order : 
Is language only [False] 
Setting install started flag 
returning fname /dwnld/.work_order 
. 
superthread:    INFO superthread server output END 
dwnldr:    INFO dwnldr server output /bin/dwnldr_startup.sh: line 3:  1829 Killed                  
dwnldr 
dwnldr:    INFO dwnldr server output END 
ntp:    INFO ntp server output 18 Jan 05:16:19 ntpd[2133]: precision = 13 usec18 Jan 
05:16:26 ntpd[2133]: system event 'event_restart' (0x01) status 'sync_alarm, 
sync_unspec, 1 event, event_unspec' (0xc010)/bin/ntp_startup.sh: line 70:  2133 Killed                  
ntpd -gn 
ntp:    INFO ntp server output END 
Wed Jun 18 04:20:56 UTC 2008 
INIT: Restarting system. 
uut3-AXP> 
The AXP network module reboots after the installation has completed.

b. Verify that the AXP-PERL software package installed by entering the show software packages command.
uut3-AXP(config)>show software packages
Installed Packages: 
 - Installer (Installer application) (1.0.5.0) 
 - Bootloader (Primary) (Service Engine Bootloader) (1.0.2) 
 - JAVALIN (Virtual Server Development System) (1.0.5) 
 - Infrastructure (Service Engine Infrastructure) (2.3.3.0) 
 - Global (Global manifest) (1.0.5) 
 - guest_os (Javalin Guest OS Add-on Package) (1.0.5) 
 - Bootloader (Secondary) (Service Engine Bootloader) (1.0.2.0) 
 - Core (Service Engine OS Core) (2.4.1.0) 
 - GPL Infrastructure (Service Engine GPL Infrastructure) (2.2.2.0) 
Installed Plug-ins: 
 - perl-5.8.8 (perl-5.8.8) (1.0.5) 
c. Install the cli_plugin component package from the FTP Server
uut3-AXP> software install add url ftp://172.18.152.88/AXP/images/ 
axp-cli-plugin.nme.1.0.5.pkg username ftp_username password ftp_username_password
The following is normal output after installing the cli_plugin package.
WARNING:: This command will install the necessary software to 
WARNING:: complete an add-on install. It is recommended that a backup be done 
WARNING:: before installing software. 
Downloading ftp axp-cli-plugin.nme.1.0.5.pkg 
Bytes downloaded : 2997 
Validating package signature ... done 
This is add on installation. 
Validating installed manifests ..........complete. 
Found new Add-On subsystem SID: b4b0ee92-cf8e-472b-8434-e8e7412ec71a Name: cli_plugin 
Version: 1.0.5 
Starting payload download 
File : axp-cli-plugin.nme.1.0.5.prt1 Bytes : 87798 
Validating payloads match registered checksums... 
 - axp-cli-plugin.nme.1.0.5.prt1 .verified 
Generating the add-on-install work order : 
Is language only [False] 
Setting install started flag 
returning fname /dwnld/.work_order 
. 
superthread:    INFO superthread server output END 
dwnldr:    INFO dwnldr server output /bin/dwnldr_startup.sh: line 3: 1839 Killed                  
dwnldr 
dwnldr:    INFO dwnldr server output END 
ntp:    INFO ntp server output 17 Jun 21:24:34 ntpd[2143]: precision = 12 usec17 Jun 
21:24:40 ntpd[2143]: system event 'event_restart' (0x01) status 'sync_alarm, 
sync_unspec, 1 event, event_unspec' (0xc010)17 Jun 22:24:43 ntpd[2143]: offset 
0.000000 sec freq 0.000 ppm error 0.000008 po 
ntp:    INFO ntp server output END 
INIT: Restarting system. 
uut3-AXP> 
The AXP reboots after the installation completes.

d. Verify that the cli_plugin component package was installed by entering the show software packages command.
uut3-AXP> show software packages 
Installed Packages: 
 - Installer (Installer application) (1.0.5.0) 
 - Bootloader (Primary) (Service Engine Bootloader) (1.0.2) 
 - JAVALIN (Virtual Server Development System) (1.0.5) 
 - Infrastructure (Service Engine Infrastructure) (2.3.3.0) 
 - Global (Global manifest) (1.0.5) 
 - guest_os (Javalin Guest OS Add-on Package) (1.0.5) 
 - Bootloader (Secondary) (Service Engine Bootloader) (1.0.2.0) 
 - Core (Service Engine OS Core) (2.4.1.0) 
 - GPL Infrastructure (Service Engine GPL Infrastructure) (2.2.2.0) 
Installed Plug-ins: 
 - cli_plugin (CLI Plugin bundle to allow custom CLI plugin) (1.0.5) 
 - perl-5.8.8 (perl-5.8.8) (1.0.5) 
uut3-AXP> 
Step 2 Install SkipWare on the AXP network module
uut3-AXP>software install add url ftp://172.18.152.88/AXP/images/skipware.4.8.0.2.pkg 
username ftp_username password ftp_username_password
WARNING:: This command will install the necessary software to 
WARNING:: complete an add-on install. It is recommended that a backup be done 
WARNING:: before installing software. 
Downloading ftp skipware.4.8.0.2.pkg 
Bytes downloaded : 6354 
Validating package signature ... Foundation verification failed 
Trying Third Party verification 
Validating new manifest file /dwnld/pkgdata/skipware.4.8.0.2.pkg from package 
/dwnld/pkgdata/skipware.4.8.0.2.pkg 
Extracting development certificate and authorization 
Third Party verification passed for skipware.4.8.0.2.pkg 
done 
This is add on installation. 
Validating installed manifests ...........complete. 
Found new Add-On subsystem SID: c7349068-e200-42eb-aa26-d51ec01886f3 Name: skipware 
Version: 4.8.0.2 
Foundation verification failed 
Trying Third Party verification 
Validating new manifest file /tmp/manifest/skipware_manifest.sig from package 
/dwnld/pkgdata/skipware.4.8.0.2.pkg 
Extracting development certificate and authorization 
Third Party verification passed for Manifest skipware_manifest.sig 
Starting payload download 
File : skipware.4.8.0.2.prt1 Bytes : 3576921 
Validating payloads match registered checksums... 
 - skipware.4.8.0.2.prt1 ....verified 
Generating the add-on-install work order : 
Is language only [False] 
Creating Third Party work order 
Generating the third party add-on-install work order for skipware : 
Setting install started flag 
returning fname /dwnld/.work_order 
. 
superthread:    INFO superthread server output END 
dwnldr:    INFO dwnldr server output /bin/dwnldr_startup.sh: line 3: 1850 Killed                  
dwnldr 
dwnldr:    INFO dwnldr server output END 
ntp:    INFO ntp server output 8 Sep 14:00:48 ntpd[2153]: precision = 11 usec 8 Sep 
14:00:54 ntpd[2153]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 
1 event, event_unspec' (0xc010) 8 Sep 14:01:36 ntpd[2153]: peer 192.168.2.1 event 
'event_reach' (0x84) status ' 
ntp:    INFO ntp server output END 
exec_script apphosting_install.sh skipware 
Installation parameters: 
  Application name: skipware 
Checking if application exists...no 
Generating static context id...2 
Creating application instance... 
Adding application skipware to system startup... 
Setting application environment... 
Setting application capabilities... 
All done! 
Application Hosting Environment Integration. Return code is success. 
exec_script populate_default_sysdb_rsrc_limits.sh 
skipware,2400,65536,8192,2400,65536,8192,c7349068-e200-42eb-aa26-d51ec01886f3,/ 
Creating Resource limit directories for the application 
0 
Application Resources Allocation. Return code is success. 
715 
Reading 715 from input stream ... 
612 
Reading 612 from input stream ... 
exec_script create_tmp_post_install_script.sh skipware,/bin/post-install.sh 
creating temporary post install directory. Return code is success. 
exec_script create_dependency_file.sh c7349068-e200-42eb-aa26-d51ec01886f3,skipware 
storing dependency information. Return code is success. 
exec_script third_party_install_flag.sh third party flag 
Creating third party install flag. Return code is success. 
INIT: Restarting system. 
The AXP network module reboots after installation has completed.

Step 3 Verify that SkipWare installed by entering the command show software packages command.
uut3-AXP> show software packages 
Installed Packages: 
 - Installer (Installer application) (1.0.5.0) 
 - Bootloader (Primary) (Service Engine Bootloader) (1.0.2) 
 - JAVALIN (Virtual Server Development System) (1.0.5) 
 - Infrastructure (Service Engine Infrastructure) (2.3.3.0) 
 - Global (Global manifest) (1.0.5) 
 - guest_os (Javalin Guest OS Add-on Package) (1.0.5) 
 - Bootloader (Secondary) (Service Engine Bootloader) (1.0.2.0) 
 - Core (Service Engine OS Core) (2.4.1.0) 
 - GPL Infrastructure (Service Engine GPL Infrastructure) (2.2.2.0) 
Installed Plug-ins: 
 - cli_plugin (CLI Plugin bundle to allow custom CLI plugin) (1.0.5) 
 - perl-5.8.8 (perl-5.8.8) (1.0.5) 
skipware (None) (4.8.0.2)
uut3-AXP> 
Configuring SkipWare on the AXP Network Module

You need to configure SkipWare on the AXP network module so that any traffic coming from VLAN 2, or the Ethernet 0.2 interface, requires that a SkipWare Header be added to the packet, and any traffic coming from VLAN 3, or the Ethernet 0.3 interface, already has a SkipWare header added to the packet. It is imperative that you correctly configure the interfaces on the AXP network module to match the ISR.

Note The AXP network module identifies interfaces as Ethernet interfaces and subinterfaces, however the same interfaces display as Gigabit Ethernet interfaces and subinterfaces in the output of the show interfaces command at the AXP CLI prompt.

The ISR subinterfaces configured in the "Configuring the ISR to Redirect Traffic Using WCCP" section have the following configuration:
interface Integrated-Service-Engine2/0.2 
 encapsulation dot1Q 2 
 ip address 192.168.4.1 255.255.255.0 
!         
interface Integrated-Service-Engine2/0.3 
 encapsulation dot1Q 3 
 ip address 192.168.5.1 255.255.255.0 
!         
Step 1 Configure the Ethernet subinterfaces on the AXP network module to align with the ISR subinterfaces.
uut3-AXP> configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
uut3-AXP(config)> interface ethernet0.2 
uut3-AXP(config-interface)> ip address 192.168.4.2 255.255.255.0 
uut3-AXP(config-interface)> exit 
uut3-AXP(config)> interface ethernet0.3 
uut3-AXP(config-interface)> ip address 192.168.5.2 255.255.255.0 
uut3-AXP(config-interface)> end 
uut3-AXP> copy running-config startup-config
Building configuration... 
[OK] 
uut3-AXP> 
Step 2 Verify the that the two new subinterfaces were created by entering the show running-config command.
uut3-AXP> show running-config 
Generating configuration: 
clock timezone America/Los_Angeles 
hostname uut3-AXP 
ip domain-name localdomain 
system language preferred "en_US" 
ntp server 192.168.2.1 prefer 
ntp server 192.168.3.1 
software download server url "ftp://127.0.0.1/ftp" credentials hidden 
"6u/dKTN/hsEuSAEfw40XlF2eFHnZfyUTSd8ZZNgd+Y9J3xlk2B35j0nfGWTYHfmPSd8ZZNgd+Y9J3xlk2B35j0nfG
WTYHfmPSd8ZZNgd+Y9J3xlk2B35j0nfGWTYHfmP" 
log trace local enable 
no service password-encryption 
interface eth0 
 ip address 192.168.3.2 255.255.255.0 
 exit 
interface eth0.2 
 ip address 192.168.4.2 255.255.255.0 
 exit 
interface eth0.3 
 ip address 192.168.5.2 255.255.255.0 
 exit 
interface eth1 
 exit 
ip ssh server 
app-service skipware 
 bind interface eth0 
 hostname uut3-AXP 
 status-monitor monitor_interval 1 recovery_threshold 3 
 exit 
end 
uut3-AXP> 
Step 3 Bind the two new sub interfaces to SkipWare so SkipWare can send and receive traffic from the ISR.
uut3-AXP> configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
uut3-AXP(config)> app-service skipware 
uut3-AXP(config-skipware)> bind interface eth0.2 
uut3-AXP(config-skipware)> bind interface eth0.3 
uut3-AXP(config-interface)> end 
uut3-AXP> copy running-config startup-config
Building configuration... 
[OK] 
Step 4 Enter the show running-config command to verify that the two subinterfaces are listed in the app-service SkipWare section.
uut3-AXP> show running-config 
Generating configuration: 
...<output truncated>
app-service skipware 
 bind interface eth0 
 bind interface eth0.2 
 bind interface eth0.3 
 hostname uut3-AXP 
 status-monitor monitor_interval 1 recovery_threshold 3 
 exit 
end 
uut3-AXP> 
Step 5 Save the configuration and reboot the AXP network module to SkipWare with the newly configured interfaces.

When the AXP network module reboots, SkipWare starts automatically.
uut3-AXP> copy running-config startup-config
Building configuration... 
[OK] 
uut3-AXP> reload 
Reloading the system will terminate all end user sessions. 
Doing a reload will cause any unsaved configuration data to be lost. 
Are you sure you want to reload [y/n]? : y 
uut3-AXP> 
MONITOR SHUTDOWN... 
Step 6 Verify that SkipWare is running by entering the show app-service state command on the AXP network module.
uut3-AXP> show app-service state 
APPLICATION      STATE               HEALTH 
skipware         online               ALIVE 
uut3-AXP> 
Configure Policy Based Routing on the ISR Router

You need to define two access lists and three policy based route maps to successfully route traffic between the WAAS network module and the AXP network module running SkipWare.

Step 1 Verify all the interfaces configured on the ISR by entering the show ip interfaces brief command at the ISR privileged EXEC prompt:
UUT3#show ip interfaces brief 
Interface                  IP-Address      OK? Method Status 		      Protocol 
GigabitEthernet0/0         214.43.195.1    YES TFTP   up                    up 
GigabitEthernet0/1         192.168.11.1    YES TFTP   up                    up 
In1/0                      192.168.2.1     YES manual up                    up 
In2/0                      192.168.3.1     YES TFTP   up                    up 
In2/0.2                    192.168.4.1     YES TFTP   up                    up 
In2/0.3                    192.168.5.1     YES TFTP   up                    up 
Loopback1                  1.1.1.1         YES TFTP   up                    up 
UUT3# 
Step 2 Define the access lists.

In the tested configuration, the LAN subnet on the local ISR is 192.168.11.0/24 and the LAN subnet on the remote ISR is 192.168.12.0/24. Use these two subnets in the ACLs.

a. The following ACL is for traffic leaving the ISR to the LAN subnet on the remote ISR:

ip access-list extended WAE->AXP

permit icmp any 192.168.12.0 0.0.0.255

permit tcp any 192.168.12.0 0.0.0.255

b. The following ACL is for traffic from a remote ISR to a host on the local LAN subnet:

ip access-list extended WAN->AXP

permit icmp any 192.168.11.0 0.0.0.255

permit tcp any 192.168.11.0 0.0.0.255

Note For more information on configuring ACLs, refer Access Control Lists: Overview and Guidelines at the following URL:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_acl_ov_guideline_ps6350_TSD_Products_Configuration_Guide_Chapter.html

Step 3 Configure the policy based route maps.

The next hop addresses in the route maps are the interfaces on the respective internal AXP sub interface and WAE interface.

a. The following route map is for traffic entering the ISR from the WAN:

route-map WAN->AXP permit 10

match ip address WAN->AXP

set ip next-hop 192.168.5.2

b. The following route map is for traffic routed from the WAAS network module to the AXP network module:

route-map WAE->AXP permit 10

match ip address WAE->AXP

set ip next-hop 192.168.4.2

c. The following route map is for traffic returning from the AXP network module to the WAAS network module:

route-map SCPWAAS map permit 10

match ip address WAN->AXP

set ip next-hop 192.168.2.2

You can use the same ACLs for the WAN->AXP route map and the SCPWAAS route map as the traffic destination is the same. The only difference is the next hop address is different.

Note For more information on configuring policy based route maps, refer Policy-Based Routing at the following URL:
http://www.cisco.com/en/US/products/ps6599/products_white_paper09186a00800a4409.shtml

Step 4 Apply the route maps to the ISR interfaces.

a. Apply the WAE->AXP route map to the interface connected to the WAAS network module.
UUT3#configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
UT3(config)#interface Integrated-Service-Engine1/0 
UUT3(config-if)# ip policy route-map WAE->AXP 
UUT3(config-if)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
UUT3#
b. Apply the WAN->AXP route map to the WAN interface for incoming traffic coming on the ISR.
UUT3#configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface GigabitEthernet0/0 
UUT3(config-if)# ip policy route-map WAN->AXP
UUT3(config-if)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
UUT3#
c. Apply the SCPWAAS route map to the ISR interface connected to the AXP network module.
UUT3#configure terminal 
Enter configuration commands, one per line. End with CNTL/Z. 
UUT3(config)#interface Integrated-Service-Engine2/0 
UUT3(config-if)# ip policy route-map SCPWAAS
UUT3(config-if)#end 
UUT3#copy running-config startup-config
Building configuration... 
[OK] 
UUT3#
Configuring the Remote ISR

To successfully pass WAAS and SCPS optimized traffic end to end, you need to configure the remote ISR with the same configuration except that the IP addresses in the ACLs and the private IP addresses used must reflect the remote ISR.

Verifing WCCP

To verify that WCCP is configured and active on the ISR, enter the show ip wccp command at the privileged EXEC prompt:
UUT3#show ip wccp
Global WCCP information:
    Router information:
        Router Identifier:                   1.1.1.1
        Protocol Version:                    2.0
    Service Identifier: 61
        Number of Service Group Clients:     1
        Number of Service Group Routers:     1
             Total Packets s/w Redirected:        48707
          Process:                           222
          Fast:                              48485
          CEF:                               0
        Service mode:                        Open
        Service access-list:                 -none-
        Total Packets Dropped Closed:        0
        Redirect access-list:                -none-
        Total Packets Denied Redirect:       0
        Total Packets Unassigned:            10
        Group access-list:                   -none-
        Total Messages Denied to Group:      0
        Total Authentication failures:       0
        Total Bypassed Packets Received:     0
UUT3#
The output indicates that packets are redirected by process and fast switching. If the number of packets listed for CEF is anything other than 0, disable CEF on the ISR. For more information on how to disable CEF on the ISR, see page 10.

For detailed troubleshooting information of the WAAS network module, refer to the Operating, Maintaining, and Troubleshooting Cisco WAAS Network Modules chapter in the Configuring Cisco WAAS Network Modules for Cisco Access Routers at the following URL: http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v403/module/configuration/guide/wsnmecfg.html#wp40060.

Verifying SkipWare is Functional

To verify that SkipWare is running, perform the following procedure while logged into the AXP network module:

Step 1 Verify the state of SkipWare by entering the show app-service command.
uut3-AXP> show app-service state
                   APPLICATION                STATE               HEALTH
                      skipware               online                ALIVE
uut3-AXP> 
Step 2 If the application shows active but you are not seeing SkipWare headers on the packets on the WAN, check the statistics for inbound and outbound traffic through the virtual LAN interface on SkipWare by entering the stats lan command in SkipWare configuration mode:
uut3-AXP> app-service skipware
uut3-AXP(exec-skipware)> stats lan
LAN STATS: duration: 215:30:53
Bytes Sent                    : 258
Packets Sent                  : 3
Sent Packets Dropped          : 0
Bytes Received                : 92
Packets Received              : 2
Received Packets Dropped      : 0
uut3-AXP(exec-skipware)> 
Step 3 If the application shows active but you are not seeing SkipWare headers on the packets on the WAN, check the statistics for inbound and outbound traffic through the virtual WAN interface on SkipWare by entering the stats wan command in SkipWare configuration mode:
uut3-AXP> app-service skipware
uut3-AXP(exec-skipware)> stats wan
WAN STATS: duration: 215:31:44
Bytes Sent                    : 258
Packets Sent                  : 3
Sent Packets Dropped          : 0
Bytes Received                : 92
Packets Received              : 2
Received Packets Dropped      : 0
uut3-AXP(exec-skipware)> 
Step 4 If there are no statistical data on either interface, check the configuration on the ISR to verify that traffic is being routed based on the policy maps to the correct subinterfaces on the ISR.

Step 5 If there are statistical data on one subinterface and not the other, verify that both subinterfaces (eth0.2 and eth0.3) are bound to SkipWare prior to starting SkipWare. You must restart SkipWare to initialize both subinterfaces for traffic to pass by entering the restart skipware command from the SkipWare configuration mode:
uut3-AXP(exec-skipware)> restart skipware
Step 6 After you restart SkipWare, reset all your statistics to verify traffic has started passing after restarting SkipWare:
uut3-AXP(exec-skipware)> stats reset
System stats now reset
uut3-AXP(exec-skipware)> 
Step 7 Send some traffic from a host on the LAN subnet located on ISR to a host on the other side of the WAN. If the solution is configured correctly, TCP traffic statistics start accumulating in SkipWare and you can list them by entering the stats lan and stats wan commands in SkipWare configuration mode.

SkipWare Commands

Table 1lists the commands that SkipWare Release 4.8.0.2 support in SkipWare configuration mode at the time that this document was published. For more information on these commands, refer to the Global Protocols Incorporated web site at the following URL: www.globalprotocols.com

Table 1 SkipWare Commands

Command

Description

app-services skipware

Enters SkipWare Configuration mode.

dsiplay

Displays logging data when display-buffering is enabled.

restart skipware

Stops and then starts SkipWare.

restore config defaults

Returns the SkipWare configuration to factory defaults.

set congestion-control

Configures congestion control to per-connection, rate-pacing, or error-tolerance. Default is per-connection.

set display-buffering

Enables and disables the display of SkipWare logging messages. Default is disabled.

set lan-rate

Configures the speed for the LAN interface. Default is 100Mbps.

set mtu-size

Configures the size of the largest packet for SkipWare. Valid values range from 68 to 1500 bytes. Default is 1500 bytes.

set wan-rate

Configures the speed for the WAN interface. Default is 20Mbps.

show configuration

Displays the current configuration information for SkipWare.

show congestion-controls

Displays the current congestion control mode: per-connection, rate-pacing, or error-tolerance.

show display-buffering

Displays if display buffering is enabled or disabled.

show lan-rate

Displays the speed for the LAN interface.

show mtu-size

Displays the size of the largest packet for SkipWare.

show version

Displays the version of the SkipWare software.

show wan-rate

Displays the speed for the WAN interface.

start skipware

Starts SkipWare.

stats lan

Displays statistics for the LAN TCP/IP connection.

stats reset

Resets all statistics.

stats socket

Displays socket-level statistics.

stats tcp

Displays TCP statistics.

stats wan

Displays statistics for the WAN TCP/IP connection.

stop skipware

Stops SkipWare.

Additional Documentation

In addition to the other publications mentioned in this document, the following publications are available on WAAS, SCPS, and other Cisco IOS features:

•Space Communications Protocol Specification (SCPS)—Transport Protocol (SCPS-TP)
http://public.ccsds.org/publications/archive/714x0b2.pdf

•Configuring Cisco WAAS Network Modules for Cisco Access Routers
http://www.cisco.com/en/US/partner/docs/app_ntwk_services/waas/waas/v403/module/configuration/guide/wsnmecfg.html

•Cisco IOS Software Releases 12.4 Mainline documentation suite,
http://www.cisco.com/en/US/products/ps6350/tsd_products_support_series_home.html

Glossary

Table 2 defines the acronyms and abbreviations used in this publication.

Table 2 Acronyms

Acronym

Expansion

ACL

Access Control List

AXP

Application Extension Platform

CEF

Cisco Express Forwarding

CLI

Command-Line Interface

DNS

Domain Name System

DRE

Data Redundancy Elimination

GPi

Global Protocols, Incorporated

IP

Internet Protocol

IPv4

Internet Protocol version 4

IPv6

Internet Protocol version 6

kbps

kilobits per second

MTU

Maximum transmission size

Mbps

megabits per second

SCPS

Space Communications Protocol Standards

SSH

Secure Shell

TCP

Transmission Control Protocol

TFO

Transport Flow Optimization

UDP

User Datagram Protocol

VLAN

Virtual LAN

WAAS

Wide Area Application Acceleration Services

WAE

Wide Area Application Engine

WAN

Wide Area Network

WCCP

Web Cache Communications Protocol

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

SkipWare is a register trademark of Global Partners International.

All other trademarks mentioned in this document or website 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. (0809R)

© 2008 Cisco Systems, Inc. All rights reserved.

Hierarchical Navigation

Cisco Application Extension Platform

WAAS/SkipWare ISR Solution Configuration Note

Downloads

Table Of Contents

WAAS/SkipWare ISR Solution Configuration Note

Traditional SCPS Networks

Cisco WAAS/SkipWare Integrated Solution

Hardware

Software

Traffic Flow

Configuring the ISR Router for the WAAS/SkipWare Solution

Configuring the WAAS Central Manager and FTP Server

Configuring the WAAS Network Module

Registering the WAAS Network Module with the WAAS Central Manager

Enabling WCCP on the ISR

Configuring the ISR to Redirect Traffic Using WCCP

Activating the WAAS Network Module

Configuring the AXP Network Module

Installing SkipWare on the AXP Network Module

Configuring SkipWare on the AXP Network Module

Configure Policy Based Routing on the ISR Router

Configuring the Remote ISR

Verifing WCCP

Verifying SkipWare is Functional

SkipWare Commands

Additional Documentation

Glossary

Obtaining Documentation, Obtaining Support, and Security Guidelines

SkipWare is a register trademark of Global Partners International.

All other trademarks mentioned in this document or website 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. (0809R)

© 2008 Cisco Systems, Inc. All rights reserved.