cc/td/doc/product/webscale/webcache/ce15
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Maintaining the Cache Engines

Maintaining the Cache Engines

This chapter covers the tasks required for maintaining a Cache Engine or a cache farm:

Recovering the Cache Engine System Software

If the Cache Engine's system software becomes corrupted (for example, because of a corrupted system disk or a power failure that occurs while you are updating the system software), you can recover it using the recovery diskette included with the system, plus a system software upgrade:


Step 1   Remove the diskette drive cover from the front of the Cache Engine (as shown in Figure 4-1) by unscrewing it and insert the recovery diskette supplied with the engine. (You can order a replacement diskette if necessary.)

Step 2   In order of preference, do one of the following:

Step 3   Once the engine finishes rebooting, you can connect to the engine using FTP to copy a new image onto the engine, as described in "Upgrading the System Software." If the disk that contains the system software is damaged, call Technical Support for help.


Figure 4-1: Removing the Floppy Drive Cover

Upgrading the System Software

If a new release of the Cache Engine system software is available, you can upgrade your Cache Engine by obtaining the software from Cisco Connection Online or by ordering the upgrade media. When you have the software, to upgrade a Cache Engine:


Step 1   Put the upgrade software on your Windows NT or UNIX machine. The upgrade software is one file.

Step 2   From the Windows NT or UNIX machine, FTP to the Cache Engine and log in using an existing Cache Engine account with read-write authority (for example, the admin account). For example, to FTP to the Cache Engine 192.168.88.89:

ftp 192.168.88.89

You are placed in the correct directory, which is /ata0/. If you are not in this directory, use the cd command to change directories, putting the directory name in quotes:

cd "/ata0/"

Step 3   Change to binary mode:

bin

Step 4   Put the file to the Cache Engine. For example, if the upgrade software's file name is Ver-2.pax, enter:

put Ver-2.pax

You can now quit the FTP session.

Step 5   From the Cache Engine's console, enter the Pax command to unpack the file. For example, if the file name is CE2050_1.1_1, enter:

Pax "CE2050_1.1_1", "-x"

Replace CE2050_1.1_1 with the name of the file that you put onto the engine. You must enter all other characters as shown. When you press the Enter key, the engine starts extracting the files that comprise the system software.

This file extraction preserves your current configuration, including URL and MIME blocking lists. The Pax command creates a subdirectory for the new software version based on the version numbers for the software. Previous versions of the software remain on the engine.

Step 6   From the Cache Engine's console, reboot the engine:

reboot

Adding a Cache Engine to an Existing Cache Farm

To add a Cache Engine to a router that already has a cache farm, install the Cache Engine as described in Chapter 2, "Installing the Cache Engines." When you are configuring the Cache Engine, ensure you use the name of the existing cache farm for the Cache Farm Name, and the IP address of the router for the cache farm as the Host Router. Once you finish configuration and the engine finishes booting, the host router and other Cache Engines in the cache farm recognize the new machine as part of the farm, and start using it.

Except for potentially improved system performance, adding a Cache Engine is transparent to your users.

Moving a Cache Engine to a Different Cache Farm

Normally, you should remove a Cache Engine from the network to move it to a different cache farm; otherwise the Cache Engine will not be directly connected to its home router. Although the Cache Engine does not have to be connected directly to its home router, that is the most effective network setup. See "Removing or Replacing a Cache Engine" for more information.

If you do want to move a Cache Engine to another cache farm without changing the Cache Engine's place in the network:


Step 1   Connect to the Cache Engine you want to move using a web browser, and log in.

Step 2   Click Nerd Knobs.

Step 3   In the Network Setup group, change the Cache Farm Name for the Cache Engine to the name of the cache farm to which you want the engine to belong.

Step 4   In the Network Setup group, change the Host Router IP address to the address of the home router for the new cache farm.

Step 5   Click Set in the Network Setup group. The Cache Engine becomes part of the selected cache farm.

Removing or Replacing a Cache Engine

Warning Before working on a system that has an On/Off switch, turn OFF the power and unplug the power cord.
Warning Ultimate disposal of this product should be handled according to all national laws and regulations.

