Chapter 2: Maintaining the System Software and Hard Disk Storage

Table Of Contents

Maintaining the System Software

Upgrading the System Software

Upgrading Cache Software, Release 3.1 Systems to Release 3.1.x

Upgrading Cache Software, Release 3.0.x Systems to Release 3.1

Upgrading Cache Software, Release 2.x.x Systems to Release 3.1

Downgrading Cache Software, Release 3.1 Systems to Release 2.x.x

Maintaining the Hard Disk Storage

Disk System Overview

Preparing an swfs Partition

Preparing a sysfs Partition

Preparing a cfs Partition

Preparing a mediafs Partition

Disk Preparation Procedure for the Cisco Storage Array

Recovering the System Software

Recovering a Lost Password

Maintaining the System Software

Software maintenance in this chapter refers to the procedures necessary to load software on the Content Engine as well as to recover operation resulting from corruption of the system image or a forgotten administrator password. These procedures are presented in the following sections:

• Upgrading the System Software

• Maintaining the Hard Disk Storage

• Recovering the System Software

• Recovering a Lost Password

Upgrading the System Software

Cisco Cache software, Release 3.1 is available to download from Cisco.com.

Cache software Release 3.1 introduces optional software that requires the creation of two new types of disk partitions. The new disk partitions in Release 3.1 are the swfs (software file system) and mediafs (media file system) partitions. The swfs partition is factory-installed for Content Engines shipped with Release 3.1, but must be created when upgrading from Release 2.x or 3.0.x. The mediafs partitions can be created as necessary. Cache software, Release 3.1 upgrade and downgrade procedures are discussed in the following sections:

• Upgrading Cache Software, Release 3.1 Systems to Release 3.1.x

•

• Upgrading Cache Software, Release 2.x.x Systems to Release 3.1

• Downgrading Cache Software, Release 3.1 Systems to Release 2.x.x

See Chapter 3, "Cache Software Feature Configurations," for information on configuring optional software and the standard Cache software features.

See the "Recovering the System Software" section for instructions on booting the Content Engine in the event that the software upgrade fails.

Upgrading Cache Software, Release 3.1 Systems to Release 3.1.x

Use the procedure in this section to install more recent images of the Release 3.1 Cache software on a Content Engine running a version of Release 3.1.

Requirements

•Access to a UNIX, Linux, or Windows FTP server on which the full release image file resides.

Note A full release file comprises the 3.1 operating system, management graphical user interface (GUI), and all optional software.

•One of the full Release 3.1.x image files appropriate to the model of Content Engine:

–ce507-cache-31x.bin

–ce560-cache-31x.bin

–ce590-cache-31x.bin

–ce7320-cache-31x.bin

Procedure

This procedure demonstrates how to install a Release 3.1.x system image on a Content Engine running Release 3.1, with the assumption that all disk partitions remained unchanged.

Step 1 Connect to the Content Engine through Telnet or the console port.

Note A console port connection is required if you are changing the basic startup configuration. The Telnet session is disconnected when the Content Engine reboots.

Step 2 Save the current system configuration to Flash memory.

ContentEngine# copy running-config startup-config

Step 3 Verify that the present working directory is local1 or local2.

ContentEngine# cd /local1
ContentEngine# pwd
/local1

Step 4 Download the Release 3.1.x image from an FTP server to the Content Engine /loca1 or /local2 directory.

In the following example, the image file, ce590-311_FCS.bin, is downloaded from the /images directory of FTP server 176.16.8.9.

ContentEngine# copy ftp disk 176.16.8.9 /images ce590-31x_FCS.bin

Enter username for remote ftp server: my_ftpserver_username
Enter password for remote ftp server: my_ftpserver_password

Step 5 Install the Release 3.1.x software with the install EXEC command.

The install command copies a new system image to Flash memory and installs the optional software on the swfs partition. In the following example, the full release image file is in the sysfs directory /local1.

ContentEngine# install /local1/ce590-31x_FCS.bin

Step 6 Reboot the Content Engine.

ContentEngine# reload
Proceed with reload?[confirm] yes

Step 7 If you are installing optional software, proceed to Chapter 3, "Cache Software Feature Configurations."

Upgrading Cache Software, Release 3.0.x Systems to Release 3.1

The upgrade of a Release 3.0.x image to a Release 3.1 image is a three-part process as follows:

1. Copy a Release 3.1.x Flash memory-only image to Flash memory.

2. Boot with the Flash memory-only image, reformat the disk drives and then copy the full Release 3.1.x image to a local disk.

3. Install the full Release 3.1 image.

Requirements

The Flash memory-only file contains the Release 3.1 operating system only. The Release 3.1 full-release file contains Release 3.1 operating system and optional software.

•Release 3.1 Flash memory-only image files:

–ce7320-cache-31x.sysimg

•Release 3.1 full-release files:

–ce7320-cache-31x.bin

Procedure

Step 1 Log in to the Content Engine through Telnet or the console port.

Note A console port connection is required if you are changing the basic startup configuration. The Telnet session is disconnected when the Content Engine reboots.

Step 2 Save the current system configuration to Flash memory.

ContentEngine# copy running-config startup-config

Step 3 If you wish to retain any sysfs files (such as the transaction logs) from Release 3.0.x disks, create a sysfs disk on disk01, and copy any log files from disk00 to disk01. All contents of disk00 will be erased as part of the upgrade procedure.

Step 4 Download the Release 3.1 Flash memory-only image file to a Windows NT, Linux, or UNIX host that is running an FTP server.

Step 5 Perform the following substeps to copy the Release 3.1 Flash memory-only image file from an FTP server to the Content Engine Flash memory. In this example, the FTP server has the IP address 192.168.88.89 with the Flash memory-only system image file (ce590-31x_sysimg.flash) located in the /images directory:

a. At the EXEC command line of your Content Engine, enter the following:

ContentEngine# copy ftp flash 192.168.88.89 /images ce7320-31x.sysimg

b. Enter your FTP username and password when prompted:

Enter username for remote ftp server: my_ftpserver_username
Enter password for remote ftp server: my_ftpserver_password

The following messages appear:

Initiating FTP download. . .
Downloaded 10685440 byte image file
A new system image has been downloaded.
You should write it to flash at this time.
Write to flash [yes]: _

c. To write the new system image to Flash memory, press Enter to accept the default (yes) or enter yes.

The following message appears:

Ok, writing new image to flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

d. Reboot the Content Engine with the reload EXEC command.

ContentEngine# reload
Proceed with reload?[confirm] yes

After the reboot, the following message appears for each existing disk partition, indicating the conversion of the Release 3.0.x disk signature to the Release 3.1 format:

Converting disk signature format from 3.0 to 3.1:mydisk00
Cisco Content Engine Console

Step 6 Login as admin.

Username: admin

Step 7 Configure the device with the basic startup parameters.

This step occurs only when the device does not have a saved configuration file (such as occurs with a new device). The following lines show an interactive example of an initial configuration session:

