AXP 1.6 Developer Guide
Installing and Upgrading Software
Downloads: This chapterpdf (PDF - 128.0KB) The complete bookPDF (PDF - 9.62MB) | Feedback

Installing and Upgrading Software

Table Of Contents

Installing and Upgrading Software

Installing and Upgrading Cisco AXP

Installing a Cisco AXP Application

Installing Host OS and Application Separately

Installing Host OS and Application in a Bundle

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.6.x

Upgrade of Host OS and Application

Single Upgrade of a Bundle

Downgrading from Cisco AXP 1.5 or Higher to Cisco AXP 1.1.x

Clean Installing a Cisco AXP 1.1.x Application

Upgrading Scenarios

Pre-upgrade Scripts

Install Script Messages

Installing RPM Packages

Verifying an Application is Installed

Installing Software using a Helper Image

Additional References


Installing and Upgrading Software


The following sections explain installing and upgrading the Cisco AXP host OS and application packages:

Installing and Upgrading Cisco AXP

Upgrading Scenarios

Pre-upgrade Scripts

Install Script Messages

Installing RPM Packages

Verifying an Application is Installed

Installing Software using a Helper Image

Additional References

Installing and Upgrading Cisco AXP

The following sections show the processes for installing and upgrading applications, and the Cisco AXP host OS:

Installing a Cisco AXP Application

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.6.x

Downgrading from Cisco AXP 1.5 or Higher to Cisco AXP 1.1.x

Clean Installing a Cisco AXP 1.1.x Application

Upgrading Scenarios.

Installing a Cisco AXP Application

Use one of the following two methods to clean install the AXP 1.5 or higher host OS and your application:

Installing Host OS and Application Separately

Installing Host OS and Application in a Bundle

Installing Host OS and Application Separately

To separately install the host OS and application, perform the following steps:


Note The application must be packaged using the SDK for Cisco AXP 1.5.3 or higher.



Step 1 Install the host OS:

(Make sure that axp-k9.xxx.1.6.x.prt1 and axp-installer-k9.xxx.1.6.x.prt1 are in the same ftp directory as axp-k9.xxx.1.6.x.pkg.)

software install clean url ftp://<ftpserver>/axp-k9.xxx.1.6.x.pkg

Wait for the system to reboot.

Step 2 Install the application package:

software install package url ftp://<ftpserver>/app.1.0.pkg

Wait for the system to reboot.


Installing Host OS and Application in a Bundle

To install a single bundle containing the host OS and the application, perform the following step.


Note The prerequisite is to create a bundle.pkg consisting of your application and the host OS of Cisco AXP 1.5.3 or higher. Refer to the "Bundling Tool" section on page 151.



Step 1 software install clean url ftp://<ftpserver>/bundle.pkg

Wait for the system to reboot.


For further information on upgrading scenarios, see the "Upgrading Scenarios" section.

Upgrading from Cisco AXP 1.1.x to Cisco AXP 1.6.x

You can use one of the following two methods to upgrade from Cisco AXP 1.1.x to Cisco AXP 1.6.x.


Note The application must be packaged using the SDK for Cisco AXP 1.5.3 or higher.


Upgrade of Host OS and Application

Single Upgrade of a Bundle

Upgrade of Host OS and Application

To upgrade from Cisco AXP 1.1.x to Cisco AXP 1.6.x, separately upgrading the OS and application, perform the following steps:


Step 1 Upgrade the host OS:

(Make sure that axp-k9.xxx.1.6.x.prt1 and axp-installer-k9.xxx.1.6.x.prt1 are also in the same ftp directory as axp-k9.xxx.1.6.x.pkg.)

software install upgrade url ftp://<ftpserver>/axp-k9.xxx.1.6.x.pkg

Wait for the system to reboot.

Step 2 Upgrade the application:

software install package url ftp://<ftpserver>/application.pkg

Wait for system to reboot.

If the older version of the application exists on the system: the application is upgraded to a newer version.

If the older version of the application does not exist on the system: the application is newly installed.


Single Upgrade of a Bundle

To upgrade using a single bundle consisting of the host OS and application, perform the following step.


Note The prerequisite is to create a bundle.pkg consisting of your application and the Cisco AXP 1.6.x host OS (axp-k9.xxx.1.6.x.pkg). Refer to the "Bundling Tool" section on page 151.



Note This procedure assumes that you are upgrading from (Cisco AXP 1.1.x + application y)
to (Cisco AXP 1.6.x+ application y).



Step 1 software install upgrade url ftp://<ftpserver>/bundle.pkg

Wait for the system to reboot.


Downgrading from Cisco AXP 1.5 or Higher to Cisco AXP 1.1.x

Downgrading from Cisco AXP 1.5 or higher host OS to Cisco AXP 1.1.x—including your application—is not allowed. To downgrade, you need to do a clean install of the Cisco AXP 1.1.x host OS.

Clean Installing a Cisco AXP 1.1.x Application

To clean install the Cisco AXP 1.1.x host OS and a 1.1.x application (an application created using the 1.1.x Cisco AXP SDK), perform the following steps:


