reload issu
Upgrades the system with the images stored in the /flash/issu directory with minimal disruption to the data
traffic.
reload issu [in [hours:] minutes | at hour:minute]
Syntax Definitions
in [hours:] minutes
at hour:minute
Defaults
By default, the switch starts copying the image files to the working directory of the primary CMM imme-
diately after issuing the command if no time delay is specified.
Platforms Supported
OmniSwitch 9000E
Usage Guidelines
•
The switch must be running an In-Service Software Upgrade (ISSU) capable build, which is only those
builds that are part of the 'S##' branch (for example, 6.4.1.###.S01).
•
The primary and secondary CMMs should be fully synchronized, certified, redundant, and running an
ISSU capable 'S##' build, such as 6.4.1.123.S01, to invoke the ISSU feature.
•
Before using this command, create an ISSU directory on the switch flash (for example, /flash/issu),
then download the "S###" image files into this directory.
•
Image files used for the upgrade must be within the same 'S##' branch to pefrom an ISSU upgrade. For
example, 6.4.1.###.S02 image files cannot be used to upgrade a switch running 6.4.1.###/.S01.
•
There are four image files that are ISSU capable: Jbase.img, Jsecu.img, Jadvrout.img and Jos.img.
•
Admin user privileges are required to invoke the ISSU feature.
•
A minimum of 25MB flash space is required on the switch to accomodate all the image files needed for
the upgrade.
•
Once the images are upgraded, use the copy working certified flash-synchro command to restore
redundancy between the Primary and Secondary CMM.
Examples
-> reload issu
-> reload issu in 45
-> reload issu at 09:25
page 53-6
Optional syntax. Schedules a reload of the primary CMM to take effect
in the specified minutes or hours and minutes within the next 24 hours.
Optional syntax. Schedules a reload of the primary CMM to take place
at the specified time using a 24-hour clock.
OmniSwitch CLI Reference Guide
CMM Commands
June 2012