cc/td/doc/product/webscale/uce/uce40
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Upgrading and Downgrading Your System Software

Upgrading and Downgrading Your System Software

If you purchased a new Content Engine, Content Distribution Manager, or Content Router, Cisco Application and Content Networking Software (ACNS) is already installed on your system. If you have an existing system, you can install ACNS software by performing a software upgrade. This chapter explains how to install ACNS software whether you are upgrading one device or your entire Content Delivery Network (CDN). It also includes the downgrade procedures for each software platform.

This chapter contains the following sections:

Upgrading from ACNS 4.0 to ACNS 4.x

To upgrade from ACNS 4.0 software to a future release of ACNS software, use the copy ftp install command.

Note   If you are booting the ACNS 4.0 software while your device is connected to a Cisco console server, a console session should be active or the device could enter recovery mode. If the device enters recovery mode, you need to first activate a console session and then power cycle the device for it to boot up successfully.

Requirements

To perform an upgrade from a device that is running ACNS software, you need the following:

Procedure

To install the upgrade package file, follow these steps:

Step 1   Install the upgrade package file by using the following command:

ContentEngine# copy ftp install ftp-server package-file-path package-file-name

Step 2   After the package files are copied to your system, use the reload command to reboot.

ContentEngine# reload

The installation process continues after the reboot.

Upgrading from Cache 2.x Software to ACNS 4.0 Software

This section describes how to perform a manual upgrade from Cache 2.x software to ACNS 4.0 software and also how to accomplish an automated software upgrade of multiple Content Engines using a software script designed to automate the upgrade process. The manual upgrade process is discussed first because you need to use this procedure on at least one Content Engine before you can perform an automated upgrade.

Note   After mass upgrades from Cache 2.x Software to ACNS 4.0 Software, run the write memory command on the Content Engines to avoid configuration loss.

Performing a Manual Upgrade

Manually upgrading your system from a Cache 2.x software release to ACNS 4.0 software requires the use of an intermediate "UPGRADE" software image. This section describes how to install the UPGRADE image and how to execute an upgrade.

You can install the 2.x UPGRADE image on a Content Engine running Cache 2.x software either by using netboot or by writing the image to Flash memory. Both methods are described in this section. Read the requirements section of each method to determine which method is suitable for you.

The upgrade from a Cache 2.x software image to an ACNS 4.0 software image is a three-part process as follows:

    1. Install a special UPGRADE image.

    2. Reboot with the UPGRADE image and load a Flash memory-only image into Flash memory.

    3. Reboot the Content Engine, and then install the full-release ACNS 4.0 software image.

    Note   If you are booting the ACNS 4.0 software while your device is connected to a Cisco console server, a console session should be active or the device could enter recovery mode. If the device enters recovery mode, you need to first activate a console session and then power cycle the device for it to boot up successfully.

Before beginning your Cache 2.x software to ACNS 4.0 software upgrade, ensure that the desired Flash memory-only file (the file with the .flash extension) resides on an FTP server that is accessible to the Content Engine to be upgraded.

Also, if the Content Engine is booted from the network, you need to place the 2.x UPGRADE file onto an appropriate netboot FTP or TFTP server. We strongly recommend using FTP over TFTP for netbooting because of TFTP timeouts.

If you prefer to install on Flash memory, you must copy the 2.x UPGRADE file to the Content Engine using the copy tftp flash command and then reboot the Content Engine to begin running the upgrade image. Make sure that the Content Engine is configured to boot from Flash memory. (See the "Installing the UPGRADE Image by Writing to Flash Memory" section.)

Note   The FTP server must support passive mode FTP transfers. Verify this by doing a manual passive FTP transfer before starting the software conversion process.
Images Required for the Upgrade

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

Installing the UPGRADE Image Using Netboot

This section describes how to install the 2.x UPGRADE image by booting from a network FTP server (that is, using netboot).

Requirements

Requirements for netbooting the 2.x UPGRADE image are:

Procedure

If the Content Engine is configured to boot from Flash memory (the default boot configuration), and if an FTP or TFTP server is visible to your system on the network, you can change the boot configuration to netboot. The steps that follow explain how to change the boot configuration.

Follow these steps to run the 2.x UPGRADE image using netboot:

Step 1   Reboot the Content Engine using the reload command.

Step 2   Press any key to stop the boot process when you see the following prompt:

Press any key to stop auto-boot...

At this point, you should see a prompt such as [500 Series] or a similar prompt.

Step 3   At the prompt, enter p, and then press Enter to see the boot configuration.

[500 Series]:p boot device (flash,net) [ flash]: file name [/users2/ftp/ce40-programfix.bin]: cache IP address [ 10.1.202.152]: IP network mask [ 255.255.255.0]: server IP address [ 172.25.193.244]: gateway IP address [ 10.1.202.1]: protocol (rcp,ftp,tftp) [ ftp]: username [ johndoe]: password [ MypsWrd]: flags [ 0]:

