Troubleshooting guide

1-27
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Configuring Traffic Interception
Configuring WCCP on WAEs
• The maximum wait time (specified through the Shutdown Delay field in the WCCP Configuration
Settings window or with the wccp shutdown max-wait command [by default, 120 seconds]) has
elapsed for WCCP Version 2.
During a clean shutdown of WCCP, the WAE continues to service the flows that it is handling, but it
starts to bypass new flows. When the number of flows goes down to zero, the WAE takes itself out of the
group by having its buckets reassigned to other WAEs by the lead WAE. TCP connections can still be
broken if the WAE crashes or is rebooted without WCCP being cleanly shut down.
You cannot shut down an individual WCCP service on a particular port on a WAE; you must shut down
WCCP on the WAE. After WCCP is shut down on the WAE, the WAE preserves its WCCP configuration
settings.
Configuring Static Bypass Lists for WAEs
Note Static bypass lists are supported only for devices (but not device groups) using WAAS versions earlier
than 5.0 and are deprecated for such devices. Interception ACLS are recommended instead.
Using a static bypass allows traffic flows between a configurable set of clients and servers to bypass
handling by the WAE. By configuring static bypass entries on the branch WAE, you can control traffic
interception without modifying the router configuration. IP access lists may be configured separately on
the router to bypass traffic without first redirecting it to the branch WAE. Typically, the WCCP accept
list defines the group of servers that are accelerated (and the servers that are not). Static bypass can be
used occasionally when you want to prevent WAAS from accelerating a connection from a specific client
to a specific server (or from a specific client to all servers).
Note We recommend that you use ACLs on the WCCP-enabled router where possible, rather than using static
bypass lists or interception ACLs on the WAEs, because that is the most efficient method to control
traffic interception. If you decide to use static bypass lists or interception ACLs, we recommend using
interception ACLs because they are more flexible and give better statistics about passed-through
connections. For information about how to configure ACLs on a router, see the “Configuring IP Access
Lists on a Router” section on page 1-9. For information about how to configure an interception ACL for
a WAE, see the “Configuring Interception Access Control Lists” section on page 1-28.
To configure a static bypass list for a version 4.x WAE, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name.
Step 2 Choose Configure > Interception > Bypass Lists.
Step 3 In the taskbar, click the Create New WCCP/Inline Bypass List icon. The Creating new WCCP/Inline
Bypass List window appears.
Step 4 In the Client Address field, enter the IP address for the client.
Step 5 In the Server Address field, enter the IP address for the server.
Step 6 Check Submit to save the settings.
To configure a static bypass list from the CLI, you can use the bypass static global configuration
command.