Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Application Acceleration

From DocWiki

Jump to: navigation, search

This article describes a general troubleshooting methodology for all application accelerators.

Guide Contents
Main Article
Understanding the WAAS Architecture and Traffic Flow
Preliminary WAAS Troubleshooting
Troubleshooting Optimization
Troubleshooting Application Acceleration
Troubleshooting the CIFS AO
Troubleshooting the HTTP AO
Troubleshooting the EPM AO
Troubleshooting the MAPI AO
Troubleshooting the NFS AO
Troubleshooting the SSL AO
Troubleshooting the Video AO
Troubleshooting the Generic AO
Troubleshooting Overload Conditions
Troubleshooting WCCP
Troubleshooting AppNav
Troubleshooting Disk and Hardware Problems
Troubleshooting Serial Inline Clusters
Troubleshooting vWAAS
Troubleshooting WAAS Express
Troubleshooting NAM Integration


WAAS provides several application accelerators (also known as AOs) that accelerate various TCP protocols such as CIFS, HTTP, NFS, EPM, MAPI, SSL, and live streaming video (RTSP). These application accelerators do not accelerate specific applications, but rather they accelerate any application that uses the specified protocol.

This article describes a general troubleshooting methodology for all AOs.

General Troubleshooting Methodology for AOs

The following general troubleshooting methodology applies to all AOs:

  1. Verify the AO configuration and operational state.
  2. Verify the Application Traffic Policy configuration for the AO.
  3. Check the global and AO-specific statistics.
  4. Verify that connections are handled/optimized by the AO.
  5. Debug and trace connection-specific AO statistics.

To verify the configuration and operational status of all AOs, use the show accelerator and show license commands as shown in Figure 1.

Figure 1. Verifying All Accelerator Status

For specific information on troubleshooting individual AOs, see the following articles:

Rating: 5.0/5 (1 vote cast)

Personal tools