Step 1 (Make sure that axp-k9.xxx.1.1.x.prt1 is also in the same ftp directory as axp-k9.xxx.1.1.x.pkg)

Clean install AXP 1.1.x host OS first. (Install the application in step 2.)

software install clean url ftp://<ftp server>/axp-k9.xxx.1.1.x.pkg

Wait for the system to reboot.

Step 2 software install add url ftp://<ftpserver>/application.pkg

Wait for the system to reboot.


Note The single upgrade of a bundle containing Cisco AXP 1.1.x host OS that includes your application is not supported in Cisco AXP 1.5 or higher.



Upgrading Scenarios

The following table summarizes allowed upgrade and downgrade scenarios for Cisco AXP 1.6:

N=Not allowed; Y= Allowed.

Upgrade To:

From:
1.6 host OS
1.6 host OS +
add-on
1.6 host OS +
app
1.6 host OS + add-on + app
1.6 bundle (host OS + add-on)
1.6 bundle (host OS + app)
1.6 bundle (host OS + add-on + app)
1.6 host OS

Y

N

Y

Y

Y

Y

Y

1.6 host OS + add-on

N

N

N

N

N

N

N

1.6 host OS +
app

Y

N

Y

Y

Y

Y

Y

1.6 host OS +add-on +app

Y

N

Y

Y

Y

Y

Y


Pre-upgrade Scripts

Scripts for preupgrade or preupgrade-oldver need to be run by the installer in the appropriate virtual instance.

preupgrade scripts—are extracted from the payload that comes with the new package

preupgrade-oldver scripts—already exist on the disk, because they are derived from the older version of the subsystem that is being upgraded.

If the virtual instance is down and the user attempts to upgrade software, the installer fails. The installer runs preupgrade or preupgrade-oldver scripts in the virtual instance.

If the virtual instance is down and no preupgrade scripts are defined, the installer performs the upgrade, ignoring the down state of the virtual instance.

If the virtual instance is administratively down and preupgrade scripts are defined, the installer returns an error message that the application must be started using the no shutdown command.

Before running preupgrade scripts, it is recommended that you use the no shutdown command to disable the application. This helps ensure that the virtual instance is running and that the preupgrade hooks can run successfully during an upgrade.

If the application package defines preupgrade and preupgrade-oldver scripts, during upgrade of the package, the following decisions are made by the installer:

If the virtual instance is administratively up and in a healthy state => the installer performs the upgrade and runs the preupgrade scripts.

OR

If the virtual instance is administratively up and is an unhealthy state => an exit with a warning message occurs because preupgrade scripts cannot run in a unhealthy virtual instance.

If you cannot bring the virtual instance up to a healthy state and try to upgrade the package, including running preupgrade/preupgrade-oldver scripts, then the upgrade does not work. The workaround is to upgrade the package without running preupgrade/preupgrade-oldver scripts, by using install CLI commands with the ignore-scripts option.

Install Script Messages

During upgrading, the installer runs the two Cisco AXP install scripts: vm_pre_upgrade and vm_pre_upgrade_oldver in the appropriate virtual instance. The subsystem id for each of thesescripts is matched by the AXP CLI to the corresponding virtual instance and runs the script in the virtual instance.

During upgrading, if a pre upgrade script fails, the return code and pass/fail messages are passed by the AXP CLI to the installer. The installer aborts the upgrade and error messages are sent to the user using the console. The python-based installer has logging class methods that can be used to write error messages (or information//warning messages) to install.log.

Installing RPM Packages

RPM packages can be included with the add-on packages during packaging of the application.

For more information on installing RPM package files, refer to the "Packaging and Installing RPMs" section on page 216.

If you choose to install and/or uninstall external RPM's, you may run into some conflicts and dependency issues with the existing AXPOS. After this, the installation process may force an installation by using some of the RPM flags to ignore conflicts and dependencies.


Tip Here are some tips to resolve a forced installation:

Run a preinstallation test. Refer to the "Packaging and Installing RPMs using a Predefined Directory Path" section on page 216 for the preinstallation command.

If you skip the preinstallation test, and the installation is unsuccessful, check the installation logs for the installation process, including details in the logs for successful or unsuccessful RPM installation.


Verifying an Application is Installed

To verify your application is installed, enter the following commands.


Step 1 app-service ?

If your application is installed, the application appears in a list of applications.

Step 2 app-service <application name>

If your application is running, you enter the CLI of the guest OS shell.

Step 3 show processes

Your application appears in a list. For example, "helloworld".

Step 4 (Optional) show state

Your application appears in a list that shows the state of the application. For example a state of "online". The STATE displayed depends on your application having been written to return the health status.

Example:

	APPLICATION			STATE		 	HEALTH
	helloworld			online			ALIVE

Installing Software using a Helper Image

You can use a rescue helper image file, such as axp-helper-k9.<AIM | NME>.<release-number>, for software installation of the Cisco AXP host OS files onto a service module. Installing software using the helper image overwrites all previously existing data on the service module. To install software using a helper image, refer to "Software Recovery Using a Helper Image" in Cisco AXP 1.6 User Guide.

Additional References

Appendix 1: "Configuring the Bootloader" in Cisco AXP User Guide.