How To
Summary
This document covers how to upgrade a vHMC on x86 from V9R1+ with mandatory fix MH01857 to V9R2M950
Environment
Steps
Troubleshooting
Problem
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.
Prerequisites
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)
https://delivery04.dhe.ibm.com/sar/CMA/HMA/09aw6/1/vMH01857.readme.html
(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.
OR
- 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:
FW740_156 (740.90)
FW760_087 (760.50)
FW770_098 (770.50)
FW780_068 (780.21)
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.
8. Review the readme file
Review all additional "upgrade notes" found in the V9 R2 release notes. The readme file release notes for HMC V9 R2 M950 Recovery Media and mandatory fix can be found in IBM Fix Central at
https://delivery04.dhe.ibm.com/sar/CMA/HMA/09arr/5/vMH01869.readme.html
9. Review repair and close all service events
See https://www.ibm.com/support/pages/preparing-upgrade-or-install-hmc
########################################################################################
NETWORK
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 V9R2_network_images_x86.zip from Fix Central. From the Fix Central site, select MH01869 vHMC for x86 deploy image, click continue. Then find V9R2_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/v950/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:
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. |
||||||||||||||||||||||||||||||||||||||
| 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 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. |
To obtain fixes for V9R2M950, refer to this link -
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
19 July 2023
UID
ibm16372280