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

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

150 PowerConnect B-Series FCX Configuration Guide
53-1002266-01
Managing your IronStack
5
2 6 FCX624 001b.ed5d.9940
Do you accept the unit ids? (y/n)?: n
Enter an unused id for the UPSTREAM FCX623 unit a 1 hop(s) (1-8)[5]: 2
Enter an unused id for the UPSTREAM FCX624 unit at 2 hop(s) (1-8) [6]: 3
PowerConnect# Election, was active, no role change, assigned-ID=1
reset unit 2: diff bootup id=5
reset unit 3: diff bootup id=6
Election, was active, no role change, assigned-ID=1
PowerConnect# show stack
ID Type Role Mac Address Pri State Comment
1 S FCX624 active 0012.f239.2d40 128 local Ready
2 S FCX624 standby 0012.f2d5.2100 0 remote Ready
3 S FCX624 member 001b.ed5d.9940 0 remote Ready
Configuration Notes:
•
Renumbering may result in the removal of a unit configuration if the stack unit base module
does not match the configuration on the Active Controller. However, secure-setup renumbering
never changes the interface configuration. For example, if you switch the IDs of identical units
2 and 3, the Active Controller does not change 2/1/5 to 3/1/5 and vice versa.
•
If the configuration for the ID you select for a specific unit does not match the configuration on
that unit, secure-setup will change the static configuration into a dynamic configuration so it
can be overwritten by the learned configuration.
•
When swapping IDs for two or more identical units - for example, if units 2, 3, and 4 are
identical, changing 2 to 3, 3 to 4, and 4 to 2 will not affect the configurations of the units
except that the units will reset and assume the new IDs.
•
If you swap IDs for two units that are not identical -The Active Controller removes the
configurations and resets both units. When both units boot with new IDs, the Active Controller
learns their module types and creates new
unit configurations for both. However, all interface
configuration information related to units 2 and 3 is gone.
•
When you renumber identical units using secure-setup, the configurations are not mapped to
the new units (since the configurations match exactly). However, if you switch the IDs of units
that are not identical, a configuration mismatch occurs. Refer to
“Recovering from a mismatch”
on page 156
•
When you assign an unused ID to a stack unit, the unit is reset with the new ID. All unit and
interface configuration information related to the old stack ID is deleted. The Active Controller
learns the configuration for the new unit (instead of creating interface configuration for the
new unit.
•
Release 5.0 does not support user changes to the Active Controller ID.
•
Secure-setup does not swap configuration information for units that have had their IDs
changed. For example, it does not change the 2/1/3 interface configuration or VLAN
membership information into 3/1/3 information if the unit ID changes from 2 to 3.
•
If the configuration for a unit being replaced does not match the new unit type, the Active
Controller removes the unit configuration and associated interface configuration.
•
All learned configurations due to mismatches or the addition of new units are dynamic
configurations. To convert them into static configurations, do a write memory to preserve the
configurations if a unit is removed from the stack.