Configuration Guide User guide

FastIron Configuration Guide 311
53-1002494-02
Brocade IronStack management
Syntax: show stack connection
Adding, removing, or replacing units in an IronStack
The following sections describe how to add, remove, or replace units in an IronStack. The
recommended method is to connect units to the stack before you supply power to the units;
however, you can also connect powered units.
Installing a new unit in an IronStack using secure-setup
This method can be applied to clean units, or units that have existing configurations.
1. Connect the new unit to the stack by connecting the 10 Gbps stacking ports.
2. Run secure-setup on the Active Controller and assign an ID to the new unit. The Active
Controller will reset the new unit.
3. Once the new unit boots and joins the stack, do a write memory on the Active Controller.
Installing a new unit using static configuration
If the new unit is a clean unit and the connection is sequential you can add it using the static setup
process.
1. Enter the module configuration of the new unit into the Active Controller configuration.
2. Connect the new unit to the stack using the 10Gbps stacking ports. The sequence in which you
connect the unit must match that of the Active Controller configuration. The Active Controller
automatically resets the unit.
3. Once the new unit boots and joins the stack, do a write memory on the Active Controller. You
should see the following message.
Done hot swap: Set stack unit 3 to Fully-Operational:16
Configuration notes
Configuration on a new unit can be accomplished in three ways:
• If the Active Controller has no configuration information for the new unit, it learns the new
unit's configuration. This is a dynamic configuration and will disappear if the new unit leaves
the stack. In order for the configuration to stay on the Active Controller (to make it a static
configuration), you must do a write memory on the Active Controller.
• If the Active Controller has configuration information for a new unit, and it matches the base
module (module 1) of the new unit, no action is necessary. If configuration information for
non-base modules on the new unit does not match the information on the Active Controller, the
Active Controller learns the configuration for the new unit module types and merges it with the
information it has for the base module. This merged configuration remains static and will stay
on the Active Controller even if the new unit leaves the stack.
• If the Active Controller has configuration information for the new unit, but it does not match the
base module of the new unit, a configuration mismatch can occur where the configuration
related to this unit is removed even after the mismatch is resolved. Refer to “Recovering from a
stack unit mismatch” on page 323 for more information.