HP StorageWorks Enterprise File Services WAN Accelerator 2.1.5 deployment guide (June 2006)

64 7 - WCCP DEPLOYMENTS
Introduction to WCCP
WCCP was originally implemented on Cisco routers, multi-layer switches, and Web
caches to redirect HTTP requests to local Web caches (Version 1). Version 2, which is
implemented on HP EFS WAN Accelerators, can redirect any type of connection from
multiple routers to multiple Web caches.
You configure WCCP to redirect traffic to an HP EFS WAN Accelerator or group of
HP EFS WAN Accelerators:
 so that the HP EFS WAN Accelerators do not have to be physically in-path but
can be virtually in-path. That is, the HP EFS WAN Accelerators are configured to
be physically out-of-path devices while optimizing traffic as if they were in-path
devices.
 to redirect traffic to an HP EFS WAN Accelerator or group of HP EFS WAN
Accelerators to provide load balancing and failover support.
You can configure WCCP on the client-side HP EFS WAN Accelerator or the server-
side HP EFS WAN Accelerator. They can be in-path devices or out-of-path devices,
depending on your network environment.
The following figure illustrates WCCP configured on the client-side and an out-of-
path HP EFS WAN Accelerator on the server-side. This is an example of one type of
WCCP deployment. Contact HP technical support for further information at http://
www.hp.com.
Figure 7-1. Basic WCCP Configuration
The following steps describe how WCCP works with the HP EFS WAN Accelerator:
1. Routers and HP EFS WAN Accelerators are added to the same service group.
2. HP EFS WAN Accelerators announce themselves to the routers.
3. Routers send back the state of the service group.
4. One HP EFS WAN Accelerator takes a leadership role and tells the routers how to
redirect traffic among the HP EFS WAN Accelerators in the service group.