Dell PowerConnect B-FCXs, Руководство по настройке

Страница: 144 / 1494

102 PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Building an IronStack
5
•
Authentication of secure-setup packets provides verification that these packets are from
genuine Dell stack unit. MD5-based port verification confirms stacking ports.
•
Superuser password is required to allow password-protected devices to become members of
an IronStack.
•
The stack disable command. When this command is issued, a unit does not listen for or send
stacking packets, which means that no other device in the network can force the
stacking-disabled unit to join an IronStack.
Secure-setup can also be used to add units to an existing IronStack (refer to “Adding, removing, or
replacing units in an IronStack” on page 147) and to change the stack IDs of stack members (refer
to “IronStack unit identification” on page 122).
When secure-setup is issued on a unit that is not already the Active Controller, this unit becomes
the Active Controller, and, if it does not have an assigned priority, secure-setup assigns it a priority
of 128. Any unit that then tries to join the stack must have an assigned priority less than 128. If
secure-setup discovers a unit with a priority of 128 or higher, it changes the priority to 118.
When secure-setup is issued on a unit that is not already the Active Controller, this unit becomes
the Active Controller. If this unit does not already have an assigned priority, secure-setup will assign
this unit a priority of 128 by default, if no other units in the stack have a priority higher than 128. If
another unit in the stack has a priority of 128 or higher, secure-setup will give the Active Controller
a priority equal to the highest priority unit in the stack (which is by default the Standby Controller).
When the Active Controller and the Standby Controller have identical priorities, during a reset, the
old Active Controller cannot reassume its role from the Standby Controller (which has become the
Active Controller at the reset).
If the previous Active Controller again becomes active, and you want it to resume the role of Active
Controller, you should set the priority for the Standby Controller to a priority lower than 128. If you
do not want the previous Active Controller to remain Active Controller, you can set the same priority
for both Active and Standby Controllers (higher than, or equal to 128). For details, refer to
“IronStack unit priority” on page 123.
NOTE
Secure-setup works for units within a single stack. It does not work across stacks.
Follow the steps given below to configure a three-member stack in a ring topology using
secure-setup.
1. Connect the devices using the stacking ports and stack cabling. For more information refer to
the appropriate hardware installation guides.
2. Power on the units.
3. Connect your console to the intended Active Controller. The unit through which you run
secure-setup becomes the Active Controller by default.
4. Issue the stack enable command on the intended Active Controller.
PowerConnect# config t
PowerConnect(config)# stack enable
PowerConnect(config)# exit
PowerConnect#