Warning The ports labeled "Ethernet," "10BaseT," "Token Ring," "Console," and "AUX" are safety extra-low voltage (SELV) circuits. SELV circuits should only be connected to other SELV circuits. Because the BRI circuits are treated like telephone-network voltage, avoid connecting the SELV circuit to the telephone network voltage (TNV) circuits.

Warning This product relies on the building's installation for short-circuit (overcurrent) protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240 VAC, 10A international) is used on the phase conductors (all current-carrying conductors).

Warning This equipment is intended to be grounded. Ensure that the host is connected to earth ground during normal use.

Warning Do not work on the system or connect or disconnect cables during periods of lightning activity.

Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals.

Refer to Figure 2-1 and Figure 2-2 when installing the engine, to help you identify the connectors on the back and front of the engine.

AC receptacle. Connect the power cord to this plug.

Power switch. This switch toggles between on and off, even though the switch always returns to its initial position after you press it. Check the power light on the front of the Cache Engine to determine if the power is on (a lit power light indicates that the power is on).

Console port. This serial port connects to a console.

Ethernet port. Connect the Ethernet cable to this plug. The status lights above the connection are:

LNK. When lit, indicates that the engine is connected to the network.
ACT. When lit, indicates that the network connection is active (packets are being sent or received).
100 TX. When lit, indicates that the connection is a 100BaseTX (Fast Ethernet) connection.

Figure 2-1: The Cache Engine, Rear View

Figure 2-2: The Cache Engine, Front View

To install the Cache Engine:

Step 1 Place the Cache Engine unit in the desired location. You can mount it on a rack for your convenience, or place it on a solid, stable surface. Figure 2-3 shows how to attach the mounting brackets. You will need a Phillips-head screwdriver.

Step 2 Plug in the Cache Engine.

Step 3 Plug the network connection into the Ethernet port on the Cache Engine.

Step 4 Plug the console into the Console port on the Cache Engine using the supplied serial cable. Open a window for the engine console using your terminal emulation program.

Step 5 Turn on the Cache Engine. The Cache Engine begins booting, and sends messages to the console window. Once the operating system boots, you are ready to initialize the basic configuration.

Figure 2-3: Attaching the Mounting Brackets

Initializing the Cache Engine Configuration

Once you have installed the Cache Engine, and booted the engine's operating system, you must initialize the basic configuration. The engine prompts you through each configuration variable; you can back up to the previous variable by typing a hyphen (-) and pressing the Enter key.

To initialize the Cache Engine's basic configuration once it has booted the operating system:

Step 1 Enter values for these parameters as you are prompted:

IP Address for the Cache Engine. For example, 10.1.1.1.

IP Netmask for the Cache Engine. A netmask specifies which part of the IP address refers to the network; you can accept this value by pressing Enter, or enter a different value. For example, 255.255.255.0.

Default Gateway for the Cache Engine. This is the IP address of the router that allows the engine to connect to the network. It is not necessarily the same IP address of the engine's home router. For example, 10.1.1.1.

Replace admin Password for the Cache Engine. This is the password you want to use for the admin user account, which is predefined on the engine. The password is case sensitive and can be up to 20 characters, including spaces and any printable characters. You must enter a password for each engine on the farm. You cannot set the passwords globally.

Repeat Admin Password. Verify the password for the admin user account (or press Enter without entering a password to keep the existing password).

Note

Cache Name for the Cache Engine. The name you want to assign to the engine. You can enter any name you find meaningful. For example, cache1. The name can be up to 20 characters, and can contain spaces and any printable characters.
GMT Date/Time for your network. This is the current local date and time as measured in Greenwich Mean Time (GMT). You must use GMT because the HTTP protocol uses GMT for the timestamps on HTTP objects (web pages, graphics, and so forth).

Note

: Enter the date and time, without spaces or punctuation marks, in this format: yyyy/mm/dd hh:mm:ss, where yyyy is the four digit year (for example, 1999); mm is the two digit month (for example, 08 for August); dd is the two digit date (for example 06 for the sixth day of the month); hh is the two digit hour, from 01 to 24; mm is the two digit minutes, from 00 to 59; and ss is the two digit seconds, from 00 to 59. There is a space between the day and the hour.
: For example, to enter August 2, 1999, 8:27:53, enter 1999/08/02 08:27:53.

Note

admin

Step 2 If the basic configuration is acceptable, enter y. The Cache Engine indicates whether the configuration is accepted. At this point, the basic configuration is finished.

Step 3 Once you have entered an acceptable basic configuration, the Cache Engine displays the URL that you would use to connect to it with a web browser. For example, http://10.1.1.1 . You must use the complete URL to connect to the machine and manage it.

The user name is admin and the password is supplied by the user on the Login window.

Enabling Cache Support on the Router

