
Managing Switches in a Stack | Managing OmniSwitch 6600 Family Stacks |
|
|
|
|
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
Stack Behavior During Takeover
If there are no unsaved configuration changes and the flash directories on both the primary and secondary switches in a stack have been synchronized via the copy
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 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 configura- tion (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).
If the flash directories on the primary and secondary management modules are not synchronized (e.g., a copy
Resetting All Switches in a Stack
To reset all switches in a stack you use the reload all command by entering
at the CLI prompt. This command can be helpful in restoring the original CMM roles in a stack (see “CMM Role Redundancy” on page
page | OmniSwitch 6600 Family Hardware Users Guide September 2006 |