Table Of Contents
Upgrading and Downgrading the Software
Upgrade, Downgrade, and Interoperability Considerations
Upgrade Options
Downgrade Options
Interoperability Requirements
Feature Interoperability with Regard to ACNS 5.1 Software
Feature Interoperability with Regard to ACNS 5.2 Software
Obtaining a Software File from Cisco.com
Obtaining a Meta File from Cisco.com
Editing the Meta File
Pre-Positioning a Software File
Sample Manifest File to Pre-Position a Software File
Updating Software from the ACNS 5.2 Software Release
Determining the Current Software Version in the ACNS 5.2 Content Distribution Manager GUI
Registering a Software File URL in the ACNS 5.2 Content Distribution Manager GUI
Using a Meta File as a Template for the Software File Settings Form
Updating the Software Using the ACNS 5.2 Content Distribution Manager GUI
Multiple Device Updates for Content Engines Using Device Groups
Single Device Updates Between ACNS 5.2 Releases
Deleting a Software File from the ACNS 5.2 Content Distribution Manager GUI
Updating from ACNS 5.1.x Software to ACNS 5.x Software
Determining the Current Software Version in the ACNS 5.1 Content Distribution Manager GUI
Registering a Meta File URL in the ACNS 5.1 Content Distribution Manager GUI
Upgrading or Downgrading Using the ACNS 5.1 Content Distribution Manager GUI
Deleting an Update File from the ACNS 5.1 Content Distribution Manager GUI
Upgrading or Downgrading Between ACNS 5.x Releases Using the CLI
Upgrading and Downgrading an ACNS 5.1 Standby Content Distribution Manager Using the CLI
Migrating from ACNS 4.2 Software to ACNS 5.x Software
Upgrading a Standalone ACNS 4.2 Content Engine or Content Router
Upgrading from ACNS 4.x Software to ACNS 4.2 Software
Upgrading from ACNS 4.x Software to ACNS 4.2 Software Using the Content Distribution Manager GUI
Upgrading from ACNS 4.x Software to ACNS 4.2 Software Using the CLI
Downgrading from ACNS 5.x Software to ACNS 4.2.x Software
Downgrading from ACNS 5.1 Software to ACNS 4.2.9 Software Using the Content Distribution Manager GUI
Downgrading from ACNS 5.2 Software to ACNS 4.2.9 Software Using the Content Distribution Manager GUI
Downgrading from ACNS 5.x Software to ACNS 4.2.9 Software Using the CLI
Upgrading and Downgrading the Software
This chapter explains how to upgrade or downgrade your software and contains the following sections:
•
Upgrade, Downgrade, and Interoperability Considerations
•Obtaining a Software File from Cisco.com
•Obtaining a Meta File from Cisco.com
•Pre-Positioning a Software File
•Updating Software from the ACNS 5.2 Software Release
•Updating from ACNS 5.1.x Software to ACNS 5.x Software
•Migrating from ACNS 4.2 Software to ACNS 5.x Software
•Upgrading a Standalone ACNS 4.2 Content Engine or Content Router
•Upgrading from ACNS 4.x Software to ACNS 4.2 Software
•Downgrading from ACNS 5.x Software to ACNS 4.2.x Software
Upgrade, Downgrade, and Interoperability Considerations
In general, an ACNS network will be upgraded in a rolling fashion, so that your network might consist of nodes with different software versions for some time. You can expect the following behavior during an upgrade or downgrade of your network:
•The ACNS network continues to operate with mixed versions up to one major or minor version difference in a deployed solution.
•New features that depend on device cooperation might not be fully functional until the ACNS network upgrade is complete, but no existing features will be affected.
•While being upgraded, a node will be unavailable for a short time.
•All nodes, other than the node being upgraded, continue to operate at full capacity. The availability of other nodes is not affected during an upgrade.
•Content is preserved during an upgrade or downgrade unless channels are removed or the disk and acquisition-distribution database cleanup EXEC commands are used.
•All logs are preserved during an upgrade or downgrade, unless the disk configuration has changed. Any time disk space is reconfigured, the logs are automatically removed.
Note The CE-511 and CE-566 Content Engines only support ACNS 5.2 software; they do not support ACNS 5.1 or earlier releases of ACNS software.
We strongly recommend that you update your devices in the following order:
1. Multicast sender Content Engines
2. Multicast receiver Content Engines
3. Non-root Content Engines
4. Root Content Engines
5. Content Routers
6. Standby Content Distribution Managers
7. Primary Content Distribution Manager
Upgrade Options
The following ACNS software release upgrades can be performed:
•Any ACNS 4.2.x release (except ACNS 4.2.1) to any ACNS 5.x.x release
•Any ACNS 5.x.x release to any ACNS 5.x.x release
When you upgrade a Content Engine from any ACNS release to ACNS 5.1.9 or a later release of ACNS 5.1 software or 5.2.1 or a later release of ACNS 5.2 software, all cached RealMedia content is deleted from the Content Engine mediafs cache. This happens because the meta file formats have been changed in these releases, affecting the way that the cached RealMedia streaming file is interpreted.
Downgrade Options
The following ACNS software release downgrades can be performed:
•ACNS 5.x.x release to ACNS 4.2.x release
–After the downgrade, ACNS 5.x.x features will not work.
–Any content acquired by the ACNS 5.x.x Content Engine will be lost after the downgrade.
•ACNS 5.1 release to ACNS 5.0.3 release
–After the downgrade, ACNS 5.1-specific features will not work (for example, NTLM authentication).
–MMS content acquired by the ACNS 5.1 Content Engine remains and can be served by the Content Engine after the downgrade; however, the ACNS 5.0.3 Content Engine cannot reacquire MMS content.
–The mediafs disk space will need to be reconfigured after the downgrade.
•ACNS 5.1 release to ACNS 5.0.1 release (not recommended)
–This downgrade requires that the management database tables be manually re-created using the CLI.
–The mediafs disk space will need to be reconfigured after the downgrade.
•ACNS 5.2 release to any ACNS 5.1 or ACNS 5.0 release
•Any ACNS 5.x.x release to any ACNS 5.x.x release
Interoperability Requirements
Note Devices in an ACNS network cannot differ by more than one major or minor software version.
ACNS software releases interoperate with each other in a mixed deployment, as follows:
•Any ACNS 5.0.x Content Engine with any other ACNS 5.0.x Content Engine
•Any ACNS 5.0.x Content Engine with any other ACNS 5.1 Content Engine
•Any ACNS 5.1 Content Engine with any other ACNS 5.1 Content Engine
•Any ACNS 5.1 Content Engine with any other ACNS 5.2 Content Engine
•Any ACNS 5.2 Content Engine with any other ACNS 5.2 Content Engine
Note ACNS 4.x software releases do not interoperate with ACNS 5.x software releases.
Feature Interoperability with Regard to ACNS 5.1 Software
Content Engines running ACNS 5.0.1, 5.0.3, and 5.1 software acting in various roles such as root Content Engine, forwarder, receiver, and multicast sender may interoperate with each other in any combination of basic functionalities that are common to all releases. If a chain of forwarders passes content from a Content Engine running ACNS 5.1 software to a Content Engine running ACNS 5.0 software, and then to another Content Engine running ACNS 5.1 software, the ACNS 5.1 software features are preserved across the chain to the third Content Engine.
For example, if a higher-version forwarder is sending content to a lower-version receiver, the extra database columns are converted to a name-value pair in the metadata field and are transmitted. The lower-version receiver ignores the metadata, but still writes it to the database and passes it on to receivers farther down the chain. Hence if a receiver further down the chain is running the higher-version software, it picks up the metadata and the functionality along with it.
However, features available to a newer release do not work with other Content Engines that are running older releases. For example, a multicast backup sender (an ACNS Release 5.1 feature) does not work with multicast receivers running ACNS 5.0 software.
The multicast backup sender functions only when the receivers detect that the primary sender is down and send NACKs to trigger a retransmission of the multicast file to the backup sender. Hence, if a network has no ACNS 5.1 multicast receivers, even if it does have a multicast backup sender, the backup sender cannot become active.
Similarly, the intelligent carousel feature relies on the multicast receiver to send file requests to the multicast sender. Only receivers running ACNS 5.1 software are capable of making such requests. In a mixed network, a receiver Content Engine running ACNS 5.0 software can, however, receive the file transmission that was requested by the receiver running ACNS 5.1 software.
Feature Interoperability with Regard to ACNS 5.2 Software
Multicast File Transfer Features
ACNS 5.2 software supports new multicast file transfer features that enhance the reliability and performance of multicast file distribution in the ACNS 5.2 network. These enhancements impact the interoperability of Content Engines in a mixed network.
In earlier ACNS releases (Release 5.0 and Release 5.1), the file transfer session depended on a window of time to resend the missing packets. The sender had to transmit the packets within this window of time for each retransmission request (NACK) from receiver Content Engines. If a multicast receiver joined the session too late and missed blocks of data that were outside the transmission window, the sender would not resend the missing blocks. The receiver could not receive the entire file, and the transmission failed. The receiver had to wait until a subsequent carousel pass to recover the missed files. The receiver could only receive the entire file or nothing. A slow receiver often failed to receive a large file if the receiving rate lagged behind the sending rate.
The multicast file transfer enhancements in ACNS 5.2 software resolve these issues by eliminating the window of time for file transmissions. This feature is called checkpoint. Checkpoint allows the sender to divide the transferring file into blocks and to retransmit any and all blocks until the transfer session ends. At any time during the transfer session, a receiver can request retransmission of any block that it has missed. Also, receiver Content Engines can receive the blocks of a transfer in any order. Data transmission can occur over a longer period, and receivers can recover missed data blocks to successfully complete the transfer in most situations. Thus, file transfers are much more resistant to loss of data.
This feature also solves the problem of a multicast receiver joining a transfer session late. (In an extreme example, even if a receiver joins so late that the sender has multicast nearly all of a very large file, the receiver can still receive the data. Also, the receiver can request retransmission for all the blocks it has missed.) Even if a receiver goes offline and restarts during a transfer, it can recover missing data without requesting retransmission of the blocks it has already received.
Because of these enhancements, receivers using ACNS 5.2 software cannot interact with senders using ACNS 5.0 or 5.1 software. The ACNS 5.2 multicast receiver will ignore files sent from an ACNS 5.0 or 5.1 multicast sender. However, an ACNS 5.2 multicast sender can interoperate with ACNS 5.0 or 5.1 multicast receivers because the software detects the lower software version and disables the checkpoint feature. Therefore, we recommend that you upgrade your multicast sender to ACNS 5.2 software first and then upgrade your receivers to ACNS 5.2 software.
SMB File Acquisition
When a root Content Engine is downgraded from ACNS 5.2 software to ACNS 5.1 software, some channels are disabled and some content fails to be acquired. This problem occurs when the manifest file URL is an SMB URL with a UNC path format (for example, \\host\share\file), or when an item or crawl task specified in either the src or start-url attribute has a UNC path format.
Because ACNS 5.1 software does not support SMB file acquisition, the root Content Engine running ACNS 5.1 software is not able to fetch the manifest file or acquire content from the SMB shares. To work around this problem, do the following either before or after you downgrade the root Content Engine from ACNS 5.2 to ACNS 5.1 software:
•Remove the SMB URL from the Manifest URL field in the Channel configuration window of Content Distribution Manager GUI and use a URL with supported protocols (HTTP, FTP, OR HTTPS).
Note From an ACNS 5.1 Content Distribution Manager GUI, choose Channels > Channels > Edit Channel.
From an ACNS 5.2 Content Distribution Manager GUI, choose Content > Channels > Edit Channel > Channel Content.
•Edit the manifest file by removing content items and crawl tasks that have UNC formatted paths.
•Use the acquirer start-channel EXEC command to initiate channel acquisition and verify that the workaround is successful.
Obtaining a Software File from Cisco.com
To obtain a software file from Cisco.com, follow these steps:
Step 1 Launch your preferred web browser and point it to:
http://www.cisco.com/public/sw-center/sw-content.shtml
Step 2 When prompted, log in to Cisco.com using your designated username and password. The Content Networking window appears, listing the available software products.
Step 3 Choose a link to the content networking software product that you want. The Software Download window appears.
Step 4 Click the Download ACNS Software images (contains strong encryption) link. The Content Networking window for Cisco ACNS Cryptographic Software appears.
Step 5 Click the link to the ACNS cryptographic software release that you want. The window refreshes, listing all the software files (and meta files) available for that release.
Step 6 Locate the software file that you wish to download by consulting the Release column for the proper release version of the software. The software files will have names similar to the following:
ACNS-5.x.x-K9.bin
Step 7 To download a software file, click the link for the software file that you want. The Enter Network Password dialog box pops up. Enter your username and password and click OK.
•If this is the first time you have downloaded a software file from Cisco.com, the Encryption Software Export Distribution Authorization form appears.
–Fill out the form and click Submit. The Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy appears.
–Read the policy and click I Accept. The Encryption Software Export/Distribution Form appears.
•If you previously filled out the Encryption Software Export Distribution Authorization form and read and accepted the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy, these forms are not presented again. Instead, the Encryption Software Export/Distribution Form appears after you click OK in the Enter Network Password dialog box.
Step 8 Read the Encryption Software Export/Distribution Form, click the Yes or No radio button, and click Submit. A security alert dialog box pops up.
Step 9 Click Yes in the Security Alert dialog box. The Software Download window reappears.
Step 10 Right-click the software file link to download the software and use the Save Link As or the Save Link Target As option to save the file to your FTP or HTTP server.
Obtaining a Meta File from Cisco.com
A meta file is a text file that contains information about the location of the software file and other descriptive information about the software file. In software releases prior to ACNS 5.2 software, a meta file is required for updating software using the Content Distribution Manager GUI.
Note If you are updating software using the Content Distribution Manager GUI running ACNS 5.2 software, the meta file is optional.
To obtain a meta file from Cisco.com, follow these steps:
Step 1 Launch your preferred web browser and point it to:
http://www.cisco.com/public/sw-center/sw-content.shtml
Step 2 When prompted, log in to Cisco.com using your designated username and password. The Content Networking window appears, listing the available software products.
Step 3 Choose a link to the Content Networking Software product for which you want to obtain a meta file. The Software Download window appears.
Step 4 Click the Download ACNS Software images (contains strong encryption) link. The Content Networking window for Cisco ACNS Cryptographic Software appears.
Step 5 Click the link to the ACNS cryptographic software release for which you want to obtain a meta file. The window refreshes, listing all the meta files (and software files) available for that release.
Step 6 Locate the meta file that you wish to download by consulting the Release column for the proper release version of the software. The meta files will have names similar to the following:
ACNS-5.x.x-K9.meta
Step 7 To download a meta file, click the link for the meta file that you want. The Enter Network Password dialog box pops up. Enter your username and password and click OK.
•If this is the first time you have downloaded a meta file or software file from Cisco.com, the Encryption Software Export Distribution Authorization form appears.
–Fill out the form and click Submit. The Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy appears.
–Read the policy and click I Accept. The Encryption Software Export/Distribution Form appears.
•If you previously filled out the Encryption Software Export Distribution Authorization form and read and accepted the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy, these forms are not presented again. Instead, the Encryption Software Export/Distribution Form appears after you click OK in the Enter Network Password dialog box.
Step 8 Read the Encryption Software Export/Distribution Form, click the Yes or No radio button, and click Submit. A security alert dialog box pops up.
Step 9 Click Yes in the Security Alert dialog box. The Software Download window reappears.
Step 10 Right-click the software file link to download the software and use the Save Link As or the Save Link Target As option to save the file to your FTP or HTTP server.
Editing the Meta File
The meta file contains a pointer to the software file for updating your device, as well as other descriptive information. The following is an example of a meta file for upgrading between ACNS 5.x software releases.
description=Meta file to install ACNS5.2.0-b350 (from ACNS5.2.0)
updateFileUrl=ftp://myserver.mycorp.com/acns/ruby.bin
password=mypasswrd@mycorp.com
Note If you are updating software using the Content Distribution Manager GUI running ACNS 5.2 software, the meta file is optional.
The meta file that you download from Cisco.com needs to be edited so that it points to the new location of the software file that you saved to your FTP or HTTP server. To edit the meta file, open the file in any text editor, make the appropriate changes, and save the file. You must edit the following line items:
•updateFileUrl=
Replace the URL in this line with the new URL that the Content Engine will use to fetch the software file.
•user=
Replace the username for logging in to the Cisco.com server with the username for logging in to your FTP or HTTP server.
•password=
Replace the password for logging in to the Cisco.com server with the password for logging in to your FTP or HTTP server.
Table 17-1 describes the meta file line items.
Table 17-1 Meta File Line-Item Descriptions
Field
|
Description
|
updateFileSize
|
Size of the software file in bytes.
|
version
|
Target software version to which you want to upgrade or downgrade.
|
description
|
Comments about the meta information. (Optional.) These comments are displayed in the Content Distribution Manager GUI.
|
updateFileURL
|
URL of the software file location. This can be either an FTP URL or an HTTP URL.
Note For HTTP URLs, authenticated servers are not supported, and only port 80 is supported.
|
user
|
Login username.
|
password
|
Login password.
|
The following is a sample meta file for upgrading between ACNS 5.0 software releases.
updateFileUrl= ftp://myserver.mycorp.com/ACNS-5.0.3-K9.bin
password=mypasswrd@mycorp.com
The following sample meta file is for downgrading to ACNS 4.2 software from an ACNS 5.x software release.
updateFileUrl= ftp://myserver.mycorp.com/ACNS-5.x.x-TO-4.2.1-K9.bin
password=mypasswrd@mycorp.com
The CDM-IP field is the IP address of an ACNS 4.x Content Distribution Manager after the software is downgraded to ACNS 4.x. (This field is optional and applies only for downgrades to ACNS 4.x software.) After the downgrade, the Content Engine registers to the Content Distribution Manager with the IP address specified in this field.
Pre-Positioning a Software File
A software file is pre-positioned in the same manner as any other content item. Pre-positioning allows you to conserve bandwidth usage across the WAN and avoid congesting your network during updates. The software file is fetched one time from the origin server, replicated across your network, and stored in Content Engine caches in your LAN.
To pre-position a software file, you must complete the following tasks:
•Define a channel.
•Assign devices to the channel.
•Define the software file that you want to pre-position using a manifest file or the Content Distribution Manager GUI content import feature.
•Check the device replication status.
See "Configuring the ACNS Network for Content Acquisition."
Note Only Content Engines can be updated using pre-positioned software files. Content Routers and Content Distribution Managers do not have pre-positioned content; therefore, you cannot use the pre-positioned method for device updates for these devices.
Sample Manifest File to Pre-Position a Software File
You can use the following sample manifest file to pre-position a software file by replacing the URL with a valid software file URL.
<item src="http://your-web-server.com/folder/upgrade.bin" />
The server name or IP address of the URL in the manifest file (and in the Software File URL field in the Software File Settings window for ACNS 5.2 software [see Figure 17-1]) must match either the Origin Server field or the Request Routed FQDN field in the Content Distribution Manager GUI Web Site window.
Updating Software from the ACNS 5.2 Software Release
ACNS 5.2 software contains a number of improvements to the software update system through the Content Distribution Manager GUI that make software updates faster and easier to administer. In ACNS 5.2 software, all devices (including standby and primary Content Distribution Managers) can be updated by using the primary Content Distribution Manager GUI. A form is provided in the GUI that is used to register the software file URL instead of the meta file URL that was used in previous releases.
Determining the Current Software Version in the ACNS 5.2 Content Distribution Manager GUI
To view the current software version running on any particular device, choose Devices > Devices. The Devices window displays the software version for each device listed.
You can also click the Edit icon next to the name of a device in the Devices window. The Device Home window appears, listing the software version for that device.
Note The software version is not updated until a software update has been successfully completed. If a software update is in progress, the version number displayed is the base version, not the updated version number.
Alternatively, in the Contents pane for any given device, choose Show/Clear Commands > Show Commands. Choose version and click Submit. A secondary window pops up and displays the CLI output for the show version command.
To determine the current ACNS software version from the CLI, use the show version EXEC command.
Registering a Software File URL in the ACNS 5.2 Content Distribution Manager GUI
To update your software from the ACNS 5.2.x release using the Content Distribution Manager GUI, you must first register a software file URL with the Content Distribution Manager and configure the software file settings. The software file settings form in the Content Distribution Manager GUI defines the software file (.bin) and can be used to specify how to obtain the software file, and whether to pre-position it or download it directly to a device.
To configure the software file settings form, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose System > Software Files.
Step 2 Click the Create New Software File icon in the taskbar. The Creating New Software File window appears. (See Figure 17-1.)
Figure 17-1 Creating New Software File Window
Step 3 In the Software File URL field, enter the URL for the .bin software file that you downloaded from Cisco.com.
a. Choose a protocol (http or ftp) from the drop-down list.
b. Enter the URL of the software file. For example, a valid URL might look like this:
http://internal.mysite.com/cdn/ACNS-version.bin
where ACNS-version is the name of the software update file. (The filename might include the version number, or it might not.)
Note If you are using a pre-positioned software file and you are entering the URL manually (rather than using the Select File from Channel option), the server name or IP address of the URL in the Software File URL field must match either the Origin Server field or the Request Routed FQDN field in the Content Distribution Manager GUI Web Site window of the channel. This is not a requirement if you are downloading the software file directly from the origin server.
Alternatively, click the Select File from Channel button. A separate window pops up that allows you to choose a channel, set criteria, search the channel, and select the software file that you wish to use for the software update. (You must first pre-position the software file in the channel. See the "Pre-Positioning a Software File" section.)
Step 4 If your server requires user login authentication, enter your username in the Username field and enter your login password in the Password field. Enter the same password in the Confirm Password field.
Step 5 Enter the software version number in the Software Version field. You can copy this number from the version portion of the software filename in the software file URL.
Specify the version in one of two formats: X.Y.Z-bB or X.Y.Z.b.B, where X = major version, Y = minor version, Z = maintenance version, b = build letter, and B = build number.
Step 6 If you want the size of the software file considered during validation, enter a file size (in bytes) in the File Size field. If you leave this field blank, the URL is checked without regard to the software file size.
Step 7 To validate the Software File URL, Username, and Password fields, click the Validate Software File button.
When you click the Validate Software File button, the following occur:
•The software file URL is resolved.
•A connection to the software file URL is established using the username and password, if specified.
•If a file size is specified, the actual size of the software file is obtained and compared against the value in the File Size field.
•A message is returned, indicating success or errors encountered.
Step 8 In the Advanced Settings section, check the Auto Reload check box to automatically reload a device when you update the software.
Step 9 If you wish, you can choose one of three download methods:
•Default—Uses pre-positioned content but always falls back to direct download.
•Pre-positioned content only—Uses the local file copy if the software file URL references pre-positioned content and its replication status is complete.
•Direct download only—Directly downloads the file using the software file URL.
Note If you choose Pre-positioned content only, the software file settings that you define in this window cannot be used to upgrade a Content Distribution Manager or a Content Router, because these devices do not have pre-positioned content.
Step 10 For downgrades to ACNS 4.x software only, specify the 4.x Content Distribution Manager IP address to be used for device registration in the CDM IP Address field.
The CDM IP Address field is the IP address of an ACNS 4.x Content Distribution Manager after the software is downgraded to ACNS 4.x. (This field is optional and applies only for downgrades to ACNS 4.x software.) After the downgrade, the Content Engine registers with the Content Distribution Manager with the IP address specified in this field.
Step 11 Click Submit. A message appears indicating that the update is successful. Click OK.
Caution If your browser is configured to save the username and password for the Content Distribution Manager GUI, the browser will autopopulate the username and password fields in the Creating New Software File window. You must clear these fields before you click
Submit.
The software file that you want to use is now registered with the Content Distribution Manager. When you perform the software update, the URL that you just registered becomes one of the choices available in the Update Software window. (See the "Updating the Software Using the ACNS 5.2 Content Distribution Manager GUI" section.)
Using a Meta File as a Template for the Software File Settings Form
A meta file contains a pointer to the software file, as well as other descriptive information. A meta file is posted on Cisco.com along with each software file. (See the "Obtaining a Meta File from Cisco.com" section.)
Tip We suggest that you edit the meta file before you import it to use as a template. See the "Editing the Meta File" section. If you choose not to edit the meta file before importing it, you can edit the information in the software file settings form; however, it is best to edit the meta file first, and use it as a template for future updates.
To import a meta file to use as a template for filling in the software file settings form, follow these steps:
Step 1 Launch the Content Distribution Manager and log in using an administrative username and password.
Step 2 From the Content Distribution Manager GUI, choose System > Software Files. The Software Files listing window appears.
Step 3 Click the Import Meta File icon in the task bar. The Importing Meta File to Create New Software File window appears.
Step 4 In the Meta File URL field, enter the URL for the .meta file that you downloaded from Cisco.com.
Step 5 Click Submit. A message appears indicating that the update is successful. Click OK. The Modifying Software File window appears with the fields populated from the information in the meta file.
Step 6 Review the software file information and make changes if you wish. At this time, you can configure the Advanced Settings section, if you wish.
Step 7 Click Submit in the Modifying Software File window if you modified the form, or click Cancel to return to the Software File listing window.
Updating the Software Using the ACNS 5.2 Content Distribution Manager GUI
When updating software in your ACNS network, begin with Content Engines and Content Routers before updating the Content Distribution Manager. The Content Distribution Manager reboots at the conclusion of the update procedure, causing you to temporarily lose contact with the device and the graphical user interface. Once the Content Distribution Manager has updated its software and rebooted, it may be unable to communicate with devices running different versions of the ACNS software.
Note See the "Upgrade, Downgrade, and Interoperability Considerations" section for the correct order in which to update devices.
Multiple Device Updates for Content Engines Using Device Groups
Note This procedure is for Content Engines only. Content Routers and Content Distribution Managers cannot be associated with device groups.
To update your software from an ACNS 5.2.x software release to another ACNS 5.x software release on multiple Content Engines, follow these steps:
Step 1 From the ACNS 5.2 software Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups listing window appears, listing all the device groups in your ACNS network.
Step 2 Click the Edit icon next to the name of the device group that you want to update. The Modifying Device Group window appears.
Step 3 In the Contents pane, choose Software Update. The Software Update for Device Group window appears. (See Figure 17-2.)
Figure 17-2 Software Update for Device Group Window
Step 4 Choose the software file URL from the Software File URL list by clicking the radio button next to the filename.
Step 5 Click Submit.
To view progress on an upgrade, go to the Devices window (Devices > Devices). Software update status messages are displayed in the Software Version column. These intermediate messages are also written to the system log on Content Engines. See Table 17-2 for a description of update status messages.
Table 17-2 Update Status Messages
Update Status Message
|
Condition
|
Pending
|
The request has yet to be sent from the Content Distribution Manager to the device, or receipt of the request has yet to be acknowledged by the device.
|
Downloading
|
The download method for the software file is being determined.
|
Proceeding with Prepositioned Download
|
The download method for the software file is determined to be pre-positioning. Proceeding with download of a pre-positioned software file.
|
Proceeding with Download
|
The download method for the software file is determined to be direct download. Proceeding with the request for direct download of the software file.
|
Download in Progress (Completed ...)
|
Direct download of the software file is being processed. "Completed" indicates the number of megabytes processed.
|
Download Successful
|
The direct download of the software file has been successful.
|
Download Failed
|
The direct download of the software file cannot be processed. Further troubleshooting is required; see the device system message log.
|
Proceeding with Flash Write
|
A request has been made to write the software file to the device flash memory.
|
Flash Write in Progress (Completed ...)
|
The write of the device flash memory is being processed. "Completed" indicates the number of megabytes processed.
|
Flash Write Successful
|
The flash write of the software file has been successful.
|
Reloading
|
A request to reload the device has been made in order to complete the software update. The device may be offline for several minutes.
|
Reload Needed
|
A request to reload the device has not been made. The device must be reloaded manually to complete the software update.
|
Cancelled
|
The software update request was interrupted, or a previous software update request was bypassed from the CLI.
|
Update Failed
|
The software update could not be completed. Troubleshooting is required; see the device system message log.
|
Single Device Updates Between ACNS 5.2 Releases
Use this update procedure for Content Routers and Content Distribution Managers. You can also use this update procedure to update Content Engines one at a time.
To update your software from an ACNS 5.2.x software release to another ACNS 5.x software release on a single device, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Devices.
Step 2 Click the Edit icon of the device that you want to update. The Device Home window appears.
Step 3 Verify that the device is not already running the version that you plan to upgrade to, and that the current version has an upgrade path to the version that you plan to upgrade to.
Step 4 Click the Update Software button. The Software Update window appears.
Step 5 Choose the software file URL from the Software Files list by clicking the radio button next to the filename.
Step 6 Click Submit. Click OK to confirm your decision. The Devices listing window reappears. You can monitor the progress of your update from this window.
Software update status messages are displayed in the Software Version column. These intermediate messages are also written to the system log on Content Engines. See Table 17-2 for a description of update status messages.
For more information on the status of software upgrades on devices across your ACNS network, see the "Using the System Message Log" section.
Deleting a Software File from the ACNS 5.2 Content Distribution Manager GUI
To delete an ACNS software file, follow these steps:
Step 1 Choose System > Software Files.
Step 2 Click the Edit icon next to the software file that you want to delete. The Modifying Software File window appears.
Step 3 Click the Trash icon in the taskbar. You are prompted to confirm your decision to delete the software file.
Step 4 Click OK. You are returned to the Software Files listing window with the selected software file removed from the ACNS network.
Note When updating Content Engines, Content Routers, or standby or primary Content Distribution Managers using the CLI, follow the procedures in the "Upgrading or Downgrading Between ACNS 5.x Releases Using the CLI" section.
Updating from ACNS 5.1.x Software to ACNS 5.x Software
To upgrade or downgrade from the ACNS 5.1.x software release to another ACNS 5.x.x software release, choose between using the Content Distribution Manager GUI or the CLI.
From the Content Distribution Manager GUI, you can perform these tasks:
•Determine the current version of ACNS software.
•Register a meta file containing the software file URL in the Content Distribution Manager.
•Perform a software update for Content Engines and Content Routers in your ACNS network.
From the CLI, you can perform these tasks:
•Determine the current version of ACNS software.
•Perform a software update for individual Content Distribution Managers, Content Engines, and Content Routers.
Note ACNS 5.1 software does not support upgrading the Content Distribution Manager using the Content Distribution Manager GUI. To upgrade the Content Distribution Manager, follow the procedure in the "Upgrading or Downgrading Between ACNS 5.x Releases Using the CLI" section.
Determining the Current Software Version in the ACNS 5.1 Content Distribution Manager GUI
To determine the current ACNS software version from the Content Distribution Manager GUI, follow these steps:
Step 1 To view the current software version running on the Content Distribution Manager, choose Devices > CDM.
Step 2 Click the Edit icon next to the name of the device. The Modifying Content Distribution Manager window appears, listing the software version.
Step 3 To view the current software version running on a Content Engine, choose Devices > Content Engines.
Step 4 Click the Edit icon next to the name of the Content Engine. In the Contents pane, choose CDN Settings > Status. The software version number is displayed under the Device Information heading.
Step 5 To view the current software version running on a Content Router, choose Devices > Content Routers. Click the Edit icon next to the name of the Content Router and choose CDN Settings > Status.
Note The software version is not updated until a software upgrade has been successfully completed. If a software upgrade is in progress, the version number displayed is the base version, not the updated version number.
Step 6 Alternatively, in the Contents pane for any given device, choose Show/Clear Commands > Show Commands. Choose version and click Submit. A secondary window pops up and displays the CLI output for the show version command.
To determine the current ACNS software version from the CLI, use the show version EXEC command.
Registering a Meta File URL in the ACNS 5.1 Content Distribution Manager GUI
To upgrade software using the Content Distribution Manager GUI, you must first register the URL of a meta file with the Content Distribution Manager. A meta file contains a pointer to the software file that you want to register for updating your device, as well as other descriptive information. (See Table 17-1 for a description of meta file contents.)
To enter the meta file URL, follow these steps:
Step 1 Launch the Content Distribution Manager and log in using an administrative username and password.
Step 2 From the Content Distribution Manager GUI, choose System > Software Update. The Software Update File Registration window appears.
Step 3 To register a new meta file, click the Add Software Update File icon. The Registering New Software Update File window appears. (See Figure 17-3.)
Figure 17-3 Registering New Software Update File Window
Step 4 Paste the URL for the meta file on your web server into the field provided. (See the "Obtaining a Meta File from Cisco.com" section for a sample meta file and field descriptions.) For example, a valid URL might look like this:
http://internal.mysite.com/cdn/ACNS-version.meta
where ACNS-version is the version number of the software upgrade.
Note Do not attempt to link directly to the software file (.upg or .bin file). The relative location of the software file is provided by the meta file.
Step 5 Click Submit.
The meta file that you want to use is now registered with the Content Distribution Manager. When you perform the software update, the meta file URL that you just registered becomes one of the choices available in the Update Software window. (See Figure 17-4.)
Note The meta file URL remains the same even if the software file that it points to has been changed on your web server, such as for a patch release. When you attempt to register the new meta file, the GUI rejects it because the meta file appears to be already registered. This occurs because the meta file URL is the same, even though other contents of the meta file might have changed. Therefore, to update a previously registered meta file, you must first delete the existing entry and then register the new meta file.
To remove a registered meta file, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose System > Software Update. The Software Update File Registration window appears.
Step 2 Click the Edit icon next to the target meta file. The Modifying Software Update File window appears.
Step 3 Click the Trash icon.
Step 4 At the prompt, click OK to confirm your decision.
You can now register the new meta file.
Upgrading or Downgrading Using the ACNS 5.1 Content Distribution Manager GUI
You can upgrade software on your Content Engines and Content Routers using the Content Distribution Manager GUI. When upgrading, begin with Content Engines and Content Routers before upgrading the Content Distribution Manager.
The Content Distribution Manager reboots at the conclusion of the upgrade procedure, causing you to temporarily lose contact with the device and the graphical user interface.
Once the Content Distribution Manager has upgraded its software and rebooted, it may be unable to communicate with devices running different versions of the ACNS software.
Note ACNS 5.1 software does not support upgrading the Content Distribution Manager using the Content Distribution Manager GUI. To upgrade the Content Distribution Manager, follow the procedure in the "Upgrading or Downgrading Between ACNS 5.x Releases Using the CLI" section.
To upgrade from one ACNS 5.1 software release to another ACNS 5.x software release on your Content Engines and Content Routers, follow these steps:
Step 1 From the ACNS 5.1 software Content Distribution Manager GUI, choose Devices > Content Engines. The Content Engines window appears, listing all the Content Engines in your ACNS network.
For Content Routers, choose Devices > Content Routers. The Content Routers window appears.
For multiple Content Engine upgrades, choose Devices > Device Groups.
Step 2 Click the Edit icon next to the name of the device and click Status in the Contents pane to check the software version. Verify that the devices you are choosing are not already running the version that you plan to upgrade to, and that the current version has an upgrade path to the version that you plan to upgrade to.
Step 3 In the Contents pane, choose CDN Settings > Software Upgrade/Downgrade. The Update Software window appears. (See Figure 17-4.)
Note Always upgrade Content Engines and Content Routers before you upgrade the associated Content Distribution Manager.
Figure 17-4 Update Software Window
Step 4 Choose the meta file URL from the drop-down list.
Step 5 Click Submit.
Step 6 To view progress on an upgrade, go to the Content Engines or Content Routers window. (See Step 1.) Software update status messages are displayed in Software Version column. These intermediate messages are also written to the system log on Content Engines.
Table 17-2 shows the status update messages that are displayed in the Software Version column in the Content Engines window on the Content Distribution Manager GUI during requests for pre-positioned software files for software updates.
Table 17-3 Channel Update Status Messages
Condition
|
Update Status Message
|
The URL has been determined to be for a pre-positioned software file.
|
Proceeding with Prepositioned Download
|
A request for a pre-positioned software file has been made and is being processed. "Completed" indicates the number of megabytes processed.
|
Prepositioned Download in Progress (Completed ...)
|
A request for a pre-positioned software file was processed successfully.
|
Prepositioned Download Successful
|
A request for a pre-positioned software file was not able to be processed. Troubleshooting is required.
|
Prepositioned Download Failed
|
Note The channel update status messages are meant only for pre-positioned software files for software updates. These messages will be displayed only when a software update is in progress.
For more information on the status of software upgrades on devices across your ACNS network, see the "Using the System Message Log" section.
Deleting an Update File from the ACNS 5.1 Content Distribution Manager GUI
To delete an update file from the ACNS 5.1 Content Distribution Manager GUI, follow these steps:
Step 1 In the Update Software window (see Figure 17-4), if there are multiple files to choose from, click the button next to the update file that you want to delete. Otherwise, proceed to the next step.
Step 2 Click Delete. You are prompted to confirm your decision to delete the update file.
Step 3 Click OK. You are returned to the Software Update window with the selected update file removed from the ACNS network.
Upgrading or Downgrading Between ACNS 5.x Releases Using the CLI
To use the CLI to perform an upgrade, you need the following items:
•FTP or HTTP server with the upgrade package files
•Network connectivity between the device to be upgraded and the server hosting the upgrade files
•Appropriate .bin upgrade or downgrade package file:
–ACNS-5.x.x-K9.bin
To install the upgrade or downgrade package file using the CLI, follow these steps:
Step 1 Install the upgrade or downgrade package file by using the copy ftp install EXEC or copy http install EXEC command:
CE# copy ftp install ftp-server package-file-path package-file-name
CE# copy http install http-server package-file-path package-file-name [portnumber]
Step 2 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. For example:
CE-507# copy ftp disk ACNS-5.x.x-K9.bin
CE-507# install ACNS-5.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 3 After the package files are copied to your system, use the reload EXEC command to reboot.
The installation process continues automatically after the reboot. No further action is required.
Upgrading and Downgrading an ACNS 5.1 Standby Content Distribution Manager Using the CLI
Cisco ACNS software implements a standby Content Distribution Manager feature that allows a second Content Distribution Manager to receive updates from a primary Content Distribution Manager and therefore maintain a copy of the ACNS network configuration. If the primary Content Distribution Manager fails, the standby can be used to replace the primary.
For interoperability, when a standby Content Distribution Manager is used, it must be at the same software version as the primary Content Distribution Manager in order to maintain the full Content Distribution Manager configuration.
When upgrading an ACNS network containing a standby Content Distribution Manager, use the following procedure:
Step 1 Stop the standby Content Distribution Manager using the no cms enable command.
Step 2 Stop the primary Content Distribution Manager using the no cms enable command. Stopping the Content Distribution Manager does not affect the other ACNS network content request or content pre-positioning services.
Step 3 Install the new software version on the primary Content Distribution Manager using the copy ftp install {hostname | ip-address} remotefiledir remotefilename EXEC command.
The primary Content Distribution Manager will reboot as part of the installation procedure.
Step 4 After the reboot, it is best to copy to a safe place the Content Distribution Manager database backup that is made as part of the software upgrade. These backups are made in the /local/local1 directory and have a .dump file extension. These files can be copied to another location using the copy ftp disk {hostname | ip-address} remotefiledir remotefilename localfilename EXEC command.
Step 5 Restart the primary Content Distribution Manager using the cms enable command.
Step 6 Ensure that the status of devices is "online" in the Content Distribution Manager device lists and that the ACNS network is working with the new Content Distribution Manager software.
Step 7 Upgrade the standby Content Distribution Manager using the copy ftp install {hostname | ip-address} remotefiledir remotefilename command.
The standby Content Distribution Manager will reboot as part of the installation process.
Step 8 Restart the standby Content Distribution Manager using the cms enable command.
When downgrading a Content Distribution Manager, you must restore a previous database backup before installing the downgraded software version. Use the following procedure to downgrade a Content Distribution Manager:
Step 1 If there is a standby Content Distribution Manager, stop it using the no cms enable command.
Step 2 Stop the primary Content Distribution Manager using the no cms enable command. Stopping the Content Distribution Manager does not affect the other ACNS network content request or content pre-positioning services.
Step 3 Use the cms database backup command to back up the existing primary Content Distribution Manager database if you wish to retain the current configuration data. This action creates a database .dump file in the /local/local1 directory.
Step 4 Once the backup is complete, the existing database must be cleared of all tables present in it. Use the cms database delete command to delete the embedded database files.
Step 5 Restore the database backup that matches the version of the downgraded software to the primary Content Distribution Manager using the cms database restore filename command. This database backup must be present on the Content Distribution Manager to use the cms database restore filename command. When the Content Distribution Manager is upgraded, a database backup .dump file will be created in the /local/local1 directory. To copy the database backup file to the device, use the copy ftp disk {hostname | ip-address} remotefiledir remotefilename localfilename command.
Step 6 Install the downgraded software version on the primary Content Distribution Manager, using the copy ftp install {hostname | ip-address} remotefiledir remotefilename EXEC command. The primary Content Distribution Manager will reboot as part of the installation procedure.
Step 7 After the reboot, restart the CMS processes using the cms enable command.
Step 8 If there is a standby Content Distribution Manager, create a database backup of the existing database by using the cms database backup command. This will create a database .dump file in the /local/local1 directory.
Step 9 Install the downgraded software version on the standby Content Distribution Manager using the copy ftp install {hostname | ip-address} remotefiledir remotefilename EXEC command. The software version must match the version of the primary Content Distribution Manager. The standby Content Distribution Manager will reboot as part of the installation procedure.
Step 10 After the reboot, the CMS database must be re-created so that the database definition matches the version of the software. To do this, first use the cms database delete command to remove the old software version database. Then run the cms database create command to create the matching database definition.
Step 11 Restart the CMS on the standby Content Distribution Manager using the cms enable command. The standby Content Distribution Manager will request a full data update from the primary Content Distribution Manager.
Migrating from ACNS 4.2 Software to ACNS 5.x Software
If you are upgrading a device that is operating as part of an ACNS network or if you are migrating an entire network to ACNS 5.x software, you must carefully follow the migration procedure that is documented in the Cisco ACNS Software Migration Guide, Release 5.x. This document is available online at the following URL:
http://www.cisco.com/en/US/products/sw/conntsw/ps491/products_getting_started_guides_list.html
Note Cisco Systems currently supports two migration options for your network. The first option requires that you shut down your ACNS network and convert the entire network to ACNS 5.x software. The second option allows you to continue operating your ACNS network while you perform a gradual migration to ACNS 5.x software.
In deciding which option to use, you should consider the performance requirements of your network and what additional equipment might be required to complete the network migration method you choose.
To upgrade from a previous release of ACNS software to ACNS 5.x software, you must be running ACNS 4.2 software or a later version of ACNS 4.x software. If you are running ACNS 4.1.3 or an earlier version of ACNS software, you must first upgrade your software to ACNS 4.2 before you can upgrade to ACNS 5.x software. (See the "Upgrading from ACNS 4.x Software to ACNS 4.2 Software" section.)
If you are running Cache software or E-CDN software, first upgrade to ACNS 4.2 software and then upgrade to ACNS 5.x software. For these upgrade instructions, refer to the Cisco ACNS Software Maintenance and Troubleshooting Guide that is available online at the following URL:
http://www.cisco.com/en/US/products/sw/conntsw/ps491/prod_maintenance_guides_list.html
Note Upgrading from Internet CDN (ICDN) software to ACNS software is not supported.
Note When upgrading from ACNS 4.2 software to ACNS 5.x software, any ecdnfs file systems are automatically changed to cdnfs file systems. Files are not deleted unless the administrator specifically deletes them.
Upgrading a Standalone ACNS 4.2 Content Engine or Content Router
This section describes how to upgrade from ACNS 4.2 software to ACNS 5.x software on a device that is not operating as part of an ACNS network. After performing this upgrade procedure, you must manually configure the device and register it with the Content Distribution Manager before it can join the ACNS 5.x network, or else it can operate as a standalone caching device.
To perform an upgrade from ACNS 4.2 software to ACNS 5.x software on a Content Engine or Content Router that is not operating as part of an ACNS 4.2 ACNS network, you need the following items:
•FTP or HTTP server with the upgrade package files
•Network connectivity between the device to be upgraded and the server hosting the upgrade files
•Appropriate .bin upgrade package file:
–ACNS-4.2.x-TO-5.x.x-K9.bin
To install the upgrade package file, follow these steps:
Step 1 Install the upgrade package file by using the copy ftp install or copy http install EXEC command:
Device# copy ftp install ftp-server package-file-path package-file-name
Device# copy http install http-server package-file-path package-file-name [portnumber]
Step 2 After the package files are copied to your system, use the reload command to reboot.
The standalone Content Engine or Content Router is now running ACNS 5.x software.
After this upgrade procedure, the device can be manually configured and registered with the Content Distribution Manager in order to join the ACNS 5.x network. (See "Getting Started.")
If you wish to connect the standalone Content Engine to an ACNS 5.x network, follow these steps:
Step 1 In the Content Engine CLI, configure the IP address of the Content Distribution Manager for the ACNS network by using the cdm ip global configuration command.
ContentEngine(config) cdm ip cdmIPaddress
Step 2 Enable the Centralized Management System (CMS).
ContentEngine(config)# cms enable
Step 3 Write the current configuration to memory.
ContentEngine# write memory
After you upgrade from ACNS 4.2.x software to ACNS 5.x software, we strongly recommend that you reconfigure the Content Engine for Network Time Protocol (NTP) to ensure that the system clock on the Content Engine is synchronized with the NTP time server clock. This can be done on the Content Engine by using the ntp server {ip-address | hostname} global configuration command or by using the Content Distribution Manager GUI. (See the "Configuring NTP Settings" section.)
Upgrading from ACNS 4.x Software to ACNS 4.2 Software
Cisco ACNS 5.x software introduces significant changes from the functionality of ACNS 4.2 software. The existing ACNS network must run ACNS 4.2 software in order to be migrated to ACNS 5.x software. If ACNS network devices are running a software version earlier than ACNS 4.2, they must first upgrade to ACNS 4.2 software before the migration process. This ensures that the pre-positioned content is preserved in the migration process.
This section describes how to upgrade from ACNS 4.x software to the ACNS 4.2 software release. You can choose between using the Content Distribution Manager GUI or the CLI.
Upgrading from ACNS 4.x Software to ACNS 4.2 Software Using the Content Distribution Manager GUI
If you choose to use the Content Distribution Manager GUI to perform the upgrade, you must use the following file set:
•ACNS-4.x.x-K9.upg
•ACNS-4.x.x-K9.meta
To install the upgrade package file using the Content Distribution Manager GUI, follow these steps:
Step 1 From the ACNS 4.x Content Distribution Manager GUI, choose Channels > Channel Console, and follow these steps:
a. Click the Add Channel button at the top of the window.
b. Click the Edit button next to the channel that you added.
c. Create a channel named "MANUAL_UPGRADE" by entering MANUAL_UPGRADE in the Name field.
d. Check the Auto-Replicate check box.
e. Click the Save Changes button at the top of the window.
Step 2 Choose Devices > Bandwidth to make sure that the replication bandwidth has been set correctly for each device that you are going to upgrade or downgrade. Make the settings as high as your available bandwidth allows.
Step 3 Choose Channels > Subscriber to subscribe your devices to the MANUAL_UPGRADE channel.
Step 4 Choose Channels > Channel Editor > Media Importer to import the upgrade or downgrade package files.
a. Import the upgrade or downgrade package files to the MANUAL_UPGRADE channel.
b. Choose Channels > Channel Editor > Import Progress to make sure that the Import Progress status field shows 100 percent completion.
c. Wait an additional 20 minutes or so for the channel replication to finish.
d. Choose Channels > Channel Console, and verify that the Replication Status field shows 100 percent completion for the MANUAL_UPGRADE channel.
Step 5 Choose Devices > Software Update to execute the upgrade or downgrade for Content Engines and Content Routers. (The Content Distribution Manager is upgraded or downgraded in another step later on.)
a. Choose the upgrade or downgrade package version, and then choose all the device names of the devices that you want upgraded or downgraded. Click the Start Update button.
b. Wait approximately 30 minutes for the upgrade or downgrade to be completed.
Step 6 Verify that the upgrade or downgrade was successful by checking the Version field in the Software Update window. If the upgrade or downgrade was successful, the Version field for the chosen device is updated with the new software version.
Step 7 After the upgrade or downgrade is complete for all your Content Engines and Content Routers, you need to upgrade or downgrade your Content Distribution Manager.
a. Choose Devices > Software Update. Choose the upgrade or downgrade package version, and then choose your Content Distribution Manager. Click the Start Update button at the top of the window.
b. Wait for the upgrade or downgrade to be completed.
Upgrading from ACNS 4.x Software to ACNS 4.2 Software Using the CLI
If you choose to use the CLI to perform an upgrade for a device that is running ACNS 4.x software, you need the following:
•FTP server with the upgrade package files
•Network connectivity between the device to be upgraded and the server hosting the appropriate files
•Appropriate .bin upgrade file: ACNS-4.x.x-K9.bin
To install the upgrade file using the CLI, follow these steps:
Step 1 Install the upgrade file by using the copy ftp install or copy http install EXEC 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 EXEC command to reboot.
The installation process continues automatically after the reboot. No further action is required.
Downgrading from ACNS 5.x Software to ACNS 4.2.x Software
Cisco ACNS 5.x software and ACNS 4.2 software have significant functional differences.When you downgrade from an ACNS 5.x release to an ACNS 4.x release, note the following:
•After the downgrade, ACNS 5.x.x features will not work.
•Any content acquired by the ACNS 5.x.x Content Engine will be lost after the downgrade.
Use the following files for the downgrade:
•ACNS-5.x.x.x.x-TO-4.2.x-K9.bin software file, where x corresponds to the current version.
•acns4_cdm_ip.meta
This downgrade meta file registers the device with the ACNS 4.2 Content Distribution Manager and to points to the software (.bin) file for the downgrade.
Downgrading from ACNS 5.1 Software to ACNS 4.2.9 Software Using the Content Distribution Manager GUI
To downgrade to ACNS 4.2 software using the ACNS 5.1 Content Distribution Manager GUI, follow these steps:
Step 1 Obtain the correct software file from Cisco.com. (See the "Obtaining a Software File from Cisco.com" section.)
Step 2 Obtain the correct meta file (acns4_cdm_ip.meta) from Cisco.com. (See the "Obtaining a Meta File from Cisco.com" section.)
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 and save it. (See the "Editing the Meta File" section.)
•In the updateFileUrl field, replace the URL with the URL to the ACNS-5.1.x.x-TO-4.2.9-K9.bin software file that you downloaded from Cisco.com.
•Edit the username and password.
Step 4 Register the meta file URL with the Content Distribution Manager.
•Follow the procedure in the "Registering a Meta File URL in the ACNS 5.1 Content Distribution Manager GUI" section.
•In the Software Update Meta File URL field (see Figure 17-3), enter the URL of the downgrade meta file.
Step 5 To complete the downgrade, follow the procedure in the "Upgrading or Downgrading Using the ACNS 5.1 Content Distribution Manager GUI" section.
Downgrading from ACNS 5.2 Software to ACNS 4.2.9 Software Using the Content Distribution Manager GUI
To downgrade to ACNS 4.2 software using the ACNS 5.2 Content Distribution Manager GUI, follow the procedures in the "Updating Software from the ACNS 5.2 Software Release" section.
In the section, "Registering a Software File URL in the ACNS 5.2 Content Distribution Manager GUI," enter the following information in the Creating Software File window (see Figure 17-1):
•In the Software File URL field, enter the URL of the software downgrade file.
ACNS-5.2.x.x-TO-4.2.9-K9.bin
where x corresponds to the current version that you are using.
•In the CDM IP Address field, specify the 4.x Content Distribution Manager IP address to be used for device registration.
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 itself.
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.)
Step 2 Obtain the correct meta file (acns4_cdm_ip.meta) from Cisco.com. (See the "Obtaining a Meta File from Cisco.com" section.)
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.)
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 a 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, use the reload EXEC command to reboot.
The installation process continues automatically after the reboot. No further action is required.