You may use Ctrl-D to abort Configuration Dialog at any prompt.
Would you like to enter the initial configuration?[yes]:yes
host name:mycontentengine
Admin password:mypassword
Please enter an interface from the following list:
0:FastEthernet 0/0
1:FastEthernet 0/1
enter choice:0
cache IP address: 10.1.1.1
IP network mask:255.255.0.0
Gateway IP address: 10.1.1.2
Use this configuration? [yes]:yes

Step 8 Erase all partitions on disk00 with the disk erase-all-partitions EXEC command.

ContentEngine# disk erase-all-partitions disk00

Step 9 Create the swfs disk partition with the disk recover EXEC command.

ContentEngine# disk recover

The swfs partition is created on disk00.

Step 10 Partition, format, and mount a sysfs partition.

A sysfs partition on a disk other than disk00 may already exist from Release 3.0.x. The sysfs partition is the repository for various log files (syslog, error log, and transaction logs). The full-release image file is downloaded to this partition. In the following example, a sysfs partition named disk00/01 is allocated 25 percent of the total disk and mounted at /local1. For further information on sysfs, see the "Maintaining the Hard Disk Storage" section.

ContentEngine# disk partition disk00/01 25% sysfs
ContentEngine# sysfs format disk00/01
ContentEngine# sysfs mount disk00/01 local1

Step 11 Partition, format, and mount mediafs disk partitions.

The mediafs partitions are used by the RealProxy to cache streaming objects. The mount point for this partition (like the cfs partition) is not visible to the user. The following example demonstrates how a mediafs partition of 10 GB is formatted and mounted as one of the partitions on disk03. For further information on mediafs, see the "Maintaining the Hard Disk Storage" section.

ContentEngine# disk partition disk03/01 10g mediafs
ContentEngine# mediafs format disk03/01
ContentEngine# mediafs mount disk03/01

Step 12 Verify that the present working directory is local1 or local2.

ContentEngine# cd /local1
ContentEngine# pwd
/local1

Step 13 Download the full-release image file to the sysfs directory with the copy ftp disk EXEC command.

In the following example, the full-release image file ce7320-cache-31x.bin is downloaded from the /images directory of the FTP server 176.16.8.9:

ContentEngine# copy ftp disk 176.16.8.9 /images ce7320-cache-31x.bin

Enter username for remote ftp server: my_ftpserver_username
Enter password for remote ftp server: my_ftpserver_password

Step 14 Install the full-release image software with the install EXEC command.

The install command copies a new system image to Flash memory and installs the optional software on the swfs partition. In the following example, the full Release 3.1 image file is stored in the sysfs directory /local1.

ContentEngine# install /local1/ce7320-cache-31x.bin

Step 15 When the CLI prompt reappears, reboot the Content Engine with the reload EXEC command. Enter yes to confirm.

ContentEngine# reload
Proceed with reload?[confirm] yes

Step 16 Set the system clock if necessary with the clock set EXEC command.

ContentEngine# clock set 14:22:00 24 Jan 2001
WARNING: Setting the clock may cause a temporary service interruption.
Do you want to proceed?[no] yes
Mon Jan 24 14:22:00 EST 2001
ContentEngine#

Step 17 If you are installing optional software, proceed to Chapter 3, "Cache Software Feature Configurations."

Upgrading Cache Software, Release 2.x.x Systems to Release 3.1

Note Verify that the features you require are in Release 3.1.1. See Chapter 3, "Cache Software Feature Configurations."

The upgrade of a Release 2.x.x image to a Release 3.x.x. image is a three-part process as follows:

1. Install a special upgrade image.

2. Reboot with the upgrade image, rewrite the boot ROM, and load a Flash memory-only image into Flash memory.

3. Reboot with the Flash memory-only image, format disk drives, then install the full 3.1.x image.

Requirements

Select the image file appropriate to the model of the Content Engine.

• Serial console access is required on the Content Engine to be upgraded.

• One of the following upgrade image files is required:

– ce507-cache-2.x-UPGRADE.bin

–ce507-cache-2.x-UPGRADE.pax

–ce560-cache-2.x-UPGRADE.bin

–ce560-cache-2.x-UPGRADE.pax

–ce590-cache-2.x-UPGRADE.bin

–ce590-cache-2.x-UPGRADE.pax

•Flash memory-only image files for the Release 3.1 software:

–ce507-31x.flash

–ce560-31x.flash

–ce590-31x.flash

•Full-release image files for Release 3.1:

–ce507-cache-31x.bin

–ce560-cache-31x.bin

–ce590-cache-31x.bin

Procedure

Before starting your Release 2.x to Release 3.1.x upgrade, ensure that the desired Release 3.1.x Flash memory-only image file resides on an FTP server that is accessible to the Content Engine to be upgraded.

Step 1 Log in to the Content Engine through the console port.

Console access is necessary for entering initial network configuration information.

Step 2 Install the transition image for your model of Content Engine according to normal Cache software Release 2.x upgrade procedures.

Note This procedure assumes that the Content Engine is configured to boot from Flash memory. See the Cache software Release 2.x documentation for netboot and install procedures.

Step 3 With the transition image installed, determine whether the Content Engine IP parameters are properly configured with the show running-config EXEC command.

ContentEngine# show running-config

Building configuration...
Current configuration:
!
. . .
hostname ContentEngine
!
interface ethernet 0
ip address 172.16.193.250 255.255.255.224
ip broadcast-address 172.16.193.255
exit
!
!
interface ethernet 1
exit
!
ip default-gateway 172.16.193.225
ip name-server 172.16.2.133
ip domain-name cisco.com
ip route 0.0.0.0 0.0.0.0 172.16.193.225
. . .

If the IP parameters need to be modified, use the ip interface configuration command and the ip global configuration command. For instance, the basic IP parameters of IP address, default gateway, and netmask can be configured as follows:

ContentEngine# config
ContentEngine(config)# ip default-gateway ipaddress
ContentEngine(config)# interface ethernet 0
ContentEngine(config-if)# ip address ipaddress netmask
ContentEngine(config-if)# exit
ContentEngine(config)# exit
ContentEngine# write memory

Building configuration.... . [OK]
ContentEngine#

Note The Content Engine must be rebooted for changed IP parameters to take effect.
The write memory EXEC command saves the configuration to Flash memory.

Step 4 Access the Content Engine TCL shell and enter upgrade to execute the TCL upgrade script.

ContentEngine# tcl
tcl% upgrade

Step 5 Enter the following information when prompted:

•Server host name or IP address of the FTP server on which the 3.1.x Flash memory-only image resides

•Filename and path to the Release 3.1.x Flash memory-only image on the FTP server

•Filename of the Release 3.1.x Flash memory-only image file

•Username on the FTP server

•Password on the FTP server

•Confirmation of the FTP configuration (enter yes)

•Confirmation of the startup configuration parameters (enter yes)

If you do not confirm the startup parameters, you must perform a startup configuration when the Content Engine boots with the Flash memory-only image.

•Password

•Confirmation to begin writing the Flash memory-only image to Flash memory (enter yes)

