Upgrading Stack Software
Context
Three methods can be used to upgrade the software version of a stack: system restart and fast upgrade. The following table compares these upgrade methods.
Upgrade Method |
Upgrade Mechanism |
Usage Scenario |
|---|---|---|
|
System restart |
After you specify the new system software to use at the next startup, the stack restarts. |
This upgrade method is commonly used but will cause lengthy service interruptions. Therefore, this method applies to the scenarios insensitive to the service interruption time. |
|
Fast upgrade |
An upgrade is completed through switchovers between the stack member switches. The standby switch is upgraded first, and then the master switch. |
This upgrade method shortens service interruptions and applies to the scenarios sensitive to the service interruption time. |
Do not remove or reinstall cards, and optical modules or power cycle the switch during a software upgrade.
Ensure network stability and do not perform other service configurations on the network during a software upgrade.
Procedure
- Upload the system software.
- Load the new system software to the system master MPU. For details on how to upload the system software, see File Management in the CloudEngine 12800 and 12800E Series Switches Configuration - Basic Configuration Guide.
- Run the copy source-filename all#flash: or copy source-filename destination-filename all command to copy the system software to all the MPUs.
- Perform a software upgrade.
System restart
Run the startup system-software system-file all command to specify the name of the system software to use at the next startup.
Run the reboot command to restart the stack.
Fast upgrade
Run the startup system-software system-file all command to specify the name of the system software to use at the next startup.
Run the system-view command to enter the system view.
Run the stack command to enter the stack management view.
(Optional) Run the stack upgrade fast rollback-timer time command to set the timeout period of a fast stack upgrade.
By default, the timeout period of a fast stack upgrade is 80 minutes.
To view the timeout period, run the display stack upgrade fast rollback-timer command.
This command specifies the time taken to upgrade the switch that functions as the standby switch before the upgrade instead of the entire stack system.
Run the stack upgrade fast command to start a fast upgrade.
After performing a fast upgrade, you can run the display stack upgrade status command to check the upgrade status.
If 40GE high-speed cables are used to connect stack member devices, you cannot fast upgrade switches from versions earlier than V100R003C00 to V100R003C00 or a later version.
When 40GE QSFP+ AOC cables are used for stack connections, the stack cannot be upgraded using fast upgraded from a version earlier than V100R005C10 to V100R005C10 or a later version.
If the current stack connection mode is different from the stack connection mode for the next startup, the stack fast upgrade cannot be performed.
In a stack established in MPU connection mode, if no forwarding link is available, the stack cannot be upgraded fast.
During the fast upgrade of a stack, the SFU reset due to heartbeat loss is a normal situation and does not affect services.
During a fast stack upgrade, to shorten traffic interruptions, ensure that upstream and downstream devices are dual-homed to stacked devices using Eth-Trunk.
It is recommended a backup IP address be configured for the stack management interface before a fast upgrade to prevent a failure to manage member devices when the stack fails the fast upgrade and splits.