How To
Summary
This document describes how to Upgrade the HMC 7042-CR9 ONLY from V9R1M942 to V9R2M950
*** All 7042 hardware and V9 HMC code are end of service support (EOS). Consider getting a new model HMC (7063) or a Virtual HMC***
Environment
Steps
Before upgrading:
- The minimum HMC level required to upgrade to HMC V9 R2 M950 for 7042-CR9 is HMC V9 R1 M940 SP2 along with a Mandatory fix MH01857.
-
HMC V9R1M942 + mandatory fix MH01857 (This fix must be the last fix installed, before performing this Upgrade. It is not cumulative)
https://delivery04.dhe.ibm.com/sar/CMA/HMA/09aw4/4/MH01857.readme.html
(This fix is not included in any service pack or iFix, so you can check if its installed by running CLI command lshmc -V and if it is not listed, then install it)You can find the fix here, under service pack: HMC V9R1M942, +Show Patched By-
- This image includes all fixes from V9R2 M950 base up to an including V9R2M950.4. Updates to this base level are only allowed starting with 950.5 maintenance (PTF MH01883) or higher.
- Example procedure for creating a bootable image for this Recovery media to install or upgrade a 7042-CR9 to V9R2M950 can be found here
- HMC V9 R M950 continues to provide support for POWER7, POWER8, and POWER9 processor-based systems.
- 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 0009-0008-00000000”.
- This HMC V9 R2 M950 is for 7042-CR9 only and does not support other 7042 models. This is the last release to support the 7042-CR9.
- If two HMCs manage the same server, both HMCs must be at the same version, release and maintenance level.
- It is recommended to have all connected VIOS servers on the latest level that is, Virtual I/O Server (VIOS) level 3.1.x. To have optimal performance from the GUI, ensure all Virtual I/O Servers are at level 3.1.1.x level, or later.
- All running partitions (AIX, Linux, and VIOS) need to be at Reliable Scalable Cluster Technology (RSCT) version 3.2.0.0, or later. It is recommended to have AIX 7.1 TL4 or higher and AIX7.2 TL0 or higher; these levels contain RSCT 3.2.1.0.
- Reboot the HMC
If the HMC has not been restarted recently, restart before you begin the upgrade. To reboot, either:
- Use the GUI task HMC Management > Console Management > shutdown or restart the Management Console > restart HMC then click OK.
OR
- Use the command hmcshutdown -r -t now - Review the readme file
The readme /release notes for HMC V9R2M950 Recovery Media and mandatory fix can be found in IBM Fix Central at https://delivery04.dhe.ibm.com/sar/CMA/HMA/09laq/1/MH01885.readme.html
- Download the HMC_Recovery_V9R2M950_CR9.iso image from Fix Central or - IBM FTP site
- Create bootable USB image by using the instructions at https://www.ibm.com/support/pages/node/6436841 (Must use Linux OS for this to work)
- The USB media is now ready.
-
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 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 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 -
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. If your not using a USB, run the command saveupgdata -r disk then skip to Step 3.a. 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 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 that uses 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
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:
Local HMC: Select HMC Management > Console Management > Open a Restricted Shell
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 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(that is, mount /media/sda1 for USB flash drive)
c. Run the command ls –lthat uses the same mount point as in step b above - "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 umountthat uses 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.
-
Insert the USB with (V9R2M950_CR9.iso Recovery) in the 7042-CR9 and reboot.
-
When the BIOS Splash screen appears to select F12 to select, boot device as USB.
-
The HMC reads the media and displays the Hardware Management Console install Wizard window. Select the wanted option "Upgrade to a new version" or "Install".
-
Continue with the installation or upgrade.
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 HMC's 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. If your not using a USB, run the command saveupgdata -r disk then skip to Step 3.
a. | 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 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: a. Mount the media: 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 b. Run the command ls –l 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 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 V9R2M950
1. |
Download the V9R2_network_images_cr9.zip from Fix Central. From the Fix Central site, select MH01885 HMC Recovery V9R2M950 for 7042-CR9 *Only*, click continue. Then find V9R2_network_images_cr9.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/cr9/ 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 (June 2016 refresh images):
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. |
||||||||||||||||||||||||||||||||||||||
2. | Set the HMC to do the next reboot from the special location on the hard 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 the following methods: Option 1. HMC GUI: HMC Management > Console Management > shutdown 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 might 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 V9R2M950 is complete, you should be able to remotely access the HMC again. |
|||||||||||||||||||||||||||||||||||||||
To obtain and apply the corrective service updates for V9, refer to document
Additional Information
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
11 June 2024
UID
ibm16437029