Managing Redundancy In A Stack And Cmm; Rebooting The Switch - Alcatel-Lucent OmniSwitch AOS Release 6 Manual

Managing CMM Directory Content

Managing Redundancy in a Stack and CMM

The following section describe circumstances that the user should be aware of when managing the CMM
directory structure on a switch with redundant CMMs. It also includes descriptions of the CLI commands
designed to synchronize software between the primary and secondary CMMs.

Rebooting the Switch

On OmniSwitch Stackable Series switches, when you reload the primary switch CMM in a stack, the
secondary switch takes over the primary function. If the stack is comprised of three or more switches, then
the original primary switch becomes "idle" and the next available "idle" switch becomes the secondary
CMM. For more information on stacks, see the "Managing Stacks" chapter found in the appropriate Hard-
ware Users Guide.
You can specify a reboot of the secondary CMM by using the secondary keyword in conjunction with the
reload command. For example, to reboot the secondary CMM, enter the reload command as shown:
-> reload secondary
In this case, the current primary CMM continues to run, while the secondary CMM reboots.
Scheduling a Reboot
It is possible to cause a reboot of the primary or secondary CMM at a future time by setting time parame-
ters in conjunction with the reload command.
For example, to schedule a reboot of the secondary CMM in 8 hours and 15 minutes on the same day,
enter the following at the prompt:
-> reload secondary in 08:15
Note. Scheduled reboot times should be entered in military format (i.e., a twenty-four-hour clock).
Cancelling a Scheduled Reboot
To cancel a scheduled reboot, use the cancel keyword. A cancel command can be specified for a primary
reboot, a secondary reboot, or all currently scheduled reboots. For example, to cancel the primary reboot
set above, enter the following:
-> reload secondary cancel
Secondary CMM Fail Over
While rebooting the switch during normal operation, a secondary CMM is installed, the switch will "fail
over" to the secondary CMM. "Fail over" means the secondary CMM takes the place of the primary
CMM. This prevents the switch from ceasing functionality during the boot process.
With OmniSwitch Stackable Series switches only, when the primary switch CMM in a stack fails over, the
secondary switch takes over the primary function. If the stack comprises three or more switches, then the
original primary switch becomes "idle" and the next available "idle" switch becomes the secondary CMM.
For more information on stacks, see the "Managing Stacks" chapter found in the appropriate Hardware
Users Guide. However, with OmniSwitch Chassis-based switches, if the versions of the software on the
primary and secondary CMM are not synchronized, the NI modules on the switch will restart, causing
packet loss.
OmniSwitch AOS Release 6 Switch Management Guide
Managing Redundancy in a Stack and CMM
July 2010 page 5-25