FTP Server IP Address: 172.16.63.150
Remote Filename :ce590-31x_sysimg.flash
Remote username : my_ftp_username
Remote password : my_ftp_password
Are you sure you want to do this?
Type YES if you are:YES
upgrade:checking integrity of cookie...
cookie is valid.
upgrade:allocating memory for new image...
upgrade:saving old bootrom (boot by hitting 'D')...
. . . . . . . . BootROM length is 304397
Current Network parameters for this box are:
Ip address = 172.10.13.8
Ip mask = 255.255.255.0
Ip gateway = 172.10.55.2
Host name = CE_590
Those parameters may be saved so that the new version software will
automatically pick them up. If you choose not to save them now,
you'll need to input them manually later during upgrade process.
Want to save those network parameters now? Save?[yes]: yes
upgrade:Please specify password for admin so that upgraded software
will be safer after it comes up. Valid password would be alphanumerics
containing 3 to 8 characters.
Note:Your password WON'T BE SHOWN on the screen when you type it.
Enter password: ******
Re-enter password: ******
Password is accepted.
upgrade:save network parameters....
upgrade:initiating FTP download...
upgrade:12713984 bytes transferred
About to write to flash! Your old software will
no longer exist on flash. Are you sure you
want to do this? Type YES if you are: YES
Ok, initiating flash write
FlashUpgrade:invoked
FlashUpgrade[0]: erasing: . - programming:
FlashUpgrade[1]: erasing: . - programming:
FlashUpgrade[2]: erasing: . - programming:
....

Flash memory is now updated with the Release 3.1 Flash memory-only image.

Step 6 Perform a cold reboot using the following command:

tcl% reboot cold

The Content Engine reboots from Flash memory, running the Release 3.1 Flash memory-only system image.

Step 7 Perform the following substeps to partition and format the disk drives in the Content Engine for the Release 3.1 software requirements.

Release 3.1 software cannot read or write Release 2.x disk partitions. The optional software available with Release 3.1 requires creating new disk partitions. See the "Maintaining the Hard Disk Storage" section for details on Release 3.1 disk partitions.

a. View all disk drives available to the Content Engine (and Storage Array if connected) by entering the show disks EXEC command:

ContentEngine# show disks
disk00 (scsi host 0, channel 0, id 0)
disk01 (scsi host 0, channel 0, id 1)

b. Remove all disk partitions with the disk erase-all-partitions EXEC command:

ContentEngine# disk erase-all-partitions disk00
ContentEngine# disk erase-all-partitions disk01

c. Create an swfs partition with the disk recover EXEC command. The swfs partition stores components of the Release 3.1 optional software.

ContentEngine# disk recover

d. Create and mount a sysfs partition. In this example we create a partition consuming 20 percent of the total disk space on disk00.

ContentEngine# disk partition disk00/01 20% sysfs
ContentEngine# sysfs format disk00/01
ContentEngine# sysfs mount disk00/01 local1

Step 8 Change the present working directory to /local1 with the cd EXEC command:

ContentEngine# cd /local1
ContentEngine# pwd
/local1
ContentEngine#

Step 9 Download the full Release 3.1 image with the copy ftp disk EXEC command:

ContentEngine# copy ftp disk server-address server-directory ce590-31x_FCS.bin

When the following FTP authentication challenge appears, enter your FTP username and password:

Enter username for remote ftp server: my_ftp_user_name
Enter password for remote ftp server: my_ftp_password

The image file is downloaded to the currently mounted sysfs directory.

Step 10 Install the downloaded image file with the install EXEC command.

ContentEngine# install ce590-31x_FCS.bin

Step 11 Save the running configuration with the write mem EXEC command:

ContentEngine# write mem

Step 12 Reboot the Content Engine with the reload EXEC command.

ContentEngine# reload
Proceed with reload?[confirm] yes

Once the reboot is complete, Release 3.1 and optional software are ready for configuration.

Downgrading Cache Software, Release 3.1 Systems to Release 2.x.x

The downgrade of a Release 3.1 image to a Release 2.x.x image is a three-part process as follows:

1. Netboot with a special transition image.

2. With the transition image, rewrite the boot ROM, and load a Release 2.x.x Flash memory-only image into Flash memory.

3. Reboot with the Flash memory-only image, reformat the disk drives, and install a standard Release 2.x.x .pax file.

Requirements

Select the image file appropriate to the Content Engine.

•Serial console access is required on the Content Engine to be downgraded.

•One of the following transition image files is required:

– ce507-cache-2.x-UPGRADE.bin

–ce560-cache-2.x-UPGRADE.bin

–ce590-cache-2.x-UPGRADE.bin

•One of the following Release 2.3.0 Flash memory-only image files is required:

–ce507-cache-230.flash

–ce560-cache-230.flash

–ce590-cache-230.flash

•One of the full 2.x.x software release files is required:

–ce507-2.x.x_FCS.pax

–ce560-2.x.x_FCS.pax

–ce590-2.x.x_FCS.pax

Note The Release 3.1.x to Release 2.x transition file may contain the word UPGRADE although it is used in a downgrade procedure.

Procedure

Before starting your Release 3.1 to Release 2.x.x downgrade, ensure that the transition image, the Release 2.3.0 target Flash memory-only image, and the full Release 2.x.x software release file reside on an FTP server that is accessible to the Content Engine being downgraded.

Step 1 Log in to the Content Engine through the console port.

Console access is necessary for entering initial network configuration information.

Before proceeding with the following steps, read and understand the entire procedure. Step 3 requires that you act promptly, or you will be required to start over.

Step 2 At the CLI prompt, reboot the Content Engine with the reload EXEC command.

ContentEngine# reload
Proceed with reload?[confirm] yes

The autoboot sequence begins and the BIOS boot messages appears.

Symbios, Inc. PCI boot ROM successfully installed!
.....
.....

Step 3 Perform the following substeps to interrupt the autoboot sequence:

a. Press the D key when you see the following message:

Cisco CE Booting From Flash.

b. Press the Spacebar when you see the following message:

Press any key to stop auto-boot...

Step 4 Perform the following substeps to enable the Content Engine to netboot the upgrade image.

a. Enter c in the [CE500 Series] field.

[CE500 Series]:c

b. Enter the network parameters to enable a netboot from the Release 2.x upgrade image on the FTP server, as shown in the example:

boot device (flash,net) [ flash]:net
file name [ ] :/somedirectory/ce590-cache-2.x-UPGRADE.bin
cache IP address [ 10.1.16.104]:
IP network mask [ 255.255.254.0]:
server IP address [ ]:172.16.63.150
gateway IP address [ 10.1.16.1]: 10.1.16.2
protocol (rcp,ftp,tftp) [ ]: ftp
username [ ]: my_ftp_username
password [ ]: my_ftp_password
flags [ 0]:

Step 5 Enter @ in the [CE500 Series]field to continue the boot sequence.

[CE500 Series]: @

boot device (flash,net) [ net]:
file name [/somedirectory/ce590-cache-2.x-transition.bin]:
cache IP address [ 10.1.16.104]:
IP network mask [ 255.255.254.0]:
server IP address [ 172.16.63.150]:
gateway IP address [ 10.1.16.2]:
protocol (rcp,ftp,tftp) [ ftp]:
username [ my_ftp_username]:
password [ my_ftp_password]:
flags [ 0]:

