Brocade FastIron Ethernet Switch Stacking Configuration Guide - Manual (Page 86)

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
device# 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
device# show stack
ID Type Role MAC Address Pri State Comment
1 S FCX624 active 0000.0039.2d40 128
local Ready
2 S FCX624 standby 0000.00d5.2100 0
remote Ready
3 S FCX624 member 0000.005d.9940 0
remote Ready
Configuration notes for renumbering stack units
• 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 - for example, unit 2 is an FCX648 and unit 3 is
an FCX624, you may cause a configuration mismatch. If this happens, 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 stack unit mismatch.”
• 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.
• 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.
Syslog, SNMP, and traps for stack units
Syslog messages from stack units are forwarded to, and can be viewed from, the active controller.
All stack units support SNMP gets, sets, and traps, which are managed by the active controller. An
SNMP trap is sent from a stack unit to the stack active controller, and forwarded from the active
controller to an SNMP-configured server. An external network management station can execute
SNMP gets and sets for MIBs and collect information about any port on the stack.
SNMP traps can be configured for the insertion or removal of a stack unit or uplink module, and for
optic identification.
Configuration notes for renumbering stack units
84 FastIron Ethernet Switch Stacking Configuration Guide
53-1003090-02