Q:What is WCCP (web cache communication protocol)?
A:To make it simple WCCP is a protocol running between a router and a network appliance for allowing safer and smarter redirection of traffic.
Q:When you say network appliance what do you mean?
A: In WCCPv1 the protocol was used only for redirection of web traffic (and only TCP port 80) so it was clearly very limited for web application (hence the name), however since WCCPv2 the usage and capability expended and WAN optimization devices (WAAS, Riverbed SteelHead etc.) Security Appliances (Cisco WSA, Bluecoat WAF etc.) are using WCCP to receive traffic for optimization or content security handling.
Q: What are the main components of WCCP?
A: That is an Excellent Question :-) , well
- Redirector - The Router or group of routers
- Web Cache - That is the misleading part as is called a web cache but as mention above the network appliance can be also appliance that is performing MAPI or CIFS optimization, note that also the web cache function can be a cluster of Web Cache Engines that get traffic based on assignment method (lets elaborate on that later...)
Q: What are the responsibilities of the Redirector and Web Cache?
A: It seems like we are on the same page as you have some grate questions
- Redirector Jobs
- Listen for Web Cache Registration/s
- Intercept trafic according to configuration
- Redirect to the relevant Cache Engine according to the calculated assignment (again, we will elaborate later) in case there are multiple
- There are 2 redirection methods (L2/GRE)
- Maintain state by simply exchange control messages
- Web Cache Jobs
- Register to a Redirector list (one or more)
- Maintain state by simply exchange control messages
- Receive traffic from Redirector handle and send it to its destination
A: When redirector want to redirect traffic first he need to know to who he can send the traffic and if the web cache is active and ready to receive the traffic, and from the other end the web cache want to know who is going to send him traffic and tell him what he allowed to send (if he want to limit him)
That state is maintained with messages that are exchanged
Web Cache - send HERE_I_AM
Redirector - react with I_SEE_YOU
pic1: in the following you can see and example of packet capture between Redirector to Web Cache Engine
Q: You mention also something about redirection method (GRE/L2)?
A: I see you keep tracking , so yes! there are 2 Redirection methods L2 and GRE
GRE - as it sounds the router will create a GRE tunnel it will use to send traffic over to the Web Cache, the Web Cache return traffic can be L2 or Generic GRE (WAAS implementation)
L2 - simply mean traffic that need to be redirected the router will re-write the MAC destination to the Web Cache MAC address.
Show command over the router, you can see that Service ID 61 there is 1 Web Cache 1 Router Assignment HASH and redirection is GRE:
C881-K9-IL1#sh ip wccp summary
WCCP version 2 enabled, 2 services
Service Clients Routers Assign Redirect Bypass
------- ------- ------- ------ -------- ------
Default routing table (Router Id: 172.24.190.113):
61 1 1 HASH GRE GRE
62 0 0 HASH/MASK GRE/L2 GRE/L2
Q: What is HASH and MASK ?
A: The WCCP was intended to provide a scalable and robust way of redirection traffic allowing high amount of traffic to load share between multiple Cache Engines and the Algorithm used to perform load sharing is either by HASH (default in most routers) or MASK (default mostly in L3 Switches)
Q: Almost forgot , what is service ID 61 62...?
A: As you remember the WCCP started to allow only TCP port 80 redirection however as there requirement modified there was a need to make it more flexible by allowing what is called dynamic service groups, the service group can define ports and redirection assignments based on source / destination...
Q: Why do I need 2 or more groups?
A: Some of the Cache Engines like WAAS are doing what is called transparent proxy , that mean that traffic sent from Client to Origin (Web Server) will keep the IP SRC/DST, so if traffic will be redirected only when sent from Client to Origin the return traffic will not be intercepted and it will be an asymmetric TCP connection that will be eventuality terminated as although the session is transparent TCP ports and seq/ack are not and both Client and Server will see that they are not actually talking to each other both directions, so now you will ask me so why not just set the same Service to intercept both direction, that is a good question and the answer is each Service Group has an assignment that determine to which Web Cache to Send the traffic , if you set the same HASH to both sides your traffic may return to the Wrong Web Cache so in order for traffic to return to the same Cache Engine you need to have the flip side of the Assignment
ip wccp source-interface Loopback0
ip wccp 61
ip wccp 62
ip address 184.108.40.206 255.255.255.255
ip address 220.127.116.11 255.255.255.252
ip wccp 62 redirect in
ip address 18.104.22.168 255.255.255.0
ip wccp 61 redirect in
description “WAAS Segment”
ip address 22.214.171.124 255.255.255.252
Note: That Cisco have a default preconfigured behavior for SID 61 and 62
61 : hash is based on source IP
62 : hash is based on destination IP
OK Folks hope that provide some clarity and understanding, WCCP is really not very scary and very useful protocol :-)
Note: there are some excellent info in Cisco and also some limitation with platforms but I wanted to make sure first that there is clarity to the fundamentals