Loading from the network
Attaching network interface fei0... done.
Attaching network interface lo0... done.
Loading... Starting at 0x108000...

Step 6 Log in to the Content Engine as admin.

Step 7 With the upgrade image installed, verify that the Content Engine IP parameters are properly configured with the show running-config EXEC command.

ContentEngine# show running-config

Building configuration...
Current configuration:
!
. . .
hostname ContentEngine
!
interface ethernet 0
ip address 10.1.16.104
ip broadcast-address 172.16.193.255
exit
!
!
interface ethernet 1
exit
!
ip default-gateway 10.1.16.2
ip name-server 172.16.2.133
ip domain-name cisco.com
ip route 0.0.0.0 0.0.0.0 172.16.193.225
. . .

If the IP parameters require modification, use the ip interface configuration command and the ip global configuration command. For instance, the basic IP parameters of IP address, default gateway, and netmask can be configured as follows:

ContentEngine# config
ContentEngine(config)# ip default-gateway ipaddress
ContentEngine(config)# interface ethernet 0
ContentEngine(config-if)# ip address ipaddress netmask
ContentEngine(config-if)# exit
ContentEngine(config)# exit
ContentEngine# write memory

Building configuration.... . [OK]
ContentEngine#

Note The Content Engine must be rebooted for changed IP parameters to take effect.
The write memory EXEC command saves the configuration to Flash memory.

Step 8 Access the Content Engine TCL shell and enter upgrade to execute the TCL upgrade script.

ContentEngine# tcl
tcl% upgrade

Step 9 Enter the following information when prompted:

•Server host name or IP address of the FTP server on which the Release 2.x.x Flash memory-only image resides

•Filename and path to the Release 2.x.x Flash memory-only image on the FTP server

•Filename of the Release 2.x.x Flash memory-only file

•Username on the FTP server

•Password on the FTP server

•Confirmation of the FTP configuration (enter yes)

•Refusal to save the network parameters (enter no)

By not confirming the startup parameters, you are forced to perform a startup configuration when the Content Engine boots with the Flash memory-only image.

•Password

•Confirmation to begin writing the Flash memory-only image to Flash memory (enter yes)

Note If the Content Engine being downgraded was previously upgraded from Release 2.x.x to Release 3.1 with the procedures described in the "Upgrading Cache Software, Release 2.x.x Systems to Release 3.1" section, the Release 2.x system network configuration is still preserved in Flash memory and may be different from the Release 3.1.x configuration displayed by the upgrade script. If you type yes to confirm the network parameters, it is the former Release 2.x configuration that boots.

FTP Server IP Address: 172.16.63.150
Remote Filename :ce590-cache-230.flash
Remote username : my_ftp_username
Remote password : my_ftp_password
Are you sure you want to do this?
Type YES if you are:YES
upgrade:checking integrity of cookie...
cookie is valid.
upgrade:allocating memory for new image...
upgrade:saving old bootrom (boot by hitting 'D')...
. . . . . . . . BootROM length is 304397
Current Network parameters for this box are:
Ip address = 172.10.13.8
Ip mask = 255.255.255.0
Ip gateway = 172.10.55.2
Host name = CE_590
Those parameters may be saved so that the new version software will
automatically pick them up. If you choose not to save them now,
you'll need to input them manually later during upgrade process.
Want to save those network parameters now? Save?[yes]: no
upgrade:initiating FTP download...
upgrade:12713984 bytes transferred
About to write to flash! Your old software will
no longer exist on flash. Are you sure you
want to do this? Type YES if you are: YES
Ok, initiating flash write
FlashUpgrade:invoked
FlashUpgrade[0]: erasing: . - programming:
FlashUpgrade[1]: erasing: . - programming:
FlashUpgrade[2]: erasing: . - programming:
....

Flash memory is now updated with the Release 2.x.x Flash memory-only image.

Step 10 Perform a cold reboot using the following command:

tcl% reboot cold

The Content Engine begins the autoboot sequence.

Step 11 Change the boot device parameter to boot the Content Engine from Flash Memory.

Perform the following substeps to interrupt the autoboot sequence:

a. Press the D key when you see the following message:

Cisco CE Booting From Flash.

b. Press the Spacebar after you see the following message:

Press any key to stop auto-boot...

c. Enter c in the [CE500 Series] field.

[CE500 Series]:c

d. Enter flash as the boot device parameter. Change the network parameters as necessary.

boot device (flash,net) [ net]:flash
file name[/somedirectory/ce590-cache-2.x-UPGRADE.bin ]:
cache IP address [ 10.1.16.104]:
IP network mask [ 255.255.254.0]:
server IP address [ 172.16.63.150]:
gateway IP address [ 10.1.16.2]:
protocol (rcp,ftp,tftp) [ ftp]:
username [ my_ftp_username]:
password [ my_ftp_password]:
flags [ 0]:

Step 12 Enter @ in the [CE500 Series] field to continue the boot sequence.

[CE500 Series]: @
boot device (flash,net) [ flash]:
file name [/somedirectory/ce590-cache-2.x-upgrade.bin]:
cache IP address [ 10.1.16.104]:
IP network mask [ 255.255.254.0]:
server IP address [ 172.16.63.150]:
gateway IP address [ 10.1.16.1]:
protocol (rcp,ftp,tftp) [ ftp]:
username [ my_ftp_username]:
password [ my_ftp_password]:
flags [ 0]:

Starting at 0x108000...

The Content Engine is now running the Release 2.x.x Flash memory-only image.

Step 13 Log in as admin.

Step 14 Perform the following substeps to partition and format the disk drives of the Content Engine for Release 2.x.x software.

Release 2.x.x software cannot read or write Release 3.x disk partitions.

a. List all the disk drives available to the Content Engine with the show disk EXEC command:

contentengine# show disks
/c0t0d0 (scsi bus 0, unit 0, lun 0)
/c0t1d0 (scsi bus 0, unit 1, lun 0)

b. Partition and format all the disk drives with the disk manufacture EXEC command:

contentengine# disk manufacture c0t0d0
contentengine# disk manufacture c0t1d0

Step 15 Install and reload the 2.x .pax file of your choice according to standard Release 2.x upgrade procedures.

Maintaining the Hard Disk Storage

Disk maintenance consists of creating and modifying disk partitions according to the configuration of the Content Engine. See the Cisco Cache Software Command Reference, Release 3.1 for descriptions of commands and usage guidelines. Explanations and procedures for disk maintenance are included in the following sections:

• Disk System Overview

• Preparing an swfs Partition

• Preparing a sysfs Partition

• Preparing a cfs Partition

• Preparing a mediafs Partition

• Disk Preparation Procedure for the Cisco Storage Array

Disk System Overview

Release 3.1 has four types of disk file systems, each with an associated disk partition type, as described in Table 2-1.

Table 2-1 Cache Software Release 3.1 Disk Partition Types

Partition Name

