Table Of Contents
Upgrading AON Software
Obtaining AON Software
Upgrade Paths
Upgrading AON 1.x Releases
Downloading Files
Upgrading to from AON 1.x to AON 2.1
Upgrading the AON Management Console to Version 2.1
Upgrading the AON Appliance
Upgrading the AON-SM
Upgrading the AON-NM
Upgrading AON 2.1 Releases
Upgrading from AON 2.1 to AON 2.1.1
Upgrading from AON 2.1 to AON 2.1.2
Upgrading from AON 2.1.1 to AON 2.1.2
Upgrading Firmware on the AON Appliance
Upgrading to AON 2.4
Upgrading the AON Management Console to Version 2.4
Upgrading Nodes to Version 2.4
Upgrading to AON 3.0
Upgrading the AON Management Console to Version 3.0
Upgrading Nodes to Version 3.0
Upgrading AON Software
The procedure that follows explains how to upgrade your Application-Oriented Networking (AON) environment to Cisco Application-Oriented Networking 3.0. It includes the following sections:
•
Obtaining AON Software
•
Upgrade Paths
•
Upgrading AON 1.x Releases
•
Upgrading AON 2.1 Releases
•
Upgrading to AON 2.4
•
Upgrading to AON 3.0
Caution 
Data loss may occur if you attempt to upgrade from a 1.
x release to AON version 2.1.1 or later. You must first upgrade from 1.
x to version 2.1.
Obtaining AON Software
AON software is available at the following URL:
http://www.cisco.com/public/sw-center/aon.shtml
Upgrade Paths
Table 2-1 lists the valid upgrade paths for each AON software release.
Table 2-1 AON Upgrade Paths
Current AON Release
|
Valid Upgrade Paths
|
Node Upgrade Required
|
AON 1.x
|
AON 2.1 only
|
Yes
|
AON 2.1.0
|
Any AON 2.x
|
Only if upgrading to AON 2.4
|
AON 2.1.x
|
Any AON 2.x
|
Only if upgrading to AON 2.4
|
AON 2.2
|
AON 2.4
|
Yes1
|
AON 2.4
|
AON 3.0
|
Yes
|
Upgrading AON 1.x Releases
AON version 2.1 includes a new software architecture to improve the process of upgrading nodes for future AON software releases. Consequently, this upgrade has several unique steps that differ from previous upgrade procedures. After this migration, future upgrades will be delivered in smaller files, and upgrades will require less downtime to complete.
Note
Be sure to read this procedure completely before beginning the upgrade. The upgrade procedure for version 2.x releases is different from that of version 1.x releases.
Downloading Files
To perform this upgrade, make sure you have downloaded the files listed in Table 2-2.
Table 2-2 Files Required to Upgrade from an AON 1.x Release
Platform
|
Required files
|
AON Management Console
|
aon-amc_2.1.0.173_k9_lnx.upgrade.bin
|
AON Development Studio
|
aon-ads_2.1.0.173_k9_installer_win.exe
|
Cisco 8340 AON Appliance
• APL-AON-8340-K9
|
Helper files:
• aon-apl-8340_2.1.0.173_k9_helper_lnx.pkg
• aon-apl-8340_2.1.0.173_k9_helper_lnx
• aon-apl-8340_2.1.0.173_k9_helper_lnx.prt1
Image files:
• aon-apl-8340_2.1.0.173_k9_lnx.pkg
• aon-apl-8340-full_2.1.0.173_k9_lnx.prt1
• aon-apl-8340-installer_2.1.0.173_k9_lnx.prt1
|
AON Service Module
|
Migration files:
• aon-svc_1.x_to_2.1.0.173_k9_helper_lnx.pkg
• aon-svc_1.x_to_2.1.0.173_k9_helper_lnx.prt1
• aon-svc_1.x_to_2.1.0.173_k9_helper_lnx.manifest
Helper files:
• aon-svc_2.1.0.173_k9_helper_lnx.pkg
• aon-svc_2.1.0.173_k9_helper_lnx.prt1
Image files:
• aon-svc_2.1.0.173_k9_lnx.pkg
• aon-svc-full_2.1.0.173_k9_lnx.prt1
• aon-svc-installer_2.1.0.173_k9_lnx.prt1
|
AON Network Module
|
Helper file
• aon-nm_2.1.0.173_k9_helper_lnx
Image files:
• aon-nm_2.1.0.173_k9_lnx.pkg
• aon-nm-full_2.1.0.173_k9_lnx.prt1
• aon-nm-installer_2.1.0.173_k9_lnx.prt1
|
Upgrading to from AON 1.x to AON 2.1
The steps that follow cover the tasks required for upgrading AMC and AON nodes and the order in which the must be performed. For more detailed instructions on the individual tasks that comprise this upgrade, see the following sections in this document:
•
Upgrading the AON Management Console to Version 2.1
•
Upgrading the AON Appliance
•
Upgrading the AON-SM
•
Upgrading the AON-NM
Note
This procedure refers to the default installation directory of /opt/amc. If your AMC is installed in a different directory, substitute that location when performing the steps below.
Upgrade Prerequisites
Before beginning, be sure to complete the following steps:
•
Download all of the files needed to upgrade your AON environment. See Table 2-2 for a list of necessary files.
•
Develop a backup and recovery strategy for the devices in your environment. At minimum you should have a TFTP server to store node configurations and external storage to back up your version 1.1 AMC installation.
•
Verify that the Cisco IOS and CatOS versions for the switches and routers that host AON nodes, and upgrade any platforms as required. See the Release Notes for Cisco Application-Oriented Networking Version 2.1 for software requirements.
Caution 
You must ensure that any existing deployment requests are in the open (unstaged) state before you shut down AMC for the upgrade. Failure to do so may result in data loss.
To complete the upgrade, perform the following steps:
Step 1
Ensure that all users of ADS have synchronized PEP and message type changes before you begin the upgrade. Deploy these changes to nodes if necessary.
Step 2
Use tar or a similar command to back up the directory in which AMC is installed.
a.
For example: tar cvzf amc1_1_backup.tar.gz /opt/amc
b.
Copy the backup file to an external device.
Step 3
On each node being upgraded, copy the system and start-up configurations to a TFTP server.
a.
Use copy running-config startup-config to save the current system configuration.
b.
Use copy running-config tftp to copy the configuration to a TFTP server.
Step 4
Use the following steps to upgrade AMC to version 2.1.0.173.
a.
Deactivate any active nodes.
b.
Log in to the server running AMC as root.
c.
Run aon-amc_2.1.0.173_k9_lnx.upgrade.bin. Near the end of the upgrade, it prompts you to start AMC. You must enter no here.
Note
Do not start AMC until instructed to do so in Step 6.
For detailed instructions on upgrading AMC, see the "Upgrading the AON Management Console to Version 2.1" section.
Step 5
Run the data upgrade script.
a.
Change to the /opt/amc/bin directory.
b.
Use ./upgradeData to run the script
Step 6
Use ./amcd start to launch AMC.
Step 7
Upgrade each node to version 2.1.0.173.
a.
See the following sections of this document for detailed instructions:
–
Upgrading the AON Appliance
–
Upgrading the AON-SM
–
Upgrading the AON-NM
b.
After each node restarts, use configuration terminal mode to enter a new AON configuration so that the node can register with AMC.
c.
Restart AON. Nodes will be shown as Registered on AMC, and you must activate each node.
Note
You may see errors in aons.log when an upgraded node restarts. This occurs because the upgrade changes have not yet been deployed from AMC.
Step 8
Deploy the upgrade changes from Step 5.
a.
Use AMC to deploy the property set changes to all nodes. There should be a global deployment request and a deployment request for each node.
b.
Restart the nodes.
The initial bundle sent to the nodes contains the fully upgraded configuration.
Note
Ensure that all AON Development Studio users uninstall all previous versions of ADS before they install ADS version 2.1.0.173.
Upgrading the AON Management Console to Version 2.1
To upgrade AMC, perform the following steps.
Step 1
Copy the file to the local machine and make it executable.
[root@localhost root]# chmod +x aon-amc_2.1.0.173_k9_lnx.upgrade.bin
Step 2
Execute the upgrade package and enter the information requested by the application.
[root@localhost root]# ./aon-amc_2.1.0.173_k9_lnx.upgrade.bin
Enter the directory to install the AMC to [/opt/amc]:/opt/amc
Directory "/opt/amc" exists.
Upgrade existing installation? [y|n]:y
Attempting to stop any AMC processes in /opt/amc
Stopping AMC...Waiting for services to complete...Killing process with id 14221
Stopping AMC Database...Done.
Configuring the ports that the AMC will listen on.
If you are installing more than one AMC, these values
must be unique to each installation.
Enter a port for https [7010]:
Enter a port for communication with AONS nodes [7011]:
Enter a port for server shutdown signals [7025]:
Enter a port for the database [2638]:
Enter AMC logging level (DEBUG|INFO|NOTICE|WARN|ERROR|FATAL) [INFO]:
Enter log file rollover threshold size (KB) [1024]:
Enter number of backup logs to keep [5]:
The AMC requires a keystore file and password
to communicate with the AONS node.
Enter the path to the keystore file [/root/amcKeystore.localhost.cisco.com.jks]:
You may optionally enter a keyname within the keystore.
Enter a keyname, otherwise enter none [none]:
Enter a password for this keystore:
about to load the root certs
Loading /opt/amc/admin/security/keystores/ciscocerts/cap-rtp-003.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-root.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca-dev.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-test-ca-2048.cer
Setting permissions for AMC installation...
Finalizing installation...
Would you like to run the AMC now? [y|n]:n
Note
Do not run AMC until you run the upgradeData script. See Step 5 for details.
Upgrading the AON Appliance
To upgrade the AON Appliance, perform the following steps:
Step 1
Use AMC to deactivate the node, then reboot the appliance. Wait for the bootloader prompt, then enter ***.
Please enter '***' to change boot configuration: ***
[tg3-5704]Ethernet addr: 00:14:5E:1C:20:60
Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit)
Link is up at 10 Mbps, half duplex.
Cisco Bootloader Version : 2.0.0.6
Step 2
Use the config command to update the IP information as necessary and enter the name of the helper image.
IP Address > 192.168.51.2
IP Netmask > 255.255.255.0
TFTP Server > 192.168.1.1
Gateway IP Address > 192.168.50.1
Default Helper-file > aon-apl-8340_2.1.0.173_k9_helper_lnx
Default Boot [none|disk] [disk] >
Step 3
Use the boot network command to boot the new helper image from the TFTP server.
Cisco Bootloader> boot network
Me: 192.168.51.2, Server: 192.168.1.1, Gateway: 192.168.50.1
Netbooting aon-apl-8340_2.1.0.173_k9_lnx.pkg (CTRL-C aborts)
Downloading aon-apl-8340_2.1.0.173_k9_lnx.pkg
Validating package signature ... done
WARNING:: Software installation will clear disk contents
prepfs.sh: olympus reiser /mnt clean
The number of cylinders for this disk is set to 4306.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): Partition number (1-4):
Command (m for help): Command action
p primary partition (1-4)
Partition number (1-4): First cylinder (1-4306, default 1): Using defa
Last cylinder or +size or +sizeM or +sizeK (1-4306, default 4306):
Command (m for help): The partition table has been altered!
Calling ioctl() to re-read partition table.
<-------------mkreiserfs, 2003------------->
mkreiserfs: Guessing about desired format..
mkreiserfs: Kernel 2.4.24 is running.
Initializing journal - 0%....20%....40%....60%....80%....100%
Starting payload download
Step 4
Once the helper loads, enter 1 to install software.
Welcome to Cisco Systems Helper Software
Please select from the following choices:
5 Configure IP parameters
6 Display status of RAID array
(Type '?' at any time for help)
Step 5
Enter the package name of the version 2.1 image and the URL for the server hosting the helper image. If the server is password-protected, enter the user and password required to gain access to the file. If no password is required, leave these fields blank.
Package name: aon-apl-8340_2.1.0.173_k9_lnx.pkg
Server url: http://192.168.1.1/aonimages/
Downloading aon-apl-8340_2.1.0.173_k9_lnx.pkg
Validating package signature ... done
WARNING:: Software installation will clear disk contents
prepfs.sh: olympus reiser /mnt clean
Note
The output during software installation and startup is extensive. It has been removed here for brevity.
Welcome to Cisco AON Engine
AON boot: hit RETURN to set boot flags: 0001
********** rc.aesop ****************
Setting timezone: timezone is America/Los_Angeles
Loading Tarari Drivers...
SUCCESS: Loaded Tarari Drivers
Loading Cisco WCCP module
wccp: v1.00 (20000327), debug=0
Destination Gateway Genmask Flags MSS Window irtt Iface
Reading Manifest...Processing: /sw/installed/manifest/gpl_infrastructure_manifes
Processing: /sw/installed/manifest/installer_manifest.sig
Processing: /sw/installed/manifest/oscore_manifest.sig
Processing: /sw/installed/manifest/global_manifest.sig
Processing: /sw/installed/manifest/aon_manifest.sig
Processing: /sw/installed/manifest/infrastructure_manifest.sig
Populating internal database .. complete.
INIT: Entering runlevel: 2
********** rc.post_install ****************
****************************************
****************************************
Changing owners and file permissions.
Change owners and permissions complete.
INIT: Switching to runlevel: 4
INIT: Sending processes the TERM signal
STARTED: dwnldr_startup.sh
Step 6
Enter your administrator password and go to configuration terminal mode, then create an AON configuration so the node can register with AMC.
Upgrading the AON-SM
In order to make the transition to the new architecture described in the "Upgrading AON 1.x Releases" section, the AON-SM requires a migration image that serves as a bridge from the old architecture to the new. To complete the upgrade, you will:
1.
Reload and enter the version 1.1 helper.
2.
Install the migration image. This will install a version 2.1 helper image into flash.
3.
Reload and enter the version 2.1 helper.
4.
Install the version 2.1 application image.
Note
The AON-SM contains two helper images, the primary helper image on cf:4 and the secondary helper image on cf:5. For the transition to version 2.1, we recommend you dedicate one of these helper image to be an AON 2.1 helper image and the other helper image to contain the AON 1.1 helper image. This will enable the ability to install either AON 1.1 images or AON 2.1 images as desired.
This procedure assumes that you will use the primary helper (cf:4) for version 2.1 and the secondary helper (cf:5) for version 1.1.
To upgrade the AON-SM to version 2.1, complete the following steps:
Step 1
Use AMC to deactivate the node, then set the boot device to cf:4 and reset the module:
•
CatOS:
Router> (enable) reset module_number cf:4
This command will reset module 5.
Unsaved configuration on module 5 will be lost
Do you want to continue (y/n) [n]? y
Module 5 shutdown in progress.
Do not remove module 5 until shutdown completes.
•
Cisco IOS:
Router# hw-module module module_number reset cf:4
Device BOOT variable for reset = <cf:4>
Warning: Device list is not verified.
Proceed with reload of module? [confirm]y
Step 2
When the module finishes reloading, establish a session to it.
•
CatOS:
Router# (enable) session module_number
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 127.0.0.31 ... Open
•
Cisco IOS:
Router# session slot module_number processor 1
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 127.0.0.31 ... Open
Step 3
Enter the IP configuration details in the version 1.1 helper.
Welcome To Cisco AON Installer
**********************************
* AON Installer IP Configuration *
**********************************
Please enter the IP address of your module: 10.94.0.20
Please enter the netmask of your module: 255.255.255.0
Please enter the default gateway for your module: 10.94.0.1
The following IP configuration is set:
Do you wish to use this configuration (y,n) [n] y
Step 4
Use the software install command to install the migration image from your HTTP or FTP server.
•
FTP:
AONinstaller#> software install package url
ftp://server_ip_address/path_to_images/aon-svc_1.x_to_2.1.0.173_k9_helper_lnx.pkg
user username password password
•
HTTP:
AONinstaller#> software install package url
http://server_ip_address/path_to_images/aon-svc_1.x_to_2.1.0.173_k9_helper_lnx.pkg
Note
The installer cannot resolve domain names. Be sure to use only an IP address when you enter a URL.
% Total % Received % Xferd Average Speed Time Curr.
Dload Upload Total Current Left Speed
100 27768 100 27768 0 0 27768 0 0:00:01 0:00:00 0:00:00 7712k
Retrieving aon-svc_2.1.0.173_k9_lnx_slim_migration.manifest from 10.47.0.2
Manifest Version retrieved is 1.0
Manifest Version matches package version
WARNING: This is an unrecoverable operation!
WARNING: This will completely replace the existing AON helper image.
Do you wish to continue (y,n) [n] y
Which Helper would you like to update primary or secondary (p,s) [p] p
Retrieving aon-svc_2.1.0.173_k9_lnx_slim_migration.prt1 from 10.47.0.2
% Total % Received % Xferd Average Speed Time Curr.
Dload Upload Total Current Left Speed
100 12.1M 100 12.1M 0 0 10.9M 0 0:00:01 0:00:01 0:00:00 10.9M
Validating security header...done
Extracting files from package...done
Installing software onto the system...
Wed Jan 25 00:56:01 UTC 2006
Step 5
Once the migration image finishes loading, exit the session and reset the module.
•
CatOS:
Console> (enable) reset module_number cf:4
This command will reset module 5.
Unsaved configuration on module 5 will be lost
Do you want to continue (y/n) [n]? y
Module 5 shutdown in progress.
Do not remove module 5 until shutdown completes.
•
Cisco IOS:
Router# hw-module module module_number reset cf:4
Device BOOT variable for reset = <cf:4>
Warning: Device list is not verified.
Proceed with reload of module? [confirm]y
Step 6
When the module resets, establish a session to the version 2.1 helper and enter 1 to install the version 2.1 software.
Welcome To Cisco AON Installer
Welcome to Cisco Systems Helper Software
Please select from the following choices:
5 Configure IP parameters
6 Temporarily disable login (for password recovery)
(Type '?' at any time for help)
Step 7
Enter the IP configuration details in the migration helper.
The following IP configuration is set:
Do you wish to use this configuration (y,n) [n] y
Step 8
Enter 1 to install software
Please select from the following choices:
5 Configure IP parameters
6 Temporarily disable login (for password recovery)
(Type '?' at any time for help)
Note
The output produced during software installation and startup is extensive. It has been removed here for brevity.
Step 9
Enter the package name for the version 2.1 application image and the HTTP or FTP URL for the server hosting the files. Include any username or password needed to access the server.
Package name: aon-svc_2.1.0.173_k9_lnx.pkg
Server url: http://10.47.0.2/aonimages/
Downloading aon-svc_2.1.0.173_k9_lnx.pkg
Validating package signature ... done
WARNING:: Software installation will clear disk contents
prepfs.sh: kplus reiser /mnt clean
Step 10
When the module reloads, reset the boot device to hdd:1.
•
CatOS:
Console> (enable) reset module_number hdd:1
This command will reset module 5.
Unsaved configuration on module 5 will be lost
Do you want to continue (y/n) [n]? y
Module 5 shutdown in progress.
Do not remove module 5 until shutdown completes.
•
Cisco IOS:
Router# hw-module module module_number reset hdd:1
Device BOOT variable for reset = <hdd:1>
Warning: Device list is not verified.
Proceed with reload of module? [confirm]
Step 11
When the module reloads, establish a session and use configuration terminal to create an AON configuration to enable the node to register with AMC.
Upgrading the AON-NM
To upgrade an AON-NM, perform the following steps:
Step 1
Use AMC to deactivate the node, then reboot the AON-NM. Wait for the bootloader prompt, then enter ***.
Please enter '***' to change boot configuration: ***
Cisco Bootloader Version : 2.0.0.4
Step 2
Use the config command to change IP configuration as necessary and to enter the name of the new helper image.
IP Address [192.168.169.92] >
IP Netmask [255.255.255.0] >
TFTP Server [192.168.1.1] >
Gateway IP Address [192.168.169.65] >
Default Helper-file [aon-nm_2.1.0.173_k9_helper_lnx] >
Ethernet Interface [internal] >
Default Boot [none|disk] [disk] >
Default Bootloader [primary|secondary] [primary] >
Updating flash with bootloader configuration
Step 3
Use the boot network command to load the helper from the TFTP server.
Cisco Bootloader> boot network
Me: 192.168.169.92, Server: 192.168.1.1, Gateway: 192.168.169.65
Netbooting aon-nm_2.1.0.173_k9_helper_lnx (CTRL-C aborts)
Dbg: Final image size: 11962750
in verifysignature_md5, MD5 hash generated now, str format:hexmd5:15ab0186f45a4
Verifying signature now...
verifysignature_md5, Orig MD5 hash generated during encryption:15ab0186f45a40b0
Image signature verified successfully
Note
The output produced during software installation and startup is extensive. It has been removed here for brevity.
Step 4
Once the helper loads, enter 1 to install software.
Welcome to Cisco Systems Helper Software
Please select from the following choices:
(Type '?' at any time for help)
Step 5
Enter the package name of the version 2.1 image and the URL for the server hosting the helper image. If the server is password-protected, enter the user and password required to gain access to the file. If no password is required, leave these fields blank.
Package name: aon-nm_2.1.0.173_k9_lnx.pkg
Server url: http://192.168.1.1/aonimages/
Downloading aon-nm_2.1.0.173_k9_lnx.pkg
Validating package signature ... done
Welcome to Cisco AON Engine
Mon Mar 6 11:48:28 UTC 2006
AON boot: hit RETURN to set boot flags: 0001
****************************************
****************************************
Changing owners and file permissions.
Change owners and permissions complete.
INIT: Switching to runlevel: 4
INIT: Sending processes the TERM signal
STARTED: dwnldr_startup.sh
Step 6
Enter your administrator password and go to configuration terminal mode, then create an AON configuration so the node can register with AMC.
Upgrading AON 2.1 Releases
Version 2.1.1 of Cisco Application-Oriented Networking provides you the ability to upgrade only AMC, while leaving some or all nodes at version 2.1. A mix of 2.1 and 2.1.1 nodes can interact with one another and with a version 2.1.1 AMC.
Additionally, AON 2.1.1 supports online upgrade of nodes. You can upgrade a node from within the AON application. It will download only the data needed to perform an incremental upgrade, then reboot, resulting in a much smaller period of downtime compared to previous AON releases.
Upgrading from AON 2.1 to AON 2.1.1
The steps that follow cover the tasks required for upgrading AMC and AON nodes from version 2.1 to version 2.1.1.
Caution 
Data loss may occur if you attempt to upgrade from a 1.
x release to AON version 2.1.1. You must first upgrade from 1.
x to version 2.1.
Note
This procedure refers to the default installation directory of /opt/amc. If your AMC is installed in a different directory, substitute that location when performing the steps below.
Upgrade Prerequisites
Before beginning, be sure to complete the following steps:
•
Download all of the files needed to upgrade your AON environment. If you are upgrading nodes, copy the appropriate files to an FTP server.
•
Develop a backup and recovery strategy for the devices in your environment. At minimum you should have a TFTP server to store node configurations and external storage to back up your AMC installation.
•
Verify that the Cisco IOS and CatOS versions for the switches and routers that host AON nodes, and upgrade any platforms as required.
Caution 
Data loss may occur if deployment requests are staged when you begin the upgrade. You must ensure that any existing deployment requests are in the open (unstaged) state before you shut down AMC for the upgrade.
This upgrade requires you to upgrade only AMC to version 2.1.1. You are not required to upgrade nodes unless you want the benefit of the software defects resolved since the previous release. Should you elect to upgrade only some nodes, your AON environment can operate with a mix of 2.1 and 2.1.1 nodes.
To complete the upgrade, perform the following steps:
Step 1
Ensure that all users of ADS have synchronized PEP and message type changes before you begin the upgrade. Deploy these changes to nodes if necessary.
Step 2
Use tar or a similar command to back up the directory in which AMC is installed.
c.
For example: tar cvzf amc1_1_backup.tar.gz /opt/amc
d.
Copy the backup file to an external device.
Step 3
On each node being upgraded, copy the system and start-up configurations to a TFTP server.
a.
Use copy running-config startup-config to save the current system configuration.
b.
Use copy running-config tftp to copy the configuration to a TFTP server.
Step 4
Use the following steps to upgrade AMC to version 2.1.1.53.
a.
Deactivate any active nodes.
b.
Log in to the server running AMC as root.
c.
Run aon-amc_2.1.1.53_k9_lnx.upgrade.bin. Near the end of the upgrade, it prompts you to start AMC. You must enter no here.
Note
Do not start AMC until instructed to do so in Step 6.
Step 5
Run the data upgrade script.
a.
Change to the /opt/amc/bin directory.
b.
Use ./upgradeData to run the script
Step 6
Use ./amcd start to launch AMC.
Note
If you are upgrading only AMC, you have completed this procedure. If you are also upgrading nodes, proceed to Step 7.
Step 7
Establish a session to the node you are upgrading, then use the software install command to load the upgrade package.
aon-sm-1> $software install upgrade url ftp://server-address/aon-svc_2.1.1.53_k9_lnx.pkg
username user password password$
Note
Only FTP is supported for online software upgrades.
WARNING:: This command will install the necessary software to
WARNING:: complete an upgrade.
Would you like to continue? [n] y
Downloading aon-svc_2.1.1.53_k9_lnx.pkg
Validating package signature ... done
Validating installed manifests .......complete.
Starting payload download
File : aon-svc-full_2.1.1.53_k9_lnx.prt1 Bytes : 177750810
Validating payloads match registered checksums...
- aon-svc-full_2.1.1.53_k9_lnx.prt1
..........................................................................................
................................................................................verified
Note
The output produced during software installation and startup is extensive. It has been removed here for brevity.
Step 8
After waiting a few moments, session to the AON node and verify that it has successfully started. Use the show version command to verify that the node is running new software version.
CPU Model: Pentium III (Coppermine)
Module Type: Catalyst 6500 Series AON Module (WS-SVC-AON-1-K9)
Module Serial: SAD092007UK
Global Software Version: 2.1.1.53
Step 9
Use AMC to activate the node, then go to Network Node > Manage > Show to confirm that AMC reflects the node's new software version.
Upgrading from AON 2.1 to AON 2.1.2
The steps that follow cover the tasks required for upgrading AMC and AON nodes from version 2.1 to version 2.1.2.
Caution 
Data loss may occur if you attempt to upgrade from a 1.
x release to AON version 2.1.2. You must first upgrade from 1.
x to version 2.1.
Note
This procedure refers to the default installation directory of /opt/amc. If your AMC is installed in a different directory, substitute that location when performing the steps below.
Upgrade Prerequisites
Before beginning, be sure to complete the following steps:
•
Download all of the files needed to upgrade your AON environment. If you are upgrading nodes, copy the appropriate files to an FTP server.
•
Develop a backup and recovery strategy for the devices in your environment. At minimum you should have a TFTP server to store node configurations and external storage to back up your AMC installation.
•
Verify that the Cisco IOS and CatOS versions for the switches and routers that host AON nodes, and upgrade any platforms as required.
Caution 
Data loss may occur if deployment requests are staged when you begin the upgrade. You must ensure that any existing deployment requests are in the open (unstaged) state before you shut down AMC for the upgrade.
This upgrade requires you to upgrade only AMC to version 2.1.2. You are not required to upgrade nodes unless you want the benefit of the software defects resolved since the previous release. Should you elect to upgrade only some nodes, your AON environment can operate with a mix of 2.1 and 2.1.2 nodes.
To complete the upgrade, perform the following steps:
Step 1
Ensure that all users of ADS have synchronized PEP and message type changes before you begin the upgrade. Deploy these changes to nodes if necessary.
Step 2
Use AMC to deactivate all active nodes.
Step 3
Use tar or a similar command to back up the directory in which AMC is installed.
c.
For example: tar cvzf amc1_1_backup.tar.gz /opt/amc
d.
Copy the backup file to an external device.
Step 4
On each node being upgraded, copy the system and start-up configurations to a TFTP server.
a.
Use copy running-config startup-config to save the current system configuration.
b.
Use copy running-config tftp to copy the configuration to a TFTP server.
Step 5
Use the following steps to upgrade AMC to version 2.1.2.29.
a.
Deactivate any active nodes.
b.
Log in to the server running AMC as root.
c.
Run aon-amc_2.1.2.29_k9_lnx.upgrade.bin. Near the end of the upgrade, it prompts you to start AMC. You must enter no here.
Note
Do not start AMC until instructed to do so in Step 7.
Step 6
Run the data upgrade script.
a.
Change to the /opt/amc/bin directory.
b.
Use ./upgradeData to run the script
Step 7
Use ./amcd start to launch AMC.
Note
If you are upgrading only AMC, you have completed this procedure. If you are also upgrading nodes, proceed to Step 8.
Step 8
Establish a session to the node you are upgrading, then use the software install command to load the upgrade package.
aon-sm-1> $software install upgrade url ftp://server-address/aon-svc_2.1.2.29_k9_lnx.pkg
username user password password$
Note
Only FTP is supported for online software upgrades.
WARNING:: This command will install the necessary software to
WARNING:: complete an upgrade.
Would you like to continue? [n] y
Downloading aon-svc_2.1.2.29_k9_lnx.pkg
Validating package signature ... done
Validating installed manifests .......complete.
Starting payload download
File : aon-svc-full_2.1.2.29_k9_lnx.prt1 Bytes : 177744975
Validating payloads match registered checksums...
- aon-svc-full_2.1.2.29_k9_lnx.prt1
..........................................................................................
................................................................................verified
Calculating delta.... complete.
Retrieving calculated file change sets:
- Installed file sets...complete.
- Target file change sets...complete.
Comparing changed source and target files...complete.
Calculating upgrade work order ... complete.
Creating uninstall change sets:
complete. No added files found.
- logging added components ... complete. No removed files found.
Clearing previous downgrade files ... complete.
Uninstall change set processing complete.
Writing upgrade work order to disk ... complete.
Disabling disk spindown on /dev/hdc
setting standby to 0 (off)
SHUTDOWN: cli_state.sh shutdown Success
SHUTDOWN: AONSShutdown Success
SHUTDOWN: procMgr -p ntp stop Success
SHUTDOWN: procMgr -p stunnel_client stop Success
SHUTDOWN: procMgr -p stunnel_server stop Success
install-files.sh /dwnld/.work_order
Remove ///sw/installed/manifest/global_manifest.sig
add_file /dwnld/pkgdata/aon-svc_2.1.2.29_k9_lnx.pkg 1 /
sw/installed/manifest/global_manifest.sig none
Remove //dwnld/pkgdata/aon-svc_2.1.2.29_k9_lnx.pkg
Remove //dwnld/pkgdata/aon-svc-full_2.1.2.29_k9_lnx.prt1
The AON node reboots and returns you to the command line of the host router or switch.
Step 9
After waiting a few moments, session to the AON node and verify that it has successfully started. Use the show version command to verify that the node is running new software version.
CPU Model: Pentium III (Coppermine)
Module Type: Catalyst 6500 Series AON Module (WS-SVC-AON-1-K9)
Module Serial: SAD092007UK
Global Software Version: 2.1.2.29
Step 10
Use AMC to activate the node, then go to Network Node > Manage > Show to confirm that AMC reflects the node's new software version.
Upgrading from AON 2.1.1 to AON 2.1.2
To upgrade from AON 2.1.1 to AON 2.1.2 run the AON upgrade installer— aon-amc_2.1.2.29_k9_lnx.upgrade.bin—and upgrade the firmware for Cisco 8300 AON Appliance series.
Upgrading Firmware on the AON Appliance
If you are upgrading software on an existing Cisco 8300 AON Appliance, the firmware upgrade must be completed before installing AON 2.1.2 or later software images.
Note
The Cisco Application-Oriented Networking version 2.1.2 images already contain the updated device drivers needed for the new firmware.
Note
Once you upgrade to AON version 2.1.2, you cannot downgrade to an earlier AON software version. This new firmware set works on the older version of Cisco 8300 AON Appliance hardware.
Warning
Once you start the upgrade process, do not remove the CD from the system until you complete Step 23.
Warning
Do not remove power or reboot the system while one of the updates are running. Removal of power in the middle of a firmware update can damage components.
For more detailed instructions on the individual tasks that comprise this upgrade, see the following sections in this document:
•
Upgrade Prerequisites
•
Upgrading Firmware and BIOS
Upgrade Prerequisites
•
You must be physically present wherever the hardware is installed to manually insert the CD containing the software.
•
Access the Cisco 8300 AON Appliance hardware through a Remote Console Terminal or directly via keyboard and monitor or a direct serial cable connection. You can use a good telnet client (CRT, secure CRT, HyperTerminal) to connect to the Appliance hardware.
Note
Do not use an SSH client because it does not work correctly.
•
All the firmware upgrades must be done with a device that is physically connected to the hardware and contains all the necessary software. We suggest that you burn the firmware upgrade software file onto a single CD after downloading the file from Cisco.com. The file apl-aon-8342-biosfwupdate.iso contains all of the necessary firmware upgrades.
Upgrading Firmware and BIOS
Step 1
Use AMC to deactivate the node, then insert the CD into the CD drive.
Warning
Do not eject the CD until you have completed the entire procedure.
Step 2
From the CLI, properly restart your machine. The system automatically recognizes the CD and boots into DOS, and displays boot information as follows:
ISOLINUX 3.11 2005-09-02 Copyright (C) 1994-2--5 H. Peter Anvin
Cisco AON 8300 Series Appliance BIOS and Firmware Update for AON 2.1.2, 2.2
Defaults to "disk" if press <Enter> or after 5 minute timeout
disk) BOOT to Cisco Bootloader or hard disk drive
bios) INSTALL interactive System BIOS 1.09, ZUEC54BUS 2006/06/15
diag) INSTALL unattended Diagnostic 1.05, ZUYT27A
bmc) INSTALL BMC firmware 2.07, Z2BT05E 2006/05/10, IPMI 2.0
cpld) INSTALL CPLD firmware 1.06, HEUD18A
raidbios) INSTALL ServeRAID 8i BIOS 5.1-0 Build 9234 2006/6/14
getver) LOAD SPint v3.02 to get version of BIOS, BMC; get ringdumps
Type choice at boot: prompt
Step 3
At the prompt, type BMC, then press Enter.
The following information displays during the BMC upgrade:
Decompressing BMC firmware
reading fullfw.cmt...wrote 15357 SRECa to fullfw.mot
BMC's IPMI level migration starting (step 1 of 4).
Config Loader Version 1.0, OSA Technologies, INC. (c) 2005
Upload configurations from BMC
Flash Loader v1.29.0.45, OSA Technologies, Inc. (c)2005
Writing to Address: 0x0007F280.......OK
BMC Firmware and SDRs updated successfully!!!
BMC's IPMI level migration still in progress (step 2 of 4).
BMC's IPMI level migration still in progress (step 3 of 4).
BMC's IPMI level migration still in progress (step 4 of 4).
Config Loader Version 1.0 . OSA Technologies, Inc. (c)2005
Download configurations to BMC
Any user passwords on the BMC will need to be redefined after
BMC's IPMI level migration completed.
Updating BMC's Boot Block.
Please remove the disk from the drive and restart the system.
Note
The BMC upgrade takes about 3 minutes.
Step 4
At the prompt, type Reboot, then press Enter.
Step 5
After the machine reboots, type cpld and press Enter. Then you follow the following:
==============================================================
Spint/x460/x260 CPLD UPDATE DISKETTE
==============================================================
Current time is xxxxx, 2006 at 16:36:51
Current level of CPLD code - 1.03
Code level after flash - 1.06
**************DO NOT POWER OFF THE SYSTEM OR REMOVE AC POWER DURING PLD FLASH
Please enter choice and then press enter
Step 6
Enter A and press Enter.
This starts the CPLD upgrade. When it has completed, that screen displays the following:
You have successfully flashed the CPLDs for this system.
*****************REMOVE AC POWER CORD AND REBOOT SYSTEM*******************
*****************REMOVE AC POWER CORD AND REBOOT SYSTEM*******************
*****************REMOVE AC POWER CORD AND REBOOT SYSTEM*******************
Step 7
Type Reboot and then press Enter.
Step 8
After the machine reboots, type raidbios and press Enter.
Note
If asked for a second diskette, just ignore the request and press Enter.
Step 9
When asked for a confirmation to upgrade to RAID BIOS, type Y.
The screen displays the following:
Adaptec Flash Utility V5.1-0 B9234
(c) Adaptec Inc. 1999-2006. All Rights Reserved.
Updating Controller 0 (IBM ServRAID 8i)
Please insert disk labeled "IBM ServRAID 8i Firmware Disk 1"
and press ENTER or press ESC to cancel
Reading flash image file (Build 9234) ...
Please insert disk labeled "IBM ServRAID 8i Firmware Disk 2"
amd press ENTER or press ESC to cancel
Reading flash image file (Build 9234) ...
AFU is about to update firmware on controller(s) IBM ServRAID 8i
*** PLEASE DO NOT REBOOT THE SYTEM DURING THE UPDATE ***
This might take a few minutes.
Writing IBM ServRAID 8i flash image to controller 0...OK. Verifying...OK.
Please restart the computer to allow firmware changes to take effect.
Step 10
Type Reboot and then press Enter.
Step 11
After the machine reboots, type BIOS and press Enter.
The update utility displays the following:
3 - Backup Current POST/BIOS
4 - Restore POST/BIOS from the backup version on a drive
5 - Restore POST/BIOS from the ROM backup version
Step 12
Select Option 1 and press Enter.
Step 13
When prompted for the serial number, type Y for yes and enter the serail number found on the faceplate of the Appliance.
Step 14
When prompted for the machine type, type Y for yes and enter 8863PDH.
Step 15
When prompted for a value for the asset tag, type N for no.
Step 16
When prompted for saving the current Flash code to disk, type N for no.
Step 17
When prompted for a confirmation of BIOS upgrade, select option 1 again.
After the BIOS upgrade completes, the machine should automatically reboot.
Step 18
After the machine reboots, type diag and press Enter.
The update utility displays the following:
The system Diagnostic is being updated.
This may take upto 5 minutes.
Do not power off or restart the system during this procedure.
When the System Diagnostic upgrade is complete, the screen displays the following:
Thanks for using the POST/BIOS Utility
Step 19
Type reboot and press Enter to restart the system.
Step 20
After the machine reboots, type getver at the command prompt and press Enter.
Step 21
Type x366 and press Enter.
Note
The information scrolls by fast.
Step 22
You can use cntrl-s to pause and review the output. Following is a typical example:
This nodes BMC address = 0CA8
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
³ Spint Dump Tool Ver 3.02 ³
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Current time is Thursday Jul 6, 2006 at 18:58:42
Current BMC Time is: 7/6/2006 19:1:0
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
POST/BIOS Build ID = ZUEC54BUS
CPU Card CPLD Revision = 0D
PCI Card CPLD Revision = 19
I/O Card CPLD Revision = 12
Step 23
Remove the CD from the DVD-CD drive.
Step 24
Type reboot and press Enter.
Step 25
After the machine reboots, the screen displays the following:
Symmetric Multiprocessing System
04096 MB Memory: Installed
4 Processor Packages Installed
Press F12 to select boot device
Enter F1.
Step 26
Ignore the interim screen that displays "Configuration Error" and press Enter.
Step 27
In the following screen displaying "Configuration/Setup Utility," select Load Default Settings.
Step 28
Press Enter.
Step 29
Next select Exit Setup and confirm to save changes.
The system reboots and returns you to the Cisco Boot Loader.
Upgrading to AON 2.4
You can upgrade to AON 2.4 from any of the following releases:
•
AON version 2.1.0
•
AON version 2.1.1
•
AON version 2.1.2
•
AON version 2.1.5
•
AON version 2.2
Unlike earlier releases, the AMC installer upgrades both the code and the data from the previous AMC installation. There is no need to run a separate process to upgrade PEPs, message types, and attribute domains.
Note
Due to architectural improvements, you must upgrade all nodes to version 2.4. A 2.4 AMC cannot manage nodes running previous software releases.
Note
If you are upgrading an AON Appliance from version 2.1.1 or earlier, you must first upgrade firmware and BIOS on the appliance. See the "Upgrading Firmware on the AON Appliance" section.
Projects
AON 2.4 introduces the concept of projects to partition the work performed by different development teams. A project contains all of the resources, created by a team. Resources created using previous AON releases are distributed among two projects during the upgrade. All PEP and message type resources are placed in a user project, while all other resources (property sets, extensions, etc.) are placed in the predefined "System" project.
Prefixes are used to identify resources created by individual projects. Each project has a unique prefix which is prepended to the name of each resource belonging to the project. By convention, the predefined "System" project has no prefix. During the installation, you will be asked to specify a name and prefix for the user project, and the prefix will be added to the names of all PEPs and message types. After the upgrade, you can find these resources in the project you specified
Note
Due to a defect in AON Release 2.4, you cannot use a number as the first character of a prefix. Use only a letter.
For more details about projects, see the Enterprise Lifecycle Management chapter of the AON Administration Guide
Users
AON 2.4 includes two new user roles, application developer and system administrator. The system administrator is a super user. Users with the following roles in previous AON releases now have this role:
•
network administrator
•
security administrator
•
application administrator
For more information on user roles, see the AMC Administration chapter of the AON Administration Guide.
Upgrading the AON Management Console to Version 2.4
Note
This procedure refers to the default installation directory of /opt/amc. If your AMC is installed in a different directory, substitute that location when performing the steps below.
Upgrade Prerequisites
Before beginning, be sure to complete the following steps:
•
Download all of the files needed to upgrade your AON environment.
•
Develop a backup and recovery strategy for the devices in your environment. At minimum you should have a TFTP server to store node configurations. The AMC installer will give you the opportunity to backup your database before proceeding with the upgrade. If you elect to perform this backup, you must specify a location for which AMC has write permissions.
•
Ensure that there are no open deployment requests (DRs) within AMC. The installer exits if it finds open DRs.
•
Verify that the Cisco IOS and CatOS versions for the switches and routers that host AON nodes, and upgrade any platforms as required. See the appropriate Release Notes for Cisco Application-Oriented Networking for requirements that apply to your AON release.
To upgrade AMC, perform the following steps.
Step 1
Ensure that ADS users have synchronized PEPs, message types, and other data with AMC.
Step 2
Use AMC to deactivate any active nodes.
Step 3
Copy the AMC upgrade file to the local machine and make it executable.
[root@localhost root]# chmod +x aon-amc_2.4.0.58_k9_lnx.upgrade.bin
Step 4
Execute the upgrade package and enter the information requested by the application.
[root@cisco opt]# ./aon-amc_2.4.0.58_k9_lnx.upgrade.bin
Enter the directory to install the AMC to [/opt/amc]:
Directory "/opt/amc" exists.
Upgrade existing installation? [y|n]:y
Attempting to stop any AMC processes in /opt/amc
Stopping AMC...Waiting for services to complete...Done.
Stopping AMC Database...Done.
Starting AMC Database...Done.
sleeping for 15 seconds ...
Getting AMC Version as:2.1.2.29
Checking the database for active Global Deployment Requests...
Checking the database for active Node Deployment Requests...
Done checking database for active Global and Node Deployment Requests
Stopping AMC Database...Done.
Would you like to back up the AMC directory? [y|n]:y
The estimated backup file size is: 252.0M
Please specify the backup location: [/tmp]:
Backing up existing AMC directory - /opt/amc - Please wait !!!
Configuring the ports that the AMC will listen on.
If you are installing more than one AMC, these values
must be unique to each installation.
Enter a port for https [7010]:
Enter a port for communication with AONS nodes [7011]:
Enter a port for server shutdown signals [7025]:
Enter a port for the database [2638]:
Enter AMC logging level (DEBUG|INFO|NOTICE|WARN|ERROR|FATAL) [INFO]:
Enter log file rollover threshold size (KB) [1024]:
Enter number of backup logs to keep [5]:
The AMC requires a keystore file and password
to communicate with the AONS node.
Enter the path to the keystore file [/root/amcKeystore.cisco.com.jks]:
You may optionally enter a keyname within the keystore.
Enter a keyname, otherwise enter none [none]:
Enter a password for this keystore:
about to load the root certs
Loading /opt/amc/admin/security/keystores/ciscocerts/cap-rtp-003.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-root.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca-dev.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-test-ca-2048.cer
Setting permissions for AMC installation...
Finalizing installation...
Enter a Project Name (up to 256 characters) [USER_PROJECT]:Resources_2_1
Enter a Project Prefix (up to 50 characters) [PREFIX]:Res_2_1
Starting AMC Database...Done.
sleeping for 15 seconds ...
Database Upgrade Begins...
Output of the upgrade process can be found in /opt/amc/log/upgradeData.log
Stopping AMC Database...Done.
The backup file can be located at /tmp/20061115162508.AMCbackup.tar.gz
The upgrade process may have generated Global and Node DRs, please log onto the AMC and
deploy all staged DRs to complete the AMC upgrade process.
Would you like to run the AMC now? [y|n]:y
Starting AMC Database...Done.
AMC logfile is /opt/amc/log/amc.log
To uninstall, run '/opt/amc/bin/amcSetup uninstall'.
Step 5
Ensure that ADS users uninstall any previous versions of the application, then they must install version 2.4. Previous versions of ADS will not connect to AMC version 2.4.
Upgrading Nodes to Version 2.4
Due to architectural improvements, you must upgrade all nodes to version 2.4. AMC version 2.4 cannot manage nodes running releases before AON 2.4.
To upgrade a node, perform the following steps:
Step 1
Use AMC to deactivate the node. Establish a session to each node and use the software install command to load the upgrade package.
aon-sm-1> $software install clean url ftp://server-address/aon-svc_2.4.0.58_k9_lnx.pkg
username user password password$
Note
Only FTP is supported for online software upgrades.
WARNING:: This command will install the necessary software to
WARNING:: complete an upgrade.
Would you like to continue? [n] y
Downloading aon-svc_2.4.0.58_k9_lnx.pkg
Validating package signature ... done
Validating installed manifests .......complete.
Starting payload download
File : aon-svc-full_2.4.0.58_k9_lnx.prt1 Bytes : 177750810
Validating payloads match registered checksums...
- aon-svc-full_2.4.0.xx_k9_lnx.prt1
..........................................................................................
................................................................................verified
Note
The output generated during an upgrade is extensive. It has been removed for brevity.
After completing the upgrade, the AON node reboots.
Step 2
After waiting a few moments, session to the AON node and verify that it has successfully started. Use the show version command to verify that the node is running new software version.
CPU Model: Pentium III (Coppermine)
Module Type: Catalyst 6500 Series AON Module (WS-SVC-AON-1-K9)
Module Serial: SAD092007UK
Global Software Version: 2.4.0.58
Step 3
Using AMC, wait for the node to register, then go to Network Node > Manage > Show to confirm that AMC reflects the node's new software version.
Step 4
Use AMC to activate the node. AMC will then deploy upgraded configuration data to the node.
Upgrading to AON 3.0
You can upgrade to AON 3.0 from any of the following releases:
•
AON version 2.1.0
•
AON version 2.1.1
•
AON version 2.1.2
•
AON version 2.1.5
•
AON version 2.2
•
AON version 2.4
•
AON version 2.4.2
Unlike earlier releases, the AMC installer upgrades both the code and the data from the previous AMC installation. There is no need to run a separate process to upgrade PEPs, message types, and attribute domains.
Note
Due to architectural improvements, you must upgrade all nodes to version 3.0. A 3.0 AMC cannot manage nodes running previous software releases.
Note
If you are upgrading an AON Appliance from version 2.1.1 or earlier, you must first upgrade firmware and BIOS on the appliance. See the "Upgrading Firmware on the AON Appliance" section.
Projects
AON 3.0 allows you to set up of projects to partition the work performed by different development teams. A project contains all of the resources, created by a team. Resources created using previous AON releases are distributed among two projects during the upgrade. All PEP and message type resources are placed in a user project, while all other resources (property sets, extensions, etc.) are placed in the predefined "System" project.
Prefixes are used to identify resources created by individual projects. Each project has a unique prefix which is prepended to the name of each resource belonging to the project. By convention, the predefined "System" project has no prefix. During the installation, you will be asked to specify a name and prefix for the user project, and the prefix will be added to the names of all PEPs and message types. After the upgrade, you can find these resources in the project you specified
For more details about projects, see the Enterprise Lifecycle Management chapter of the AON Administration Guide, 3.0.
Users
AON 3.0 includes two user roles, application developer and system administrator. The system administrator is a super user. Users with the following roles in previous AON releases now have this role:
•
network administrator
•
security administrator
•
application administrator
For more information on user roles, see the AMC Administration chapter of the AON Administration Guide.
Upgrading the AON Management Console to Version 3.0
Note
This procedure refers to the default installation directory of /opt/amc. If your AMC is installed in a different directory, substitute that location when performing the steps below.
Upgrade Prerequisites
Before beginning, be sure to complete the following steps:
•
Download all of the files needed to upgrade your AON environment.
•
Develop a backup and recovery strategy for the devices in your environment. At minimum you should have a TFTP server to store node configurations. The AMC installer will give you the opportunity to backup your database before proceeding with the upgrade. If you elect to perform this backup, you must specify a location for which AMC has write permissions.
•
Ensure that there are no open deployment requests (DRs) within AMC. The installer exits if it finds open DRs.
•
Verify that the Cisco IOS and CatOS versions for the switches and routers that host AON nodes, and upgrade any platforms as required. See the appropriate Release Notes for Cisco Application-Oriented Networking for requirements that apply to your AON release.
To upgrade AMC, perform the following steps.
Step 1
Ensure that ADS users have synchronized PEPs, message types, and other data with AMC.
Step 2
Use AMC to deactivate any active nodes.
Step 3
Copy the AMC upgrade file to the local machine and make it executable.
[root@localhost root]# chmod +x aon-amc_3.0.0.x_k9_lnx.upgrade.bin
Note
The complete release number in the upgrade package name has the format 3.0.0.x, where x represents the build number.
Step 4
Execute the upgrade package and enter the information requested by the application.
Note
The complete release number in the upgrade package name has the format 3.0.0.x, where x represents the build number.
Note
The logging level that you specify when the prompt Enter AMC logging level for new functional modules (TRACE|DEBUG|INFO|NOTICE|WARN|ERROR|FATAL) [INFO]: appears is applied only to the new modules that are installed, not to modules installed with previous releases.
[root@cisco opt]# ./aon-amc_3.0.0.x_k9_lnx.upgrade.bin
Enter the directory to install the AMC to [/opt/amc]:
Directory "/opt/amc" exists.
Upgrade existing installation? [y|n]:y
Attempting to stop any AMC processes in /opt/amc
Stopping AMC...Waiting for services to complete...Done.
Stopping AMC Database...Done.
Starting AMC Database...Done.
sleeping for 15 seconds ...
Getting AMC Version as:3.0.0.x
Checking the database for active Global Deployment Requests...
Checking the database for active Node Deployment Requests...
Done checking database for active Global and Node Deployment Requests
Stopping AMC Database...Done.
Would you like to back up the AMC directory? [y|n]:y
The estimated backup file size is: 252.0M
Please specify the backup location: [/tmp]:
Backing up existing AMC directory - /opt/amc - Please wait !!!
Configuring the ports that the AMC will listen on.
If you are installing more than one AMC, these values
must be unique to each installation.
Enter a port for https [7010]:
Enter a port for communication with AONS nodes [7011]:
Enter a port for server shutdown signals [7025]:
Enter a port for the database [2638]:
Enter AMC logging level for new functional modules
(TRACE|DEBUG|INFO|NOTICE|WARN|ERROR|FATAL) [INFO]:
Enter log file rollover threshold size (KB) [1024]:
Enter number of backup logs to keep [5]:
The AMC requires a keystore file and password
to communicate with the AONS node.
Enter the path to the keystore file [/root/amcKeystore.cisco.com.jks]:
You may optionally enter a keyname within the keystore.
Enter a keyname, otherwise enter none [none]:
Enter a password for this keystore:
about to load the root certs
Loading /opt/amc/admin/security/keystores/ciscocerts/cap-rtp-003.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-root.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-manu-ca-dev.cer
Loading /opt/amc/admin/security/keystores/ciscocerts/cisco-test-ca-2048.cer
Setting permissions for AMC installation...
Finalizing installation...
Enter a Project Name (up to 256 characters) [USER_PROJECT]:Resources_2_1
Enter a Project Prefix (up to 50 characters) [PREFIX]:Res_2_1
Starting AMC Database...Done.
sleeping for 15 seconds ...
Database Upgrade Begins...
Output of the upgrade process can be found in /opt/amc/log/upgradeData.log
Stopping AMC Database...Done.
The backup file can be located at /tmp/20061115162508.AMCbackup.tar.gz
The upgrade process may have generated Global and Node DRs, please log onto the AMC and
deploy all staged DRs to complete the AMC upgrade process.
Would you like to run the AMC now? [y|n]:y
Starting AMC Database...Done.
AMC logfile is /opt/amc/log/amc.log
To uninstall, run '/opt/amc/bin/amcSetup uninstall'.
Step 5
Ensure that ADS users uninstall any previous versions of the application, then they must install version 3.0. Previous versions of ADS will not connect to AMC version 3.0.
Upgrading Nodes to Version 3.0
Due to architectural improvements, you must upgrade all nodes running previous AON versions to version 3.0. AMC version 3.0 cannot manage nodes running releases before AON 3.0.
To upgrade a node, perform the following steps:
Step 1
Use AMC to deactivate the node. Establish a session to each node and use the software install command to load the upgrade package.
aon-sm-1> $software install clean url ftp://server-address/aon-svc_3.0.0.x_k9_lnx.pkg
username user password password$
Note
Only FTP is supported for online software upgrades.
Note
The complete release number in the package name has the format 3.0.0.x, where x represents the build number.
WARNING:: This command will install the necessary software to
WARNING:: complete an upgrade.
Would you like to continue? [n] y
Downloading aon-svc_3.0.0.x_k9_lnx.pkg
Validating package signature ... done
Validating installed manifests .......complete.
Starting payload download
File : aon-svc-full_3.0.0.x_k9_lnx.prt1 Bytes : 177750810
Validating payloads match registered checksums...
- aon-svc-full_3.0.0.x_k9_lnx.prt1
..........................................................................................
................................................................................verified
Note
The output generated during an upgrade is extensive. It has been removed for brevity.
After completing the upgrade, the AON node reboots.
Step 2
After waiting a few moments, session to the AON node and verify that it has successfully started. Use the show version command to verify that the node is running new software version.
CPU Model: Pentium III (Coppermine)
Module Type: Catalyst 6500 Series AON Module (WS-SVC-AON-1-K9)
Module Serial: SAD092007UK
Global Software Version: 3.0.0.x
Note
The complete release number has the format 3.0.0.x, where x represents the build number.
Step 3
Using AMC, wait for the node to register, then go to Network Node > Manage > Show to confirm that AMC reflects the node's new software version.
Step 4
Use AMC to activate the node. AMC will then deploy upgraded configuration data to the node.