issu update-software

issu update-software [validate|confirm]

Description

Initiates ISSU to the alternate boot location. The newer operating system image must be downloaded to the alternate boot location prior to running this command. Additionally, the current running operating system version must match the version that is stored in the current boot location or ISSU will not be allowed.

Starting an ISSU will cause the running configuration to be saved in case an error is encountered that requires a reboot to recover the switch. In addition, a special configuration checkpoint will be stored to disk and can used to roll back to the pre-ISSU firmware. During the ISSU process all management methods (CLI, REST, WebUI) will be blocked from making configuration changes to the switch. The configuration block is active from the time ISSU starts until the the time ISSU switchover is complete. After the ISSU switchover completes, the newly upgraded alternate management module is active and switch configuration can resume.

Parameter	Description
validate	Runs all pre-ISSU validations without executing the actual upgrade. The validation runs in the background, however its results will be displayed in real time for approximately the next three minutes . If the validation is not finished within that time frame or if the display is aborted with Control+C or Control+Z, the results can be queried using the show issu validation command.
confirm	Confirms the software update and cancels the configured rollback timer. If the rollback timer is configured and this command is not executed after an ISSU when it expires, then the pre-ISSU checkpoint is copied to the startup configuration and the system is rebooted to the image used before ISSU. Note: To perform an intentional system rollback before the timer expires, a manual downgrade must be executed through the following steps: Copy the pre-ISSU checkpoint to the startup configuration using the copy checkpoint pre-issu-startup-config startup-config command. Boot to the previous image using the boot system command.

Usage

Note the following points before running this command:

• The newer operating system image must be downloaded to the alternate boot location prior to running this command.
• The current running operating system version must match the version that is stored in the current boot location or ISSU will not be allowed.
• This operation is disruptive and will result in the management interface being disconnected during the process.
• The running configuration will be stored in case an error is encountered that requires a reboot to recover the switch.
• During the ISSU process all management methods (CLI, REST, WebUI) are blocked from making configuration changes to the switch. The configuration changes are not allowed from the time ISSU starts until ISSU switchover is complete. After the ISSU switchover completes, the newly upgraded alternate management module is actived and switch configuration is resumed.
• The VSF Conductor will reboot as part of the ISSU process. This will cause the VSF Conductor's interfaces to flap. If these interfaces are participating in spanning-tree as standalone interfaces, then it will trigger spanning-tree re-convergence, resulting in traffic disruption for few seconds.
• It is recommended to configure a ring topology before initiating ISSU.
• During the ISSU process, the show core-dump all, show tech all, and copy support-files commands all may fail to run or display correct output.

Examples

Initiating an in-service software upgrade:

Initiating an ISSU, but stopping it without confirming the upgrade:

Confirming the ISSU configuration when the rollback timer has been configured and started:

Confirming the ISSU configuration when the rollback timer has not started:

Executing an ISSU "dry run" where all pre-ISSU validations are run without executing the actual upgrade:

Executing an ISSU "dry run" where all pre-ISSU validations are run and the user aborts the ISSU validation on screen display without user confirmation:

Executing an ISSU "dry run" where all pre-ISSU validations are run without executing the actual upgrade and the validation progress has finished successfully:

Executing an ISSU validation while a previous ISSU is unconfirmed, i.e. the rollback timer is still running:

Executing an ISSU "dry run" when the validations are taking more than three minutes to complete, then checking the result of the validation afterwards:

Command History

Release	Modification
10.11	Validate and confirm parameters added.
10.10	Command introduced.

Command Information

Platforms	Command context	Authority
6300	config	Administrators or local user group members with execution rights for this command.