This document provides instructions to upgrade model 7042 and x86 vHMC HMC from Version 8.8.6 or later to Version 9 Release 1 Maintenance 910 (V9 R1 M910)
This release is out of service support, and the document will not be updated.
Before you begin this Upgrade, please note,
The HMC can no longer be updated directly from public.dhe.ibm.com. HMC update is supported directly from Fix Central by using SFTP option or by staging the updates on a local server.
The getupgfiles command will no longer support connecting to public.dhe.ibm.com directly. Instead, first download the network upgrade files from Fix Central or from public.dhe.ibm.com using ftps or https and place them on a local FTP server.
These instructions apply to x86 based HMCs (model 7042 or vHMC on x86). They are not intended for ppc based vHMC or model 7063.
(If you need to perform a Scratch (clean) Installation use this link) - https://www.ibm.com/support/pages/node/6470281
Prerequisites
Complete the following:
1. Verify HMC model is compatible with 9.1.0
HMC V9 R1 M910 supports the following HMC models:
· X86: 7042-CR7, 7042-CR8, 7042-CR9, 7042-OE1, and 7042-OE2
2. Verify HMC minimum level
The minimum HMC levels required for the upgrade are:
HMC 8.8.6 + SP1(or supersede)
HMC 8.8.7 + mandatory fix (MH01706/MH01707) or supersede.
3. Confirm machine type model and serial number are correct
Use one of the methods to verify that the Machine Type Model and Serial Number (MTMS) matches the information on the tag on the front of the physical HMC. If they do not match, do not attempt the upgrade. To resolve the problem, contact IBM Hardware at 1-800-426-7378 (800-IBM-SERV), Option 1 for hardware, and request a BIOS flashes to correct the MTMS:
| o |
On the HMC GUI interface, select Updates in the left navigation panel. Find Model Type and Serial number in the HMC Code Level section of the right panel. |
| o |
From a restricted shell command line, type the following command and press Enter: lshmc -v *TM is the machine type model, and *SE is the serial number. |
4. Reboot the HMC
Restart the HMC 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 command hmcshutdown -r -t now
5. Verify Server Model and Firmware are compatible
All managed servers must be a POWER7 or later model. 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".
Click here for a complete list of supported combinations of HMC V9 code levels and server firmware levels. While the HMC can perform basic management tasks and upgrades on earlier servers, servers that do not comply to the supported level need to be updated soon after the HMC upgrade is complete.
6. Review the readme file
The readme file release notes for HMC V9 R1.0 Recovery Media and mandatory fix can be found in IBM Fix Central at https://download4.boulder.ibm.com/sar/CMA/HMA/07hb4/8/MH01733.readme.html
7. Server managed by dual (redundant) HMCs require that both HMCs are 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 8.8.6 to 9.1.0, upgrade a backup HMC first, set the upgraded HMC as the master, then upgrade the previous master. This will ensure a master 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 repair and close all service events
See https://www.ibm.com/support/pages/preparing-upgrade-or-install-hmc
9. "Classic" login is not available.
HMC V9 R1 M910 does not allow “Classic” GUI log in. The functions that were previously available in the HMC Classic interface are now available in the HMC Enhanced+ interface. For more information, see:
· http://www.ibm.com/support/docview.wss?uid=nas8N1022258
10. Select one of the following tabs for instructions on the upgrade method you want to use:
o .iso images: Instructions for downloading the fixes and installing them from USB flash or optical media.
o Ordering Using DVDs: Instructions for ordering optical media from IBM and installing from media.
o Network: Instructions for upgrading the HMC over the network; either directly from the IBM FTP site or alternately, from a local FTP server.
11. Virtual HMC (vHMC) must be upgraded by using the Network option.
We recommend upgrading to the new image that uses 500GB by following the steps:
- From the current HMC version (e.g. HMC V8.860.0), upgrade to HMC V9 R1 M910
- 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 R1 M910 image which uses a 500GB disk.
- After the HMC boots up with the 500GB disk, restore the Critical Console data
.iso images
|
Instructions for downloading the image and upgrading from media
Step 1: Obtain HMC 9.1.0 .iso image
1. Download and burn the HMC Version 9.1.0 Recovery DVD: HMC_Recovery_V9R1M910_1_x86.iso
2. Burn the .iso as an image to DVD-R media.
Step 2: Save Profile Data
Use one of the following options to 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.
Option 1: Use HMC GUI interface
| a. |
Expand Resources, then All Systems |
| b. |
Select the first managed system by checking the box in front of the server name. |
| c. |
Under Actions select View All Actions > Legacy > Manage Partition Data > Backup. |
| d. |
In the Profile Data backup window, type a name for the backup file, and click OK. |
| e. |
You get a window that the profile data was backed up. Click OK. |
|
Repeat a through e for each additional system managed by this HMC. Once you have a partition data backup for each managed system, continue with Step 3.
|
Option 2: Use restricted shell command line
At the command prompt, enter the following command, which saves 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 3: 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 again before performing the upgrade.
| 1. |
Prepare media to use for Save Upgrade Data. You need a USB flash drive.
USB flash drive must be formatted FAT32 with a single partition and it cannot be password protected. Plug the flash drive into a USB port on the front of the HMC. Wait until you hear 3 beeps (or approximately 1 minute) for the HMC to detect the flash drive.
Note: Save Upgrade Data overwrites any existing save upgrade data on the media. It will not overwrite any backup Management Console Data already on the media.
|
| 2. |
Save Upgrade Data can be performed by using either HMC GUI or restricted shell command line.
Use the HMC GUI:
a. Select HMC Management. > Console Management
b. Select Save Upgrade Data.
c. Select media type USB flash drive, click Next, and then click Finish.
Use restricted shell command line:
Use the following command specifying "diskusb" for USB flash drive.
saveupgdata -r diskusb
|
| 3. |
Wait for the Save Upgrade Data task to complete. If the task fails, contact your next level of support before proceeding. If the Save Upgrade Data task is successful, the following optional procedure can be performed to verify the data:
Local HMC: Select HMC Management > Console Management > Open a Restricted Shell Terminal
Remotely: Log in via ssh.
b. Mount the media:
1. Run the command lsmediadev to determine the mount point of the USB flash drive. In the example, USB flash drive is /media/sda1
device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD
device=/dev/fd0,mount_point=/media/floppy,type=2,description=internal diskette drive
device=/dev/hda,type=6,description=internal hard disk drive
device=/dev/sda1,mount_point=/media/sda1,type=3,description=USB flash memory device
2. Run the command mount (that is, mount /media/sda1 for USB flash drive)
c. Run the command ls –l by using the same mount point as in step b - "example" ls -l /media/sda1
d. Verify that there are five tar files with the following names:
ACMSaveData.tar
RSCTSaveUpgrade.tar
SaveCCFWUpgradeData.tar
SaveHSCSystemUpgradeData.tar
SaveProfileDataUpgrade.tar
If any of these tar files are missing, contact your next level of support.
e. Issue the command umount by using the same mount point as in step b
Note: The Save Upgrade Data is saved to the hard disk drive on the HMC as well as the USB flash drive. The Save Upgrade Data on the media is used only to recover from an unexpected error under the direction of support personnel.
|
| 4. |
Once the Save Upgrade Data task is successful, remove the USB flash drive.
|
Step 4: Upgrade HMC to 9.1.0 (from Recovery Media)
Do the following at the HMC interface to upgrade the HMC by using the Recovery DVD.
| 1. |
Insert V9.1.0 recovery media (which was either ordered from IBM or downloaded and burned to DVD as indicated above) into the DVD-RAM drive.
|
| 2. |
Click HMC Management, then click the Shutdown or restart menu option.
|
| 3. |
Select restart HMC and click OK. Note: If the HMC fails to restart from optical, the boot manager might need to be called (in other words, press F12 during the boot process) in order to get the HMC to boot from the optical drive.
|
| 4. |
The HMC reads the media in the DVD-RAM drive and displays the Hardware Management Console Install Wizard window. Highlight Next button (use tab/alt-Tab or arrow keys to move), and press Space bar or Enter to select.
Note: If the Save Upgrade Data (Step 3) was not performed, you will see a warning window that save upgrade data was not found on the hard disk. Cancel the upgrade, remove the recovery media from the DVD drive, reboot the HMC, complete Step 3 to Save Upgrade Data, then start the upgrade process again.
|
| 5. |
Using tab or arrow keys to move the cursor and the space bar to select an option, select Upgrade to a new release (need asterisk on Upgrade to a new release as shown):
( * ) Upgrade to a new release
( ) Install
Highlight Next button, and press Enter.
|
| 6. |
On Upgrade Confirmation screen, highlight Finish, and press Enter to start the Upgrade process.
|
| 7. |
The HMC installs V9 from the media, restores the data preserved by the Save Upgrade Data task, and then completes the booting process.
Note: The initial reboot can take 30 - 45 minutes. Do not reboot or power off; wait for the boot to complete. IBM is investigating a rare issue where the HMC upgrade can indefinitely hang at "Processing SaveHSCSystemUpgradeData.tar....." If the HMC stays at "Processing SaveHSCSystemUpgradeData.tar....." for more than one hour contact IBM support for further problem determination.
|
| 8. |
Select "Log on and launch the Hardware Management Console web application", then log in using your user ID and password. |
|
Ordering / Using DVDs/CDs
|
Instructions for ordering the DVD and upgrading from media
Step 1: Order the HMC Version 9.1.0 Recovery DVD: MH01733
Step 2: Save Profile Data
Use one of the following options to 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.
Option 1: Use HMC GUI interface
| a. |
Expand Resources, then All Systems |
| b. |
Select the first managed system by checking the box in front of the server name. |
| c. |
Under Actions select View All Actions > Legacy > Manage Partition Data > Backup. |
| d. |
In the Profile Data backup window, type a name for the backup file, and click OK. |
| e. |
You get a window that the profile data has been backed up. Click OK. |
|
Repeat a through e for each additional system managed by this HMC. Once you have a partition data backup for each managed system, continue with Step 3.
|
Option 2: Use restricted shell command line
At the command prompt, enter the following command which saves 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 3: 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 again before performing the upgrade.
| 1. |
Prepare media to use for Save Upgrade Data. You need a USB flash drive.
USB flash drive must be formatted FAT32 with a single partition and it cannot be password protected. Plug the flash drive into a USB port on the front of the HMC. Wait until you hear 3 beeps (or approximately 1 minute) for the HMC to detect the flash drive.
Note: Save Upgrade Data overwrites any existing save upgrade data on the media. It does not overwrite any backup Management Console Data already on the media.
|
| 2. |
Save Upgrade Data can be performed by using either HMC GUI or restricted shell command line.
Use the HMC GUI:
a. Select HMC Management. > Console Management
b. Select Save Upgrade Data.
c. Select media type USB flash drive, click Next, and then click Finish.
Use restricted shell command line:
Use the following command specifying "diskusb" for USB flash drive.
saveupgdata -r diskusb
|
| 3. |
Wait for the Save Upgrade Data task to complete. If the task fails, contact your next level of support before proceeding. If the Save Upgrade Data task is successful, the following optional procedure can be performed to verify the data:
a. Open a restricted shell terminal as follows:
Local HMC: Select HMC Management > Console Management > Open a Restricted Shell Terminal
Remotely: Log in ssh.
1. Run the command lsmediadev to determine the mount point of the USB flash drive. In the example below, USB flash drive is /media/sda1
device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD
device=/dev/fd0,mount_point=/media/floppy,type=2,description=internal diskette drive
device=/dev/hda,type=6,description=internal hard disk drive
device=/dev/sda1,mount_point=/media/sda1,type=3,description=USB flash memory device
2. Run the command mount (for example, mount /media/sda1 for USB flash drive)
c. Run the command ls –l by using the same mount point as in Step b. - "example" ls -l /media/sda1
d. Verify that there are five tar files with the following names:
ACMSaveData.tar
RSCTSaveUpgrade.tar
SaveCCFWUpgradeData.tar
SaveHSCSystemUpgradeData.tar
SaveProfileDataUpgrade.tar
If any of these tar files are missing, contact your next level of support.
e. Issue the command umount using the same mount point as in Step b.
|
| 4. |
Once the Save Upgrade Data task is successful, remove the USB flash drive. |
Step 4: Upgrade HMC to 9.1.0 (from Recovery Media)
Do the following at the HMC interface to upgrade the HMC by means of the Recovery DVD.
| 1. |
Insert V9 recovery media (which was either ordered from IBM or downloaded and burned to DVD as indicated) into the DVD-RAM drive. |
| 2. |
Click HMC Management, then click the Shutdown or restart menu option.
|
| 3. |
Select restart HMC and click OK. Note: If the HMC fails to restart from optical, the boot manager may need be called (in other words, press F12 during the boot process) in order to get the HMC to boot from the optical drive.
|
| 4. |
The HMC reads the media in the DVD-RAM drive and displays the Hardware Management Console Install Wizard window. Highlight Next button (use tab/alt-Tab or arrow keys to move, and press Space bar or Enter to select.
Note: If the Save Upgrade Data (Step 3) was not performed, you see a warning window that save upgrade data was not found on the hard disk drive. Cancel the upgrade, remove the recovery media from the DVD drive, reboot the HMC, complete Step 3 to Save Upgrade Data, then start the upgrade process again.
|
| 5. |
Using tab or arrow keys to move the cursor and the space bar to select an option, select Upgrade to a new release (need asterisk on Upgrade to a new release as shown):
( * ) Upgrade to a new release
( ) Install
Highlight Next button, and press Enter.
|
| 6. |
On Upgrade Confirmation screen, highlight Finish and press Enter to start the Upgrade process.
|
| 7. |
The HMC installs 9.1.0 from the media, restores the data preserved by the Save Upgrade Data task, and then completes the booting process.
Note: The initial reboot can take 30 - 45 minutes. Do not reboot or power off; wait for the boot to complete. IBM is investigating a rare issue where the HMC upgrade can indefinitely hang at "Processing SaveHSCSystemUpgradeData.tar....." If the HMC stays at "Processing SaveHSCSystemUpgradeData.tar....." for more than one hour contact IBM support for further problem determination.
|
| 8. |
Select "Log on and launch the Hardware Management Console web application", then log in using your user ID and password. |
|
Network
|
Instructions for upgrading from a network server
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.
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 more 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 again before performing the upgrade.
| 1. |
Prepare media to use for Save Upgrade Data. You need a USB flash drive.
USB flash drive must be formatted FAT32 with a single partition and it cannot be password protected. Plug the flash drive into a USB port on the front of the HMC. Wait until you hear 3 beeps (or approximately 1 minute) for the HMC to detect the flash drive.
Note: Save Upgrade Data overwrites any existing save upgrade data on the media. It does not overwrite any backup Management Console Data already on the media.
|
| 2. |
Use the following command specifying "diskusb" for USB flash drive.
saveupgdata -r diskusb.
|
| 3. |
Wait for the Save Upgrade Data task to complete. If the task fails, contact your next level of support before proceeding. If the Save Upgrade Data task is successful, the following optional procedure can be performed to verify the data:
a. Mount the media:
1. Run the command lsmediadev to determine the mount point of the USB flash drive. In the example, USB flash drive is /media/sda1
device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD
device=/dev/fd0,mount_point=/media/floppy,type=2,description=internal diskette drive
device=/dev/hda,type=6,description=internal hard disk drive
device=/dev/sda1,mount_point=/media/sda1,type=3,description=USB flash memory device
2. Run the command mount (for example, mount /media/sda1 for USB flash drive)
b. Run the command ls –l by using the same mount point as in Step 1.- "example" ls -l /media/sda1
c. Verify that there are five tar files with the following names:
ACMSaveData.tar
RSCTSaveUpgrade.tar
SaveCCFWUpgradeData.tar
SaveHSCSystemUpgradeData.tar
SaveProfileDataUpgrade.tar
If any of these tar files are missing, contact your next level of support.
d. Issue the command umount by using the same mount point as in Step 1.
Note: The Save Upgrade Data is saved to the hard disk drive on the HMC as well as the media. The Save Upgrade Data on the media is used only to recover from an unexpected error under the direction of support personnel.
|
| 4. |
Once the Save Upgrade Data task is successful, remove the USB flash drive. |
Step 3: Upgrade the HMC to 9.1.0
| 1. |
Download the V9.1.0 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.
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/v910/x86
The parameters of the getupgfiles command:
| -h |
The host name or IP address of the remote FTP server. |
| -u |
The user ID to log in to the remote site. |
| --passwd |
The password to log in to the remote site. If this option is omitted, you are prompted for the password. |
| -d |
The directory on the remote site that contains the upgrade files. |
The following files are downloaded to the directory indicated (June 2016 refresh images):
| File name |
Description |
Destination |
Size |
BSD Checksum |
| img2a |
kernel image |
/hmcboot |
5885920 |
30078 |
| img3a |
Ram Disk file system |
/hmcboot |
39556365 |
61643 |
| base.img |
Base Image |
/hmcboot |
1167077376 |
31985 |
| disk1.img |
Base HMC Image and Service Doc |
/hmcdump |
3010166784 |
15930 |
| hmcnetworkfiles.sum |
checksums |
/hmcdump |
55 |
n/a |
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 ctl+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.
|
| 2. |
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.
|
| 3. |
Reboot the HMC using one of these 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. IBM is investigating a rare issue where the HMC upgrade can indefinitely hang at "Processing SaveHSCSystemUpgradeData.tar....." If the HMC stays at "Processing SaveHSCSystemUpgradeData.tar....." for more than one hour contact IBM support for further problem determination.
|
| 4. |
At the Hardware Management Console login prompt, log in using your user ID and password.
|
|
Once the HMC reboots, the installation starts and typically takes about an hour. After the installation of V9.1.0 is complete, you should be able to remotely access the HMC again.
|
| 5. |
Install the required fixes for V9.1.0 using the link provided. |
Optional: Using a local server
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/v910/x86
Files:
img2a
img3a
base.img
disk1.img
hmcnetworkfiles.sum
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 myserver -u myuserid --passwd mypassword -d /mydirectory |
Install the required fixes for V9
To obtain and apply the corrective service updates for V9, refer to document
https://www.ibm.com/support/pages/node/688025
[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"POWER7","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]