The cache engines in service group specify traffic to be redirected by protocol (TCP or UDP) and port
(source or destination). Each service group has a priority status assigned to it. Packets are matched
against service groups in priority order.
Support for Multiple Routers
WCCPv2 allows multiple routers to be attached to a cluster of cache engines. The use of multiple routers
in a service group allows for redundancy, interface aggregation, and distribution of the redirection load.
WCCPv2 provides optional authentication that enables you to control which routers and cache engines
become part of the service group using passwords and the HMAC MD5 standard. Shared-secret MD5
one-time authentication (set using the ip wccp [password [0-7] password] global configuration
command) enables messages to be protected against interception, inspection, and replay.
Web Cache Packet Return
If a cache engine is unable to provide a requested object it has cached due to error or overload, the cache
engine will return the request to the router for onward transmission to the originally specified destination
server. WCCPv2 provides a check on packets that determines which requests have been returned from
the cache engine unserviced. Using this information, the router can then forward the request to the
originally targeted server (rather than attempting to resend the request to the cache cluster). This
provides error handling transparency to clients.
Typical reasons why a cache engine would reject packets and initiate the packet return feature include
WCCPv2 can be used to adjust the load being offered to individual cache engines to provide an effective
use of the available resources while helping to ensure high quality of service (QoS) to the clients.
WCCPv2 allows the designated cache to adjust the load on a particular cache and balance the load across
the caches in a cluster. WCCPv2 uses three techniques to perform load distribution:
By using these hashing parameters, you can prevent one cache from being overloaded and reduce the
potential for congestion.
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide—Release 12.1 E
Instances when the cache engine is overloaded and has no room to service the packets
Instances when the cache engine is filtering for certain conditions that make caching packets
counterproductive (for example, when IP authentication has been turned on)
Hot Spot Handling—Allows an individual hash bucket to be distributed across all the cache engines.
Prior to WCCPv2, information from one hash bucket could only go to one cache engine.
Load Balancing—Allows the set of hash buckets assigned to a cache engine to be adjusted so that
the load can be shifted from an overwhelmed cache engine to other members that have available
Load Shedding—Enables the router to selectively redirect the load to avoid exceeding the capacity
of a cache engine.
Configuring Web Cache Services Using WCCP