Supermicro SuperBlade SBM-GEM-X2C+, Руководство пользователя

Страница: 184 / 404

Superblade Network Modules User’s Manual
7-56
Enabling Stacking
By default, Supermicro switches act as stand-alone switches. This stand-alone default
facilitates using 10G Ethernet ports as Extreme Ethernet ports for uplinks.
When stacking is enabled the stacking ports are dedicated for stacking purposes.
Stacking can be enabled using the command
stack
with the switch identifier and
priority. The detailed command syntax is explained below.
In the stacking mode, any firmware upgrade in the Master Switch will automatically
initiate a firmware upgrade to all attached stack member switches. Firmware upgrade
confirmation from stack member switches will be displayed in the Master Switch
management interface.
Also in the stacking mode, the user can reload all stacked switches or any selected
stack member switch from the master management interface.
The interface numbers change between stacking and non-stacking cases due to the
switch ID. So configurations saved for stacking are not valid for non-stacking cases and
vice versa.
Adding Stacking Members
Connect the stacked switches using stacking cables. For better redundancy, connect
the switches daisy-chained as shown in
Figure 7-48 . This chain connectivity helps to
maintain stacking in case a single link or switch fails.
Before connecting switches in stacking, make sure stacking is enabled in all switches
and that the switch identifier and priorities are all configured properly.
NOTE: When stacking is enabled, the switch needs to be rebooted to make it
effective.
NOTE: When a switch is acting as a stand-alone switch with stacking disabled,
all physical interfaces are numbered as
0/1
to
0/n
.
When the switch is in stacking mode, the interfaces are numbered as
<switch
id>/1
to
<switch id> / n
.
In non-stacking mode, the switch ID is considered to be 0 .
NOTE: If you choose stacking using the
stack
command from a non-stacking
case, and the configurations are already saved for restoring the switch, it will
rename the configuration file by adding a suffix
_nonstack
and will not restore
this file when the switch reboots with stacking enabled.
Similarly, if you choose non-stacking using the
no stack
command from the
stacking case, and the configurations are already saved for restoring the switch,
it will rename the configuration file by adding a suffix
_stack
and will not
restore this file when the switch reboots with stacking disabled.