IBM Support

Version 6: Installing HMC Corrective Service from Removable Media

Troubleshooting


Problem

This document describes how to install HMC Corrective Service updates that have been copied to removable media such as CD-ROM or USB stick.

Resolving The Problem

Important Note: This document pertains to V6 and earlier versions of HMC code, when updates were available as .zip files. For Version 7 HMC levels, HMC updates are provided as .iso files. To find information for updating HMC Version 7 and later see IBM Fix Central or contact your support representative.



Background

The HMC Corrective Service Web site lists two methods that can be used to apply HMC Corrective Service. One method is to update from CD-ROM. The CD can either be ordered from IBM or the CD can be created by downloading and burning an iso image from the HMC web site. A second method to install corrective service is to use FTP protocol to a remote server that contains a zip file image of the fix. The remote server can be the IBM service FTP server or the fix can be downloaded and installed on a local FTP server such as an IBM i5/OS partition. The instructions state that the HMC graphical user interface must be used to perform the installation. They direct the user to select Licensed Internal Code Maintenance -> HMC Code Update -> Install Corrective Service, and then to chose one of the two methods to install the update.

These methods may not be convenient for situations where the HMC is on a private network without FTP access or when the administrator does not have access to CD burning software that can handle iso image files. This document describes a third method that allows the HMC to update directly from a zip file placed on any mountable media type such as USB storage, diskette, CD/DVD, or even the local hard drive.

HMC Code Update from Removable Media

The following instructions describe an alternate procedure that allows the HMC corrective service update to be downloaded from the Web site, copied to removable media, and then applied to the HMC. This procedure requires the use of the HMC command line interface to perform the update.

1.Download the fix as in "zip" file format from the following HMC Corrective Service Web site:

https://techsupport.services.ibm.com/server/hmc/power5

Note the filename for use in later steps. The file name is case-sensitive.
2.Copy the zip file to removable media.

CD-R / DVD-R
This requires a PC with an operating system (for example, Microsoft Windows XP) or a software package that can burn data CDs. Do not extract the files from the zip. Do not use any advanced options on the burn (for example, leaving the cd open). Do not use any proprietary CD formats.

Diskette/USB Device
Verify there is enough free space for the fix. Copy the file to the formatted diskette/USB drive. The USB stick must be formatted FAT or FAT32 and not use any private encryption software. Early versions of the HMC require that the USB stick be a single partition.
3.Open a restricted shell or remote ssh session.
To open a restricted shell, right-click on the HMC desktop, select terminals, and then rshterm. If the desktop is not visible, minimize the HMC graphical interface window.
4.Determine the mount point.
Insert the removable media.

Version 6.1.3
Type the command lsmediadev to list the media devices that are available for use and their mount point. If the device is not shown, the HMC did not detect it. Verify that the device is formatted correctly, and run the command again.
    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/sda1,mount_point=/media/sda1,type=3,description=USB flash memory device
Version 6.1.2 and earlier
USB: Locate the USB device mount point. Type the command cat /etc/fstab | grep HOTPLUG. If the USB device was detected, the command will return a line similar to the following:
/dev/sda1 /media/sda1 auto rw,sync,noauto,user,exec,owner 0 0 #HOTPLUG Gi4D.mazCmF4yeS6
The output shows the mount point of the USB storage device in the second column. The mount point will be /media/sda1, /media/sdb1, and so on, depending on the version and model of HMC.

CD/DVD: The mount point is /media/cdrom

Diskette: The mount point is /media/floppy
5.Mount the media.
Run the command:
mount <mountpoint> where <mountpoint> is the mount point determined in Step 4.
6.List the file.
Run the command:
ls <mountpoint> where <mountpoint> is the mount point determined in Step 4.

The output includes the zip file name to be used in the next step. If the ls command fails, examine the format used to burn the CD, the format. Determine if there are media errors.
7.Run the update command:

Note: The command and file name are case sensitive.

updhmc -t l -f <mountpoint>/<filename.zip>

where <mountpoint> is the mount point determined in Step 4, l is the lower case letter L (as in LIMA rather than the number 1), and <filename.zip>is the file name listed in the output of Step 6. Example: updhmc -t l /media/sdb1/MH00111.zip

The HMC code update occurs at this point. Determine if there are any error messages. If an error occurs, refer to the section Common Errors below.
8.Unmount the drive:

Run the command
umount <mountpoint> where <mountpoint> is the mount point determined in Step 4. Note the command is umount not unmount.
9.Restart. Most updates require a restart of the HMC to take effect. Examine the info file on the Web site for details.

To reboot from the restricted shell command line, enter the following command:
hmcshutdown -t now -r
10.Verify a successful update. At a restricted shell prompt, type the command:

lshmc -V

Verify that the Release or fix level applied is listed in the output; for example:
    version= Version: 4
    Release: 2.1
    HMC Build level 20040908.1
    MH00156: 5250proxy Fix (10-13-2004)
    MH00176: Hardware Server startup Fix (11-10-2004)

Local Hard drive
The update file can also be copied directly to the HMC over the network using secure copy protocol, then the update can be run from the local hard drive. For example, the command to use PuTTY secure copy to copy a file would be as follows:

pscp -scp MH00111.zip hscroot@<hmc>:/tmp/HM00111.zip where <hmc>is the hmc host name or ip address. Specify -c on the updlic command to delete the file after the update. For example:
updhmc -t l -c -f /tmp/<filename.zip>

Common Errors
oExpanding the zip file.

Do not extract the zip file contents when burning the CD. Although this procedure may work, it often results in a corrupt signature. Leave the zip file intact.
oUsing the graphical Install Corrective Service Utility (or updhmc -t m option).

The Install Corrective Service Utility's "Apply corrective service from removable media (for example, CD-ROM)" can not update from a CD loaded with the zip file. It is intended only for the CDs ordered from IBM Service or burned using the iso image file. The method described in this document requires the use of updhmc command with a Media or Server object type of Local File System (-t l).
oHMC errors or Java dumps during the update.

These are often caused by media errors or a corrupt zip file. To test the media and data, you should do the following:

1. Insert the burned CD on a non-HMC PC, and use a compression tool (for example, Zip, Pkzip, Winzip, or Windows XP) to test the integrity of the zip file.

2. Try copying the file to the HMC hard drive:

cp /mnt/cdrom/<filename.zip> /tmp/<filename.zip>

If a media error exists, it will be reported by the copy command. Remove the local file after the copy operation. Or, run the command updhmc from the local directory, and use the -c option to delete the file after the update.

[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"HMC","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"5.3.0;5.3.5;5.4.0;5.4.5;6.1.0;6.1.1","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Historical Number

359440871

Document Information

Modified date:
22 September 2021

UID

nas8N1015801