Stack mismatches
When a stack mismatch occurs, the active controller can put any stack member into a non-operational state, which disables all of the ports except the stacking ports. Stack mismatches can occur for a variety of reasons.
NOTE
After a stack mismatch, the active controller can still download an image to the non-operational unit.
The active controller generates a log message whenever it puts a stack unit into a non-operational state. The following examples describe the types of mismatches and the related log message:
- Advanced feature mismatch - The active controller is enabled for advanced features (such as BGP), and the stack unit is not enabled.
Stack: Unit 2 0000.0020.0100 doesn’t have the matching advanced feature privileges
- Image mismatch - A stack unit is running a different software image than the active controller is running.
Stack: Unit 2 0000.0020.0100 image mismatch
- Configuration mismatch - The module configuration for a stack unit does not match the reserved configuration on the active controller.
Stack: Unit 2 0000.0020.0100 config mismatch
- Memory allocation mismatch - The active controller does not have enough memory to accommodate the stack unit.
Stack: Malloc failure for unit 2.0000.0020.0100