In-Service Software Upgrade - Alcatel-Lucent OmniSwitch AOS Release 6 Manual

Managing CMM Directory Content

In-Service Software Upgrade

The In-Service Software Upgrade (ISSU) feature is used to patch the CMM images (NI patches are not
supported) running on an OmniSwitch 9000E with minimal disruption to data traffic.The CMM images
can be patched only on fully synchronized, certified, and redundant systems currently running an ISSU
capable build.
Note. Switches running an 'R##' build, such as 6.4.1.123.R01 do not support ISSU patches. The switch
must first be upgraded to an 'S##' build such as 6.4.1.123.S01. Contact Service & Support for the latest
ISSU capable release.
Note. ISSU patches are only supported within the same 'S##' branch. For example, if a switch is running
6.4.1.123.S01 then only 6.4.1.###.S01 images can be used to perform an ISSU patch. If a switch is
running 6.4.1.234.S02 then only 6.4.1.###.S02 images can be used to perform an ISSU patch.
Note. The images which are ISSU capable are Jbase.img, Jsecu.img, Jadvrout.img and Jos.img. These
images are used to perform a patch to the CMM only, any NI related issues cannot be addressed with an
ISSU patch.
Note. A minimum of 25 MB flash space must be present in the switch to accommodate the image files that
are used to patch existing image files. This feature is only supported on the OmniSwitch 9000E.
Using the ISSU feature requires the admin user to first create an ISSU directory in the flash memory of the
primary CMM (flash/issu). This directory is where the 'S##' image files are downloaded to the switch.
These are the image files that are used to patch the existing 'S##' files on the switch.
1
Ensure that the switch is fully synchronized, certified, and redundant and that is is currently running an
ISSU capable "S" build.
2
Create the flash/issu directory and copy the ISSU supported images to the /flash/issu directory.
After the ISSU directory is created and image files are downloaded to this directory, then the
command is used to start the following patch process:
3
The switch copies image files to the flash/working directory from the flash/issu directory of the
primary CMM.
4
The switch synchronizes the image files in the flash/working directory of the primary CMM with the
files on the secondary CMM.
5
The secondary CMM reloads with the patched working directory image files.
6
When the secondary CMM completes the reload, the primary CMM transfers control to the secondary.
As a result of this process, the system is patched with minimal disruption to data traffic. Also, the primary
and secondary will have the same images in their flash/working directory and will have changed roles
(for example, primary will act as secondary and the secondary as primary).
OmniSwitch AOS Release 6 Switch Management Guide July 2010
In-Service Software Upgrade
reload issu
page 5-31