Configuring WCCP
Web Cache Communication Protocol (WCCP) is a Cisco-developed content-routing protocol that provides a mechanism to redirect traffic flows in real-time. The FortiADC supports Version 2 (WCCPv2).
With WCCP, the FortiADC can forward client traffic to WCCP compatible devices, where additional actions will be performed (that are not native to the FortiADC), and then, after undergoing these processes, the traffic will be sent back to the FortiADC.
To configure a WCCP object:
- Go to System > WCCP.
- Click Create New to display the configuration editor.
- Complete the configuration according to the table below.
- Click save.
- Go to Networking > Interface. Select an interface and open the dialogue.
- Under Mode Specifics, find the WCCP button, and click On. (Default is off).
- Click save.
- Go to Server Load Balance > Virtual Server.
- Select a virtual server. Go to Monitoring.
- Enable the WCCP button, click on.
|
Only Layer 7 Virtual Servers are supported. |
| Settings | Description |
|---|---|
|
Service ID |
Name of the service group. Range 0-255. |
|
Authentication |
|
|
Forward Method |
|
|
Return Method |
|
|
Assignment Method |
Defines which assignment method the FortiADC prefers:
|
Group Address . |
IP multicast address used by the cache routers. The default, 0.0.0.0, means the FortiADC will ignore multicast WCCP traffic. Otherwise, set the address between 244.0.0.0 to 239.255.255.255. |
|
Router ID |
IP address known to all cache engines, and identifies an interface on the FortiADC to the cache engines. If all cache engines connect to the same FortiADC interface, use the default address of 0.0.0.0. However, if the cache engines can connect to different FortiADC interfaces, you must set router-id to a specific IP address, which must then be added to the configuration of the cache engines that connect to that interface. |
|
Server List |
IP address and netmask for up to four cache servers. |