This document covers how to upgrade a vHMC on x86 from V9R1+ with mandatory fix MH01857 to V9R2M950
This document provides instructions to upgrade vHMC on x86 from Version 9 Release 1 Maintenance 910 + MH01857
Resolving The Problem
These instructions apply to x86 based vHMCs 5765-HMW.
Before upgrading, complete the following:
1. Verify the vHMC is V9R1M910 or higher
2. Check disk size of current image. If it is 160Gb then we recommend upgrading to the new image that uses 500GB by following these steps:
- From the current HMC version (e.g. HMC V8.860.0 to V9 R1 M910), upgrade to HMC V9 R2 M950
- When the upgrade is complete the HMC is now at a new version but still has a 160GB disk.
- Perform a Critical Console Data backup, excluding network information and store the backup to a remote location.
- Deploy the new HMC V9 R2 M950 image which uses a 500GB disk.
- After the HMC boots up with the 500GB disk, restore the Critical Console data
3. Check memory - increase memory to 16GB minimum (32Gb recommended)
4. Verify vHMC minimum level and that the "Upgrade interim Fix" is applied.
The minimum HMC levels required for the upgrade are:
Mandatory fix for vHMC on x86: MH01857 (This fix can be installed on V9R1M910 or higher, and has to be the last fix installed prior to the upgrade.)
(V9R1 + MH01857)
(The MH01857 fix can be found on Fix Central under, Power Systems Management Consoles, Power Hardware Management Console virtual appliance for x86 (V9R1, All platforms), then click the +Show Patched By, under > vHMC V9R1M941 for x86
5. Reboot the vHMC
If the vHMC has not been restarted recently, restart before you begin the upgrade. To reboot, either:
- Use the GUI task HMC Management > Console Management > Shut Down or restart the Management Console > Restart HMC then click OK.
- Use the CLI command hmcshutdown -r -t now
6. Verify Server Model and Firmware are compatible
All POWER7 processor-based servers must have a firmware level that supports TLS1.2 before the hmc upgrade. The minimum levels required are:
Failure to update the firmware to the minimum levels before upgrade result in a persistent no connection state.
Management of POWER6 and older servers is not supported by HMC V9 Attempts to manage POWER6 and older servers result in a connection state of Version Mismatch and connection_error_code “Connection not allowed".
7. Server managed by dual (redundant) HMCs require that both HMCs be upgraded to the same release
When a server is managed by dual (or redundant) HMCs, both HMCs must be upgraded to the same release.
When upgrading multiple HMCs that are part of a Power Enterprise Pool (PEP) from 9.1.0 to 9.2.950, it is recommended to upgrade a backup HMC first. Next set the upgraded HMC as the primary, then upgrade the previous primary. This ensures a primary is always available.
After one HMC is upgraded the servers on the redundant HMC can go to a "Version Mismatch" state, with reference code "Save area version mismatch". This state clears when the redundant HMC is upgraded.
9. Review repair and close all service events
This section describes how to perform the upgrade over the network instead of from Recovery DVD. The network upgrade can be done by using FTP, sftp, or nfs protocol. If the HMC does not have direct internet access the network upgrade files can be staged on a local server (see "Using 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 http://www.ibm.com/support/docview.wss?uid=nas8N1022259.
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.
|a.||Download the V9.2.950 network upgrade files to the HMC.
To upgrade from a local server instead of direct from the IBM FTP site, refer to "Using a local server" section of this page.
Open Restricted Shell (or ssh session) and type the following command:
getupgfiles -h public.dhe.ibm.com -u anonymous --passwd anonymous -d /software/server/hmc/network/v950/x86
The parameters of the getupgfiles command:
The following files are downloaded to the directory indicated:
While the download is running, there is no indication of progress in the restricted shell. To monitor progress, open another restricted shell session and monitor the files and file sizes. For example, the following command loops indefinitely querying the file sizes every 30 seconds: while true; do ls -l /hmcdump ; ls -l /hmcboot ; sleep 30; done (Use ctrl+c to end).
Once the files have all been downloaded successfully, the getupgfiles command returns to the command prompt and the ls -l command will no longer list the files in the directory as the target directories are unmounted.
|b.||Set the HMC to do the next reboot from the special location on the hard disk drive where the downloaded V9 files are stored by typing the following command:
chhmc -c altdiskboot -s enable --mode upgrade
Note: Remove any USB flash drive that contains HMC backup Management Console Data before performing a network upgrade. Failure to remove the drive results in failed network upgrade.
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 V9.2.950 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.
|e.||Install the required fixes for V9.2.950 using the link provided below.|
1. Use FTP to do a binary download of the upgrade files from the IBM server to a directory on a local server:
IBM Server: public.dhe.ibm.com/software/server/hmc/network/v950/x86
2. Verify the download Use a BSD checksum tool to verify that the checksum of each file matches the expected checksum documented in the table above.
3. Perform the upgrade as described above. However, in Step 1, modify the getupgfiles command to point to your local FTP server. For example:
getupgfiles -h my server -u my userid --passwd my password -d /my directory
To obtain fixes for V9R2M950, refer to this link -
08 December 2021