White Papers

Table Of Contents
The unit with the numerically highest priority is elected the master management unit, and the unit with the second highest
priority is the standby unit.
The range is from 1 to 14.
The default is 0.
Managing Redundancy on a Stack
Use the following commands to manage the redundancy on a stack.
Reset the current management unit and make the standby unit the new master unit.
EXEC Privilege mode
redundancy force-failover stack-unit
A new standby is elected. When the former stack master comes back online, it becomes a member unit.
Prevent the stack master from rebooting after a failover.
CONFIGURATION mode
redundancy disable-auto-reboot stack-unit
This command does not affect a forced failover, manual reset, or a stack-link disconnect.
Display redundancy information.
EXEC Privilege mode
show redundancy
Resetting a Unit on a Stack
You may reset any stack unit except for the master management unit, as shown in the following message.
% Error: Reset of master unit is not allowed.
To rest a unit on a stack, use the following commands.
Reload a stack-unit.
EXEC Privilege mode
reset stack-unit unit-number
Reload a member unit, from the unit itself.
EXEC Privilege mode
reset-self
Reset a stack-unit when the unit is in a problem state.
EXEC Privilege mode
reset stack-unit unit-number {hard}
Verify a Stack Configuration
The light of the LED status indicator on the front panel of the stack identifies the units role in the stack.
Off indicates the unit is a stack member.
The master LED is in OFF state for the standby unit.
Solid green indicates the unit is the stack master (management unit).
Displaying the Status of Stacking Ports
To display the status of the stacking ports, including the topology, use the following command.
Display the stacking ports.
EXEC Privilege mode
822
Stacking