For netboot you need to set the boot device to "net" and provide the connectivity information about the FTP server. The next step explains this.

Step 4   At the prompt, enter c, and then press Enter to enter the new configuration. Fill in the fields with information pertaining to your FTP server setup.

For example,

[500 Series]:c '.' = clear field; '-' = go to previous field; ^D = quit boot device (flash,net) [ flash]:net file name [/users2/ftp/ce40-programfix.bin]:/dir1/ce507-2.x-UPGRADE-K9.bin cache IP address [ 10.1.202.152]:10.1.2.3 IP network mask [ 255.255.255.0]:255.255.255.0 server IP address [ 172.25.193.244]:172.25.193.244 gateway IP address [ 10.1.202.1]:10.1.2.1 protocol (rcp,ftp,tftp) [ ftp]:ftp username [ user4]:homer password [ MypsWrd]:duffbeer flags [ 0]:0

Step 5   Type "@" at the [500 Series] prompt to start the netboot.

[CE500 Series]:@ boot device (flash,net) [ net]: file name [/dir1/ce507-2.x-UPGRADE-K9.bin]: cache IP address [ 10.1.2.3]: IP network mask [ 255.255.255.0]: server IP address [ 172.25.193.244]: gateway IP address [ 10.1.2.1]: protocol (rcp,ftp,tftp) [ ftp]: username [ homer]: password [ duffbeer]: flags [ 0]: Loading from the network Attaching network interface fei0... done.

If the netboot is successful, the Content Engine boots and begins running the 2.x UPGRADE image.

Step 6   To verify that the 2.x UPGRADE image is running on your Content Engine, log in and enter the show version command.

ce-homer# show version Cisco Content Engine Copyright (c) 1986-2000 by Cisco Systems, Inc. Software Release:CE ver 2.51 (Build:#6 09/17/01) Compiled:14:17:18 Sep 17 2001 by biff Image text-base 0x108000, data_base 0x44380c System restarted by Power Up The system has been up for 1 minute, 14 seconds. System booted from Network - Host:171.69.26.37 File:/auto/ucsb/target/cepro_2.x-UPGRADE-b06/ce40/ce560-cache-2.x-UPGRADE-b06.bin

The output shows that the 2.x UPGRADE image is running on the Content Engine.

If the output does not show that the 2.x UPGRADE image is running, you can power cycle the device and repeat the netboot procedure.

The most common problems are:

Installing the UPGRADE Image by Writing to Flash Memory

This section explains how to install the 2.x UPGRADE image by writing it to Flash memory.

Requirements

The requirements for writing the 2.x UPGRADE image to Flash memory are:

Procedure

To run the 2.x UPGRADE image by writing to Flash memory, follow these steps:

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

Step 2   Change directory to /local.

ContentEngine# cd /local

Step 3   Use the copy tftp flash command and provide the FTP server address and filenames. For example,

ContentEngine# copy tftp flash TFTP Server IP Address:172.25.193.244 Remote Filename:ce560-cache-2.x-UPGRADE-b05.bin Copying 172.25.193.244:ce560-cache-2.x-UPGRADE-b05.bin to flash Step 1, copy tftp to disk 1656260 bytes transferred... Step 2, copy disk to flash The flash image is about to get re-programmed. Continue?[no]:YES Warning!! Don't power-cycle the box while FLASH is being programmed File size = 1656260 Erasing program-image sectors in flash: . . . . . . . . . . . . . . Programming program-image sectors in flash: 100% complete... Checking to see that the file was copied correctly... OK

Step 4   After the write to Flash memory is complete, reboot the Content Engine using the reload command.

ContentEngine# reload Proceed with reload?[confirm]

Step 5   To verify that the 2.x UPGRADE image is running on your Content Engine, log in and enter the show version command.

ContentEngine# show version Cisco Content Engine Copyright (c) 1986-2000 by Cisco Systems, Inc. Software Release:CE ver 2.51 (Build:#5 08/28/01) Compiled:13:18:48 Aug 29 2001 by bbalagot Image text-base 0x108000, data_base 0x44378c System restarted by Reload The system has been up for 1 minute, 25 seconds. System booted from "flash"

The output shows that your system has booted from Flash memory; therefore, the write to Flash memory has been successful, and the 2.x UPGRADE image is running on the Content Engine.

Executing the Upgrade

After you have installed the 2.x UPGRADE image and it is running on your device, you need to issue the Content Engine Tool Command Language (TCL) upgrade command and then perform a cold reboot. The upgrade command saves the Cache 2.x bootloader to Flash memory so that you can downgrade at a future time, if needed. The upgrade command also writes the Flash memory-only image to Flash memory.

Caution   Do not use the copy tftp flash and copy disk flash commands in the middle of the procedure for executing the 2.x UPGRADE image. This could cause corruption of the Flash image. This image is only for upgrade purposes and only the TCL upgrade command should be used.

During the reboot, the Flash memory-only image in Flash memory detects that there is no image on the system disk and asks for the FTP server information so it can download and install the full-release ACNS software image (ce5xx-ACNS-4.0.3-K9.bin) on the system disk.

To continue with the upgrade procedure, follow these steps:

Step 1   With the upgrade image installed, use the show running-config EXEC command to check the interface ethernet 0 field and the ip default-gateway field for the correct IP parameters.

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 command in interface configuration mode and the ip command in global configuration mode. 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#

Step 2   Access the TCL shell and enter upgrade to execute the TCL upgrade feature.

ContentEngine# tcl tcl% upgrade

Step 3   Enter the following information when prompted:

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.

CE-507# tcl % upgrade Please select from one of following actions: (1) Upgrade to ACNS 4.0 (2) Upgrade to Cache Software Release 3.x (3) Downgrade to Cache Software Release 2.x (4) quit Please input 1, 2, 3 or 4: 1 Please provide information for downloading new flash image. FTP Server IP Address (containing new flash image): 172.25.193.244 Remote Filename for new flash image: /nfs/ruby/centralbuild/target/ruby_latest/ce507-ACNS-4.0.3-K9.flash Remote username: johndoe Remote password: Please also provide information for downloading ACNS4.0 release software. FTP Server IP Address (for downloading ce507-ACNS-4.0.3-K9.bin): ce507-ACNS-4.0.3-K9.bin 172.25.193.244 Remote directory for ACNS4.0 release software: /nfs/ruby/centralbuild/target/ruby_latest/ ACNS4.0 release software file name: ce507-ACNS-4.0.3-K9.bin Remote username: johndoe Remote 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: using eth-port-0 Ip address = 10.10.0.231 Ip mask = 255.255.255.0 Ip gateway = 10.10.0.100 Host name = CE-507 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: 11272192 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: FlashUpgrade[3]: erasing: . - programming: FlashUpgrade[4]: erasing: . - programming: FlashUpgrade[5]: erasing: . - programming: . . . FlashUpgrade[79]:erasing:. - programming: FlashUpgrade[80]:erasing:. - programming: FlashUpgrade[81]:erasing:. - programming: FlashUpgrade[82]:erasing:. - programming: FlashUpgrade[83]:erasing:. - programming: FlashUpgrade[84]:erasing:. - programming: FlashUpgrade[85]:erasing:. - programming:

Flash memory is now updated with the ACNS 4.0 software Flash memory-only image.

Step 4   Perform a cold reboot using the following command:

tcl% reboot cold

The Content Engine reboots from Flash memory, running the ACNS 4.x software Flash memory-only system image. Bootup messages begin streaming on the console for approximately 10 minutes. After 10 minutes, look for the Username prompt.

If the upgrade was performed during a Telnet session, the session terminates after you issue the reboot cold command. You must wait 10 minutes and then reopen a Telnet session to the Content Engine. If the upgrade was successful, you should see the Username prompt.

Performing an Automated Upgrade for Multiple Devices

Cisco Content Engines running Cache 2.x software are often deployed in large numbers. Upgrading each of these Content Engines individually to ACNS 4.x software could be time-consuming.

The following upgrade process allows you to upgrade Content Engines in groups. The results of each upgrade are logged.

This upgrade process involves installing an upgrade/downgrade manager image on one Content Engine (CE1) and providing CE1 with a list of other Content Engines (CE2, CE3 CEn) to be converted. The upgrade manager is then responsible for communicating with each listed Content Engine and upgrading it.

Note   After performing a multiple device upgrade from Cache 2.x software to ACNS 4.0 software, use the write memory command on the Content Engines to avoid configuration loss.

Requirements

This upgrade process requires the following main components:

    1. Upgrade/downgrade manager images for your Content Engine model (ce507, ce560, or ce590)

The upgrade/downgrade manager images have all the necessary files required to upgrade an entire list of Content Engines.

    2. List of Content Engines to be upgraded

This list must include the following:

    3. Target upgrade images for your Content Engine model (ce507, ce560, or ce590)

Sample Content Engine List File

The following is a sample Content Engine list file. In this example, the CEIP field shows the IP address of the Content Engine as seen by the manager Content Engine from outside the network firewall; the CACHEIP field shows the IP address that is assigned to the Content Engine's Fast Ethernet 0 interface. If there were no firewall, these two fields could have the same IP address.

