How To
Summary
This document provides instructions to upgrade vHMC for PowerVM or the HMC 7063-CR2 appliance from V10R2M1030 (or higher) to V11R1M1110. The V11 HMC product will support Power9, Power10 and Power11 systems so if you have older Power systems such as Power8 then be advised those will not be managed post upgrade of the HMC.
There are multiple methods such as upgrade using network images, upgrade using DVD or upgrade using USB Flash that can be used and each will be detailed below. The prerequisite steps that need to be performed prior to the upgrade are the same for each and that will be the first steps detailed. Then the different upgrade methods that you can use will be described afterwards.
Once you complete the prerequisite steps, you can skip to the section of the document that details the upgrade method you want to use to complete the task.
Objective
Upgrade the HMC to V11R1M1110
Environment
Model 7063-CR2 (ppc) appliance
Virtual HMC (vHMC) on PowerVM (Product ID 5765-VHP)
Steps
1. Prerequisites to complete prior to starting the upgrade to V11R1
A. Verify HMC model is compatible with V11R1M1110
(1) HMC V11 R1 M1110 supports the following HMC models.
- Open Power : 7063-CR2
- (vHMC) PowerVM Power9, Power10 and Power11
- Minimum memory supported for vHMC is 16GB and disk size is 500GB.
(2) Note that models 7042, 7063-CR1 and vHMC on PowerVM Power8 are not supported for HMC V11R1M1110
B. Verify that the Power systems being managed are compatible with HMC V11R1M1110
(1) HMC V11 R1 M1110 supports Power9, Power10 and Power11 systems.
(2) Before upgrading an HMC connected to an FSP-based managed system with FW1050 to V11 R1 M1110, you must update the system firmware to at least MH1050_058 (FW1050.20) or higher. Otherwise, the system might end up in No Connection state with the reason as 'Version Mismatch' after the HMC is upgraded.
(3) Management of POWER8 and older servers is not supported by HMC V11. Attempts to manage Power8 and older servers will result in a connection state of Version Mismatch and connection_error_code “Connection not allowed 0009-0008-00000000”.
C. Make sure your HMC is at the minimum level required to install or upgrade to HMC V11 R1 M1110.
(1) If you are upgrading from a previous release the minimum level you can upgrade from is as follows:
- HMC V10 R2 M1030
- You can also upgrade from higher build levels than the minimum (V10 R2 M1040, V10 R3 M1050 or M1060) as well
(2) No requisite ifix is required as had been a practice in earlier releases.
D. If two HMCs manage the same server, both HMCs will need to be upgraded to the same version, release and maintenance level.
E. Review, repair and close all service events.
(1) See following document if you are not sure how to do this task.
(2) A simple CLI command to close all service events is, "chsvcevent -o closeall"
F. Verify date and time is correct on the HMC (can use the "date" command in CLI).
G. Review the readme file of the V11 R1 M1110 posted on fix central for the Recovery Media package.
See MF71730 readme html on IBM Fix Central
H. Reboot the HMC
(1) If the HMC has not been booted recently, you should restart before beginning the upgrade.
- Using CLI - hmcshutdown -t now -r
- Using GUI - HMC Management > Console Management > Shut Down are restart the Management Console > restart HMC then click OK
(2) On the 7063-CR2 appliance you can use the BMC (if configured) to check the Petitboot screen on reboot or access the physical appliance. The vHMC products also have console type access which we will not cover in detail here, but those also can be used to check status after reboot.
(3) Having the BMC configured on the 7063-CR2 is very useful if you are working remotely to the HMC and the document linked below describes how to configure it.
https://www.ibm.com/support/pages/how-configure-bmc-hmc-7063-cr2
2. Upgrade Options for HMC V11 R1 M1110
A. Upgrade Options Overview
(1) After verifying all prerequisite tasks have been completed you can start the upgrade steps. There are several options you can use. The traditional options are required if starting from the minimum release level of V10 R2 M1030 or M1031 and involve using CLI only with network upgrade files, using DVD or using USB Flash Drive. To use the DVD method you will either have to have a USB attached DVD drive connected to your appliance or use the virtual DVD feature of the 7063-CR2 BMC interface.
(2) In HMC release V10 R2 M1040 there was a new GUI feature added, but did require some manual preparation of the network install images as well.
(3)The easiest option for upgrading the HMC was introduced in V10 R3 M1060 which allows complete use of the GUI and connecting directly to IBM to obtain the network image files.
(4) All methods will be described in the next sections below so pick the one you are most comfortable with.
- If HMC is at V10 R2 M1030 or M1031 - Use Option 2 (Network Upgrade), Option 3 (DVD Method) or Option 4 (USB Flash Drive)
- If HMC is at V10 R2 M1040 or higher - Use Option 1, 2, 3 or 4
- If HMC is at V10 R2 M1060 or higher - Use Option 1, 2, 3 or 4
B. Option 1 - HMC GUI Upgrade Task (Use if at HMC V10 R2 M1040 or higher)
(1) The M1060 release is the most automated upgrade task via GUI if your HMC can connect to IBM Web Site over the Internet. If you have to stage the HMC Upgrade files to a local system or to the HMC then the steps you take for M1040 are the same for M1060 release as well.
(2) The M1040 release implementation works like the Network Upgrade getupgfiles task described later, so you will need the network files to use the GUI option. If you are at M1060 and the HMC is able to access IBM Web Site then you can skip the manual download of network images step.
HMC GUI Upgrade Task
Step 1. Download the V11R1_network_images_ppc.zip from Fix Central. From the Fix Central site, select MF71730 HMC Recovery V11R1M1110 for 7063 Machine Type, click continue. Download option is set to HTTPS. Then find V11R1_network_images_ppc.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/v1110/ppc/ to download the network files to your local server.
Step 2. Go to HMC Management, and select the box for Upgrade HMC.
Step 3. Then click the Save Upgrade Data
NOTE - The picture shows HMC Only, but we recommend selecting one of the alternatives, rather than HMC only, for Save Location.
Step 4. Once the Save Upgrade Data is completed, click Next
Step 5. Select the Download location. Remember you need the network files for this option. Select the option where you put the unzipped files. In this screen FTP is selected, you would need the FTP server name or IP address, user and password, and directory where you unzipped the files. Then click Download upgrade files.
NOTE: If your HMC is at V10 R3 M1060 or higher you have the additional download location option of "IBM website" you can use if your HMC is able to connect to IBM Services. Using the IBM website option will avoid having to manually download and stage the network install images.
Step 6. When the download is completed, you should get a Summary screen. Click the Reboot and Upgrade option.
NOTE: Upgrading HMC can take up to 2 hours to complete and requires the HMC to be restarted. All users will be logged out of their HMC sessions during restart. Tasks that are started while the HMC is being upgraded will fail if they are not completed before the HMC is restarted.
C. Option 2 - Network Upgrade
Note: This method uses the HMC CLI and is one of three options available if at V10R2M1031 or lower
NETWORK UPGRADE
NOTE: 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.
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 using FTP, sftp or nfs protocol from your local server.
This section describes how to perform the upgrade over the network instead of from Recovery DVD. The network upgrade can be done using FTP, sftp or nfs protocol from your local server.
Restricted Shell Access
This upgrade method requires restricted shell command-line access.
This upgrade method requires restricted shell command-line access.
From the local HMC, (V10R2) select Console 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 additional 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
Perform a Save Profile Data for each managed system to save an additional 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) again before performing the upgrade. If your not using a USB, run the following command then skip to Step 3.
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) again before performing the upgrade. If your not using a USB, run the following command then skip to Step 3.
saveupgdata -r disk
| a. | Prepare a USB flash drive to use for Save Upgrade Data. 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 will overwrite any existing save upgrade data on the media. It will not overwrite any backup Management Console Data already on the media. |
| b. | Use the following command specifying "diskusb" for USB flash drive. saveupgdata -r diskusb. |
| c. |
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:
1. Mount the media: 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 Run the command mount (for example, mount /media/sda1 for USB flash drive) 2. Run the command ls –l using the same mount point as in Step 1 above. - "Example" ls -l /media/sda1 3. 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. 4. Issue the command umount using the same mount point as in Step 1 above. Note: The Save Upgrade Data will be 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.
|
| d. | Once the Save Upgrade Data task is successful, remove the USB flash drive. |
Step 3: Upgrade the HMC to V11 R1 M1110
| a. |
Download the V11R1_network_images_ppc.zip from Fix Central. From the Fix Central site, select MF71730 HMC Recovery V11R1M1110 for 7063 Machine Type, click continue. Then find V11R1_network_images_ppc.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/v1110/ppc/ to download the network files to your local server.
Open Restricted Shell (or ssh session) and type the following command: getupgfiles -r sftp -h myserver -u myuser --passwd mypassword -d /mydirectory The parameters of the getupgfiles command:
The following files will be 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 where the downloaded V11 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 will result in failed network upgrade. |
||||||||||||||||||||||||||||||||||||||||
| c. |
Reboot the HMC using one of the following methods:
Method 1. HMC GUI: HMC Management > Console Management > Shut Down or restart the Management Console > restart HMC
then click OK
Method 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 Petitboot screen should appear and you may need to arrow up and wait a bit for the Install from alternate disk option) then installation starts and typically takes about an hour. After the installation of V11R1M1110 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.
|
D. Option 3 - Upgrade using DVD
DVD Method
Instructions for upgrading from DVD media (DVD should be DVD+R DL)
This section shows how to use the BMC console viewer to upgrade using a remote virtual DVD. An external USB DVD drive can be used instead of remote virtual media.
Step 1: Download the Recovery DVD image Download the HMC Version 11R1M1110 Recovery DVD: HMC_Recovery_V11R1M1110_ppc.iso
External USB DVD drive: Burn the .iso as an image to DVD+R DL media. (This recovery media MF71730 cannot be ordered)
Step 2: Save Profile Data
Use one of the following options to perform a Save Profile Data for each managed system to save an additional 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.
This section shows how to use the BMC console viewer to upgrade using a remote virtual DVD. An external USB DVD drive can be used instead of remote virtual media.
Step 1: Download the Recovery DVD image Download the HMC Version 11R1M1110 Recovery DVD: HMC_Recovery_V11R1M1110_ppc.iso
External USB DVD drive: Burn the .iso as an image to DVD+R DL media. (This recovery media MF71730 cannot be ordered)
Step 2: Save Profile Data
Use one of the following options to perform a Save Profile Data for each managed system to save an additional 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.
Method 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 will get a popup 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. |
Method 2: Use restricted shell command line
At the command prompt, enter the following command which will 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 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.
At the command prompt, enter the following command which will 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 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.
| a. | Prepare media to use for Save Upgrade Data. You will 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 will overwrite any existing save upgrade data on the media. It will not overwrite any backup Management Console Data already on the media. |
| b. | Save Upgrade Data can be performed using either HMC GUI or restricted shell command line. Use the HMC GUI: 1) Select HMC Management. > Console Management 2) Select Save Upgrade Data. 3) Select media type USB flash drive, click Next, and then click Finish. Use restricted shell command line: Run the following command specifying "diskusb" for USB flash drive: saveupgdata -r diskusb |
| c. | 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: 1. Open a restricted shell terminal Local HMC: Select HMC Management > Console Management > Open a Restricted Shell Terminal Remotely: Log in via ssh. 2. Mount the media: a. 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 b. Run the command mount (for example, mount /media/sda1 for USB flash drive) 3. Run the command ls –l using the same mount point as in Step b above. - "Example" ls -l /media/sda1 4. 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. 5. Issue the command umount using the same mount point as in Step b above. |
| d. | Once the Save Upgrade Data task is successful, remove the USB flash drive. |
Step 4: Upgrade HMC to V11R1M1110 (from Recovery DVD or ISO)
| a. |
Load the Recovery DVD (for External USB DVD drive)
1. Insert the USB drive 2. Insert the Recovery DVD into the drive. 3. Reboot the HMC
4. Select the option to Upgrade
|
| b. |
BMC Virtual Media (for 7063-CR2)
Mount the iso image using BMC remote virtual media.
1. From your workstation log in to the BMC web interface (https:// ). Default login is root/OpenBmc. 2. Select Server Control. 3. Select Virtual Media Example 1: Screen display of where you need to be in the BMC GUI:
 4. Choose File, and go select the iso file named HMC_Recovery_V11R1M1110_ppc.iso that you previously downloaded to your workstation.
5. Click Start
6. Reboot the HMC
7. When the Petitboot menu is displayed, select the Install Hardware Management Console option that is located under USB. When you get the menu to Install or Upgrade, you need to use your arrow keys to select Upgrade, and enter.
Example 2. Screen display of Petitboot menu.
 8. If you have the Petitboot system password set you will need to enter it when prompted.
Example 3. Screen display if you have Petitboot system password set
 NOTE: If you do not know the Petitboot system password, see this link for assistance,
9. The upgrade can take upto two hours.
|
E. Option 4 - Upgrade using USB Flash Drive
USB Flash Method
Instructions for downloading the image (.img file)and upgrading from USB media
Step 1: Obtain HMC_1110_USB.zip file
a. Go to Fix Central. From the Fix Central site, select MF71730 HMC Recovery V11R1M1110 for 7063 Machine Type, click continue. Set download option to HTTPS. Then find HMC_1110_USB.zip and download to your PC. Then unzip the file, and follow instructions in b. link below
Step 1: Obtain HMC_1110_USB.zip file
a. Go to Fix Central. From the Fix Central site, select MF71730 HMC Recovery V11R1M1110 for 7063 Machine Type, click continue. Set download option to HTTPS. Then find HMC_1110_USB.zip and download to your PC. Then unzip the file, and follow instructions in b. link below
b. Use this link to create a bootable USB https://www.ibm.com/support/pages/node/7092036
(This works on MAC or Windows)
Step 2: Save Profile Data
Use one of the following options to perform a Save Profile Data for each managed system to save an additional copy of partition/profile configurations.
Step 2: Save Profile Data
Use one of the following options to perform a Save Profile Data for each managed system to save an additional 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 will get a popup 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 will 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 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.
| a. | Prepare media to use for Save Upgrade Data. You will 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 will overwrite any existing save upgrade data on the media. It will not overwrite any backup Management Console Data already on the media. |
| b. | Save Upgrade Data can be performed using either HMC GUI or restricted shell command line. Use the HMC GUI: 1) Select HMC Management. > Console Management 2) Select Save Upgrade Data. 3) 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 |
| c. | 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: 1. Open a restricted shell terminal Local HMC: Select HMC Management > Console Management > Open a Restricted Shell Terminal Remotely: Log in via ssh. 2. Mount the media: a. 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 b. Run the command mount (i.e., mount /media/sda1 for USB flash drive) 3. Run the command ls –l using the same mount point as in step b above - "Example" ls -l /media/sda1 4. 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. 5. Issue the command umount using the same mount point as in step b above Note: The Save Upgrade Data will be 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. |
| d. | Once the Save Upgrade Data task is successful, remove the USB flash drive. |
Step 4: Upgrade HMC to V11R1M1110 (from Bootable USB)
Do the following at the HMC interface to upgrade the HMC by means of the Bootable USB.
| a. | Insert V11R1M1110 formatted USB flash drive. |
| b. | Reboot the HMC Click HMC Management > Console Management, then click the Shutdown or restart the Management Console option Select restart HMC and click OK. |
| c. |
When the Petitboot menu is displayed, select the Install Hardware Management Console option that is located under USB. Press enter.
 |
