User guide

Configuring Virtual Chassis Virtual Chassis - ISSU

OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 13-15

Virtual Chassis - ISSU

Upgrading a virtual chassis can be performed by uploading the new images to the Master chassis and

rebooting the entire virtual chassis. Prior to rebooting the Master will copy the new image files to the

Slave and once the virtual chassis is back up the entire virtual chassis will be synchronized and running

with the upgraded code.

The standard procedure is as follows:

1 Connect to the Virtual Chassis using the VC-EMP IP address.

2 Upload the new images to the Master chassis.

3 Reboot the entire virtual chassis

4 The new images are copied to the Slave chassis prior to rebooting and the entire virtual chassis is

synchronized when it comes back up.

Virtual Chassis - Upgrading with ISSU

The In-Service Software Upgrade (ISSU) feature is used to upgrade a Virtual Chassis with minimal

network disruption. Each switch can be upgraded individually without requiring the entire Virtual Chassis

to be rebooted at the same time.

The ISSU upgrade overview:

1 The Virtual Chassis will first verify that it is in a state that will allow a successful ISSU upgrade.

2 It will then copy the images and configuration files of the ISSU specified directory to the Slave chassis

and reload the entire Slave chassis from the ISSU directory. The Slave chassis reloads with the new image

files.

3 When the Slave has rebooted and rejoined the Virtual Chassis it is now using the new image files. The

Master chassis is now reset which causes the Slave chassis to become the new Master chassis.

4 When the original Master chassis reloads it comes back as a Slave chassis. To restore the role of

Master to the original Master chassis the current Master can be rebooted and the original Master will take-

over, assuming the Master role.

Performing an ISSU Upgrade

Note. The example below uses a directory named ‘issu_dir’. However, the directory can be any user-

defined directory.

1 Ensure that the Virtual Chassis is fully synchronized and certified.