Purpose of Partition

cfs (cache file system)

Caches HTTP and FTP objects.

mediafs (media file system)

Caches streaming media files.

swfs (software file system)

Stores portions of the optional software.

sysfs (system file system)

Stores system image files and output from logging processes.

Up to four partitions can coexist on the same physical disk, but there can be only one swfs partition per system. The partitions on a disk can have different sizes. The partitions are checked and repaired automatically when they mounted during the bootup or system reload sequence.

In the CLI, each disk is uniquely identified with a diskname made from the word "disk" and a two-digit identifier (for example, disk00, disk01, disk02, and so forth). Partition names consist of the disk name, a forward slash character, and the partition number (for example, disk00/00, disk00/01, disk00/02, disk00/03, disk01/00, and so forth).

A disk partition must be formatted and mounted before the system can use it for storage. To create a partition on a disk, use the disk partition EXEC command. To format, mount, and unmount the different partition types, use the cfs, mediafs, and sysfs EXEC commands.

Note The swfs partition is factory-installed, or created as part of a software upgrade procedure and cannot be unmounted or modified.

Use the disk manufacture and disk prepare EXEC commands to make an entire disk a mediafs or cfs partition type. For the specified disk, either command unmounts all partitions, erases all partitions, creates the specified partition type, and formats the disk, but only the disk manufacture command mounts the newly created partition.

Use the disk erase-all-partitions, and disk erase-partition EXEC commands to erase all or a specified partition from a disk.

To display all the disks available to the Content Engine, use the show disks EXEC command.

ContentEngine# show disks
disk00 (scsi host 0, channel 0, id 0)
disk01 (scsi host 0, channel 0, id 1)
disk02 (scsi host 3, channel 0, id 0)
disk03 (scsi host 3, channel 0, id 1)
disk04 (scsi host 3, channel 0, id 2)
disk05 (scsi host 3, channel 0, id 3)
disk06 (scsi host 3, channel 0, id 4)
disk07 (scsi host 3, channel 0, id 5)
disk08 (scsi host 3, channel 0, id 8)
disk09 (scsi host 3, channel 0, id 9)

To display the partitions on a specific disk, use the show disk-partitions diskname EXEC command.

ContentEngine# show disk-partitions disk00
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: SWFS 32 14226579 System Reserved
1: SYSFS 14226611 21338112 mounted at local1
2: NONE
3: NONE

Use the show sysfs volumes, show cfs volumes, and show mediafs volumes EXEC commands to display information particular to the respective partition types.

For information on how to create, modify, or use a specific disk partition, refer to the appropriate section as follows:

• Preparing a sysfs Partition

• Preparing a cfs Partition

• Preparing a mediafs Partition

• Disk Preparation Procedure for the Cisco Storage Array

Preparing an swfs Partition

The software file system (swfs) partition stores portions of optional software, such as the RealProxy. The swfs partition is either factory-installed or installed during a software upgrade. There is only one swfs partition permitted in the system. It is always on disk00, cannot be unmounted or removed, and is fixed in size at 1.5 gigabytes.

Table 2-1describes the Release 3.1 commands related to the swfs partition.

Table 2-2 Software File System (swfs) Related Commands

swfs-Related Command

Syntax

Description

disk recover

disk recover

Creates an swfs partition at disk00/00.

show disk-partitions

show disk-partitions diskname

Displays disk partition information.

show disks

show disks

Displays disk names and Small Computer System Interface (SCSI) identifiers.

If disk00 is damaged or replaced, perform the following actions to re-create the swfs partition:

Step 1 Power down the system.

Step 2 Insert the new disk drive.

Step 3 Power up system.

Step 4 Log in and execute the disk recover EXEC command.

Step 5 Verify that the partition was created with the show disk-partitions disk00 EXEC command.

ContentEngine# show disk-partitions disk00
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: SWFS 32 3145728 System Reserved
1: SYSFS 3145760 32419840 mounted at local1
2: NONE
3: NONE

Free disk space: 880 blocks (0 M)

Step 6 Reinstall the Release 3.1 full-system image that contains the option software.

Preparing a sysfs Partition

The sysfs partitions store Content Engine logging processes and downloaded system images. Two sysfs mounting points are currently supported by the Cache software (local1 and local2). The sysfs partitions are typically on disk00 or disk01. At least one sysfs partition must be mounted before logging processes can operate. The content of sysfs partitions can be viewed or manipulated with the commands listed in Table 2-3.

Table 2-3 System File System (sysfs)-Related Commands

sysfs-Related Command

Syntax

Description

cd

cd directoryname

Changes the current directory.

copy

copy disk flash imagename

copy disk ftp {hostname | ipaddress} remotefiledir remotefilename localfilename

copy disk startup-config filename

copy flash disk imagename

copy ftp disk {hostname | ipaddress} remotefiledir remotefilename localfilename

copy ftp flash {hostname | ipaddress} remotefiledir remotefilename

copy running-config disk filename

copy running-config startup-config

copy running-config tftp {hostname | ipaddress} remotefilename

copy startup-config disk filename

copy startup-config tftp {hostname | ipaddress} remotefilename

copy system-status disk filename

copy tech-support disk filename

copy tech-support tftp {hostname | ipaddress} remotefilename

copy tftp disk {hostname | ipaddress} remotefilename localfilename

copy tftp flash {hostname | ipaddress} remotefilename

Copies configuration or image files to disk, Flash memory, or remote server.

cpfile

cpfile sourcefilename targetfilename

Copies files.

delfile

del filename

Removes a file.

deltree

deltree directory

Removes directory and all subdirectories.

dir

dir [directory]

Displays files in long list format.

disk

disk erase-all-partitions diskname

disk erase-partition partition

disk partition partition partition_size sysfs

Disk management commands.

logging

logging console enable

logging console priority loglevel

logging disk {enable | filename filename | priority loglevels | recycle size}

logging facility facility

logging host {ipaddress | priority loglevel}

Configures system logging (syslog). Log files are written the currently mounted sysfs volume.

lls

lls [directory]

Displays directory files in long list format.

ls

ls [directory]

Displays files in directory.

mkdir

mkdir directory

Makes directory.

mkfile

mkfile filename

Makes 0 byte file (for testing).

pwd

pwd

Displays path name of present working directory.

rename

rename oldfilename newfilename

Renames a file.

show disk-partitions

show disk-partitions diskname

Displays disk partition information.

show disks

show disks

Displays disk names and SCSI identifiers.

sysfs

sysfs check partition_name

sysfs format partition_name

sysfs mount partition_name {local1 | local2}

sysfs repair partition_name

sysfs sync

sysfs unmount {local1 | local2}

Maintains system file system partitions.

rmdir

rmdir directory

Removes directory.

show disk-partitions

show disk-partitions diskname

Displays disk partition information.

show disks

show disks

Displays disk names and SCSI identifiers.

show statistics

show statistics http usage

show statistics transaction-logs

Displays statistics relevant to sysfs partitions.

show sysfs

show sysfs volumes

Displays sysfs partition names, mount status, and sizes.

transaction-log