| d. | The HMC reads the media in the 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 above) was not performed, you will 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 above to Save Upgrade Data, then start the upgrade process again. |
| e. | Using tab or arrow keys to move the cursor and the space bar to select an option, select Upgrade to a new version (need asterisk on Upgrade to a new release as shown below): ( * ) Upgrade to a new version ( ) Install Highlight Next button, and press Enter. |
| f. | On Upgrade Confirmation screen, highlight Finish, and press Enter to start the Upgrade process. |
| g. | The HMC installs V11R1M1110 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. . |
| h. | Select "Log on and launch the Hardware Management Console Web application", then log in using your user ID and password. |
3. Review and final thoughts
A. Prerequisite Steps were described
B. Upgrade options and steps were describe
C. Following final reboot of HMC the release should show the new release.
(1) Can view "HMC details" in the Dashboard view and should see V11 R1 M1110 under the Level / Version section.
(2) Using CLI "lshmc -V" should show
version= Version: 11
Release: 1
Service Pack: 1110
HMC Build level 2507090120
","base_version=V11R1
D. Upgrade to V11 is now complete. There may be follow-on ifixes or service packs to install if available which are covered in different documentation.
E. If using 7063-CR2 physical appliance consider updating firmware.
(1) 7063 Firmware updates can be found at Fix Central
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSRUTI","label":"HMC FOR POWER"},"ARM Category":[{"code":"a8m0z000000bowEAAQ","label":"Hardware Management Console"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]
Was this topic helpful?
Document Information
Modified date:
15 August 2025
UID
ibm17240298