Filter
Top Products
Managing Switches in a Stack Managing OmniSwitch 6600 Series Stacks
page 3-18 OmniSwitch 6600 Series Hardware Users Guide April 2004
Changing the Secondary CMM Role to Primary
To change a switch with a secondary role to primary use the takeover command. For example, while
logged into either the primary or secondary switch enter:
-> takeover
at the CLI prompt. In a stack consisting of two switches the primary switch will become secondary. In a
stack consisting of three or more switches the secondary switch will become primary, the idle switch with
lowest slot number will become secondary, and the switch that was primary will become idle.
You can determine the current CMM role of a switch by examining the PRI and SEC LEDs on the
switch’s front panel. Refer to Chapter 2, “OmniSwitch 6600 Series Chassis and Hardware Components,”
for more information. You can also use the show running-directory command to display whether the
switch into which you are currently logged is primary or secondary. For example:
-> show running-directory
Running CMM : PRIMARY,
Running configuration : CERTIFIED,
Certify/Restore Status : CERTIFY NEEDED,
Synchronization Status : SYNCHRONIZED,
Stacks Reload on Takeover: PRIMARY ONLY
In this example, the user is currently logged in to the switch with the primary CMM role.
Note. Before using the takeover command, verify that the switches in the stack are synchronized. Other-
wise, data flow and switch management functions may be interrupted due to incorrect or outdated soft-
ware when a switch takes over the primary CMM role. For more information, refer to “Synchronizing
Switches in a Stack” on page 3-17.
Module Behavior During Takeover
If there are no unsaved configuration changes and the flash directories on both the primary and secondary
management modules have been synchronized via the copy flash-synchro command, no modules will be
reloaded if a management module takeover occurs. As a result, data flow is not interrupted on the modules
during the takeover.
If a configuration change is made to one or more modules (e.g., a VLAN is configured on several differ-
ent interfaces), and the changes are not saved via the write memory command, the corresponding modules
will automatically reload if a management module takeover occurs. Data flow on the affected modules will
be interrupted until the reload is complete. Note that the modules will reload whether or not the flash
synchronization status shows SYNCHRONIZED. This is because the unsaved changes have occurred in
the running configuration (i.e., RAM), and have not been written to the flash directory’s configuration file.
In this case, a list of only the affected modules displays in the table output (e.g., 1 6 9 12).
If the flash directories on the primary and secondary management modules are not synchronized (e.g., a
copy flash-synchro command has not been issued recently), all modules will be reloaded automatically if
a management module takeover occurs. Data flow will be interrupted on all modules until the reload is
complete.