WCCP was initially designed as a component of Cisco IOS Software whose purpose was to intercept HTTP traffic traversing a router and redirect that traffic to a local cache with the aim of reducing access times to websites and conserving wide area link upstream bandwidth. With the introduction of WCCPv2, the scope of the protocol widened to include traffic types other than HTTP, allowing the protocol to be used as a more general interception mechanism. In WCCPv2 clients specify the nature of the traffic to be intercepted and forwarded to external devices, which are then in a position to provide services, based upon the traffic type, such as WAN optimization and application acceleration.
WCCP v2 protocol
WCCP v2 specifies interactions between one or more WCCP servers and one or more WCCP clients. The WCCP server role can be performed by some intelligent router device; the WCCP client could be a content caching engine or some other service delivering appliance. The purpose of the interaction is to establish and maintain the transparent redirection of selected types of traffic flowing through a router or group of routers. The selected traffic is redirected to a cache engine or group of caches with the aim of providing some kind of service such as optimizing network resource usage, lowering response times, improving security and so on. WCCP transparently redirects a variety of traffic types, specified by protocol (TCP or User Datagram Protocol [UDP]) and port. End users do not know that the page came from the cache engine rather than from the originally requested web server.
WCCP best practices for WAAS deployment
Use WCCP GRE encapsulation when working with routers because most routers do not support L2 redirection. Use WCCP L2 Redirection as the packet forwarding method when working with switches or Cisco 7600 series routers, because redirection can be performed in hardware. This approach minimizes the CPU workload on the Cisco WAE and the switch, and can improve overall performance.
Do not use the default mask when using Mask Assignment.
Branch Mask Value: In a branch office, source IP addresses are typically assigned sequentially by DHCP. This results in addresses that vary only in the least significant bits. Mask distribution can be maximized here by specifying a WCCP mask in the range of 0x1 thru 0x7F depending on the number of WAAS devices.
Data Center Mask Value: In a large enterprise network address allocation scheme, these subnets vary in the third tuple of the IP address quadruple (/24 address mask) so the WCCP mask can be specified between 0xF00 thru 0x7F00.For a large Data Center with /16 address mask for branch locations, use WCCP masks in the range of 0xF0000 and 0x7F0000.
For topologies, where Path Affinity needs to be maintained between the WCCP router/switch and WAAS, use WCCP GRE Return or Generic GRE as the WAAS Egress Method.
For Catalyst 6500/7600 platforms which does GRE in the hardware, use Generic GRE as the Egress Method for Path Affinity requirement, instead of using WCCP GRE Return
Incase if WCCP weight factors are used, to guarantee complete WCCP failover coverage, use weight factors for individual devices that are greater than 100.
Avoid specifying tcp ports as part of an ACL for WCCP Redirect List. This can cause severe issues if the network configuration results in any packet fragmentation.
Instead of using Static Bypass Feature of WAAS, apply WCCPv2 redirect list ACLs on the router/switch wherever possible to prevent unnecessary processing and packet routing on the router/switch.
While configuring WCCP on the Router, it is always recommended to enable IP CEF on the router.
The following best practices should be followed for implementing WCCP on a hardware-based platform: L2 Forwarding;Mask Assignment; Inbound Interception; No "ip wccp redirect exclude in"; WAAS Egress Method: IP Forwarding, Generic GRE (Cat6k PFC-based systems only)
Before placing any "ip wccp redirect out" CLI command on a router interface, always check to make sure you have already placed an "ip wccp exclude in" on the interface through which the WAAS WAEs will return traffic to the router. Failure to do this may result in total loss of connectivity with the router.
Hello all, We'd like to upgrade our 2 Nexus 5672UP switches from version 7.3(2) to 7.3(8). 6 FEX's are single-attached to these devices. 3 to nexus 1 and 3 to nexus 2. They're thus not connected in a vPC. The question is now: is it recommended t...
Hello, Need migration assistance. I have double sided vpc between POD core(N7706) and multiple Pod Access switches(N9ks) and HSRP resides alongwith STP primary on Pod Core 7706s. I need ...
Hi.. I installed aci simulator (4.26o) on vm. Then, I upload aci app (Citrix_ADCManager) by apic gui. However the installation failed... like below Could I test ACI app (stateful or stateless) by aci simulator? is it possib...
I have just deployed DNCM within a small greenfield DC environment. Thus far , I have been able to discover my switches and have them populate within my inventory of fabric switches. However, when I go in to actually push out my created fabric template I ...
Hello,I have a couple of DC power supplies for our 9396px switches - UCSC-PSU-930WDC, however, they are now obsolete and the replacement product is UCSC-PSU2V2-930DC.Does anybody know if UCSC-PSU2V2-930DC is compatible with 9396px given the fact...