
33-6
Catalyst 3550 Multilayer Switch Software Configuration Guide
78-11194-09
Chapter 33 Configuring Web Cache Services By Using WCCP
Configuring WCCP
Enabling the Web Cache Service, Setting the Password, and Redirecting Traffic
Received From a Client
MD5 password security requires that the switch and cache engines be configured with the same
password. Each cache engine or switch authenticates the security component in a received WCCP packet
immediately after validating the WCCP message header. Packets failing authentication are discarded.
For WCCP packet redirection to operate, you must configure the switch interface connected to the client
to redirect inbound HTTP packets.
This procedure shows how to configure these features on routed ports. To configure these features on
SVIs, see the configuration examples that follow the procedure.
Beginning in privileged EXEC mode, follow these steps to enable the web cache service, to set a
password, to configure routed interfaces, and to redirect inbound packets received from a client to the
cache engine. This procedure is required.
Note
Before configuring WCCP commands, configure the SDM template, and reboot the switch. For more
information, see the
“Optimizing System Resources for User-Selected Features” section on page 7-27
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip wccp web-cache [password
encryption-number password]
Enable the web cache service on your switch. By default, this feature is
disabled.
(Optional) For [password encryption-number password], specify an
encryption number. The range is 0 to 7. Use 0 for not encrypted, and use
7 for proprietary. Specify a password name up to seven characters in
length. The switch combines the password with the MD5 authentication
value to create security for the connection between the switch and the
cache engine. By default, no password is configured, and no
authentication is performed.
You must configure the same password on each cache engine.
When authentication is enabled, the switch discards messages that are not
authenticated.
Step 3
interface interface-id
Enter interface configuration mode, and specify the interface connected
to the cache engine or the web server.
Step 4
no switchport
Enter Layer 3 mode.
Step 5
ip address ip-address subnet-mask
Configure the IP address and subnet mask.
Step 6
no shutdown
Enable the interface.
Step 7
exit
Return to global configuration mode. Repeat Steps 3 through 7 for each
cache engine and web server.
Step 8
interface interface-id
Enter interface configuration mode, and specify the interface connected
to the client.
Step 9
no switchport
Enter Layer 3 mode.
Step 10
ip address ip-address subnet-mask
Configure the IP address and subnet mask.
Step 11
no shutdown
Enable the interface.