transaction-log force {archive | export}

Forces archive of working log file to make a transaction log file.

transaction-logs

transaction-logs archive interval every-day {at time | every hour}

transaction-logs archive interval every-hour {at minute | every interval}

transaction-logs archive max-file-size filesize

transaction-logs enable

transaction-logs export enable

transaction-logs export ftp-server {hostname | servipaddrs} login passw directory

transaction-logs file-marker

transaction-logs sanitize

Configures transaction logging.

type

type filename

Displays a file to screen.

The following example prepares a secondary sysfs partition on disk01, assuming that a primary disk sysfs partition already exists on disk00/01:

Step 1 Use the show disks EXEC command to display partition types and sizes on disk01.

ContentEngine# show disk-partitions disk01
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: NONE
1: NONE
2: CFS 32 10669934 mounted
3: MEDIAFS 10669966 14226579 mounted
Free disk space: 10669935 blocks (5209 M)

The sysfs partition can be at disk01/00 or disk01/01, with a maximum size of 5209 megabytes.

Step 2 Use the disk partition EXEC command to create a 100-megabyte sysfs partition at disk01/00.

ContentEngine# disk partition disk01/00 100M sysfs

ContentEngine# show disk-partitions disk01
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: SYSFS 24896545 204800 unformated, unmounted
1: NONE
2: CFS 32 10669934 mounted
3: MEDIAFS 10669966 14226579 mounted
Free disk space: 10465135 blocks (5109 M)

Step 3 Format the sysfs partition with the sysfs format EXEC command.

ContentEngine# sysfs format disk01/00
Formatting sysfs on disk01/00
Formatting disk01/00 sysfs ok

ContentEngine# show disk-partitions disk01
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: SYSFS 24896545 204800 formatted, unmounted
1: NONE
2: CFS 32 10669934 mounted
3: MEDIAFS 10669966 14226579 mounted
Free disk space: 10465135 blocks (5109 M)

Step 4 Use the sysfs mount EXEC command to mount the sysfs partition at volume name /local2.

ContentEngine# sysfs mount disk01/00 local2
Checking sysfs on disk01/00
disk01/00 has been checked OK
Mounted disk01/00 to /local2

ContentEngine# show disk-partitions disk01
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: SYSFS 24896545 204800 mounted at local2
1: NONE
2: CFS 32 10669934 mounted
3: MEDIAFS 10669966 14226579 mounted
Free disk space: 10465135 blocks (5109 M)

Preparing a cfs Partition

The cfs partitions cache HTTP and FTP objects. The contents of a cfs partition cannot be examined or modified (other than by deleting all the objects with cfs clear or by completely erasing a partition). Commands related to maintaining the cfs partitions are listed in Table 2-4.

Table 2-4 Cache File System (cfs)-Related Commands

cfs-Related Command

Syntax

Description

cfs

cfs clear partition [force]

cfs format partition

cfs mount partition

cfs reset partition

cfs sync partition

cfs unmount partition

Cache file system commands.

disk

disk erase-all-partitions diskname

disk erase-partition partition

disk manufacture diskname cfs

disk partition partition partition_size cfs

disk prepare diskname cfs

Disk management commands for cfs partitions.

show cfs

show cfs {statistics | volumes}

Displays cache file system status.

show disk-partitions

show disk-partitions diskname

Displays cfs disk partitions, sizes, and mount status.

show disks

show disks

Displays disk names and SCSI identifiers.

show statistics

show statistics cfs

show statistics http usage

Displays cfs-related statistics.

The following example makes all of disk07 a cfs partition. Use the disk manufacture EXEC command to unmount existing partitions, and then erase, partition, format, and mount disk07 as a single cfs partition.

ContentEngine# disk manufacture disk07 cfs
Unmounting partition disk07/01 ...Ok
Partitioning the disk ...ok
Writing disk signature ...ok
Formatting the partition ...Formatting cfs on disk07/00
Formatting disk07/00 cfs ok
ok.
Mounting the partition ...ok.

ContentEngine# show disk-partitions disk07
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: CFS 32 35566448 mounted
1: NONE
2: NONE
3: NONE
Free disk space: 0 blocks (0 M) .

If all the cfs partitions are unmounted, the Content Engine continues to fulfill client content requests directly with the origin servers, though no content can be cached. To unmount a cfs partition, use the cfs unmount partition EXEC command. The cfs unmount partition command frees the in-memory data structures that map to the physical (disk) cfs partition.

The cfs clear partition command deletes nonbusy objects from the specified cfs volume. A nonbusy object is an object that is not being accessed (read or written). The cfs clear partition command (without force) deletes all possible objects without generating a broken GIF or HTML message to the client.

The cfs clear partition force command deletes all objects, busy or nonbusy, and may generate broken GIF or HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Content Engine disk when a cfs clear partition force command is executed, the application stops caching that object but still delivers the object from the web server to the client.

The cfs reset partition command unmounts, formats, and mounts a specified partition. Unmounting a partition can result in broken GIF or HTML messages for objects that are being read from the disk (cache hits) when the command is executed. When a cfs partition is reset, all cfs data on that partition is lost.

Note The cfs reset command cannot be invoked on an unmounted partition.

The cfs format partition command creates the cache file system internal "dbs" for the cfs partition of the disk if the partition is unmounted. It formats the cfs partition to prepare it for a cfs mount. The cfs mount partition command creates and maps data structures in memory to the cfs partition.

The cfs sync partition command synchronizes the cache file system contents from memory to disk. Although synchronization is performed at regular intervals while the Content Engine is running, this command can be used to ensure that all data is written to disk before you reset or turn off the Content Engine. Synchronization can also be done with the cache synchronize command.

Preparing a mediafs Partition

The optional streaming media software caches streaming media files in the mediafs partitions. The content on a mediafs partition cannot be examined. Commands related to maintaining mediafs partitions are listed in Table 2-5.

Table 2-5 Media File System (mediafs)-Related Commands

mediafs-Related Command

Syntax

Description

disk

disk erase-all-partitions diskname

disk erase-partition partition

disk manufacture diskname mediafs

disk partition partition partition_size mediafs

disk prepare diskname mediafs

Disk management commands.

mediafs

mediafs {format partition_name | mount partition_name | sync partition_num | unmount partition_num}

Media file system commands.

show disk-partitions

show disk-partitions diskname

Displays disk partition information.

show disks

show disks

Displays disk names and SCSI identifiers.

show mediafs

show mediafs volumes

Displays information for mediafs partitions.

show statistics

show statistics mediacache real requests

show statistics mediacache real savings

Displays mediafs-related statistics.

If all the mediafs partitions are unmounted, the Content Engine continues to fulfill client streaming media content requests directly with the origin servers, though no content can be cached. To unmount a mediafs partition, use the mediafs unmount partition-num EXEC command. The mediafs unmount partition-num command frees the in-memory data structures that map to the physical (disk) mediafs partition.

The mediafs format partition command creates the cache file system internal "dbs" for the mediafs partition of the disk if the partition is unmounted. It formats the mediafs partition to prepare it for a mediafs mount. The mediafs mount partition-name command creates and maps data structures in memory to the mediafs partition.

