IBM Support

Upgrading or Replacing the HMC Hardware



This document describes the procedure for replacing an existing HMC. The procedure requires re-entering or replicating the configuration from the old HMC to the new HMC.


Replacement implies an existing HMC is being removed and a new HMC model type or serial number is installed where much of the HMC configuration, specifically the host name and IP address, will be the same on the new HMC. Common examples include the following:

o "Upgrading" an older model such as 7042-CR* with a newer model such as 7063-CR1 or 7063-CR2

o A same model swap where only the serial number changes.

o "Upgrading" an older model to virtual HMC (vHMC).

Resolving The Problem

If this procedure is not followed, some of the errors which may be encountered include the following:

o Open Serviceable Events which cannot be closed
o Platform Event Logs which are not reported or called home through Serviceable Events
o RMC communication problems between the HMC and partitions
o Errors attempting to restore a backup from another HMC model/type/serial (which is unsupported)
o Errors attempting to restore upgrade data from another HMC model/type/serial (which is unsupported, on older model HMC's CR8 and below) See exception.
 * There is an exception. Data can be migrated to a new hmc using the saveupgdata and rstupgdata commands for the following source/target combinations: 
        1. V9 R2 (7042-CR9) to V10 R1 (7063-CR1 or CR2) restore upgrade data is fine.  Run Saveupgdata -r diskusb --migrate -i netcfg on the V9R2 HMC 
        2. HMC (7063-CR1 or CR2) is at V9R2M952 or V10R1M1010, you can rstupgdata -r usb --migrate
        3. For  7042-CR9 or 7063-CR1 V9 R1 to V9 R2, min level on target should be 952 or later.
        4. 7063-CR1 or CR2 V9 R2 and 1011 or later for V10 R1 - these min levels  are specific to  migrate PCM  data

Other considerations
Verify HMC Version / release
If the HMC manages a server, the new HMC must be at the same version/release or newer than the model being upgraded. "down leveling" the HMC version/release is not supported. Connecting a down level HMC to a server will result in a "version mismatch - save area version mismatch" connection state (HMC 7.7.8 and higher) or corruption of the partition configuration (HMC 7.7.7 and earlier).

Dual HMCs
When two HMCs manage the same server both HMCs must be at the same version/release.
- If the new HMC is at the same version and release as the existing HMCs then no special action is required.
- If the new HMC is at a higher version/release then the existing HMCs, then the dual HMC must be upgraded to the same version/release as the new HMC model. The order to perform the upgrades varies:
a) Existing HMCs are V7R7.8 or later
The order does not matter. No special action is needed however when the first upgraded HMC connects to the server, the down level HMC may show the server in "save area version mismatch" state. The down level HMC will not be able to manage the server until it has been upgraded to the same version.

b) Existing HMCs are Version 7.7.7 or lower
To prevent corruption of the partition configuration, you must ensure the down level HMC is disconnected from the servers before connecting the V7R7.8 or higher HMC. See "Configure the new HMC" step 3 for more information.

Before removing the old HMC
1. Close all serviceable events.

a. Verify that all serviceable events reported against a managed server have been reported to IBM and repaired.
b. Close the serviceable events.
Set a new controller for any Power Enterprise Pool
When Power Enterprise Pools (PEP 1.0) are used to manage Mobile Capacity on Demand processors and/or memory, the recommend procedure is to set another HMC in the pool as controller before continuing with the next step. If there is only one HMC for the pool then the HMC can be "re-mastered" after the upgrade or control can be transferred to the new HMC if the new HMC will have a different ip address and hostname.

For additional information, refer to the following
3. Permanently remove all server connections.

a. Record all current connections:
  • 1) Access the restricted shell
    Local HMC: Click HMC Management, Open Restricted Shell Terminal.
    Remote: ssh to the HMC.
    2) Run lssysconn -r all
    3) Save the output.

b. Expand Systems Management, Servers.

c. For each server, remove the connection:
  • 1) Select the server.
    2) Expand Connections, select Reset or Remove Connections, select Remove Connection, click OK.

d. For each frame, remove the connection.
  • 1) Access restricted shell
    2) Run lssysconn -r all | grep type=frame
    3) Record the IP address of the frame connections listed in the output. (Example below in bold text: and
    • lssysconn -r all | grep type=frame

    4) For each listed IP address, issue the command: rmsysconn --ip <ip of frame> -o remove
    Example: rmsysconn --ip -o remove

e. Ensure all connections have been removed.
  • 1) Access restricted shell
    2) Run lssysconn -r all
    3) Verify that there are no connections listed as shown in the example below:
    lssysconn -r all
    No results were found.
Record configuration information

Record any information that you intend to transfer. Note that HMC data replication can be used to replicate information onto the new hardware. Information that can be replicate includes: Customer contact information data; User data (user profiles, task roles and resource roles); Outbound connectivity configuration data. A different IP address will be needed temporarily to perform the replication.

For a list of items to record see the document, Items to Document Prior to Performing Scratch Installation of the HMC at
5. Remove the HMC.

Configure the new HMC
Note: Restoring upgrade data or backup HMC data to a different HMC is not supported.
1. Configure Network Settings.

Use the Setup Wizard or HMC Configuration, Change Network Settings to configure the settings recorded earlier.
2. Configure additional settings.

Configuration data cannot be restored from one HMC to another model; however, some information such as users, roles, and call home configuration can be replicated. For further information on replication, refer to this URL:

Additional settings to consider manually restoring are as follows:
* Scheduled operations
* Manage Serviceable Event Notification
* Existing system plans
* User home directory data
3. Connect to server.
Note: If the server is managed by another HMC, verify the other HMC is at V7R7.8 or higher. If it is V7R7.7 or lower (and this new HMC is at V7R7.8 or higher) then stop. You must upgrade HMC2 or remove the server connections from HMC2 before continuing. If the 2nd HMC's hardware will also be upgraded you must perform "Before removing the old HMC" steps 1-3 on this second HMC before continuing. If the 2nd HMC's hardware will not be changed, then you must do one of the following before proceeding:
1) Scratch install or upgrade HMC2 software to the same version/release
2) Remove all server connections (or disconnect the Ethernet cable to the servers) until after HMC2 software has been upgraded to the same version/release.
Failure to do so will result in partition configuration corruption.

Depending on the server firmware level and type of network configuration, the servers may reconnect automatically.

a. Expand Systems Management, Servers.

b. Reconnect the servers and frames.
For servers connected on the private DHCP server network, you should wait approximately 5 minutes for the server to reconnect. Note: For POWER5 servers, this can take over 20 minutes. To force a rediscovery immediately, do the following:

1) Disconnect the Ethernet cable from the Server's FSP HMCx port
2) Wait one minute
3) Reconnect the Ethernet cable
4) Server should appear within 3 minutes.

Servers connected using an open network need to be manually added.

c. For each connection, enter the HMC access password.

d. Verify all servers and frames are connected:
1) Access the restricted shell
Local HMC: Click HMC Management, Open Restricted Shell Terminal.
Remote: ssh to the HMC.
2) Run lssysconn -r all
3) Compare the output to the output from the original HMC.
4. Re-Configure Power Enterprise Pools.
If applicable, add the new HMC back to the Power Enterprise Pool.  If there is no other HMC managing the pool recover the pool.
For additional information, refer to the following  and

[{"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


Document Information

Modified date:
09 February 2024