|
Table Of Contents
Web Cache Communication Protocol Version 2
Redirection for Multiple TCP Port Destined Traffic
Load Distributing Applications
Client IP Address Transparency
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring a Service Group Using WCCP Version 2
Running a Reverse Proxy Service
Registering a Router to a Multicast Address
Informing a Router of Valid IP Addresses
Setting a Password for a Router and Cache Engines
Disabling Caching for Certain Clients
Verifying WCCP Configuration Settings
Monitoring and Maintaining Using WCCP Version 2
Performing a General WCCP Version 2 Configuration
Running a Reverse Proxy Service
Registering a Router to a Multicast Address
Informing a Router of Valid IP Addresses
Setting a Password for a Router and Cache Engines
Disabling Caching for Certain Clients
Web Cache Communication Protocol Version 2
This appendix describes the Web Cache Communication Protocol (WCCP) Version 2 feature. It includes information on the benefits of this new feature, supported platforms, and other information you may need to work with WCCP Version 2.
•Feature Overview
•Supported Platforms
•Supported Standards, MIBs, and RFCs
•Prerequisites
•Configuration Tasks
•Monitoring and Maintaining Using WCCP Version 2
•Configuration Examples
•Command Reference
•Glossary
Feature Overview
The Web Cache Communication Protocol (WCCP) feature allows you to use a Cache Engine to handle web traffic, reducing transmission costs and downloading time. This traffic includes user requests to view pages and graphics on World Wide Web servers, whether internal or external to your network, and the replies to those requests. When a user requests a page from a web server (located in the Internet), the router sends the request to a Cache Engine. If the Cache Engine has a copy of the requested page in storage, the Cache Engine sends the user that page. Otherwise, the Cache Engine retrieves the requested page and the objects on that page from the web server, stores a copy of the page and its objects, and forwards the page and objects to the user.
WCCP transparently redirects Hypertext Transfer Protocol (HTTP) requests going to the intended server to a Cache Engine. End users do not know that the page came from the Cache Engine rather than the originally requested web server.
WCCP Version 2 now contains the following new features:
•Multiple router support
•Improved security
•Faster throughput
•Redirection of multiple TCP port-destined traffic
•Load distributing applications capability
•Client IP addressing transparency
Multirouter Support
WCCP Version 2 enables a series of Cache Engines, called a Cache Engine cluster, to connect to multiple routers. This feature provides redundancy and a more distributed architecture for instances when a Cache Engine needs to connect to a large number of interfaces. This strategy also has the benefit of keeping all the Cache Engines in a single cluster, avoiding unnecessary duplication of web pages across several clusters.
How Version 1 Works
With WCCP Version 1, only a single router services a cluster, becoming the default home router for the cluster. In this scenario, this router is the device that performs all the IP packet redirection. Figure C-1 illustrates how this configuration appears.
The following sequence of events details how this process works:
1. Each Cache Engine records the IP address of the router servicing the cluster.
2. The Cache Engines then transmit their IP addresses to the router, indicating their presence to one another in the cluster.
3. The router then replies to the Cache Engines, establishing that each can connect to the other in the cluster, providing a view or a list of Cache Engine addresses in the cluster, indicating that each can recognize each other.
4. Once the view has been established, one Cache Engine is designated as the lead and indicates to the router how IP packet redirection should be performed. The lead Cache Engine is defined as one seen by all the routers in the service group and that has the lowest IP address.
Figure C-1 Cache Engine Network Configuration Using WCCP Version 1
How Version 2 Works
With WCCP Version 2, multiple routers can service a cluster, allowing available routers to obtain status as the device that redirects packets for data coming from each of the Cache Engines in the cluster. Figure C-2 illustrates how this configuration appears. You can configure the router to run one of two services:
•Web cache which is a global service that sends content to a large collection of destination World Wide Web servers.
•Reverse proxy which is a local service that sends content to a small number of destination World Wide Web servers.
The subset of Cache Engines within a cluster and routers connected to the cluster that are running the same service is known as a service group.
WCCP Version 2 addresses the issue of multiple routers being available to the cluster by allowing either a list of routers or an IP multicast address to be created on the Cache Engine. The difference in these two strategies is as follows:
•In the multiple router strategy, the Cache Engine sends a notification of its presence to an explicit router address.
•In the multicast address strategy, the Cache Engine sends a notification to one address, which provides coverage for all routers in the service group, for example, 224.0.0.0, which will indicate packets be sent to a multicast address of 224.0.0.0, which would send a multicast packet to all routers in the service group.
If you are adding and removing routers dynamically, the multicast address strategy provides for easier configuration because you do not need to change the configuration for each device in the WCCP network.
The following sequence of events details how this process works:
1. Instead of having one central "home router," each Cache Engine defines a list of routers and stores the list in its memory.
2. Each Cache Engine announces its presence and view of the service group to the list of router IP addresses with which they have been configured. The routers reply with their view which is a list of Cache Engine addresses in the group.
3. Once the view is consistent across all Cache Engines in the cluster, one Cache Engine is designated as the lead and sets the policy that the routers need to deploy in redirecting packets.
Also, you need to configure the router(s) that will become members of the service group:
•Configure an IP multicast address for use by the cluster.
•Enable the ip wccp command.
For network configurations where the Cache Engine sends to a target router a packet that needs to traverse an intervening router, the router being traversed must be configured to perform IP multicast routing. You must configure two components to enable traversal over an intervening router:
•Enable IP multicast routing using the ip multicast routing command.
•Enable the interfaces to which the Cache Engines will connect to receive multicast transmissions using the ip pim command.
Figure C-2 Cache Engine Network Configuration Using WCCP Version 2
How Routers and Cache Engines Communicate
Routers and Cache Engines become aware of each other and form a service group using a management protocol. Once the service group has been established, one of the Cache Engines is designated to determine load assignments among the Cache Engines.
If there is a group of Cache Engines, the one seen by all routers and that has the lowest IP address becomes the lead Cache Engine. The role of this Cache Engine is to determine how traffic should be split across Cache Engines. The assignment information is passed to the entire service group from the designated Cache Engine so that the routers of the group can redirect the packets properly and the Cache Engines of the group can manage their load better.
Improved Security
Security between a Cache Engine and a router is now stronger because the Cache Engine's location in a cluster is more strongly circumscribed. WCCP Version 2 provides authentication that enables you to control which routers and Cache Engines become part of the service group using passwords and the HMAC MD5 standard set by the ip wccp [password [0-7] password] command.
Faster Throughput
Cisco Express Forwarding (CEF) has been integrated into WCCP Version 2 and provides fast packet redirection.
Redirection for Multiple TCP Port Destined Traffic
WCCP Version 2 enables more TCP ports to have traffic redirected to the Cache Engine. Previously, web-cached information could be redirected only if it was destined for TCP port 80. Many applications require packets intended for other ports to be redirected, for example, proxy-web cache handling, FTP caching, FTP proxy handling, web caching for ports other than 80, and Real Audio, video, and telephony applications.
Packets that the Cache Engines do not service are tunneled back to the same router from where they were received. Once a router has received a formerly redirected packet, it knows not to redirect it again.
The criteria set for determining whether to redirect the traffic is as follows:
•IP protocol
•Ports
•Priority
•Distribution scheme
•Default handling
Note that service information has been added to the protocol to indicate which service the WCCP messages refer to. This information is used to help validate that service group members are all using or providing the same service.
Web Cache Packet Return
WCCP Version 2 filters packets to determine which redirected packets have been returned from the Cache Engine and which ones have not. It does not redirect the ones that have been returned because the Cache Engine has determined that the packets should not be cached. WCCP Version 2 returns packets that the Cache Engine does not service to the same router from which they were transmitted. Typical reasons why a Cache Engine would reject packets and initiate packet return are:
•Instances when the Cache Engine is overloaded and has no room to service the packets.
•Instances when the Cache Engine is filtering certain conditions that make caching packets counterproductive, for example, when IP authentication has been turned on.
Load Distributing Applications
WCCP Version 2 has the capability to adjust the load being offered to individual Cache Engines to provide more effective use of the resources available and at the same time help to ensure high quality of service to the clients. It uses three techniques to perform this task:
•Hot Spot Handling allows an individual hash bucket, or a pool of IP addresses to which routers are mapped, to be distributed across all the Cache Engines.
•Load Balancing allows the set of hash buckets assigned to a Cache Engine to be adjusted so that the load can be shifted from an overwhelmed Cache Engine to other members that have available capacity.
•Load Shedding enables the router to selectively redirect the load to avoid exceeding the capacity of the Cache Engines.
Client IP Address Transparency
The Cache Engine accepts traffic and establishes the connection with the client, acting as if it were the original destination server. Once the connection is established, if the object being requested is not available on the Cache Engine, the engine then establishes its own connection out to the original destination server.
Benefits
Redundancy
Access to multiple routers provides backup support for a failed connection between a Cache Engine and the router. Multiple routers can access a Cache Engine server cluster.
Improved Security
Security between a Cache Engine and a router is now stronger as the Cache Engine's place in a cluster is more strongly circumscribed. Also authentication is now available using the HMAC MD5 security feature.
Faster Redirection
CEF provides fast redirection by using more efficient levels of switching, specifically, the process switch.
Increased Control over Traffic Selected for Redirection
The ability to redirect traffic destined to multiple TCP ports provides more flexibility for more applications, for example, proxy-web cache handling, FTP caching, FTP proxy handling, and Real Audio, video, and telephony applications, all targeted to various TCP ports. Previously, only applications with traffic destined to TCP port 80 could have traffic redirected.
Client IP Address Transparency
The Cache Engine accepts traffic and establishes the connection with the client acting as if it were the original destination server. Once the connection is established, if the object being requested is not available on the Cache Engine, the engine then establishes its own connection out to the original destination server.
Restrictions
The following limitations apply to WCCP Version 2:
•The Time To Live (TTL) value of routers servicing a cluster must be 15 seconds or less.
•The protocol needs to include the list of routers in the service group as part of its messages to properly depict the view.
•Because the messages may now be IP multicasted, members may receive messages that will not be relevant or are duplicates. Appropriate filtering needs to be performed.
•Service groups can comprise up to 32 Cache Engines and 32 routers.
•All Cache Engines in a cluster must include all routers servicing the cluster in its configuration. If a cache within a cluster does not include one or more of the routers in its configuration, the service group will detect the inconsistency and the Cache Engine will not be allowed to operate within the service group.
•Multicast addresses must be between 224.0.0.0 and 239.255.255.255.
•WCCP works only with IP networks.
Related Features and Technologies
To understand how WCCP Version 2 works, you must understand concepts associated with the Cache Engine.
Related Documents
•Cisco IOS Configuration Fundamentals Configuration Guide
•Cisco IOS Configuration Fundamentals Command Reference
Supported Platforms
The following platforms are supported:
Supported Standards, MIBs, and RFCs
MIBs
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
Before you use WCCP Version 2, you must complete the following tasks:
•Properly install and configure a cluster connected to one or more routers.
•Configure IP on the interface connected to the Internet and the interface connected to the Cache Engine. The interface connected to the Cache Engine must be an Ethernet or Fast Ethernet interface.
Configuration Tasks
You can configure a router to run the web cache and reverse proxy services associated with WCCP Version 2. Each service may be configured simultaneously. Perform the following tasks to configure a cluster with multiple routers.
• Configuring a Service Group Using WCCP Version 2
• Running the Web Cache Service
• Running a Reverse Proxy Service
• Registering a Router to a Multicast Address
• Informing a Router of Valid IP Addresses
• Setting a Password for a Router and Cache Engines
• Disabling Caching for Certain Clients
Configuring a Service Group Using WCCP Version 2
Running the Web Cache Service
Running a Reverse Proxy Service
Registering a Router to a Multicast Address
Informing a Router of Valid IP Addresses
Setting a Password for a Router and Cache Engines
Command PurposeStep 1
Router(config)# ip wccp web-cache password [0-7] password
Sets a password for the Cache Engine the router is trying to access.
Disabling Caching for Certain Clients
Verifying WCCP Configuration Settings
Step 1 To view the configuration, enter the show running-config command.
A sample configuration follows:
Console# show running-config
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname router4
!
enable secret 5 $1$nSVy$faliJsVQXVPW.KuCxZNTh1
enable password alabama1
!
ip subnet-zero
ip wccp web-cache
ip wccp 99
ip domain-name cisco.com
ip name-server 10.1.1.1
ip name-server 10.1.1.2
ip name-server 10.1.1.3
!
!
!
interface Ethernet0
ip address 10.3.1.2 255.255.255.0
no ip directed-broadcast
ip wccp web-cache redirect out
ip wccp 99 redirect out
no ip route-cache
no ip mroute-cache
!
interface Ethernet1
ip address 10.4.1.1 255.255.255.0
no ip directed-broadcast
ip wccp 99 redirect out
no ip route-cache
no ip mroute-cache
!
interface Serial0
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
interface Serial1
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
ip default-gateway 10.3.1.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.3.1.1
no ip http server
!
!
!
line con 0
transport input none
line aux 0
transport input all
line vty 0 4
password alaska1
login
!
end
Step 2 To view values associated with WCCP variables, enter the show ip wccp command. The following output is displayed:
show ip wccp
Global WCCP Information:
Service Name: web-cache:
Number of Cache Engines: 1
Number of Routers: 1
Total Packets Redirected: 213
Redirect access-list: no_linux
Total Packets Denied Redirect: 88
Total Packets Unassigned: -none-
Group access-list: 0
Total Messages Denied to Group: 0
Total Authentication failures: 0
Service Name: 99
Number of Cache Engines: 1
Number of Routers: 2
Total Packets Redirected: 198
Redirect access-list: -none-
Total Packets Denied Redirect: 0
Total Packets Unassigned: 0
Group access-list: 11
Total Messages Denied to Group: 0
Total Authentication failures: 0
Monitoring and Maintaining Using WCCP Version 2
Command PurposeRouter# show ip wccp
or
Router# show ip wccp {web-cache | 99}
Displays global statistics related to WCCP.
Router# show ip wccp {web-cache | 99} detail
Queries the router for information on which Cache Engines of a specific service group the router has detected. The information can be displayed for either a web cache or the reverse proxy service, which is indicated by a value of 99.
Router# show ip interface
Displays status about whether any ip wccp direct commands are configured on an interface.
Router# show ip wccp {web-cache | 99} view
Displays which devices in a particular service group have been detected and which Cache Engines are having trouble becoming visible to all other routers to which the current router is connected. The information can be displayed for either a web cache or the reverse proxy service, which is indicated by a value of 99.
Configuration Examples
This section provides the following configuration examples:
• Performing a General WCCP Version 2 Configuration
• Running a Reverse Proxy Service
• Registering a Router to a Multicast Address
• Informing a Router of Valid IP Addresses
• Setting a Password for a Router and Cache Engines
• Disabling Caching for Certain Clients
Performing a General WCCP Version 2 Configuration
The following example shows a general WCCP Version 2 configuration session:
ip wccp web-cache group-address 224.1.1.100 password alabama1
interface ethernet0
ip wccp web-cache redirect out
Running a Web Cache Service
The following example shows a web cache service configuration session:
configure terminal
ip wccp web-cache
interface ethernet 0
ip wccp web-cache redirect out
Running a Reverse Proxy Service
The following example shows a reverse proxy service configuration session:
configure terminal
ip wccp 99
interface ethernet 0
ip wccp 99 redirect out
Registering a Router to a Multicast Address
The following example shows how to register a router to a multicast address of 224.1.1.100:
configure terminal
ip wccp web-cache group-address 224.1.1.100
interface ethernet 0
ip wccp web cache group-listen
Informing a Router of Valid IP Addresses
To achieve better security, you can notify the router which IP addresses are valid addresses for a Cache Engine attempting to register with the current router, using a standard access list. The following example, shows a standard access list configuration session where the access list number is 10 for some sample hosts:
access-list 10 permit host 11.1.1.1
access-list 10 permit host 11.1.1.2
access-list 10 permit host 11.1.1.3
ip wccp web-cache group-list 10
Setting a Password for a Router and Cache Engines
The following example shows a WCCP Version 2 password configuration session where the password is alabama2:
configure terminal
ip wccp web-cache password alabama2
Disabling Caching for Certain Clients
To disable caching for certain clients, servers, or client/server pairs, you can use WCCP access lists. The following example shows any requests coming from 10.1.1.1 or going to 12.1.1.1 will bypass the cache. while all other requests will be serviced normally:
configure terminal
ip wccp web-cache redirect-list 120
access-list 120 deny tcp host 10.1.1.1
access-list 120 deny tcp any host 12.1.1.1
access-list 120 permit ip any any
Displaying WCCP Settings
The following example displays WCCP settings, using the show running-config command:
Console# show running-config
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname router4
!
enable secret 5 $1$nSVy$faliJsVQXVPW.KuCxZNTh1
enable password alabama1
!
ip subnet-zero
ip wccp web-cache
ip wccp 99
ip domain-name cisco.com
ip name-server 10.1.1.1
ip name-server 10.1.1.2
ip name-server 10.1.1.3
!
!
!
interface Ethernet0
ip address 10.3.1.2 255.255.255.0
no ip directed-broadcast
ip wccp web-cache redirect out
ip wccp 99 redirect out
no ip route-cache
no ip mroute-cache
!
interface Ethernet1
ip address 10.4.1.1 255.255.255.0
no ip directed-broadcast
ip wccp 99 redirect out
no ip route-cache
no ip mroute-cache
!
interface Serial0
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
interface Serial1
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
ip default-gateway 10.3.1.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.3.1.1
no ip http server
!
!
!
line con 0
transport input none
line aux 0
transport input all
line vty 0 4
password alaska1
login
!
end
Command Reference
This section documents new or modified commands that configure the WCCP Version 2 feature. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
• ip wccp
In Cisco IOS Release 12.0(1)T or later, you can search filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
clear ip wccp
To remove Web Cache Communication Protocol (WCCP) statistics maintained on the router either for a particular service or for all the services, use the clear ip wccp EXEC command.
clear ip wccp {web-cache | service-number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release Modification11.1 CA
This command was introduced.
11.2 P
This command was introduced.
12.0(3)T
This command has been expanded to be explicit about service.
Usage Guidelines
Use the show ip wccp and show ip wccp detail commands to display WCCP statistics.
Example
clear ip wccp web cache
Related Commands
Command Descriptionip wccp
Directs a router to enable or disable the support for a service group.
show ip wccp
Displays global statistics related to the WCCP feature.
ip wccp
To direct a router to enable or disable the support for a Cache Engine service group, use the ip wccp global configuration command. To remove the ability of a router to control support for a service group, use the no form of this command.
ip wccp {web-cache | service-number} [group-address groupaddress] [redirect-list access-list] [group-list access-list] [password [0-7] text]
no ip wccp {web-cache | service-number} [group-address groupaddress] [redirect-list access-list] [group-list access-list] [password [0-7] password]Syntax Description
Syntax Description (Continued)
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The command is disabled by default.
Example
The following example shows a router configured to run WCCP reverse proxy service, using (listening to) the multicast address of 224.1.1.1:
ip wccp 99 group-address 224.1.1.1
Related Commands
Command Descriptionip wccp group-listen
Configures an interface on a router to enable or disable the reception of IP multicast packets for the WCCP feature.
ip wccp group-listen
To configure an interface on a router to enable or disable the reception of IP multicast packets for the Web Cache Communication Protocol (WCCP) feature, use the ip wccp group-listen interface configuration command. To remove control of the reception of IP multicast packets for the WCCP feature, use the no form of this command.
ip wccp {web-cache | service-number} group-listen
no ip wccp {web-cache | service-number} group-listenSyntax Description
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Example
The following example shows that multicast packets have been enabled for a web cache with an address of 224.1.1.100.
configure terminal
ip wccp web-cache group-address 224.1.1.100
interface ethernet 0
ip wccp web cache group-listen
Related Commands
ip wccp redirect exclude in
To configure an interface to enable or disable excluding packets received on an interface from being redirected to a Cache Engine, use the ip wccp redirect exclude in interface configuration command. To disable a router's ability to verify appropriate packets being redirected to a Cache Engine, use the no form of this command.
ip wccp redirect exclude in
no ip wccp redirect exclude inSyntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Note that the command is global to all the services and should be applied to any inbound interface that has been configured to be excluded from redirection on an outbound interface that the traffic will traverse.
Related Commands
ip wccp redirect out
To configure an interface to enable a router's ability to verify that appropriate packets are being redirected to a Cache Engine, use the ip wccp redirect out interface configuration command. To disable a router's ability to verify appropriate packets being redirected to a Cache Engine, use the no form of this command.
ip wccp {web-cache | service-number} redirect out
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Example
configure terminal
ip wccp 99
interface ethernet 0
ip wccp 99 redirect out
Related Commands
Command Descriptionip wccp redirect exclude in
Configures an interface to enable or disable excluding packets received on an interface from being cached.
ip wccp version
To configure the WCCP version number, use the ip wccp version global configuration command. The default WCCP version is Version 2. Use this command to override the default.
ip wccp version {1 | 2}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Example
ip wccp version 1
show ip interface
To display status about any ip wccp direct commands configured on an interface, use the show ip interface EXEC command.
show ip interface [type-number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable. A usable interface is one through which the software can send and receive packets. If the software determines that an interface is not usable, it removes the directly connected routing entry from the routing table. Removing the entry allows the software to use dynamic routing protocols to determine backup routes to the network (if any).
If the interface can provide two-way communication, the line protocol is indicated to be running. If the interface hardware is usable, the interface is indicated to be running.
If you specify an optional interface type, you will see only information on that specific interface.
If you specify no optional arguments, you will see information on all the interfaces.
When an asynchronous interface is encapsulated with Point-to-Point Protocl (PPP) or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
Example
The following example displays output from the show ip interface command, using the interface e3/0:
show ip interface e3/0
Ethernet3/0 is up
Internet address is 17.1.1.38/24
Broadcast address is 255.255.255.255
Address determined by non-volatile memory
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is enabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is disabled
IP Optimum switching is enabled
IP multicast fast switching is enabled
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
Probe proxy name replies are disabled
Gateway Discovery is disabled
Policy routing is disabled
Network address translation is disabled
WCCP Redirect outbound is enabled
WCCP Redirect exclude is disabled
Table C-2 describes the fields shown in the example.
Related Commands
show ip wccp
To display global statistics related to the Web Cache Communication Protocol (WCCP) feature, use the show ip wccp EXEC command.
show ip wccp {web-cache | service-number} [view | detail]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Use the clear ip wccp command to reset the counter for the "Packets Redirected" information.
Example
The following example is sample output from the show ip wccp command:
show ip wccp
Global WCCP Information:
Service Name: web-cache:
Number of Cache Engines: 1
Number of Routers: 1
Total Packets Redirected: 213
Redirect access-list: no_linux
Total Packets Denied Redirect: 88
Total Packets Unassigned: -none-
Group access-list: 0
Total Messages Denied to Group: 0
Total Authentication failures: 0
Service Name: 1
Number of Cache Engines: 1
Number of Routers: 2
Total Packets Redirected: 198
Redirect access-list: -none-
Total Packets Denied Redirect: 0
Total Packets Unassigned: 0
Group access-list: 11
Total Messages Denied to Group: 0
Total Authentication failures: 0
Table C-3 describes the fields shown in the example.
Related Commands
show ip wccp detail
To query the router for information on which Cache Engines of a specific service group the router has detected, use the show ip wccp detail EXEC command.
show ip wccp {web-cache | service-number} detail
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release Modification11.1CA and 11.2 P
This command was introduced in Cisco IOS Release 11.1 CA and Release 11.2 P.
12.0(3)T
This command was expanded to indicate the router information.
Example
The following example displays Cache Engine and Web Cache Communication Protocol (WCCP) router statistics for a particular service group:
show ip wccp web-cache detail
WCCP Router information:
IP Address 192.168.88.10
Protocol Version: 2.0
WCCP Cache-Engine Information
IP Address: 192.168.88.11
Protocol Version: 2.0
State: Usable
Initial Hash Info: AAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAA
Assigned Hash Info: FFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFF
Hash Allotment: 256 (100.00%)
Packets Redirected: 21345
Connect Time: 00:13:46
Table C-4 describes the fields shown in the example.
Related Commands
show ip wccp view
To display which devices in a particular service group have or have not been detected by all other routers to which the current router is connected, use the show ip wccp view EXEC command.
show ip wccp {web-cache | service-number} view
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Example
The following sample output from the show ip wccp service 1 view command:
show ip wccp service 1 view
WCCP Router Informed of:
192.168.88.10
192.168.88.20
WCCP Cache Engines Visible
192.168.88.11
192.168.88.12
WCCP Cache Engines Not Visible:
-none-
If any Cache Engine is displayed under the WCCP Cache Engines Not Visible field, the Cache Engine needs to be reconfigured to add this router to it. Table C-5 describes the fields shown in the example
Table C-5 show ip wccp view Field Descriptions
Related Commands
Glossary
Cache Engine—A device that stores objects being downloaded from the web for future use by the host.
Cache Engine cluster—A collection of Cache Engines that are controlled by one or more routers.
Cisco Express Forwarding (CEF)—A scalable, distributed, Layer 3 switching solution designed to meet performance requirements of the Internet and enterprise networks.
hash buckets—A pool of IP addresses to which individual servers are mapped.
reverse proxy service—A service that duplicates network content and distributes it across a small number of destination World Wide Web servers.
service group—A subset of Cache Engines within a cluster and routers connected to the cluster that are running the same service, either web cache or reverse proxy.
view—A list of addresses of the Cache Engines and routers in the service group.
WCCP Version 1—A protocol that allows you to use a Cache Engine to handle World Wide Web traffic, thus reducing transmission costs and downloading time. The Cache Engines in the cluster can be mapped to only one router.
WCCP Version 2—A protocol that allows you to use a Cache Engine to handle World Wide Web traffic and other services in a similar manner to WCCP Version 1. Specified services can be mapped to multiple routers.
web cache service—A service that handles large collections of destination World Wide Web servers with various IP addresses throughout the network. The network content, rather than being duplicated across all Cache Engines, is assigned to a particular Cache Engine.
Posted: Wed Aug 25 17:35:50 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.