
33-5
Catalyst 3550 Multilayer Switch Software Configuration Guide
78-11194-09
Chapter 33 Configuring Web Cache Services By Using WCCP
Configuring WCCP
Configuring WCCP
These sections describe how to configure WCCP on your switch:
•
Default WCCP Configuration, page 33-5
•
WCCP Configuration Guidelines, page 33-5
•
(required)
Default WCCP Configuration
shows the default WCCP configuration.
WCCP Configuration Guidelines
Before configuring WCCP on your switch, make sure to follow these configuration guidelines:
•
Do not configure the cache engine for GRE because the switch does not support traffic forwarding
by using GRE. For more information, refer to the documentation that shipped with the cache
engines.
•
Make a direct Layer 2 connection from the cache engines to the switch so that the switch can
perform Layer 2 rewrites for WCCP redirection. The Cisco Cache Engines require the use of a Fast
Ethernet interface for a direct connection. You also can connect the switch to the cache engine by
using a 10/100/1000 port if the connection is a direct Layer 2 connection.
•
Connect up to 32 cache engines to a single Catalyst 3550 switch.
•
Connect only one Catalyst 3550 switch to multiple cache engines. Do not connect multiple
Catalyst 3550 switches to multiple cache engines.
•
Configure the switch interfaces that are connected to the web clients, the cache engines, and the web
server as Layer 3 interfaces (routed ports and switch virtual interfaces [SVIs]). For HTTP packet
redirection to work, the servers, cache engines, and clients must be on different subnets.
•
Do not configure the clients, cache engines, or web servers on the same switch interface.
•
Do not configure the switch with both WCCP and multiple VPN routing/forwarding (multi-VRF)
instances in customer edge (CE) devices.
•
Modify the Switch Database Management (SDM) template to enable the switch to support 144-bit
Layer 3 TCAM by using the sdm prefer extended-match, sdm prefer access extended-match, or
sdm prefer routing extended-match global configuration command. For more information on the
SDM templates, see the
“Optimizing System Resources for User-Selected Features” section on
•
Do not configure WCCP and policy-based routing (PBR) on the same switch interface.
Table 33-1 Default WCCP Configuration
Feature
Default Setting
WCCP enable state.
WCCP services are disabled.
Protocol version.
WCCPv2.
Redirecting traffic received on an interface.
Disabled.