Alcatel-Lucent 6850-48 Manuale Hardware
Managing OmniSwitch 6850 Series Stacks
Reloading Switches
OmniSwitch 6850 Series Hardware Users Guide
September 2009
page 4-31
Reloading All Switches in a Stack
Reloading all switches in the stack is essentially a full reboot of the virtual chassis. This can be useful in
restoring a stack’s previously configured topology—i.e., the stack’s saved slot numbers and management
roles. Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued.
restoring a stack’s previously configured topology—i.e., the stack’s saved slot numbers and management
roles. Note, however, that all data flow on the stack is interrupted whenever a full reboot is issued.
To reset all switches in a stack use the
command. For example:
-> reload all
Important. Before issuing the reload all command, be sure to read the sections below. Understanding
topics such as software synchronization and the effects of saved slot information can help users avoid
unexpected results following a full stack reboot.
topics such as software synchronization and the effects of saved slot information can help users avoid
unexpected results following a full stack reboot.
Software Synchronization During a Full Reload
If the checksum value on the stack’s non-primary switches differs in any way from the checksum value on
the primary switch, the primary switch automatically distributes its system and configuration software to
all other switches in the stack whenever a full reload is executed.
the primary switch, the primary switch automatically distributes its system and configuration software to
all other switches in the stack whenever a full reload is executed.
During this automatic software synchronization, system and configuration software on the secondary and
idle switches is overwritten. Because the primary switch’s “last known good” software is propagated to all
switches, the synchronization process helps ensure effective redundancy across the stack.
idle switches is overwritten. Because the primary switch’s “last known good” software is propagated to all
switches, the synchronization process helps ensure effective redundancy across the stack.
Effects of Saved Slot Number Information on the Reload Process
Depending on the status of saved slot information across the stack, there are different slot numbering and
management role scenarios that can occur following a full reboot. For this reason, checking the current
stack topology before issuing a full reboot is strongly recommended. To check the current stack topology,
use the
management role scenarios that can occur following a full reboot. For this reason, checking the current
stack topology before issuing a full reboot is strongly recommended. To check the current stack topology,
use the
command. Refer to the OmniSwitch CLI Reference Guide for detailed
command information.
Possible saved slot number conditions include:
• All switches have unique saved slot information
• No switches in the stack have saved slot information
• Some switches have saved slot information, others do not
• Two or more switches have duplicate slot information
All Switches Have Unique Saved Slot Information
If a full reload is issued and all switches have unique slot numbers saved to their boot.slot.cfg files, the
slot numbers will be assigned according to the saved slot information. The primary management role will
be given to the switch with the lowest saved slot number. The secondary management role will be given to
the switch with the second-lowest saved slot number. All other switches will be assigned to idle roles.
slot numbers will be assigned according to the saved slot information. The primary management role will
be given to the switch with the lowest saved slot number. The secondary management role will be given to
the switch with the second-lowest saved slot number. All other switches will be assigned to idle roles.
An illustrated example of this method for assigning slot numbers and management roles is provided on
pages
pages
.