The mediafs sync partition_num command synchronizes the cache file system contents from memory to disk. Although synchronization is performed at regular intervals while the Content Engine is running, this command can be used to ensure that all data is written to disk before you reset or turn off the Content Engine. Synchronization can also be done with the cache synchronize command.

The following example makes all of disk07 a mediafs partition. Use the disk manufacture EXEC command to unmount existing partitions, and then erase, partition, format, and mount disk07 as a single mediafs partition.

ContentEngine# disk manufacture disk07 mediafs
Partitioning the disk ...ok
Writing disk signature ...ok
Formatting the partition ...Formatting mediafs on disk07/00
Formatting disk07/00 mediafs ok
ok.
Mounting the partition ...Checking MEDIAFS on disk07/00
disk07/00 has been checked OK
Mounted disk07/00 ok
ok.

ContentEngine# show disk-partitions disk07
Disk size in 512 byte blocks: 35566448
num: type start size status
-----------------------------------------------------
0: MEDIAFS 32 35566448 mounted
1: NONE
2: NONE
3: NONE
Free disk space: 0 blocks (0 M)

Disk Preparation Procedure for the Cisco Storage Array

The Cisco Storage Array is shipped with unformatted hard disks. You must partition, format and mount each drive. Storage Array disks are most often intended for mediafs and cfs partitions, although it is possible to create sysfs partitions too. Use the disk manufacture or disk prepare EXEC commands to make an entire disk a mediafs or a cfs partition. Use the disk partition, cfs, mediafs, and sysfs EXEC commands to create and maintain different partition types on the same disk.

The following procedure describes how to create new partitions on a Cisco Storage Array:

Step 1 Make sure that the disk drives are properly inserted into the Storage Array slots, and that the SCSI cable connectors on the Content Engine and Storage Array are tightened.

Step 2 Power on the Storage Array, and then power on the Content Engine.

Step 3 Determine which disks are accessible to the Content Engine with the show disks EXEC command.

Console# show disks
disk00 (scsi host 0, channel 0, id 0)
disk01 (scsi host 0, channel 0, id 1)
disk02 (scsi host 3, channel 0, id 0)
disk03 (scsi host 3, channel 0, id 1)
disk04 (scsi host 3, channel 0, id 2)
disk05 (scsi host 3, channel 0, id 3)
disk06 (scsi host 3, channel 0, id 4)
disk07 (scsi host 3, channel 0, id 5)

The leftmost hard disk inserted in an SA-6 Storage Array bus is always disk 02. Counting to the right, the next disk is 03, the next disk is 04, and so on. There can be empty slots between disks on the same bus, but this is not recommended.

In a two-host, split-bus configuration, each bus is counted independently. For example, in a split-bus, fully populated SA-6 Storage Array, bus 0 disknumbers are 02, 03, and 04, and bus 1 disknumbers are also 02, 03, and 04. If the first disk on bus 1 is removed (slot 5 is empty) and the Content Engine is rebooted, bus 0 numbers are still 02, 03, and 04, but bus 1 numbers are 02 and 03. The empty disk slot is skipped, and the count begins with the first detected disk on bus 1.

Step 4 Execute the disk manufacture command for each disk dedicated entirely as a mediafs or a cfs partition.

In the following example, disk02 and disk03 are dedicated to the mediafs and the cfs, respectively. They are partitioned, formatted, and mounted with the disk manufacture EXEC command. Disk03 is allocated 50 percent to the mediafs, and 50 percent to the cfs:

ContentEngine# disk manufacture disk02 mediafs
Partitioning the disk ...ok
Writing disk signature ...ok
Formatting the partition ...Formatting mediafs on disk02/00
Formatting disk02/00 mediafs ok
ok.
Mounting the partition ...Checking MEDIAFS on disk02/00
disk02/00 has been checked OK
Mounted disk02/00 ok
ok.

ContentEngine# disk manufacture disk03 cfs
Partitioning the disk ...ok
Writing disk signature ...ok
Formatting the partition ...Formatting cfs on disk03/00
Formatting disk03/00 cfs ok
ok.
Mounting the partition ...ok.

ContentEngine# disk partition disk04/00 50% cfs
ContentEngine# disk partition disk04/01 50% mediafs

ContentEngine# cfs format disk04/00
Formatting cfs on disk04/00
Formatting disk04/00 cfs ok

ContentEngine# mediafs format disk04/01
Formatting cfs on disk04/01
Formatting disk04/01 mediafs ok

ContentEngine# cfs mount disk04/00
ContentEngine# mediafs mount disk04/01
Checking MEDIAFS on disk04/01
disk04/01 has been checked OK
Mounted disk04/01 ok

Step 5 Enter the show cfs volumes and show mediafs volumes EXEC commands to verify that the partitions are correctly sized, formatted, and mounted.

ContentEngine# show cfs volumes
show cfs volumes
disk03/00 : mounted size: 35566448
disk04/00 : mounted size: 17783224

ContentEngine# show mediafs volumes
show mediafs volumes
disk02/00 : mounted size: 35566448
disk04/01 : mounted size: 17783224

Recovering the System Software

The Content Engine has a resident rescue system image that is invoked should the image in
Flash memory be corrupted. A corrupted system image can result from a power failure that occurs while a system image is being written to Flash memory. The rescue image can download a system image to the Content Engine main memory and write it to Flash memory.

To install a new system image with the rescue image, perform the following steps:

Step 1 Download the .bin system image file to a Windows NT, Linux, or UNIX host that is running an FTP server.

Step 2 Establish a console connection to the Content Engine and open a terminal session.

Step 3 Reboot the Content Engine by toggling the power on/off switch.

The rescue image dialog menu appears. The following example demonstrates how to interact with the rescue dialog (user input is denoted by entries in bold typeface):

