Configuration Guide User guide

320 FastIron Configuration Guide
53-1002494-02
Image mismatches
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 for stack units
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.
Brocade# 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. 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 283).
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. On the other hand, the Active Controller deletes the dynamic
configuration for a unit if it leaves. (Refer to Table 48 for definitions of static and dynamic
configurations.)
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.
Configuration mismatches can happen during manual setups, or when moving a unit from one
stack to another stack or a unit’s ID is changed by Secure Setup.
When you renumber identical units using secure-setup, the configurations are not mapped to the
new units (since 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. Refer to “Recovering from a
stack unit mismatch” on page 323.