# Upgrade Manager Content Engine list file # This file lists of configuration information for the upgrade manager # to carry out a mass upgrade of several CEs. # # Copyright (c) 2001 Cisco Systems, Inc. All rights reserved. . . . # The following lines list the individual CEs and their config info # Format: # CE = <CEIP> <USERNAME> <PASSWORD> <CACHEIP> <NETMASK> <GATEWAY> CE = 172.25.192.148 admin default 10.1.1.21 255.255.255.0 10.1.1.1 CE = 172.25.192.149 admin default 10.1.1.22 255.255.255.0 10.1.1.1 CE = 172.25.192.150 admin default 10.1.1.23 255.255.255.0 10.1.1.1 CE = 172.25.192.151 admin default 10.1.1.24 255.255.255.0 10.1.1.1

Procedure

To perform an automated upgrade, follow these steps:

Step 1   Prepare a list of Content Engines to be upgraded. Use the list format shown in the "Sample Content Engine List File" section.

Step 2   Install the upgrade/downgrade manager images on one of the Content Engines, which then becomes the manager Content Engine. The following two images are required:

Step 3   Log in as admin.

Step 4   Configure the sysfs storage.

ContentEngine# disk config sysfs 1GB

Step 5   Reboot the Content Engine for the sysfs configuration to take effect. The sysfs storage space is automatically mounted in the local1 directory.

Step 6   Log in as admin and change directory to /local1.

ContentEngine# cd /local1

Step 7   Download the list of Content Engines to be upgraded to the manager Content Engine, as follows:

ContentEngine# copy ftp disk server_holding_ce_list remote_path remote_ce_list_filename local_ce_list_filename

Step 8   Download the Cache 2.x software upgrade image (ce5xx-2.x-UPGRADE-K9.bin), the ce5xx-ACNS-4.0.3-K9.flash image, and the ce5xx-ACNS-4.0.3-K9.bin image to the Content Engine local1 directory.

ContentEngine# copy ftp disk server_holding_images remote_path ce560-2.x-UPGRADE-K9.bin ce560-2.x-UPGRADE-K9.bin ContentEngine# copy ftp disk server_holding_images remote_path ce560-ACNS-4.0.3-K9.flash ce560-ACNS-4.0.3-K9.flash ContentEngine# copy ftp disk server_holding_images remote_path ce560-ACNS-4.0.3-K9.bin ce560-ACNS-4.0.3-K9.bin

Step 9   Invoke the upgrade/downgrade feature to perform the upgrade.

ContentEngine# upgrade local_ce_list_filename
Caution   Do not use the copy tftp flash and copy disk flash commands in the middle of the procedure for executing the 2.x UPGRADE image. This could cause corruption of the Flash image.

Step 10   Check the log files and verify that the software on the listed Content Engines was successfully upgraded.

To retrieve the log files, use the copy disk ftp command. In the following example, the copy disk ftp command retrieves the upgrade.log file for the Content Engine with the IP address 172.16.10.10.

ContentEngine# copy disk ftp 1.1.1.1 /remote_dir 172.16.10.10.upgrade.log 172.16.10.10.upgrade.log

where:

1.1.1.1 is the remote server where the file is going to be stored.

172.16.10.10.upgrade.log (the first one) is the filename that is stored on the remote machine.

172.16.10.10.upgrade.log (the second one) is the local copy to be sent.

Downgrading from ACNS 4.0 Software to Cache 2.x.x Software

If you want to restore your system to an earlier software release, you can do that by downgrading the software.

Caution   Do not downgrade an ACNS 4.0 software system to Cache 2.x.x software if the system originally had CDN Enterprise 2.1 software or E-CDN 3.0.2 software installed. Otherwise, the system may become nonoperational.
Note   This downgrade procedure is a manual procedure.

Downgrading from a ACNS 4.0 software image to a Cache 2.x.x software image involves the following tasks:

    1. Loading a Cache 2.x.x software Flash memory-only image into Flash memory

    2. Rebooting with the Flash memory-only image

    3. Reformatting the disk drives and reconfiguring network settings

    4. Installing a standard Cache 2.x.x software .pax file

Requirements

This downgrade procedure requires the following items:

Procedure

Before beginning your ACNS 4.0 software to Cache 2.x.x software downgrade, ensure that the Cache 2.3.1 software target Flash memory-only image and the full-release Cache 2.x.x software file reside on an FTP server that is accessible to the Content Engine being downgraded.

Step 1   Log in to the Content Engine command-line (CLI) through the console port.

Step 2   Install the Flash image by using the copy ftp install command as follows:

ContentEngine# copy ftp install ftp_server_ip directory_name ce5xx-ACNS-4.0.x-TO-CE-Cache-231.bin

You should receive a message stating that the new software is installed after you reload.

Step 3   Reboot the Content Engine by using the reload command.

After you enter the reload command, the Cache 2.x software flash image is written to Flash memory and the Content Engine reboots again, this time automatically.

Step 4   After the second reboot, the Content Engine network configuration is lost. Log in to the Content Engine as admin and reconfigure your network settings by using the interface command and the ip command in global configuration mode. For example:

Console(config)# interface FastEthernet 0/0 ip address A.B.C.D M.N.O.P Console(config)# ip default-gateway G.H.I.J

Step 5   Perform the following substeps to partition and format the disk drives of the Content Engine for Cache 2.x.x software. The disk drives are currently configured for ACNS 4.0 software. Cache 2.x.x software cannot read or write ACNS 4.0 software disk configurations.

    ContentEngine# show disks /c0t0d0 (scsi bus 0, unit 0, lun 0) /c0t1d0 (scsi bus 0, unit 1, lun 0)
    ContentEngine# disk manufacture disk_name

The Cache 2.x.x software disk manufacture command partitions and formats the drives named.

Step 6   Download the Cache 2.x software .pax file of your choice from the FTP server by using the copy ftp disk command. When prompted, enter the following information:

Step 7   Install the downloaded Cache 2.x.x software .pax file by issuing the install filename command. Supply the local filename that you entered in Step 6.

Step 8   Reboot the Content Engine by using the reload command. The Content Engine reboots with the selected Cache 2.x.x software running.

To use the Cache 2.x.x software, refer to the following publications:

Upgrading from Cache 3.x Software to ACNS 4.0 Software

This section describes how to upgrade your system from any Cache 3.x software release to ACNS 4.0 software.

Note   To upgrade Cache 3.1.x software to ACNS 4.0 software, you must be logged in as admin with privilege 15.

Requirements

To complete the upgrade procedure, you need to download the upgrade installation file from the server to your local hard disk drive. Before you can download the upgrade installation file, you need the following:

Procedure

To copy the upgrade installation file to your local hard disk drive, follow these steps:

Step 1   Connect to the Content Engine through the console port or open a Telnet session and log in as admin.

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 upgrade installation file from an FTP server to the Content Engine /local1 or /local2 directory.

In the following example, the image file ce507-CE-Cache-3.1.x-TO-ACNS-4.0.3-K9.addon is downloaded from the /images directory of FTP server 176.16.8.9.

ContentEngine# copy ftp disk 176.16.8.9 /images ce507-CE-Cache-3.1.x-TO-ACNS-4.0.3-K9.addon Enter username for remote ftp server: my_ftpserver_username Enter password for remote ftp server: my_ftpserver_password

Step 5   Verify that the file has been successfully downloaded by checking the directory list for the upgrade installation file, as shown in the following example:

ContentEngine# dir size time of last change name -------------- ------------------------- ----------- 4096 Sun Aug 12 08:49:26 2001 <DIR> core_dir 4096 Fri Aug 17 00:41:51 2001 <DIR> errorlog 4096 Fri Aug 17 20:22:49 2001 <DIR> logs 16384 Sun Aug 12 08:49:12 2001 <DIR> lost+found 4096 Thu Aug 16 00:12:15 2001 <DIR> service_logs 93429580 Fri Aug 17 20:45:54 2001 ce507-CE-Cache-3.1.x-TO-ACNS-4.0.3-K9.addon

To verify that the file was downloaded successfully, confirm that the file size of the upgrade installation file in the directory list is the same size as the upgrade installation file on the server.

Step 6   Install ACNS 4.0 software with the install EXEC command.

    ContentEngine# cd /
    ContentEngine# install /local1/ce507-CE-Cache-3.1.x-TO-ACNS-4.0.3-K9.addon

The install command copies a new system image to Flash memory and then reboots the system. Your system should reboot with ACNS 4.0 software running.

Note   Because of a bug in Cache 3.x software, the upgrade process might be interrupted, and you might see an error message similar to the following:
Cannot create directory /sw/installdir/upg_diamond_to_ruby/_tmp. Install addon "Cisco Cache 3.x to ACNS 4.0 Upgrade Bundle" failed (256)

To fix this problem, install the deltmppatch.addon patch file as you would install any other .addon file:

ContentEngine# copy ftp disk 1.2.3.4 /foldername/ deltmppatch.addon deltmppatch.addon ContentEngine# install deltmppatch.addon

Installing the patch file cleans up the directory and the upgrade can be retried.

Downgrading from ACNS 4.0 Software to Cache 3.1 Software

If you want to restore your system to an earlier software release, you can do so by downgrading the software.

Requirements

To downgrade your system from ACNS 4.0 software to Cache 3.1 software, you need to download the downgrade installation file from an FTP server to your local hard disk drive and install Cache 3.1 software.

Before you can download the file, you need the following:

Procedure

To complete the software downgrade, follow these steps:

Step 1   Configure a static address on the device. For example:

ce#config ce(config)#interface FastEthernet 0/0 ce(config-if)#ip address 10.1.202.151 255.255.255.0 ce(config-if)#exit ce(config)#ip default-gateway 10.1.202.1 ce(config)#exit ce#write mem

Step 2   Download the downgrade installation file, as follows:

ContentEngine# copy ftp install ip-addr_of_server dir-name ce7320-ACNS-4.0.x-TO-CE-Cache-311.bin

Step 3   Enter the reload command:

ContentEngine# reload

The system reboots and then automatically installs Cache 3.1 software. It then automatically reboots a second time and comes up with the Cache 3.1 software running.

Step 4   After Cache 3.1 software reboots, download realmedia.addon to the /local1 directory on the Content Engine and install it using the following command:

disk partition disk00/02 400M sysfs (400M is user selectable) sysfs format disk00/02 sysfs mount disk00/02 local1 cd /local1 copy ftp disk (download realmedia.addon file) install realmedia.addon

To use the Cache 3.1 software, refer to the following publications:

Upgrading from CDN Enterprise 2.x Software or E-CDN 3.0.x Software to ACNS 4.0 Software

To upgrade your system from any CDN Enterprise 2.x software release or E-CDN 3.0.x software release to ACNS 4.0 software, you need the following:

Freeing Required Disk Space for the Upgrade

Before you begin the upgrade procedure, make sure that you have enough free hard disk space available.

ACNS software sysfs functions use approximately 4 GB of disk space, and by default, the upgrade procedure allocates 1 GB of disk space for cfs functions and 1 GB of disk space for mediafs functions for each hard disk drive installed (Content Engines only). Therefore, depending on the hardware platform and the number of hard disk drives installed in the chassis, a certain amount of free disk space is required for the upgrade procedure.

Note   To change the Content Engine default disk space allocations for cfs and mediafs functions, open the upgrade package text files in any text editor and modify the CFS-SIZE and MEDIAFS-SIZE fields in the .meta file. The values for these fields are assumed to be in gigabytes. The default value for each is 1 GB. The CFS-SIZE field can have a value of 0, 1, or 2; however, because of a software limitation, CFS-SIZE cannot exceed 2 GB. For example, if you enter the following modification, CFS-SIZE 2 MEDIAFS-SIZE 2, you allocate 2 GB of disk space for cfs functions and 2 GB of disk space for mediafs functions.

Table 4-1 lists the amount of free disk space required for a successful software upgrade.


Table 4-1: Free Disk Space Required for Software Upgrade
Hardware Platform CDN Enterprise 2.x Software and E-CDN 3.0.x Software

Content Distribution Manager or Content Router

5 GB

Content Engine
(1 hard disk drive)

7 GB

Content Engine
(2 hard disk drives)

10 GB

Content Engine
(n hard disk drives)

7 + ((n - 1) * 3) GB

If the Content Distribution Manager or Content Engine does not have enough free disk space, the upgrade operation aborts. No content is lost; however, you need to unsubscribe channels or manually remove content to free disk space to successfully complete the software upgrade operation. The following sections describe how to free some disk space on a Content Engine and on a Content Distribution Manager.

Removing a Content Engine from a Subscribed Devices List

In a Content Distribution Network, the content resides on the Content Distribution Manager (CDM) and is assigned to one or more channels. Content Engines are subscribed to CDM channels so that subscribers can access the content on that channel. When you unsubscribe a Content Engine from a channel, the disk space that was used by the content in that channel is cleared. To unsubscribe a Content Engine from a channel, you use the Content Distribution Manager GUI to remove the device from the list of subscribed devices.

To remove a Content Engine from the subscribed devices list, follow these steps.

Note   The maximum size of all subscribed channels should be the total hard disk size minus the required free space size.

Step 1   From the Channels menu, choose Subscriber.

The Subscriber dialog box appears.

Step 2   Make sure that the correct channel is displayed in the Channel Selector field. If it is not, choose the correct channel from the drop-down list.

Step 3   Under the heading Subscribed Devices, check the check box next to each Content Engine that you want to remove, or click All to choose all Content Engines on the list; click None to clear your selections.

Step 4   Click Unsubscribe.

The Content Engine is removed from the list of Content Engines subscribed to the selected channel and moved back to the Unsubscribed Devices list.

For more information, refer to the "Removing a Content Engine from a Subscribed Devices List" section in Chapter 3 of the Cisco Enterprise CDN Software User Guide, Version 3.0.

When you have cleared the required amount of disk space, you are ready to upgrade your system software.

Removing Content from a Content Distribution Manager

Another way to clear disk space for the software upgrade procedure is to physically remove the content from the Content Distribution Manager on which the content resides.

To remove content from a Content Distribution Manager, follow these steps:

Step 1   From the Channels menu, choose Media Editor.

The Media Editor dialog box appears.

Step 2   Make sure that the correct channel is displayed in the appropriate drop-down list box. If it is not, choose the correct channel from the list.

Step 3   Check the check box next to each file that you want to remove. Click All to select all of the files or None to clear your selections.

Step 4   Click Remove. You are prompted to confirm that you want to remove the selected files.

For more information, refer to the "Removing Media from a Channel" section in Chapter 3 of the Cisco Enterprise CDN Software User Guide, Version 3.0.

When you have cleared the required amount of free disk space, you are ready to install the upgrade monitoring package and then upgrade your system software.

Monitoring the Upgrade Status

Before you upgrade your Content Distribution Manager (CDM) that is running CDN Enterprise 2.1 software or E-CDN 3.0.2 software, you need to install an upgrade monitoring package in order to monitor the upgrade status of the devices being upgraded. If your CDM is already running ACNS software, you can ignore this section.

The upgrade monitoring package contains a cgi script that is designed to monitor the status of the devices being upgraded. The upgrade software allows some of the upgrades to fail if the device does not have enough disk space. The cgi script helps you identify which devices have failed during the upgrade procedure.

Requirements

Choose the upgrade monitoring package, which contains the following two files:

Procedure

To install and use the upgrade monitoring feature, follow these steps:

Step 1   From the Media Importer page, import the two cgi script files to the MANUAL_UPGRADE channel.

Step 2   From the Software Update page, initiate the update.

Step 3   To monitor the upgrade status, launch a separate browser and enter the following URL to view the Software Update Status Report:

http://your-content-distribution-manager-ip-address/cgi-bin/update-status

Note   If you are looking at the log file in the CDM device, disregard the error messages that refer to this upgrade monitoring package.

One install script is automatically returned after you install the cgi script so that the CDM does not need to reboot. The returned script causes the system to log an error message. For example:

2001-09-18 18:00:03 I remotereq#2481 Dispatching remoteRequest:opcode \QSOFTWARE-UPDATE' 2001-09-18 18:00:03 I remotereq#2481 Initiating software update to version \QV1-2-3-rc4' 2001-09-18 18:00:03 I remotereq#2481 Executing update:/sonoma/state1/cache/cgi-update-status.upg.1412100077500012.00055e8a6a92.sn.data 2001-09-18 18:00:03 W remotereq#2481 Aborting software update (STATUS_Error "Software upgrade failed, exit 2816")

Ignore these error messages. To verify that the cgi script has been installed, point your browser to the update-status URL:

http://cdm-ip/cgi-bin/update-status

If you are able to view the URL and the status messages, then the upgrade monitoring package has been installed successfully.

Performing an Automated Upgrade for Multiple Devices

This upgrade procedure allows you to upgrade software on all your networked devices.

To upgrade your system from E-CDN 3.0.x software to ACNS 4.0 software, you need to perform the following tasks:

    1. Create a manual upgrade channel ("MANUAL_UPGRADE") to distribute the upgrade package files, if you have not already done so.

    2. Subscribe any E-CDN devices (Content Engines and Content Routers) requiring a software upgrade to the "MANUAL_UPGRADE" channel.

    3. Import software upgrade files to the "MANUAL_UPGRADE" channel on your Content Distribution Manager.

    4. Distribute software upgrade files to all devices marked for upgrade.

    5. Upgrade your Content Engines and Content Routers.

    6. Upgrade your Content Distribution Manager.

Requirements

Choose the upgrade package, which contains the following two files:

Procedure

To upgrade your system software, follow these steps:

Step 1   Use an Internet browser that is connected to your Content Distribution Manager (CDM) to administer the software upgrade. On the CDM Administration page, do the following:

Step 2   Go to the Bandwidth page to make sure that the replication bandwidth has been set correctly for each device that you are going to upgrade. Make the settings as high as your available bandwidth allows.

Step 3   Go to the Subscriber page to subscribe your devices to the MANUAL_UPGRADE channel.

Step 4   Go to the Media Importer page, to import the upgrade package files.

Step 5   Go to the Software Update page to execute the upgrade for Content Engines and Content Routers. (The Content Distribution Manager is upgraded in another step later on.)

Step 6   Verify that the upgrade was successful by checking the Version field on the Software Update page. If the upgrade was successful, the Version field for the chosen device is updated with the new software version.

Step 7   After the upgrade is complete for all your devices, you need to upgrade your Content Distribution Manager.

Enabling the WMT Server

The Windows Media Technologies (WMT) server used by the E-CDN application in ACNS 4.0 software is under license key control. When you upgrade from a CDN Enterprise 2.x software release or an E-CDN 3.0.x software release to ACNS 4.0 software, you must set the new license key, accept the license agreement, and then enable WMT before the WMT server can serve WMT requests. These commands must be entered through the ACNS CLI.

Note   You must enable WMT using the CLI. Previously, before this WMT license key management function was implemented in ACNS 4.0 software, E-CDN software automatically started and stopped the WMT server. In ACNS software, the WMT server operation is decoupled from the E-CDN application.

To enable the WMT server, enter all three of the following commands in global configuration mode:

The wmt license-key command sets the WMT license key. Although the no form of the command is available from the CLI, it simply prints an error message that the license key cannot be removed. There is no default value for the license key.

ContentEngine(config)# [no] wmt license-key key

The wmt accept-license-agreement command allows you to accept the WMT end user license agreement (EULA). Although the no form of the command is available from the CLI, it simply prints an error message that the EULA acceptance cannot be revoked. The default value is that the EULA is not accepted.

ContentEngine(config)# [no] wmt accept-license-agreement

The wmt enable command enables the WMT server. The no form of the command disables the WMT server. The default value is that WMT is disabled.

ContentEngine(config)# [no] wmt enable

If you do not enable WMT using these three commands, any request for a WMT file using the Microsoft Media Services (MMS) protocol is served using the HTTP protocol, and you cannot use the control features of the WMT player that are available only through MMS.

The following show commands display WMT status and licensing:

Downgrading from ACNS 4.0 Software to CDN Enterprise 2.1 Software or E-CDN 3.0.2 Software

If you want to restore your system to an earlier CDN software release, you can do that by downgrading the software.

Note   You can downgrade from ACNS software to CDN Enterprise software on all models except for the Content Engine 7320, which is not supported by CDN Enterprise software, and the Content Distribution Manager 4650 using the Redundant Array of Inexpensive Disks (RAID) controller V3.

In some cases, not all content is preserved. The downgrade process automatically detects potential content loss and issues a warning. In this case, you must agree to these terms before proceeding.
Note   The downgrade process from ACNS software to CDN Enterprise software fails if the device is connected to a console server, but there is no telnet session to the device. Do not perform the downgrade with a console cable connected to the device if a telnet session is not active.

To downgrade your system from ACNS 4.0 software to CDN Enterprise 2.1 software or E-CDN 3.0.2 software, you need to perform the following tasks:

    1. Create a "MANUAL_UPGRADE" channel.

    2. Subscribe any E-CDN devices requiring a software downgrade to the MANUAL_UPGRADE channel.

    3. Import software downgrade files to the MANUAL_UPGRADE channel on your Content Distribution Manager.

    4. Distribute the software downgrade files to all devices marked for downgrade.

    5. Execute the downgrade.

Requirements

If you are downgrading from ACNS 4.0 software to CDN Enterprise 2.1 software, import the following package files:

If you are downgrading from ACNS 4.0 software to E-CDN 3.0.2 software, import the following package files:

Procedure

Caution   You can downgrade from ACNS software to CDN Enterprise software after having made changes to disk allocation using the disk configure command; however, some content might not be preserved.

If you downgrade from ACNS software to CDN Enterprise software on a model that never previously had CDN Enterprise software on it, the content is not preserved.

To downgrade your system from ACNS 4.0 software to CDN Enterprise 2.1 software or E-CDN 3.0.2 software, follow these steps:

Step 1   Use an Internet browser that is connected to your Content Distribution Manager (CDM) to administer the software downgrade. On the CDM Administration page, do the following:

Step 2   Go to the Bandwidth page to make sure that the replication bandwidth has been set correctly for each device. Make the settings as high as your available bandwidth allows.

Step 3   Go to the Subscriber page to subscribe your devices to the MANUAL_UPGRADE channel.

Step 4   Go to the Media Importer page to import the downgrade package files.

Step 5   Go to the Software Update page to execute the downgrade.

Step 6   Verify that the downgrade was successful by checking the version field on the Software Update page. If the downgrade was successful, the version field for the chosen device is updated with the new software version.

Step 7   If some of the devices still show ACNS 4.0.3 for the version information, go to the System Log page to display the system messages, otherwise proceed to step 10.

If the device is in danger of losing content, the downgrade process fails and an error in the system log is generated.

Step 8   If you want to force the downgrade and lose content, choose one of the following methods:

    http:// device-ip-address/cgi-bin/force-downgrade

Step 9   Go to the Software Update page to execute the downgrade.

Step 10   After the downgrade is complete for all of your devices, then downgrade your Content Distribution Manager.

To downgrade your device from ACNS 4.0 software to CDN Enterprise 2.1 software or E-CDN 3.0.2 software using the CLI, follow these steps:

Step 1   Use the copy ftp install command, with the applicable file:

Step 2   To force a downgrade, use the ecdn force-downgrade command and then run the copy ftp install command again.

To use the CDN Enterprise 2.x software, refer to the following publications:

To use the E-CDN 3.0.x software, refer to the following publications:


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Nov 14 13:46:16 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.