This is the rescue image. The purpose of this software is to let
you download and install a new system image onto your system's
boot flash device. This software has been invoked either manually
(if you entered `***' to the bootloader prompt) or has been
invoked by the bootloader if it discovered that your system image
in flash had been corrupted.

To download an image, this software will request the following
information from you:
- which network interface to use
- IP address and netmask for the selected interface
- default gateway IP address
- server IP address
- which protocol to use to connect to server
- username/password (if applicable)
- path to system image on server

Please enter an interface from the following list:
0: FastEthernet 0/0
1: FastEthernet 0/1
0
Using interface FastEthernet 0/0

Please enter the local IP address to use for this interface:
[Enter IP Address]: 172.16.22.22

Please enter the netmask for this interface:
[Enter Netmask]: 255.255.255.224

Please enter the IP address for the default gateway:
[Enter Gateway IP Address]: 172.19.19.1

Please enter the IP address for the FTP server where you wish
to obtain the new system image:
[Enter Server IP Address]: 172.16.10.10

Please enter your username on the FTP server (or 'anonymous'):
[Enter Username on server (e.g. anonymous)]: anonymous

Please enter the password for username 'anonymous' on FTP server (an email address):

Please enter the directory containing the image file on the FTP server:
[Enter Directory on server (e.g. /)]: /

Please enter the file name of the system image file on the FTP server:
[Enter Filename on server]: dmdsysimg-test.bin

Here is the configuration you have entered:

Current config:
IP Address: 172.16.22.22
Netmask: 255.255.255.224
Gateway Address: 172.19.19.1
Server Address: 172.16.10.10
Username: anonymous
Password: *************
Image directory: /
Image filename: dmdsysimg-test.bin

Attempting download...
Downloaded 10711040 byte image file
A new system image has been downloaded.
You should write it to flash at this time.
Please enter 'yes' below to indicate that this is what you want to do:
[Enter confirmation ('yes' or 'no')]: yes
Ok, writing new image to flash
..................................................................................Finished writing image to flash.
Enter 'reboot' to reboot, or 'again' to download and install a new image:
[Enter reboot confirmation ('reboot' or 'again')]: reboot
Restarting system.

Initializing memory. Please wait.

Step 4 Log in to the Content Engine with your new admin password. Verify that you are running the correct version by entering the show version command.

Username: admin
Password:

Console> enable
Console# show version
Copyright (c) 1986-2000 by Cisco Systems, Inc.
Cisco Content Engine Software Release 3.00 (build eft Sep 21 2000)
Compiled 18:48:10 Sep 21 2000 by (cisco)

System was restarted on Sat Mar 15 22:12:25 2000.
The system has been up for 1 day, 5 hours, 26 minutes, 53 seconds.

You can now use the management interface or the CLI to enable WCCP or proxy mode and start caching.

Recovering a Lost Password

If a user password is forgotten, lost, or misconfigured, perform the following steps to reset the password.

Note There is no way to restore a lost password. You must reset the password to a new one, as described in this procedure.

Step 1 Establish a console connection to the Content Engine and open a terminal session.

Step 2 At the following prompt, press Return:

Cisco CE boot:hit RETURN to set boot flags:0009

Step 3 When prompted to enter bootflags, enter this value:

0x8000

For example:

Available boot flags (enter the sum of the desired flags):
0x4000 - bypass nvram config
0x8000 - disable login security

[CE boot - enter bootflags]:0x8000
You have entered boot flags = 0x8000
Boot with these flags? [yes]:yes
[Display output omitted]

Step 4 When the Content Engine completes the boot sequence, you are prompted to enter the username to access the CLI. Enter the default administrator user name (admin):

Cisco Content Engine Console

Username: admin

Setting the configuration flags field to 0x8000 lets you into the system, bypassing all security. Setting the configuration flags field to 0x4000 lets you bypass the NVRAM configuration.

Step 5 Once you see the CLI prompt, set the password for the user using the user modify username name password new-password command in the global configuration mode.

Step 6 Use the write command to save the configuration change.

Partition Name	Purpose of Partition
cfs (cache file system)	Caches HTTP and FTP objects.
mediafs (media file system)	Caches streaming media files.
swfs (software file system)	Stores portions of the optional software.
sysfs (system file system)	Stores system image files and output from logging processes.

swfs-Related Command	Syntax	Description
disk recover	disk recover	Creates an swfs partition at disk00/00.
show disk-partitions	show disk-partitions diskname	Displays disk partition information.
show disks	show disks	Displays disk names and Small Computer System Interface (SCSI) identifiers.

sysfs-Related Command	Syntax	Description
cd	cd directoryname	Changes the current directory.
copy	copy disk flash imagename copy disk ftp {hostname \| ipaddress} remotefiledir remotefilename localfilename copy disk startup-config filename copy flash disk imagename copy ftp disk {hostname \| ipaddress} remotefiledir remotefilename localfilename copy ftp flash {hostname \| ipaddress} remotefiledir remotefilename copy running-config disk filename copy running-config startup-config copy running-config tftp {hostname \| ipaddress} remotefilename copy startup-config disk filename copy startup-config tftp {hostname \| ipaddress} remotefilename copy system-status disk filename copy tech-support disk filename copy tech-support tftp {hostname \| ipaddress} remotefilename copy tftp disk {hostname \| ipaddress} remotefilename localfilename copy tftp flash {hostname \| ipaddress} remotefilename	Copies configuration or image files to disk, Flash memory, or remote server.
cpfile	cpfile sourcefilename targetfilename	Copies files.
delfile	del filename	Removes a file.
deltree	deltree directory	Removes directory and all subdirectories.
dir	dir [directory]	Displays files in long list format.
disk	disk erase-all-partitions diskname disk erase-partition partition disk partition partition partition_size sysfs	Disk management commands.
logging	logging console enable logging console priority loglevel logging disk {enable \| filename filename \| priority loglevels \| recycle size} logging facility facility logging host {ipaddress \| priority loglevel}	Configures system logging (syslog). Log files are written the currently mounted sysfs volume.
lls	lls [directory]	Displays directory files in long list format.
ls	ls [directory]	Displays files in directory.
mkdir	mkdir directory	Makes directory.
mkfile	mkfile filename	Makes 0 byte file (for testing).
pwd	pwd	Displays path name of present working directory.
rename	rename oldfilename newfilename	Renames a file.
show disk-partitions	show disk-partitions diskname	Displays disk partition information.
show disks	show disks	Displays disk names and SCSI identifiers.
sysfs	sysfs check partition_name sysfs format partition_name sysfs mount partition_name {local1 \| local2} sysfs repair partition_name sysfs sync sysfs unmount {local1 \| local2}	Maintains system file system partitions.
rmdir	rmdir directory	Removes directory.
show disk-partitions	show disk-partitions diskname	Displays disk partition information.
show disks	show disks	Displays disk names and SCSI identifiers.
show statistics	show statistics http usage show statistics transaction-logs	Displays statistics relevant to sysfs partitions.
show sysfs	show sysfs volumes	Displays sysfs partition names, mount status, and sizes.
transaction-log	transaction-log force {archive \| export}	Forces archive of working log file to make a transaction log file.
transaction-logs	transaction-logs archive interval every-day {at time \| every hour} transaction-logs archive interval every-hour {at minute \| every interval} transaction-logs archive max-file-size filesize transaction-logs enable transaction-logs export enable transaction-logs export ftp-server {hostname \| servipaddrs} login passw directory transaction-logs file-marker transaction-logs sanitize	Configures transaction logging.
type	type filename	Displays a file to screen.

cfs-Related Command	Syntax	Description
cfs	cfs clear partition [force] cfs format partition cfs mount partition cfs reset partition cfs sync partition cfs unmount partition	Cache file system commands.
disk	disk erase-all-partitions diskname disk erase-partition partition disk manufacture diskname cfs disk partition partition partition_size cfs disk prepare diskname cfs	Disk management commands for cfs partitions.
show cfs	show cfs {statistics \| volumes}	Displays cache file system status.
show disk-partitions	show disk-partitions diskname	Displays cfs disk partitions, sizes, and mount status.
show disks	show disks	Displays disk names and SCSI identifiers.
show statistics	show statistics cfs show statistics http usage	Displays cfs-related statistics.