Before the router can use the Cache Engine, it must know that the Cache Engine exists. This notification is done automatically by communications between the engine and the router. However, you must enable cache support in the router so that the router knows to listen for the Cache Engine.

If you later want to disable caching temporarily, you can do so by disabling cache support in the router, rather than by turning off or otherwise disabling the individual Cache Engines. (Use the no ip wccp command on the router to disable caching.)

You must already know how to configure the router to make these configuration changes. If you do not know how to configure the router, consult the Cisco IOS documentation supplied with the router. Detailed information for the commands mentioned here is in the Cisco IOS documentation. See Appendix C, Web Cache Communication Protocol Version 1, and Appendix D, Web Cache Communication Protocol Version 2, for information on which IOS software supports which version of WCCP on which platform.

To enable cache support on the router for WCCP Version 1:

Step 1 Ensure that the router is running a release of the Cisco IOS software that includes WCCP Version 1. If it does not have this support, before you can continue, you must upgrade the Cisco IOS software.

IOS versions before 12.0(3)T support only WCCP Version 1. IOS versions between 12.0(3)T and 12.0(5)T support only WCCP Version 2. IOS version 12.0(5)T or later support both WCCP Version 1 and Version 2. In IOS version 12.0(5)T or later, the default WCCP version is Version 2. You can override the WCCP default, by using the global configuration command ip wccp version 1.

If you have WCCP Version 1 configured and attempt to configure any WCCP Version 2 specific features, you will receive a configuration error.

Note

Config

WCCP

Version 2

Router List

UPDATE

Step 2 In global configuration mode, use the ip wccp enable command to enable cache support. For example, enter:

ip wccp enable

Step 3 In interface configuration mode, use the ip web-cache redirect command to have the interface redirect packets for port 80 to the Cache Engine. Enter this command for each interface that is an outgoing interface connecting to the following:

The Internet
The Internet or to subnets that contain web servers
Subnets that contain web servers

For example, to enable redirection, enter:

ip web-cache redirect

You can confirm your settings using the following show commands on the router:

show ip wccp

: Shows the number of Cache Engines and total number of packets redirected.

show ip wccp web-caches

: Shows detailed information about each Cache Engine connected to the router.

show ip interface

: Shows detailed information about an interface, including whether web cache redirect is enabled.

To enable cache support on the router for WCCP Version 2:

Step 1 Ensure that the router is running a release of the Cisco IOS software that includes WCCP Version 2. If it does not have this support, before you can continue, you must upgrade the Cisco IOS software.

In global configuration mode, use the ip wccp command to enable cache support. For example, enter:

ip wccp webcache

Step 2 In interface configuration mode, use the ip wccp web-cache redirect out command to have the interface redirect packets for port 80 to the Cache Engine. Enter this command for each interface that is an outgoing interface connecting to the following:

The Internet
The Internet or to subnets that contain web servers
Subnets that contain web servers

For example, to enable redirection, enter:

ip web-cache redirect out

You can confirm your settings using the following show commands on the router:

show ip wccp

: Shows the number of Cache Engines and total number of packets redirected.

show ip wccp web-cache detail

: Shows detailed information about each Cache Engine connected to the router.

show ip interface

: Shows detailed information about an interface, including whether web cache redirect is enabled.

Testing the Cache Engine Installation

Once you have installed and configured the Cache Engine, and enabled caching on the home router, check to ensure the Cache Engine is working properly:

Step 1 From a machine on a network that uses the home router, start a web browser and open various web pages on the Internet or your intranet. The web servers you connect to must be on a different subnet, so that the request goes through the home router. Connect to some pages more than once, to ensure that some pages you request are in the cache.

Step 2 Connect to the Cache Engine's home page, and click Status. There should be activity shown for the Cache Engine.

Step 3 Use Telnet to connect to the home router, and enter the show ip wccp web-caches command to display information about the Cache Engines. The entry for the Cache Engine should show a number greater than 0 for Packets Redirected.

If the router shows that no packets are being redirected to the Cache Engine, you need to troubleshoot your setup. See "Troubleshooting the Cache Engine" for more information.

Connecting to the Cache Engine Management Interface

You can manage the Cache Engine using the CLI or the Cache Engine management interface. To connect to the Cache Engine's management interface:

Note Please be sure to enable Java, JavaScript, and Cascading Style Sheets on your Internet Explorer or Netscape 4.0 or later browser.

Step 1 Start a web browser on a machine that has access to the network on which the Cache Engine resides.

Step 2 Open the URL for the engine, using the URL given to you during basic configuration. For example, http://10.1.1.1:8001 . You must include the port number, such as 8001, in the URL.

You are prompted for a username and password (see Figure 2-4).

Figure 2-4: Administrator's Login

Step 3 Enter a correct username and password. The Cache Engine returns the initial management page, which contains links to other management pages.

If you forget your password, you must have another administrator reset your password.

Table of Contents

Installing the Cache Engines

Collecting the Information Required for Configuration