Filter
Top Products
Managing Redundancy in a Stack Managing CMM Directory Content
page 4-24 OmniSwitch 6600 Family Switch Management Guide March 2005
Managing Redundancy in a Stack
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 CLI commands
designed to synchronize software between the primary and secondary CMMs.
Rebooting the Switch
When you reload the primary switch CMM in a stack, the secondary switch takes over the primary func-
tion. 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
“Managing Stacks” in the OmniSwitch 6600 Family Hardware 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 conjuction 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
When rebooting the switch during normal operation, and 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. When the primary
switch CMM in a stack fails over, 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 avail-
able “idle” switch becomes the secondary CMM. For more information on stacks, see “Managing Stacks”
in the OmniSwitch 6600 Family Hardware Users Guide.
If the versions of the software on the primary and secondary CMM are not synchronized, the NI modules
on the switch will restart, causing severe packet loss.