Maintaining a Stack
This section describes how to maintain a stack.
Monitoring the Stack Status
Context
To ensure normal system operations or locate faults that occur in the stack, run the following command in any view to monitor the stack running status.
Procedure
- Run the display stack [ member member-id ] command to check information about stack member switches.
- Run the display stack configuration [ member member-id | all ] command to check the stack configuration.
- Run the display stack topology[ link | neighbor ] command to check stack topology information.
- Run the display stack troubleshooting [ member member-id ] command to check the stack fault events.
Performing a Master/Standby Switchover
Context
You can manually trigger a master/standby switchover in a stack if the current roles of member switches do not meet your requirement. For example, you can perform a master/standby switchover to change the roles after a restart or restore the original roles after an upgrade.
Procedure
- Run the display switchover state command to check whether the stack meets switchover requirements.
You can perform a switchover only if the Switchover State field is Ready.
- Run the system-view command to enter the system view.
- Run the slave switchover enable command to enable the master/standby switchover function.
By default, the master/standby switchover function is enabled.
- Run the slave switchover command to perform a master/standby switchover.
Upgrading Stack Software
Context
Upgrade Method |
Upgrade Mechanism |
Usage Scenario |
|---|---|---|
MM910 upgrade |
Upgrade modules in the chassis using a management module in an unified manner. |
This upgrade method, is commonly used, which is a simple operation.It results in long-term service interruption and applies to applications that have low requirements on service interruption. |
System restart |
After you specify the new system software to use at the next startup, the stack restarts. |
This upgrade method is commonly used, which is a complex operation, but it causes service interruption in a long time. Therefore, this method can be used in 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. |
|
Procedure
- Upload the system software.
- Load the new system software to the master switch. For details on how to upload the system software, see File Management in the CX11x&CX31x&CX91x Series Switch Modules Configuration Guide - Basic Configurations.
- Run the copy source-filename destination-filename all command to copy the system software to all the member switches.
- Perform a software upgrade.
MM910 upgrade methods
For details, see CX Series Switch Module Upgrade Guide.
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.
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.
![]()
NOTE: Only the stack containing two member switches supports fast upgrade.
It is recommended that the upstream and downstream devices be connected to the stack through Eth-Trunk links to reduce the traffic interruption time during an upgrade.
If the current version does not support the Smart Channel function but the system contains mode and configuration files related to Smart Channels, fast upgrade is not supported.
Previous
