Troubleshooting
Problem
Version mismatch implies that the HMC is unable to manage the device. This document includes common causes and how to further isolate the cause of the version mismatch and correct the problem.
Resolving The Problem
Version mismatch implies that the HMC is unable to manage the device. There are several different causes. The reference code value should be used to further isolate the cause and correct the problem.
Possible Causes
| o | Save area version mismatch HMC Version 7.7.8 and later will block attempts to manage a server that has a partition configuration with a newer format by posting a new connection error state and reference code. If a HMC at Version 7.7.8 or later is connected to a server which has been managed by a newer version of HMC that updated the "save area" configuration format, the HMC will report a connection error of "Version Mismatch" with reference code "Save Area Version Mismatch". This prevents accidental corruption of the configuration. To correct the issue ,either upgrade the HMC or initialize the profile data. For further information, refer to document N1019874, Version Mismatch - Save Area Version Mismatch. The "save area" version changes are documented in the HMC release notes available in IBM fix central. Version updates have occurred at 7.7.8 (initial support), 8.8.1, 8.8.4 SP1, and 8.8.5. |
| o | Connection not allowed Reference code Connection not allowed 0009-0008-00000000 is returned when the FSP firmware and HMC versions are incompatible. The following is an example of attempting to manage a POWER5 server using HMC Version 8 Release 8.1.0 or later (which does not support the older POWER5 servers). GUI:  lssysconn CLI output: resource_type=sys,type_model_serial_num=9406-520*103E8FE,sp=primary,sp_phys_loc=unavailable,ipaddr=9.5.66.29,alt_ipaddr=unavailable,state=Version Mismatch,connection_error_code=Connection not allowed 0009-0008-00000000 To correct the issue, install a HMC version that supports the model being managed. |
| o | Unsupported Hypervisor If the server is configured for a hypervisor other then PowerVM, the HMC will return one of the following depending on the HMC version. HMC V8R8.1.0 Service Pack 1 and later:
Version Mismatch with Reference code Connecting 0000-0003-007687C8 The following is an example of attempting to connect a HMC to a POWER 8 server configured for Hypervisor Mode of OPAL. GUI:  CLI: resource_type=sys,type_model_serial_num=8286-41A*TU00010,sp=primary,sp_phys_loc=unavailable,ipaddr=9.5.31.10,alt_ipaddr=unavailable,state=Version Mismatch,connection_error_code=Connecting 0000-0000-00000000 To check the hypervisor setting first launch ASM. From the HMC, select the server in version mismatch then Operations > Launch Advanced System Manager (ASM) On models that support multiple hypervisors, the hypervisor mode setting can be found in ASM under System Configuration > Hypervisor Configuration. The Hypervisor Mode will show setting of "PowerVM" or OPAL.  If OPAL is the desired configuration then remove the connection from the HMC: Connections > Reset or Remove Connections, select Remove Connections and click OK. HMC is not supported with the OPAL Hypervisor. If PowerVM is the desired configuration then in ASM, select PowerVM and click Continue. Note: The setting can only be changed when the server is powered off. To power off the server, select Power/Restart Control > Power On/Off System. Click Save Settings and Power off. |
| o | Save Area Full HMC 7.7.8 and later. If the reference code is "Profile Data Save Area is full", refer to document N1019821, HMC Version 7 Release 7.8.0 Upgrade sizing. Note: For 7.7.8, ensure the mandatory fix (HM01388) or later is applied. |
| o | Only secondary FSP connected. Some Version 7.7 levels of HMC show version mismatch when only the secondary service processor (FSP) is connected on a dual FSP server. To check for the issue, run the command lssysconn -r all If there is a secondary service processor with state Connected but no primary (or primary shows no connection), this is the cause of the Version mismatch. Correct the networking problem to the primary. Example: resource_type=sys,type_model_serial_num=9117-MMB*1003C7R,sp=unavailable,sp_phys_loc=unavailable,ipaddr=172.16.254.254,alt_ipaddr=unavailable,state=No Connection,connection_error_code=Connecting 0000-0000-00000000 resource_type=sys,type_model_serial_num=9117-MMB*1003C7R,sp=secondary,sp_phys_loc=unavailable,ipaddr=172.16.255.253,alt_ipaddr=unavailable,state=Connected |
| o | Downlevel HMC There are two scenarios: 1. The FSP firmware does not allow the current version of the HMC to connect. This is rare as the design intent is to allow the minimum HMC version supported for the model to connect (with warnings) and update/downlevel the server firmware however there are exceptions. One example is models MMB/MHB, MMC/MHC firmware 780_54 and 770_076 and later that do not allow downlevel HMCs to connect due to a known security vulnerability. 2. The version of HMC does not recognize the service processor brand as a type that can be managed. The version of HMC must be at the minimum required by the model. For example, HMC Versions 4.1.0 to 7 can manage POWER5; earlier versions of V7 can manage i/p POWER 6 models; only V7R3.3 and later can manage a synergy POWER6 model. 9117-MMA: Later builds of the 9117-MMA are the converged model type which uses a new system brand of "S0" which indicates it's a "Synergy" system. The previous values were P0 for system p 9117-MMA and I0 for the system i 9406-MMA. HMC level V7.3.3 or higher is required to manage the S0 systems. Older versions of the HMC do not recoginze the VPD as a "version" of FSP that can be managed and will report "Version Mismatch". To check the brand (must be at power off state), access ASMI, expand System Configuration > Program Vital Product Data > System brand. To recover, upgrade the HMC to the minimum version required by the server model. |
| o | Incorrect resource type The wrong resource type is specified on the HMC for the service processor. For example, a bulk power controller (BPC) is added with a connection type "sys" or a FSP is added as a connection type "frame". lssysconn -r all may show that the resource type and MTMS do not match: resource_type=sys,type_model_serial_num=9458-100*99201PP,sp=unavailable, ipaddr=192.168.255.252,state=Version Mismatch resource_type=frame,type_model_serial_num=9458-100*99201PP,side=a,ipaddr=192.168.253.255, state=Failed Authenticati However, lssysconn -r all does not always show resource type mismatch errors. The example below is a 595 where the BPC and FSP switched addresses but lssysconn -r all still shows the incorrect MTMS and resource type: resource_type=sys,type_model_serial_num=9406-595*44K8137, sp=unavailable, ipaddr=192.168.255.253, state=version mismatch << 255.253 is the BPC ( frame, 9458-100) resource_type=sys,type_model_serial_num=9406-595*44K8137, sp=primary, ipaddr=192.168.254.255, state=connected resource_type=frame,type_model_serial_num=9458-100*9922006W, side=unavailable, ipaddr=192.168.255.254, state=version mismatch << 255.254 is the FSP (sys, 9406) resource_type=frame,type_model_serial_num=9458-100*9922006W, side=b, ipaddr=192.168.254.254, state=pending authentication - password updates required To recover: a. remove the existing resources by ip rmsysconn --ip <ip> -o remove b. Rediscover the resources The recommended procedure is to run mksysconn -o auto and let the HMC rediscover them as the correct type. Alternately add the resources using mksysconn however first verify the address and type using ASM. |
| o | Incorrect or damaged VPD data. There may be a hardware error preventing the service processor from reading VPD or invalid VPD information was entered during a hardware upgrade or repair action. The error is usually seen after an failed MES upgrade or other hardware error/repair action involving the VPD. To recover, search for any serviceable events related to VPD. Review the hardware repair procedures concerning incorrect VPD. After fixing the VPD, reset the HMC connection. |
[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"HMC","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]
Historical Number
393960006
Was this topic helpful?
Document Information
More support for:
Power System Hardware Management Console Physical Appliance
Software version:
Version Independent
Document number:
637977
Modified date:
22 September 2021
UID
nas8N1015271