It is easy to troubleshoot a WAAS application problem if you follow these steps.
First, we need to gather information about the problem
You can check whether the problem is in all applications or one application (i.e. CIFS, HTTP)
You can get the details of client IP, server IP, port details, and application details.
Find out if the problem is with one site or multiple sites. If a single site focuses more on the Branch side, and if multiple sites primarily focus on the DC side, it is more likely that they are both wrong.
Now, we need to identify the traffic flow
Assuming that multiple users are having problems with a single application/multiple applications on a single site, we will focus on the site WAE. Check if the connection is being optimized using WAAS or pass through using commands. Show statistics connection or Show stats client-ip Src ip address>. The red circle in fig-1 shows the type of optimization.
Let’s now look at the troubleshooting steps
We assume that you have checked the interface error and duplex settings on the WAE port. WCCP is redirecting traffic to WAE. Failures will affect all applications passing through WAE.
At the application (AO) Level:
If you are connecting to an AO, the following command will show you the statistics.
If dropped connections indicate a problem with AO, check the values. If the problem is not resolved, you can try to bypass AO by using custom policy or shutting down AO.
Here are the steps to create a custom policy
Step 1 – Create an application definition: This identifies the general information about your application.
Go to WAAS CMS at https://xyz.443 : Select Applications in Configure Menu. To create an application definition
Step 2: Creating an App Policy: This is what determines the action that a WAAS device will take on the traffic specified.
Go to WAAS CMS and select the WAE you wish to Define the policy. Go to MYWAN-> Manage Device -> Select WAE Edit
Step 2.1: Creating and classifying the data
Step 2.2: Create a Classifier Condition that is Matching
After creating the policy, you can use the WAE#Show connections client-ip details command: Command and verify that the connection will show either pass-through (or TFO) depending on the action you have defined in your custom policy.
Shut down a particular AO
This is used if the problem is not resolved by custom policy.
This will impact all connections related to a specific application.
If the problem persists, bypass the connection to WAE: –
Bypass WAE is the connection:
This means that you are not allowing traffic to use the WAE optimization technique. Pass-through traffic without optimization: Use the following
# Bypass static WAE (conf.t)
The following command can be used to see the pass-through connections:
If this does not solve the problem, then it is not WAE’s fault. You can also try to diagnose the problem with another prospect and involve an application team. Ethereal is used to further analyze the traffic.