Table Of Contents
Maintaining 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 Preparation Procedure for the Cisco Storage Array
Recovering the System Software
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
•
•
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:
•
•
•
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
•
Note
•
–
–
–
–
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
Note
Step 2
ContentEngine# copy running-config startup-configStep 3
ContentEngine# cd /local1ContentEngine# pwd/local1Step 4
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.binEnter username for remote ftp server: my_ftpserver_usernameEnter password for remote ftp server: my_ftpserver_passwordStep 5
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.binStep 6
ContentEngine# reloadProceed with reload?[confirm] yesStep 7
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.
2.
3.
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.
•
–
•
–
Procedure
Step 1
Note
Step 2
ContentEngine# copy running-config startup-configStep 3
Step 4
Step 5
a.
ContentEngine# copy ftp flash 192.168.88.89 /images ce7320-31x.sysimgb.
Enter username for remote ftp server: my_ftpserver_usernameEnter password for remote ftp server: my_ftpserver_passwordThe following messages appear:
Initiating FTP download. . .Downloaded 10685440 byte image fileA new system image has been downloaded.You should write it to flash at this time.Write to flash [yes]: _c.
The following message appears:
Ok, writing new image to flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .d.
ContentEngine# reloadProceed with reload?[confirm] yesAfter 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:mydisk00Cisco Content Engine ConsoleStep 6
Username: adminStep 7
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]:yeshost name:mycontentengineAdmin password:mypasswordPlease enter an interface from the following list:0:FastEthernet 0/01:FastEthernet 0/1enter choice:0cache IP address: 10.1.1.1IP network mask:255.255.0.0Gateway IP address: 10.1.1.2Use this configuration? [yes]:yesStep 8
ContentEngine# disk erase-all-partitions disk00Step 9
ContentEngine# disk recoverThe swfs partition is created on disk00.
Step 10
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% sysfsContentEngine# sysfs format disk00/01ContentEngine# sysfs mount disk00/01 local1Step 11
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 mediafsContentEngine# mediafs format disk03/01ContentEngine# mediafs mount disk03/01Step 12
ContentEngine# cd /local1ContentEngine# pwd/local1Step 13
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.binEnter username for remote ftp server: my_ftpserver_usernameEnter password for remote ftp server: my_ftpserver_passwordStep 14
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.binStep 15
ContentEngine# reloadProceed with reload?[confirm] yesStep 16
ContentEngine# clock set 14:22:00 24 Jan 2001WARNING: Setting the clock may cause a temporary service interruption.Do you want to proceed?[no] yesMon Jan 24 14:22:00 EST 2001ContentEngine#Step 17
Upgrading Cache Software, Release 2.x.x Systems to Release 3.1
Note
The upgrade of a Release 2.x.x image to a Release 3.x.x. image is a three-part process as follows:
1.
2.
3.
Requirements
Select the image file appropriate to the model of the Content Engine.
•
•
–
–
–
–
–
–
•
–
–
–
•
–
–
–
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
Console access is necessary for entering initial network configuration information.
Step 2
Note
Step 3
ContentEngine# show running-configBuilding configuration...Current configuration:!. . .hostname ContentEngine!interface ethernet 0ip address 172.16.193.250 255.255.255.224ip broadcast-address 172.16.193.255exit!!interface ethernet 1exit!ip default-gateway 172.16.193.225ip name-server 172.16.2.133ip domain-name cisco.comip 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# configContentEngine(config)# ip default-gateway ipaddressContentEngine(config)# interface ethernet 0ContentEngine(config-if)# ip address ipaddress netmaskContentEngine(config-if)# exitContentEngine(config)# exitContentEngine# write memoryBuilding configuration.... . [OK]ContentEngine#
Note
The write memory EXEC command saves the configuration to Flash memory.Step 4
ContentEngine# tcltcl% upgradeStep 5
•
•
•
•
•
•
•
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.
•
•
FTP Server IP Address: 172.16.63.150Remote Filename :ce590-31x_sysimg.flashRemote username : my_ftp_usernameRemote password : my_ftp_passwordAre you sure you want to do this?Type YES if you are:YESupgrade:checking integrity of cookie...cookie is valid.upgrade:allocating memory for new image...upgrade:saving old bootrom (boot by hitting 'D').... . . . . . . . BootROM length is 304397Current Network parameters for this box are:Ip address = 172.10.13.8Ip mask = 255.255.255.0Ip gateway = 172.10.55.2Host name = CE_590Those parameters may be saved so that the new version software willautomatically 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]: yesupgrade:Please specify password for admin so that upgraded softwarewill be safer after it comes up. Valid password would be alphanumericscontaining 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 transferredAbout to write to flash! Your old software willno longer exist on flash. Are you sure youwant to do this? Type YES if you are: YESOk, initiating flash writeFlashUpgrade:invokedFlashUpgrade[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
tcl% reboot coldThe Content Engine reboots from Flash memory, running the Release 3.1 Flash memory-only system image.
Step 7
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.
ContentEngine# show disksdisk00 (scsi host 0, channel 0, id 0)disk01 (scsi host 0, channel 0, id 1)b.
ContentEngine# disk erase-all-partitions disk00ContentEngine# disk erase-all-partitions disk01c.
ContentEngine# disk recoverd.
ContentEngine# disk partition disk00/01 20% sysfsContentEngine# sysfs format disk00/01ContentEngine# sysfs mount disk00/01 local1Step 8
ContentEngine# cd /local1ContentEngine# pwd/local1ContentEngine#Step 9
ContentEngine# copy ftp disk server-address server-directory ce590-31x_FCS.binWhen the following FTP authentication challenge appears, enter your FTP username and password:
Enter username for remote ftp server: my_ftp_user_nameEnter password for remote ftp server: my_ftp_passwordThe image file is downloaded to the currently mounted sysfs directory.
Step 10
ContentEngine# install ce590-31x_FCS.binStep 11
ContentEngine# write memStep 12
ContentEngine# reloadProceed with reload?[confirm] yesOnce 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.
2.
3.
Requirements
Select the image file appropriate to the Content Engine.
•
•
–
–
–
•
–
–
–
•
–
–
–
Note
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
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
ContentEngine# reloadProceed with reload?[confirm] yesThe autoboot sequence begins and the BIOS boot messages appears.
Symbios, Inc. PCI boot ROM successfully installed!..........Step 3
a.
Cisco CE Booting From Flash.b.
Press any key to stop auto-boot...Step 4
a.
[CE500 Series]:cb.
boot device (flash,net) [ flash]:netfile name [ ] :/somedirectory/ce590-cache-2.x-UPGRADE.bincache IP address [ 10.1.16.104]:IP network mask [ 255.255.254.0]:server IP address [ ]:172.16.63.150gateway IP address [ 10.1.16.1]: 10.1.16.2protocol (rcp,ftp,tftp) [ ]: ftpusername [ ]: my_ftp_usernamepassword [ ]: my_ftp_passwordflags [ 0]:Step 5
[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 networkAttaching network interface fei0... done.Attaching network interface lo0... done.Loading... Starting at 0x108000...Step 6
Step 7
ContentEngine# show running-configBuilding configuration...Current configuration:!. . .hostname ContentEngine!interface ethernet 0ip address 10.1.16.104ip broadcast-address 172.16.193.255exit!!interface ethernet 1exit!ip default-gateway 10.1.16.2ip name-server 172.16.2.133ip domain-name cisco.comip 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# configContentEngine(config)# ip default-gateway ipaddressContentEngine(config)# interface ethernet 0ContentEngine(config-if)# ip address ipaddress netmaskContentEngine(config-if)# exitContentEngine(config)# exitContentEngine# write memoryBuilding configuration.... . [OK]ContentEngine#
Note
The write memory EXEC command saves the configuration to Flash memory.Step 8
ContentEngine# tcltcl% upgradeStep 9
•
•
•
•
•
•
•
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.
•
•
Note
FTP Server IP Address: 172.16.63.150Remote Filename :ce590-cache-230.flashRemote username : my_ftp_usernameRemote password : my_ftp_passwordAre you sure you want to do this?Type YES if you are:YESupgrade:checking integrity of cookie...cookie is valid.upgrade:allocating memory for new image...upgrade:saving old bootrom (boot by hitting 'D').... . . . . . . . BootROM length is 304397Current Network parameters for this box are:Ip address = 172.10.13.8Ip mask = 255.255.255.0Ip gateway = 172.10.55.2Host name = CE_590Those parameters may be saved so that the new version software willautomatically 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]: noupgrade:initiating FTP download...upgrade:12713984 bytes transferredAbout to write to flash! Your old software willno longer exist on flash. Are you sure youwant to do this? Type YES if you are: YESOk, initiating flash writeFlashUpgrade:invokedFlashUpgrade[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
tcl% reboot coldThe Content Engine begins the autoboot sequence.
Step 11
Perform the following substeps to interrupt the autoboot sequence:
a.
Cisco CE Booting From Flash.b.
Press any key to stop auto-boot...c.
[CE500 Series]:cd.
boot device (flash,net) [ net]:flashfile 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
[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
Step 14
Release 2.x.x software cannot read or write Release 3.x disk partitions.
a.
contentengine# show disks/c0t0d0 (scsi bus 0, unit 0, lun 0)/c0t1d0 (scsi bus 0, unit 1, lun 0)b.
contentengine# disk manufacture c0t0d0contentengine# disk manufacture c0t1d0Step 15
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
Release 3.1 has four types of disk file systems, each with an associated disk partition type, as described in Table 2-1.
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
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 disksdisk00 (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 disk00Disk size in 512 byte blocks: 35566448num: type start size status-----------------------------------------------------0: SWFS 32 14226579 System Reserved1: SYSFS 14226611 21338112 mounted at local12: NONE3: NONEUse 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 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.
If disk00 is damaged or replaced, perform the following actions to re-create the swfs partition:
Step 1
Step 2
Step 3
Step 4
Step 5
ContentEngine# show disk-partitions disk00Disk size in 512 byte blocks: 35566448num: type start size status-----------------------------------------------------0: SWFS 32 3145728 System Reserved1: SYSFS 3145760 32419840 mounted at local12: NONE3: NONEFree disk space: 880 blocks (0 M)Step 6
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.
