Renumbering may cause loss 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 you assign an ID with an associated configuration to a stack unit with a different configuration, secure-setup changes the static configuration into a dynamic configuration so it can be overwritten by the learned configuration.
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) does not affect unit configuration except that the units are reset and assume the new IDs.
If you swap IDs for two units that are not identical (for example, unit 2 has 48 ports, and unit 3 has 24 ports), 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 removed.
When you renumber identical units using secure-setup, the configurations are not mapped to the new units (because the configurations match exactly). However, if you switch IDs on units that are not identical, a configuration mismatch occurs. Refer to
Recovering from a stack unit configuration 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.
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 configurations learned following mismatches or the addition of new units are dynamic configurations. To convert them into static configurations, execute a
write memory command on the active controller. This command preserves the configuration if a unit is removed from the stack.
