Cisco ACNS Software Upgrade and Maintenance Guide, Release 5.x
Chapter 3: Upgrading Software for the Standalone Content Engine
Downloads: This chapterpdf (PDF - 186.0KB) The complete bookPDF (PDF - 2.88MB) | Feedback

Upgrading Software for Standalone Content Engines

Table Of Contents

Upgrading Software for Standalone Content Engines

Required Upgrade Items

Installing the Software File Using the CLI

Downgrading from ACNS 5.x Software to ACNS 4.2.9 Software Using the CLI


Upgrading Software for Standalone Content Engines


This chapter explains how to upgrade ACNS software on standalone Content Engines. This chapter contains the following sections:

Required Upgrade Items

Installing the Software File Using the CLI

Downgrading from ACNS 5.x Software to ACNS 4.2.9 Software Using the CLI

The term "standalone Content Engine" is used throughout the ACNS 5.x software documentation to refer to Content Engines that ACNS administrators have intentionally not registered with a Content Distribution Manager (if there is one in the network) so that they can configure, manage, and monitor these Content Engines as standalone devices. The term "locally managed deployments" refers to deployments that consist of one or more standalone Content Engines that are functioning as caching and streaming engines. Multiple standalone Content Engines can be deployed (for example, you can deploy clusters of standalone Content Engines).


Note Before installing new software, always review the release interoperability issues and requirements in "Introduction to Upgrading Your ACNS Software."



Note This chapter does not explain the procedure for upgrading or downgrading between the ACNS 4.x release and the ACNS 5.x release. See the discussion of software migration in "Migrating from ACNS 4.x Software to ACNS 5.x Software," and the upgrade procedure in the "Upgrading a Standalone ACNS 4.2 Content Engine or Content Router" section for more information on this subject.


Required Upgrade Items

To upgrade the software on a Content Engine that is not operating as part of a centrally managed ACNS network, you need the following items:

FTP or HTTP server with the software files

Network connectivity between the device to be upgraded and the server hosting the upgrade files

Appropriate .bin software file (ACNS release image), such as the following:

ACNS-5.2.1.7-K9.bin

ACNS-5.1.11.6-K9.bin

ACNS-5.0.17.6-K9.bin

Installing the Software File Using the CLI

To install the software file, follow these steps:


Step 1 Obtain the desired software file from Cisco.com.

See the "Obtaining a Software File from Cisco.com" section for information.

Step 2 Install the software file by using the copy ftp install or copy http install EXEC command:

ContentEngine# copy ftp install ftp-server remote_file_dir ACNS-X.x.x-K9.bin

ContentEngine# copy http install http-server remote_file_dir ACNS-X.x.x-K9.bin 
[portnumber]

Step 3 Alternatively, if you want to keep a local copy of the software file on your Content Engine, you can use the copy ftp disk EXEC command, and then use the install EXEC command.

ContentEngine# copy ftp disk ACNS-X.x.x-K9.bin
ContentEngine# install ACNS-X.x.x-K9.bin

When the install command is executed, the software file is expanded. The expanded files overwrite the existing files in the Content Engine. The newly installed version takes effect after the system software is reloaded.


Note The install command does not accept .pax files. Files should be of the type .bin (for example, ACNS-5.x.x-K9.bin).


Step 4 After the software file is copied to your system, use the reload EXEC command to reboot.

ContentEngine# reload

The installation process continues automatically after the reboot. No further action is required.


Downgrading from ACNS 5.x Software to ACNS 4.2.9 Software Using the CLI

The CLI allows you to downgrade individual devices one at one time. To use the CLI to perform a downgrade to ACNS 4.x software from a device that is running ACNS 5.x software, you need the following:

FTP or HTTP server with the downgrade software files

Network connectivity between the device to be downgraded and the server hosting the appropriate files

Appropriate .bin downgrade file: ACNS-5.x.x.x-TO-4.2.x-K9.bin

Meta file containing the ACNS 4.x Content Distribution Manager IP address: acns4_cdm_ip.meta


Note We recommend that you use the Content Distribution Manager GUI to downgrade your managed Content Engines and other devices, and then use the CLI to downgrade the Content Distribution Manager.



Note If you are downgrading a Content Distribution Manager, omit Step 2 through Step 4.


To downgrade the software using the CLI, follow these steps:


Step 1 Obtain the correct software file from Cisco.com.

See the "Obtaining a Software File from Cisco.com" section for information.

Step 2 Obtain the correct meta file (acns4_cdm_ip.meta) from Cisco.com.

See the "Obtaining a Meta File from Cisco.com" section for information.

The meta file contains the information necessary for the Content Engine to be automatically registered with the ACNS 4.2 Content Distribution Manager after the downgrade is completed.

Step 3 Edit the meta file using any text editor.

See the "Editing the Meta File" section for information.

Step 4 Save the meta file to the /local1 directory on the Content Engine using the copy ftp disk EXEC command:

copy ftp disk {hostname | ip-address} remotefiledir remotefilename localfilename 

The copy ftp disk command copies a file from an FTP server to the sysfs storage space on the Content Engine.

Step 5 Copy the software file to the Content Engine by using the copy ftp install or copy http install EXEC command:

ContentEngine# copy {ftp | http} install server-containing-dng-image 
directory-to-dng-image dng-image-name

For example:

ContentEngine# copy ftp install my-ftp-server /my-ftp-directory 
ACNS-5.x.x.x-TO-4.2.x-K9.bin

Step 6 After the software file is copied to your system, reboot using the reload EXEC command.

ContentEngine# reload

The installation process continues automatically after the reboot. No further action is required.