IBM Support

Items to Document Prior to Performing Scratch Installation of the HMC

Technote (troubleshooting)


This document describes items that you should make note of prior to performing a scratch installation of the HMC. This document can also be used as a checklist to manually transfer settings to another HMC for situations such as HMC hardware upgrades or converting to vHMC.

Resolving the problem

If you have access to the HMC prior to doing a scratch installation, making note of the following items will make it easier to recover the HMC after the scratch install. In the typical basic configuration, the only required setting is step 1, the HMC network information.

Note: Most information can be gathered using the GUI or command line interface (CLI). The command line interface option is designated "CLI: " in the steps below.

1. HMC Networking information

HMC Version 6:
HMC Management -> HMC Configuration -> Customize Network Settings.

HMC Version 7 and later:
HMC Management -> Change Network Settings

Both Versions:
1) Identification tab
Record the Console name, Domain name, and Console Description.
2) Lan Adapters tab
Record the "Detail" information for each LAN adapter: Private or Open Network; is DHCP server enabled; the DHCP Address range or the Static IP Address. Click the Firewall settings and record.
3) Name Services tab
Record if DNS is enabled as well as DNS servers and domain suffix search order.
4) Routing tab
Record the default gateway. Record additional routes if any (rare).

CLI: lshmc -n

2. HMC Version
Record the current verions as you must ensure you install with the same version and release or newer.
Note: Backleveling a HMC is not supported and can result in corruption of the partition configuration information on any server managed by the HMC.

HMC Version 6:
In the navigation area, expand Licensed Internal Code Maintenance, and select HMC Code Update. In the Status area on the right, the current version, build level, and PTF list can be viewed. To view the entire list of installed fixes, it might be necessary to scroll the frame to the right or click Display HMC Version.

HMC Version 7 and later:
From Version 7 and Version 8 "classic" login:
Select Updates and record the information under HMC code level.

For Version 8 "enhanced" login:
Click the help icon in the upper left corner then select About

CLI: lshmc -V

3. Managed Servers: Verify/reset Server HMC Access Password

After the scratch installation, the HMC will automatically re-discover servers managed over the private DHCP network. Servers managed by static ip addresses will need to be manually added. When the HMC re-connects to the server, it will prompt for the HMC Access Password. If you do not know this password, you can either reset it prior to the scratch or it can be reset after the scratch installation.

For each managed server,
a) Record the ip address(es)

    HMC Version 6:
    Server and Partition > Server Management
    Select Status. Record the ip address(es).

    HMC Version 7 and later:
    Select the server then click Connections > Service Processor Status. Record the ip address(es).

    CLI record all ips:   lssysconn -r all

b) Verify password
    HMC Version 6:
    Server and Partition > Server Management
    Select the server then click menu "Selected" > "Update Managed System Password"

    HMC Version 7 and later:
    Select the server then click Operations > Update Password

    All Versions
    On the update password panel, enter the what you believe is the password using the same password for current, new and verify.  If it is correct it will complete with no error.  If it is incorrect it will return an incorrect password error.

    To reset a lost HMC access password see

    CLI verify password: chsyspwd -m <system> -t access --passwd <current password> --newpasswd <current password>

4. Record Scheduled Operations

HMC Version 6:
HMC management -> HMC Configuration -> Scheduled Operations.

1) Select all the targets by clicking on the first one, then Shift and click on the last one in the list. This will highlight all the targets. Next, click OK.
2) Record all the scheduled operations so that they can be rescheduled after the scratch install.

HMC Version 7 and later:
1) Select each Managed System, select the task Operations, and Scheduled Operations. Record any scheduled operations.
2) Select each Partition, select the task Operations, then Scheduled Operations. Record any scheduled Operations.

CLI not supported

5. Record the Call home information

HMC Version 6:
Service Applications -> Remote Support -> Customize Customer Information

Record the information on this screen.

Service Applications -> Service Agent -> Transmit Service Information

Record the information on this screen

HMC Version 7 and later:
Service Management

Record the information under:
Enable Electronic Service Agent
Manage Outbound Connectivity
Manage Customer Information

CLI (not supported at older releases)
lssacfg -t callhomeserver
lssacfg -t custinfo
lsproxy -t sslproxy

6. Record Additional User Profiles

HMC Version 6:
HMC Management -> HMC Users

HMC Version 7 and later:
HMC Management

Both Versions:
If you've created any users or Task Roles beyond what comes as default. Select the Manage HMC Users and Access and record the Users and what task roles are assigned to those users.
Select the Manage Access Task Roles and Managed Resource Roles. All default task roles start with hmc.

The --script option lists the output in a format that can be used as input the mkhmcusr and mkaccfg commands to recreate them.
lshmcusr --script
lsaccfg -r taskrole --script
lsaccfg -t resourcerole --script

7. Record remote access settings HMC

HMC Version 6:
HMC Management -> HMC Configuration

Click on each one and check if they are enabled or disabled:
o Enable or Disable Remote Command Execution
o Enable or Disable Remote Virtual Terminal

HMC Version 7 and later:
HMC Management

Click on each one and check if they are enabled or disabled:
o Remote Command Execution
o Remote Virtual Terminal
o Remote Operations

CLI: lshmc -r

8. Additional settings
Additional but less common settings to check or save include:

o Email or SNMP notification settings
Record Service Management > Manage Serviceable Event Notification settings
CLI: lssacfg -t email

o Export any existing system plans
Under System Plans, select any existing system plans and click Export System Plan to save.

CLI: cpsysplan

o Save any User home directory data
Users can use USB flash, scp or sendfile commands to copy and export/save any existing user files.
For example to save to usb: cp /home/* /media/sdb1

o Kerberos/LDAP/NTP
Record settings under HMC Management for
Configure KDC, Configure LDAP, Change Date and Time (timezone, NTP server etc).
CLI: lshmc -r
lshmcldap -r config

o Performance/Utilization settings
For each server, Operations > Change Sampling Rate; record if its enabled and the interval.
For each server, click Performance; note if its enabled and the number of days to store data.

CLI: lslparutil -r config  

o Systems Management > Power Enterprise Pools
HMC 7.7.9 and later: There are additional considerations if the HMC is the primary HMC for a Power Enterprise Pool of Mobile Capacity on Demand (CoD) resources. If the HMC is the primary HMC then one of the following must be done prior to re-installing the HMC:
Option 1 - Configure a backup HMC and failover to make it the new master HMC;
Or option 2 - Locate the PEP configuration xml file needed to create a new master. This file is made available on the  Capacity on Demand (CoD) Web site.
For more information on failing over see

CLI: lscodpool --level pool

Historical Number


Document information

More support for: HMC Firmware

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: N1011269

Modified date: 19 May 2013

Translate this page: