You can now implement a fabric-wide upgrade and reboot the switches at the same time or in a sequential order. A fabric upgrade requires downloading the new Netvisor One software package to each switch, and rolling upgrade downloads the software packages from the update server and then copies the software to each switch as the upgrade proceeds.
The upgrade controller is the switch where the fabric-upgrade-start command is issued. All upgrade commands should be executed from the upgrade controller.
The fabric upgrade feature has two phases:
- Upgrade — start the upgrade which creates and updates Netvisor One to new boot environments but does not reboot the fabric.
- Reboot — reboots the entire fabric after all server-switches are upgraded to new boot environments. It is also possible during this phase to abort the process and discard the new boot environments.
The fabric is locked during the entire process and you cannot change any configurations during the process.
Before You Begin the Fabric Upgrade
Before you begin, you may want to consider the following options for the fabric-upgrade-start command:
- auto-finish — you can specify to automatically reboot the entire fabric after the upgrade is complete.
- rolling — specify if you want to perform a rolling fabric upgrade. A rolling fabric upgrade performs the upgrade procedure on a switch-by-switch basis and copies the software package from the controller to other switches in the fabric. If you specify no-rolling, all switches are booted after the upgrade.
- abort-on-failure — specify if you want the upgrade to stop if there is a failure during the process.
- manual-reboot — specify if you want to manually reboot individual switches after the upgrade process. If you specify no-manual-reboot, all switches reboot automatically after the upgrade is complete.
- prepare — specify if you want to perform setup steps prior to performing the upgrade. This step copies the offline software package and then extracts and prepares it for the final upgrade process. Once you begin the prepare process, you cannot add new switches to the fabric.
- reboot-parallel — specify to reboot switches in parallel if the switches are in a cluster configuration. Or, you can reboot them one at time using the reboot-single option.
- reboot-group — specify the number of switches to reboot as a group in parallel mode. The default is the maximum number of switches in the fabric up to 100 switches.
Starting the Fabric Upgrade
1. Download the latest Netvisor One software from the update server onto a switch in the fabric.
2. Copy the Netvisor One software package to each switch in the fabric.
3. Select a switch in the fabric to act as the upgrade controller switch, and use the fabric-upgrade-start command to begin the upgrade.
4. Depending on the options selected, the upgrade completes by reboot the fabric or rebooting all of the switches.
Starting the Rolling Fabric Upgrade
If you opted for a rolling fabric upgrade, then the upgrade controller switch begins copying to software packages to other switches in the fabric. Other than this step, the rolling fabric upgrade has the same behavior as a fabric upgrade depending on the selected options.
You can check the status of the upgrade using the fabric-upgrade-status-show command:
CLI (network-admin@sw1) > fabric-upgrade-status-show
log switch state
----------------------------------------------- -------- ------------------
(0:00:36)Upgrading software upgrade framework sw3 Running
(0:00:08)Computing package update requirements. sw2 Running
(0:00:12)Agent needs restart sw1* Agent restart wait
The first entry in the log is the duration of the upgrade process. It does not include waiting time. The switch with the asterisk (*) is the controller server-switch where the fabric-upgrade-start command was issued.
Additional commands for the fabric upgrade feature:
- fabric-upgrade-finish — you can issue this command at any time during the fabric upgrade to reboot all nodes in the fabric and complete the upgrade. Once the upgrade phase is complete, all server-switches display the “Upgrade complete” message in the log field. You can then safely reboot the fabric.
- fabric-upgrade-abort — aborts the software upgrade process. All changes to the server-switches are cleaned up and the server-switches do not reboot. The configuration lock on the fabric is also released.
If you issue the fabric-upgrade-abort command during the upgrade process, it may take some time before the process stops because the upgrade has to reach a logical completion point before the changes are rolled back on the fabric. This allows the proper cleanup of the changes.
- fabric-upgrade-prepare-cancel — cancels a fabric upgrade that was prepared earlier.
- fabric-upgrade-prepare-resume — resume a fabric upgrade that was prepared earlier.
- fabric-upgrade-prepare-show — displays the status of prepared upgrades on the fabric nodes.