How To
Summary
This document covers how to upgrade a vHMC on x86 from V9R2 or V10R1 to V10R2M1030
Objective
Upgrade the vHMC
Prerequisites
Before upgrading, complete the following:
1. The minimum HMC levels required to perform install or upgrade via network to HMC V10 R2 M1030 are:
- Fix Central V9R2M950
- Find HMC V9R2M950 Recovery, click the + Show Patched By
- Mandatory fix for vHMC on x86: MH01941 (9.2.950.7 x86_64)
- (This fix must be the last fix installed, prior to performing this Upgrade. It is not cumulative)
- Find HMC V9R2M950 Recovery, click the + Show Patched By
- Fix Central V10R1M1010
- Find HMC V10R1M1010 Recovery, click the +Show Patched By
- Mandatory fix for vHMC on x86: MF70430 (10.1.1010.3 x86_64)
- (This fix must be the last fix installed, prior to performing this Upgrade. It is not cumulative)
- Find HMC V10R1M1010 Recovery, click the +Show Patched By
2. Minimum memory supported for vHMC is 16GB and disk size should be 500GB.
3. HMC V10 R2 M1030 provides support for managing Power10, POWER9 & POWER8 processor-based systems.
Supported Combinations - HMC and System Firmware Supported Combinations
4. Management of POWER7 and older servers is not supported by HMC V10 R2. Attempts to manage POWER7 and older servers will result in a connection state of Version Mismatch and connection_error_code “Connection not allowed 0009-0008-00000000”.
5. If two HMCs manage the same server, both HMCs must be at the same version, release and maintenance level.
6. Review the readme file
Review all additional "upgrade notes" found in the V10 R2 release notes. The readme file release notes for HMC V10 R2 M1030 Recovery Media and mandatory fix can be found in IBM Fix Central at https://download4.boulder.ibm.com/sar/CMA/HMA/0b1mi/3/vMF70432.readme.html
Review all additional "upgrade notes" found in the V10 R2 release notes. The readme file release notes for HMC V10 R2 M1030 Recovery Media and mandatory fix can be found in IBM Fix Central at https://download4.boulder.ibm.com/sar/CMA/HMA/0b1mi/3/vMF70432.readme.html
7. Review repair and close all service events
8. Reboot the vHMC
If the vHMC has not been restarted recently, restart before you begin the upgrade. To reboot, either:
- Use the GUI task Console Management > Console Management > Shut Down or restart the Management Console > Restart HMC then click OK.
OR
- Use the CLI command hmcshutdown -r -t now
- Use the GUI task Console Management > Console Management > Shut Down or restart the Management Console > Restart HMC then click OK.
OR
- Use the CLI command hmcshutdown -r -t now
Environment
HMC V10 R2 M1030 supports the following hypervisors:
- x86 : KVM, XEN, ESXi (6.5 / 7.0 / 7.0.2)
Steps
NETWORK (Make sure pre-req fix is installed, see #1. above)
Instructions for upgrading from a network server
The HMC can no longer be upgraded directly from public.dhe.ibm.com. HMC network upgrade is supported from Fix Central using the .zip file option, or from public.dhe.ibm.com and staging the upgrade on a local server.
Restricted Shell Access
This upgrade method requires restricted shell command-line access.
From the local HMC, select HMC Management > Console Management > Open a Restricted Shell terminal
From a remote location, restricted shell is available through the ssh protocol. For information on how to access HMC command line remotely see
Step 1: Save Profile Data
Perform a Save Profile Data for each managed system to save an extra copy of partition/profile configurations. For dual HMCs managing the same server this step is only needed on the upgrade of the first HMC. It cannot be run on HMC with a server in "version mismatch - save area version mismatch" state.
At the command prompt, enter the following command to save profile data for all servers:
lssyscfg -r sys -F type_model*serial_num | while read machine; do bkprofdata -m "$machine" -f Beforeupgrade$(date +%Y%m%d) ; done
Step 2: Save Upgrade Data
A Save Upgrade Data task must be done to preserve information on the HMC before performing the upgrade. You must upgrade immediately after the Save Upgrade Data task. If you restart the HMC again without doing the upgrade, you must log in and run the Save Upgrade Data task (to hard disk drive) again before performing the upgrade. CLI command - saveupgdata -r disk
Perform a Save Profile Data for each managed system to save an extra copy of partition/profile configurations. For dual HMCs managing the same server this step is only needed on the upgrade of the first HMC. It cannot be run on HMC with a server in "version mismatch - save area version mismatch" state.
At the command prompt, enter the following command to save profile data for all servers:
lssyscfg -r sys -F type_model*serial_num | while read machine; do bkprofdata -m "$machine" -f Beforeupgrade$(date +%Y%m%d) ; done
Step 2: Save Upgrade Data
A Save Upgrade Data task must be done to preserve information on the HMC before performing the upgrade. You must upgrade immediately after the Save Upgrade Data task. If you restart the HMC again without doing the upgrade, you must log in and run the Save Upgrade Data task (to hard disk drive) again before performing the upgrade. CLI command - saveupgdata -r disk
Step 3: Upgrade the HMC to V10R2M1030
| a. |
Download the V10R2_network_images_x86.zip from Fix Central. From the Fix Central site, select MF70432 vHMC for x86 deploy image, click continue. Then find V10R2_network_images_x86.zip and download to your PC. Then get the .zip file moved to your local server. Make sure the file is unzipped, which will give you the necessary network files to perform this upgrade, or use https://public.dhe.ibm.com/software/server/hmc/network/v1030/x86/ to download the network files to your local server.
Open Restricted Shell (or ssh session) and type the following command: getupgfiles -h myserver -u myuser --passwd mypassword -d /mydirectory The parameters of the getupgfiles command:
The following files are downloaded to the directory indicated:
Once the files have all been downloaded successfully, the getupgfiles command returns to the command prompt. |
||||||||||||||||||||||||||||||||||||||
| b. | Set the HMC to do the next reboot from the special location on the hard disk drive where the downloaded V10 files are stored by typing the following command: chhmc -c altdiskboot -s enable --mode upgrade |
||||||||||||||||||||||||||||||||||||||
| c. |
Reboot the HMC using one of the following methods:
Option 1. HMC GUI: HMC Management > Console Management > Shut Down or restart the Management Console > Restart HMC then click OK Option 2. Restricted shell command: hmcshutdown -t now -r Note: The initial reboot can take 30 - 45 minutes. Do not reboot or power off; wait for the boot to complete. Once the HMC reboots, the installation starts and typically takes about an hour. After the installation of V10R2M1030 is complete, you should be able to remotely access the HMC again.
|
||||||||||||||||||||||||||||||||||||||
| d. | At the Hardware Management Console login prompt, log in using your user ID and password. |
||||||||||||||||||||||||||||||||||||||
___________________________________________________________________________________________________________________________
Install required Fixes - https://www.ibm.com/support/pages/node/6857333
___________________________________________________________________________________________________________________________
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGGSNP","label":"Hardware Management Console V9"},"ARM Category":[{"code":"a8m0z000000bowEAAQ","label":"Hardware Management Console"},{"code":"a8m0z000000cw1DAAQ","label":"Hardware Management Console-\u003EHMC Upgrade\/Update"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.2.95;and future releases"}]
Was this topic helpful?
Document Information
Modified date:
01 September 2023
UID
ibm16846016