Silicon Graphics InfiniteStorage 6120 User Manual page 84

MIR_NO_CONFIG
A configuration could not be created on the backend drives. Fix the condition that prevents this
controller from creating a configuration on the backend drives. Please refer to the installation
guidelines for proper setup.
MIR_NO_QUORUM
No quorum drives could be found within the disk drives on the backend. Fix the condition that
prevents the quorum drives from being seen. This may be caused by the drives never being in
the storage array. This will normally happen on new system installations. Use the CLEAR
SUBSYSTEM MIR_STATE command to create an empty configuration. NOTE: This creates a
new configuration and the old configuration will be deleted if one existed.
MIR_NOT_LAST_CONTROLLER
This controller found a valid configuration but was not present when another controller owned
the configuration. Another controller may have cached data for this configuration. This may
happen when controllers are swapped out or if the controllers went down and restarted
individually. To use the found configuration on this controller, use the CLEAR SUBSYSTEM
MIR_STATE command.
MIR_MULTIPLE_JIS
Multiple configurations were found on the quorum disks. This may happen if the drives from
one system were installed in another system when the systems were powered down and then
rebooted. If the drives were installed in the system while running, then this should not be an
issue. A list of found configurations will be listed. Use the CLEAR SUBSYSTEM MIR_STATE
ID=<id> command to use the specified ID's configuration.
MIR_DUAL_NO_AGREE
The two connected controllers do not agree on the ID of the configuration. This may occur if
one controller saw a subset of the drives and the other controller saw a different subset of drives.
Please refer to the installation guidelines for proper setup.
MIR_CONFIG_MISMATCH
The configuration version of this firmware does not match the configuration version of that on
media. To proceed, either reload the previous version of firmware and do a backup then
upgrade, or delete your configuration to continue. Use CLEAR SUBSYSTEM CONFIGURATION
to create an empty configuration. NOTE: This creates a new configuration and the old
configuration will be deleted if one existed.
MIR_NO_LOAD_CONFIG
A configuration could not be loaded from the backend drives. Fix the condition that prevents
this controller from loading a configuration from the backend drives or use CLEAR SUBSYSTEM
MIR_STATE to create an empty configuration. Please refer to the installation guidelines for
proper setup. NOTE: This creates a new configuration and the old configuration will be deleted
if one existed.
0 0 7 - 5 5 3 3 - 0 0 1
Manual Intervention Required (MIR) Conditions
74