Filter
Top Products
PowerConnect B-Series FCX Configuration Guide 155
53-1002266-01
Image mismatches
5
Major mismatch
A major mismatch indicates an Interprocessor Communications (IPC)-related data structure
change, or an election algorithm change, or that a version of the software that does not support
stacking is installed on a unit. This can happen when the software undergoes a major change
(such as a change from 05.0.00 to 05.1.00). When a major mismatch occurs, the system logs and
prints a message similar to the following.
Warning! Recv 424 IPC in 1m from 0012.f21b.a900 e1/1/25: wrong version 5 !=6.
Please make sure all 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.
Minor mismatch
With a minor mismatch, an operating stack can still exist, but traffic is dropped from all ports
except for the stacking ports for units with the mismatched software. You can download the correct
image to the mismatched devices from the Active Controller. A minor software mismatch means
that there is no IPC or election algorithm change, but there is a release version disparity. Minor
software mismatches can happen with patch release upgrades. The system logs and prints a
message similar to the following.
Warning! put stack unit 2 to non-operational reason=image mismatch
The show stack command displays output similar to the following.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID Type Role Mac Address Pri State Comment
1 S FCX624 active 0012.f2eb.a900 128 local Ready
2 S FCX648 standby 00f0.424f.4243 0 remote NON-OP: image mismatch
3 S FCX624 member 00e0.5201.0100 0 remote Ready
If the configuration of a stack unit does not match the configuration of the Active Controller, the
stack unit will not function. You must manually correct the configuration error for the unit to
become operational within the stack. In this example, unit 2 is non-operational due to an image
mismatch. To correct this situation, use the copy flash flash command (refer to “Copying the flash
image to a stack unit from the Active Controller” on page 126).
Configuration mismatch
Generally, when a stack unit is added to or removed from the stack, its static configuration is not
overwritten by the Active Controller. However, secure-setup allows you to overwrite a static
configuration on a unit, in which case the Active Controller deletes the configuration for the old unit,
and adds the configuration of the new unit.
A configuration mismatch occurs when the base module configuration for a replacement stack unit
does not match the run time 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.