To remove a Cache Engine from a system, simply turn off the engine's power and physically remove it from the network.

The router and the Cache Engine are in constant communication: thus, when the router notices that the engine is no longer responding to it, the router stops sending requests to the engine. This is transparent to your users.

If there are other Cache Engines attached to the router, the router continues sending requests to the other engines.

When you remove a Cache Engine, the pages that were cached on the engine are no longer available to the router or other caches. Thus, you might see an increase in outgoing web traffic that might have otherwise been fulfilled by the engine you are removing. However, after a time, the router and other Cache Engines will have redistributed the load of web traffic.

If you remove the last Cache Engine from a router, you can also disable cache support on the router. However, this is not necessary; having cache support enabled when there are no Cache Engines attached has no effect on the router's performance.

To replace a Cache Engine, remove the old engine from the network. Then, add the new engine and configure it using the same configuration parameters (IP address, and so forth) that you used for the removed engine.

Disabling a Cache Farm

To disable an entire cache farm without removing the Cache Engines from the network, turn off the Web Cache Control Protocol at the home router using the router's no ip wccp global configuration command. See the documentation for your router for more information on entering configuration commands.

Replacing Cables (Pinout Information)

The Cache Engine includes these cables and adapters:

Use these cables to connect the Cache Engine console port to the COM port of a console or computer that is running a console program.

In addition to the console cable, you must supply your own standard Ethernet cable to connect the Cache Engine to your network.

This section details the pinout information for these cables, so that you can purchase the correct cable for your network connection, and replace the console cable and adapters, if that becomes necessary.

Standards for the Ethernet Cable

To connect the Cache Engine to your network, you must use one of these:

Use a cat 5 UTP cable at minimum to connect to a 100BaseT network. Use a cat 3 UTP cable at minimum to connect to a 10BaseT network.

Table 4-1 shows the pinouts for a straight-through 100BaseT cable.


Table 4-1: Straight-Through 100BaseT Cable (RJ-45 to RJ-45) Pinouts
RJ-45 Pin Signal Direction RJ-45 Pin

1

TX+

—>

1

2

TX-

—>

2

3

RX+

<—

3

4

-

-

4

5

-

-

5

6

RX-

<—

6

7

-

-

7

8

-

-

8

Table 4-2 shows the pinouts for a crossed-over 100BaseT cable.


Table 4-2: Crossed-Over 100BaseT Cable (RJ-45 to RJ-45) Pinouts
RJ-45 Pin Signal Direction RJ-45 Pin

1

TX+

—>

3

2

TX-

—>

6

3

RX+

<—

1

4

-

-

4

5

-

-

5

6

RX-

<—

2

7

-

-

7

8

-

-

8

Standards for the Console Cable and Adapters

The EIA/TIA-232 console port on the Cache Engine is configured as data terminal equipment (DTE) and uses a DB-9 connector. A console cable kit is provided with your Cache Engine to connect a console (an ASCII terminal or PC running terminal emulation software) to the console port. The console cable kit contains an RJ-45 to RJ-45 roll-over cable and 2 RJ-45 to DB-9 female DTE adapters.

By attaching the 2 RJ-45 to DB-9 adapters to the RJ-45 to RJ-45 roll-over cable, you create a DB-9 to DB-9 null modem cable. Table 4-3 shows the pinouts for this configuration.


Table 4-3: Console Cable and Adapters Pinouts
Cache Engine Console Port (DB9) DB-9 Signal

1

-

DTR

2

3

TD

3

2

RD

4

6

DCD

5

5

SG

6

4

DSR

7

8

CTS

8

7

RTS

9

-

-

You can identify a roll-over cable by comparing the two modular ends of the cable, as shown in Figure 4-2. Holding the cables in your hand, side-by-side, with the tab at the back, the wire connected to the pin on the outside of the left connector (pin 1) should be the same color as the pin on the outside of the right connector (pin 8).


Figure 4-2: Identifying a Roll-over Cable


hometocprevnextglossaryfeedbacksearchhelp
Posted: Sat Sep 28 01:12:01 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.