Major Mismatch For Stack Units; Configuration Mismatch For Stack Units - Arris Ruckus ICX 7850 Series Configuration Manual

Stack Management
Stack mismatches

Major mismatch for stack units

A major mismatch indicates an Interprocessor Communications (IPC)-related data structure change, an election algorithm
change, or a version of the software that does not support stacking. This can happen when the software undergoes a major
change (such as a change from 08.0.80 to 08.0.90). When a major mismatch occurs, the system logs and displays a message
similar to the following.
T=5h38m43.9: Warning! Recv 6004 IPC in 10m from 609c.9f2a.97e0 e1/2/1: wrong version 105 != 107.
Please make sure all stack units run the same image.
In a major mismatch, the stack cannot be built and will not operate. You must download the correct version of the software to
the mismatched units individually.

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.
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.
Recovering from a stack unit configuration mismatch
When a configuration mismatch occurs, the active controller logs and displays a configuration mismatch message and puts the
mismatched unit into a non-operational state. In the following example, the original stack unit 3 has failed, and a replacement
unit has been installed that does not match the configuration of the original unit. You should see the following message.
Warning! put stack unit 3 to non-operational reason= config mismatch
204
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01