Version mismatch state for a managed system

The Version mismatch state can occur when the redundant or dual Hardware Management Consoles (HMCs) that manage the same server are at different version and release levels.

The Version mismatch state can occur for any of the following reasons:
  • FSP firmware and HMC versions are incompatible.
  • An HMC Version 7.7.8 or later is connected to a server that was managed by a newer version of the HMC.
  • An HMC Version 7.7.8 or later is connected to a server that was managed by a lower version of the HMC and does not have enough space present to upgrade the data to HMC Version 7.7.8 or later.
  • The hypervisor or server brand or model is not supported by this version of the HMC.
To recover from the Version mismatch state, select the appropriate action, depending on the reference code that is displayed:

  • Save Area Version Mismatch

    HMC Version 7.7.8 and later blocks attempts to manage a server with a configuration at a newer level by posting a new Connection error state and reference code. If an HMC Version 7.7.8 or later is connected to a server that was managed by a newer version of the HMC that updated the configuration format, then the HMC reports a connection error of Version mismatch with the reference code Save Area Version Mismatch. This error prevents accidental corruption of the configuration.

    If you want to continue on a lower HMC version, then you must first initialize the server in the lower version of the HMC before you proceed to run any operation.

  • Profile Data Save Area is full

    The HMC uses a storage area on each managed server to store the server configuration, primarily PowerVM® partition profiles. HMC Version 7.8.0 and later increases the usage of the storage area by adding another (mostly hidden) profile for each partition. Servers that already contain many profiles might not have sufficient space to allow the HMC Version 7.8.0 and later to run properly.

    HMC Version 7.8.0 and later checks for sufficient space in this storage area and stops the connection process with a connection state of Version mismatch and a reference code of Profile Data Save Area is full if sufficient space does not exist.

  • Connecting 0000-0000-00000000 (Unsupported Hypervisor)

    A connection state of Version mismatch and a reference code of Connecting 0000-0000-00000000 (Unsupported Hypervisor) is returned when the server is configured for a hypervisor other than PowerVM.

    To recover from this state, first start the ASM by selecting the server with the Version mismatch and selecting Operations and then Launch Advanced System Manager (ASM).

    On models that support multiple hypervisors, the hypervisor mode setting can be found in the ASM by selecting System Configuration and then Hypervisor Configuration. The hypervisor mode shows a setting of either PowerVM or OPAL.

    If OPAL is the wanted configuration, then you must remove this connection from the HMC by selecting Connections and then Reset or Remove Connections. Next, select Remove Connections and click OK.
    Note: The OPAL hypervisor is not supported on the HMC.
    If PowerVM is the wanted configuration, select PowerVM from the hypervisor mode menu and click Continue.
    Note: The setting can be changed only when the server is powered off. To power off the server select Power/Restart Control and then Power On/Off System. Click Save Settings and Power off .

  • Connection not allowed

    A connection state of Version mismatch and a reference code of Connection not allowed 0009-0008-00000000 is returned when the FSP firmware and HMC versions are incompatible.

    To recover from this state, install an HMC version that supports the managed server model.

For more information about correction a Version mismatch state, see Version mismatch errors.