56-2
Catalyst 6500 Series Switch Software Configuration Guide—Release 8.7
OL-8978-04
Chapter 56 Configuring the MSFC Cisco IOS Features
WCCP
IP-in-IP Configuration Guidelines
This section describes the guidelines for configuring IP-in-IP tunneling:
•
Each hardware-assisted tunnel must have a unique source.
•
Hardware-assisted tunnels cannot share a source even if the destinations are different.
•
Use secondary addresses on loopback interfaces or create multiple loopback interfaces.
•
Each tunnel interface uses one internal VLAN.
•
Each tunnel interface uses one additional router MAC address entry per router MAC address.
•
The PFC3A does not support any PFC QoS features on tunnel interfaces.
•
The PFC3B and PFC3BXL support PFC QoS features on tunnel interfaces.
•
The PFC3 does not support GRE tunnel encapsulation and deencapsulation of multicast traffic.
•
The MSFC3 supports tunnels that are configured with egress features on the tunnel interface.
Examples of egress features are output Cisco IOS ACLs, NAT and PAT (for inside-to-outside
translation), TCP intercept, context-based access control (CBAC), and encryption.
WCCP
The Web Cache Communication Protocol (WCCP) allows you to redirect traffic to a cache engine (web
caches) and manage cache engine clusters (cache farms).
Note
•
Release 12.2(17d)SXB1 and later releases support WCCP on Supervisor Engine 2.
•
Release 12.2(18)SXD1 and later releases support WCCP on Supervisor Engine 720.
•
To use the WCCP Layer 2 PFC redirection feature, configure WCCP on the Catalyst 6500 series
switch as described in this chapter and configure accelerated WCCP on the cache engine as
described in the following publication:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/acns/v42/configuration/guide/transprt.html
•
A future release of Cisco Application and Content Networking System (ACNS) software, Release
4.2.2 and later releases support the
ip wccp
service
accelerated
command with a PFC2.
Because the WCCP service group list is scanned in the order in which service groups are created, not by
priority, with multiple dynamic WCCP services defined the traffic that matches the selection criteria for
more than one service group is not redirected to the service group with the highest priority. This problem
is resolved in Release 12.2(18)SXE.