Configuration Mismatch for Stack Units

Generally, when a stack unit is added to or removed from the stack, its static configuration is not overwritten by the active controller. However, the active controller deletes the dynamic configuration for a unit if it leaves the stack.

A configuration mismatch occurs when the base module configuration for a replacement stack unit does not match the runtime configuration on the active controller. If the configuration on the active controller is static, it cannot be overwritten by the new configuration, and a configuration mismatch occurs.

Configuration mismatches can occur during manual setup when a unit is moved from one stack to another stack or when the ID of a unit is changed by stack interactive-setup.

This is an old section, and I've simply changed secure-setup to stack interactive-setup. This needs to be reviewed for revision or removal.

When you renumber identical units using stack interactive-setup, the configurations are not mapped to the new units (because they match exactly). However, if you switch the IDs of units that are not identical, a configuration mismatch occurs.

When a configuration mismatch occurs, port-related functions on all ports are disabled on the mismatched unit (except for the stacking ports). All other functions are unaffected. For example, the active controller can still copy the unit's image or reset the unit.