Troubleshooting guide

1-9
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring AppNav
Prerequisites for AppNav Deployment
• epmap—Matches traffic for destination port 135
• HTTP—Matches traffic for destination ports 80, 3128, 8000, 8080, and 8088
• HTTPS—Matches traffic for destination port 443
• MAPI—Matches traffic for the MS RPC MAPI application (dynamic port assignment)
• NFS—Matches traffic for destination port 2049
• RTSP—Matches traffic for destination ports 554 and 8554
• class-default—Matches any TCP traffic (this class map cannot be edited or deleted)
If you use the Central Manager AppNav Cluster Wizard to create an AppNav Cluster, the wizard creates
a default policy named appnav_default. This policy is assigned by default to all ANCs in a cluster and
contains only the class-default policy rule that has the following characteristics:
• Matches class-default (any TCP) traffic.
• Distributes class-default traffic to the default WNG, which includes all WNs created by the wizard,
with no backup WNG specified.
• Contains the waas_app_default nested policy, which provides application monitoring for each of the
default class maps, except video (RTSP).
When you use the Central Manager to define a policy rule for any class that uses peer matching or
source or destination IP address matching (but not port matching), it automatically adds the
waas_app_default policy as a nested policy. The waas_app_default policy is created by the system
and monitors all application accelerators (except video), so you do not need to manually add
application accelerator monitoring to your policy rules, unless it is for the video accelerator.
If you do not use the Central Manager AppNav Cluster Wizard to create a cluster, there is no default flow
distribution, so if an incoming flow does not match any class in the AppNav policy, it is not distributed
to any WNG; instead, it is passed through.
If a WNG is defined but is not used in any policy rule, it does not receive any flows. If a policy is defined
but not applied to an ANC, it does not take effect.
The default action for a policy rule is none, which is context dependent: in a top level policy it means
pass through and if the policy is nested, it means inherit the parent policy rule action.
Prerequisites for AppNav Deployment
AppNav has the following prerequisites:
• Each WAAS appliance to be used as an AppNav Controller must contain a Cisco AppNav Controller
Interface Module.
• Each AppNav Controller must be configured in appnav-controller device mode.
Guidelines and Limitations
AppNav has the following configuration guidelines and limitations:
• An AppNav Cluster can contain a maximum of the following:
– 8 ANCs
– 32 WNs