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 AppNav-XE component on the Cisco Cloud Services Router (CSR) 1000V Series in Cisco IOS-XE Release 3.9, and describes the quick start process to easily configure the features. It also provides details of the command line interface (CLI) commands along with examples and troubleshooting tips.
The AppNav-XE solution for the Cisco Cloud Services Router 1000V Series includes the following:
Note | The WAAS service nodes are external to the Cisco CSR and their details are outside the scope of this document. |
Note | You can also use WCM to configure and monitor the WAAS service nodes but those details are outside the scope of this document. |
The AppNav-XE solution for the Cisco ASR 1000 Series Aggregation Services Router (called Cisco ASR 1000 Series) includes the following:
Note | The WAAS service nodes are external to the Cisco ASR 1000 Series and their details are outside the scope of this document. |
Note | You can also use WCM to configure and monitor the WAAS service nodes but those details are outside the scope of this document. |
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-XE 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 1, “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-XE router and adds them to the service node cluster.
Restriction
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:
1. Initiate a discovery request on the AppNav-XE component on router by doing the following:
2. Initiate a service respond on the service nodes by doing the following:
Step 1 |
Initiate a discovery request on the AppNav-XE component on router by doing the following: |
Step 2 |
Initiate a service respond on the service nodes by doing the following: |
The AppNav feature will be available in the premium package, but in the Cisco IOS-XE 3.9 release, it is not enforced.
The AppNav feature will be available in the Advanced IP Services (AIS) and Adventerprise (AES) packages, but in the Cisco IOS-XE release 3.9, it is not enforced.