1-4
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring AppNav
Information About AppNav
Interfaces on the AppNav Controller Interface Module can have three functions:
• Interception—Used to receive traffic intercepted from the network and egress traffic to the network.
The interception interface is implied based on the AppNav Controller placement and does not
require explicit configuration for this function.
• Distribution—Used to distribute traffic to the WNs and receive egressed traffic from the WNs. The
distribution interface is explicitly configured as the cluster interface for intra-cluster traffic and must
be assigned an IP address.
• Management—A management interface can be optionally and exclusively designated for
management traffic and isolated from the normal data path. We recommend that you use one of the
appliance’s built-in interfaces for management traffic and reserve the high performance interfaces
on the AppNav Controller Interface Module for interception and distribution.
You should use separate interfaces for interception and distribution for best performance, but you can
use the same interface for both functions.
AppNav Controller Interface Modules support port channel and standby logical interfaces. A port
channel allows you to increase the bandwidth of a link by combining multiple physical interfaces into a
single logical interface. A standby interface allows you to designate a backup interface in case of a
failure.
Interfaces on the AppNav Controller Interface Module support the following:
• A maximum of seven port channels with up to eight physical interfaces combined into a single port
channel group.
• A maximum of five bridge groups configured over the physical or logical interfaces.
Interfaces on the AppNav Controller Interface Module do not support the following:
• Fail-to-wire capability
• Bridge virtual interfaces (BVIs)
AppNav Policy
The AppNav policy is a flow distribution policy that allows you to control how ANCs distribute traffic
to the available WNs.
The AppNav policy consists of class maps that classify traffic according to one or more match conditions
and a policy that contains rules that specify distribution actions to WNGs for each of the classes.
This section includes the following topics:
• Class Maps, page 1-4
• Policies, page 1-5
• Nested Policies, page 1-6
• Site and Application Affinity, page 1-6
• Default Policy Behavior, page 1-8
Class Maps
AppNav class maps classify traffic according to one or more of the following match conditions:
• Peer device ID—Matches traffic from one peer WAAS device, which could be handling traffic from
a single site or a group of sites.
Comments to this Manuals