The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This guide provides an overview of the ISR-WAAS and AppNav-XE component on Cisco ISR 4451-X in Cisco IOS-XE Release 3.9, and describes the quick start process to easily configure the features. It also provides details of the CLI commands along with examples and troubleshooting tips.
The WAAS solution for Cisco ISR 4451-X includes the following:
The AppNav-XE component is made up of a distribution unit called the AppNav Controller and service nodes. The AppNav Controller distributes flows and the service nodes process the flows. Additionally up to four AppNav Controllers can be grouped together to form an AppNav Controller group to support asymmetric flows and high availability. Note that all the routers in the AppNav Controller group need to be the same platform and also have the same memory capacity.
The advantages of using the AppNav-XE component are:
The AppNav component can interoperate with the following features on the router:
The AppNav-XE component introduces the concept of a virtual interface, which allows users to configure features specific to compressed or uncompressed traffic. For instance, to monitor the traffic that is being redirected to the service node and the traffic that is returning from the service node, you can configure the FNF feature on the AppNav-UnCompress and AppNav-Compress virtual interfaces. Note that these AppNav-XE virtual interfaces appear to the user just as any other interface. However from the above list, the only features that work on the AppNav-XE virtual interfaces are FNF, ACL, and QoS (except for queueing).
Note the following points regarding configuring the AppNav-XE component:
For additional information and caveats about configuring the AppNav-XE component, see Chapter 3, “Detailed Configuration”.
The AppNav service node auto discovery feature is targeted for small branch installations. With this feature, the system automatically discovers the service nodes within the same L2 connectivity of the AppNav router and adds them to the service node cluster.
The AppNav service node auto discovery feature can only be enabled on one interface on a service node.
To enable the AppNav service node auto discovery feature, do the following:
Step 1 Initiate a discovery request on the AppNav-XE component on the router by doing the following:
a. Determine the service node group for which you want to enable the auto discovery.
b. Issue the following commands:
Step 2 Initiate a service respond on the service nodes by doing the following:
a. On the WAAS appliance, determine the interface for which you want to enable node discovery. This interface must be in the same subnet as the AppNav Controller.
b. Enable node discovery by issuing the following commands:
The term “container” refers to the KVM hypervisor that runs virtualized applications on the Cisco ISR 4451-X. The term “host” refers to the primary operating system running on a system. For ISR-WAAS on Cisco ISR 4451-X, the host is defined as a Cisco ISR 4451-X running on Cisco IOS XE Release 3.9.
The Virtualization Manager tasks vary depending on the phase of the virtual service deployment. Table 1-1 summarizes this information.
Table 1-1 Virtualization Manager Tasks
ISR-WAAS is a virtualized WAAS instance running on a Cisco IOS-XE container on a Cisco ISR 4451-X platform. ISR-WAAS provides WAN optimization functionality to the Cisco ISR 4451-X.
The Cisco ISR 4451-X does not support RAID.
ISR-WAAS can run on a Cisco ISR 4451-X router with these minimum requirements:
The Cisco ISR 4451-X requires more resources depending on the ISR-WAAS profile that you install. See Table 1-2 .
Table 1-2 Profile Specifications
|
|
|||||||
---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
To deploy both the ISR-WAAS and the AppNav-XE component on the Cisco ISR 4451-X, use the appxk9 package license.
Step 1 Enter the licensing command as follows:
Step 2 Reload the router using the following command:
Step 3 Enter the show license detail command as follows:
Step 4 To verify that the license is enabled, review the output of the command. Verify that the appxk9 package license is active and in use. The output for “Feature: appxk9” should show “License State: Active, In Use”. Here is an example:
To upgrade/downgrade the Cisco 4461 ISR running WAAS software for different versions of Cisco IOS XE, Cisco recommends the following steps.
Note Cisco 4461 ISR supports ISR-WAAS installation only from WAAS 6.4.1b release.
For the Cisco 4461 running Cisco IOS XE Fujie 16.9.1 release, follow these steps:
Step 1 Install ISR-WAAS version 6.4.1b using the service waas enable command. The appropriate OVA file should be on the flash drive of the Cisco 4461 ISR.
Step 2 To upgrade from WAAS 6.4.1b to WAAS 6.4.3, use the bin image (copy ftp/http install) process using the CLI or Central Manager.
Step 3 To downgrade back to WAAS 6.4.1b, uninstall the current version using the service waas disable command and install a new image of WAAS using step 1 above.
To upgrade/downgrade an ISR-4451-X running WAAS software for different versions of Cisco IOS XE, Cisco recommends the following steps.
For the Cisco ISR 4451-X running Cisco IOS-XE 3.9 release, follow these steps:
Step 1 Install ISR-WAAS version 5.2 using the service waas enable command. The appropriate OVA file should be on the flash drive of the Cisco ISR 4451-X.
Step 2 To upgrade from WAAS 5.2 to WAAS 5.3, use the bin image (copy ftp/http install) process using the CLI or Central Manager.
Step 3 To downgrade back to WAAS 5.2.1, uninstall the current version using the service waas disable command and install a new image of WAAS using step 1 above.
For the Cisco ISR 4451-X running Cisco IOS-XE 3.10 release, follow these steps:
Step 1 Install ISR-WAAS version 5.3 only. Do not downgrade IOS-XE to earlier versions.
Step 2 If IOS-XE 3.9 version is required, first uninstall WAAS 5.3 using the service waas disable command, then downgrade IOS-XE 3.10 to version 3.9.
Step 3 Enable WAAS 5.2 using the appropriate OVA file and the service waas enable command.