For use with Version 7 Release 7.6.0, Mandatory PTF

Contents

The information in this Readme contains fix list and other package information about the Hardware Management Console.

• HMC V7 R7.6.0 Mandatory PTF (MH01328)
• Package information for PTF MH01328
• List of fixes for MH01328
• Additional information
• HMC V7 R7.6.0 Recovery Media
• Package information
• Upgrade notes
• Enhancements and new function
• List of fixes
• Known issues
• Web browswer requirements
• Installation
• National Language Support

This package includes mandatory fixes for HMC Version 7 Release 7.6.0. You can reference this package by APAR MB03646. This image must be installed on top of HMC Version 7 Release 7.6.0 Recovery installation (MH01326) or Update installation (MH01327).

This package provides the following fixes and enhancements:

• Fixed a problem that can result in cec going to recovery state.
• Fixed a problem where the 5250proxy was slow to initialize after a reboot.
• Added support to configure a IPv6 gateway using GUI.
• Fixed a rare timing issue where a state change event may not be processed correctly. This can result in the HMC showing an correct cec state, but reporting an invalid state error when performing a task. For example server shows operating but power off command fails with "HSCL022C The managed system is not in a valid state to perform the operation.  Check the state of the managed system and retry the operation."

Notes

This package represents the Recovery image with which you can upgrade your HMC from HMC V6R1.3.0, or higher, to HMC V7R7.6.0. You can also use this package to install a clean version of HMC V7R7.6.0. You can reference this package by APAR MB03644.

• HMC Model 7310-C03 cannot be upgraded to HMC Version 7.7. This restriction is enforced in V7R7.5.
• If an HMC is used to manage any POWER7 processor based server, the HMC must be a model CR3 or later model rack-mount HMC or C05 or later deskside HMC.
• When IBM Systems Director is used to manage an HMC or if the HMC manages more than 254 partitions, the HMC should have 3GB of RAM minimum and be CR3 model or later rack-mount or C06 or later deskside.
• HMC Version 7.7.1 supports managing a maximum of 48 servers (non Power 590/595 models) or 32 IBM Power 590/595 servers with a maximum of 1024 partitions across the managed servers. The maximum is 2000 partitions for HMC Version 7.7.6 and later running on 7042-CR6 (or later) with minimum of 4GB of memory.
• The following HMC System Plan functions are not implemented for POWER7 servers:
  • Create system plan (mksysplan) capture of VIOS provisioning info (storage pools, etherchannels, shared ethernet adapters)
  • Deploy system plan Auto-install of VIOS, AIX and Linux partitions.
  • Auto-provisioning of storage pools, shared ethernet adapters and etherchannels by system plan deployment.
• Upgrading from HMC V6R1.3 requires the installing of PTF MH01127 (APAR MB02828).
• Upgrading from HMC V7R3.1.0 requires PTF MH01135 (APAR MB02661).
• The DHCP range choices of 9.6.24.x and 9.6.25.x are no longer available as DHCP server range selections in the HMC GUI for V7. The POWER 595 FHA/FHB system internal network utilizes this range. If a V6 HMC is upgraded to V7 and a POWER 595/FHA system addition is planned, change the range to an alternate available selection prior to introducing the system to the HMC. For all other system environments the range can still be used but is not visible in the GUI.
• Certificates and keyring files generated by the System Manager Security application (on HMC Version 6) will not be migrated to HMC Version 7. Applications such as remote 5250, which import the public key ring file to establish a secure connection with HMC, will need to import a new public key ring file. The new file, SM.pubkr, will be generated and stored on HMC V7 under the /opt/ccfw/data directory. You can copy this file by using the scp or sendfile command. For further information on how to set up remote 5250 using SSL, see the following support document:

  Version 7 HMC: Configuring SSL Remote 5250 Console Connection

This package provides the following new function and enhancements:

• Added support for managing POWER7 server models 9117-MMD and MHD
• Added support for managing POWER6 and POWER7 blades.
  • When converting from IVM to HMC managed blades, all partitions must be reconfigured.
  • When converting from SDMC to HMC managed blades, the SDMC must be disconnected prior to managing the blade with HMC. Dual management may result in corruption of the partition configuration.
• Added support for RAID1 on CR6 and CR7 HMC models.
• Added the ability, for capable PowerVM systems, to support the concurrent migration of up to 16 active, inactive, or suspended partitions from a managed system to one or more managed systems. This also requires VIOS 2.2.2.0 and Server Firmware Ax760 or later.
• Added support for viosvrcmd to mount device using "/export" keyword.
• Added support to allow ";" in viosvrcmd -fmt option.
• A GUI enhancement has been added on recovery panel for LPM operation. This fix will retain the Migration Recovery panel along with values entered by user if "recover" option returns with failure. This helps user to use same screen to recover the partition with force option. Otherwise user has to restart recover operation by selecting the "recover" menu option once again.
• A GUI enhancement has been added to display the error message with required line breaks for migration validation operations.

This package provides the following fixes:

General

• If the Mover Service Partitions (MSPs) used in partition mobility operations have multiple IP addresses, then you should no longer experience a significant performance degradation for partition migration operations, partition migration validation operations, and the lslparmigr -r msp command. You may still experience a significant performance degradation for the first operation performed between a pair of source and destination servers, and after an MSP is restarted or its IP address configuration is changed.
• DHCP server service is fixed to work with IPv6 addressing.
• Fixed a problem where a pegasus server request for list of all partitions on all systems fails with the exception IBMP_LPAR_CSProvider:CIM_ERR_NOT_FOUND if one or more servers have zero partitions configured.
• Fixed a problem where attempting to power off the server while in recovery state fails with an exception.

Repair and Verify fixes for POWER 750, 755, 770, and 780 servers (POWER7-based technology)

• On the Repair and Verify PBCommonQueryFRUAvailable panel, changed the wording to state 'select Yes' instead of stating to 'select Continue'.
• Enhanced the 5791 Exchange FRU procedure for DCA's, so that the panel PBBandCRemoveDCA20 informs the user in step #1 to "Verify the LEDs are off except for the Pwr FLT which may be blinking."
• Fixed the incorrect behavior of "previous" button while installing more than one BPR/BPD.
• Corrected R&V DCA Remove and Install panel graphics for FHB systems.
• Made minor improvements to the Select MES Order user interface.
• Fixed the problem where a DCA exchange could power off an entire IO drawer without notification.
• Fixed an issue where the "previous" button is missing in the detail view of an exception (PBCommonGenericMessages).
• Resolved Open/Close MES window content/sizing issues.
• Fixed a problem where performing R&V on an IO Drawer "Air Moving Device" fails during deactivate with error rc=67.

Command line changes

• The following commands have been enhanced to support Dynamic Platform Optimization: lsmemopt and optmem.
• The following commands have been enhanced to support hardware-accelerated Active Memory Expansion and hardware-accelerated memory encryption: chhwres, lshwres, and mksyscfg.
• The migrlpar command has been enhanced to allow the user to specify which physical fibre channel ports the migrated partition is to use on the destination managed system.
• The migrlpar command has been enhanced to support concurrent partition migrations and concurrent partition migration validations.
• The chhwres command has been enhanced for virtual I/O adapter add and remove operations. When adding a virtual I/O adapter to a Virtual I/O Server (VIOS) partition, chhwres has been enhanced to issue the VIOS cfgdev command to configure the device in the VIOS. When removing a virtual I/O adapter from a VIOS partition, chhwres has been enhanced to issue the VIOS rmdev command to remove the device from the VIOS partition.
• The chsyscfg command has been enhanced to set the time on managed systems.
• The lshwres command has been enhanced to display the recommended maximum number of virtual processors and the current configured number of virtual processors on a managed system.
• Secure FTP support has been added to the bkconsdata command.
• A new option, -v, has been added to the updlic command to allow the user to display progress messages.
• The mksysconn command has been changed to only attempt connections to Power systems and Power frames. The --force option can be used to override this change and attempt connections to any IP address.

This package has the following known issues:

• Support for the Remote Restart RPQ P91276 is not yet available in 7.7.6. If using Remote Restart, do not upgrade to 7.7.6. Instead, remain at 7.7.5 until a future service pack adds support.
• The optmem command does not return a 0 return code after successful execution.
• Kerberos user with expired password is allowed to log in via ssh with the warning messages: "Password expired. You must change it now." Logging via the UI is denied as usual if the [Kerberos] password is expired.
• When an HMC is upgraded to 7.7.6, "Remote Command execution" (ssh) may be disabled. Ensure that local HMC access or remote web browser access is available to re-enable Remote Command execution before upgrading.
• To ensure that the keyboard mapping is working properly for non English keyboards, codeset for the locale must be UTF-8. This can be done with the chhmc command.

  Example:

  Set the locale to French with UTF-8 codeset for use with French keyboard.
  chhmc -c locale -s modify -l fr_FR.UTF-8

  Set the locale to English with UTF-8 codeset for use with French keyboard.
  chhmc -c locale -s modify -l en_US.UTF-8

• Japanese, Chinese and Korean text cannot be entered on the GUI interface of the HMC. This affects all releases since 750. You can always use remote access to enter those characters.
• Before upgrading server firmware to 760 on a CEC with redundant HMCs connected, you must disconnect or power off the HMC not being used to perform the upgrade. This restriction is enforced by the Upgrade Licensed Internal code task.
• In most cases, the scalability and performance of HMC 7.6.0 matches that of a current HMC.

  DUAL HMC managing the same server must not be at different Versions and release levels. An HMC V7 R710 HMC and an HMC at HMCV7 R350 should not manage the same server. The HMC's should be at the same version/Release levels.

  If a new network adapter is installed on the HMC, the interface numbering can change. For example, eth0 can become eth1. However, the network configuration will stay the same because it's bound to the MAC address of the network adapter. So the configuration for eth0 will stay the same if the interface is renumbered eth1.

  If you use the Mozilla / Firefox browser to launch a remote client to your HMC, verify the following in your browser settings. Under Tools on the top menu bar of the browser, select Options. This will bring up the Options panel. If you have Block Popup Windows selected, you will need to add your HMC to the list of Allowed Sites if it is not already included in that list. Click on the Allowed Sites button and enter your HMC name on the Allowed Sites Popups panel. The remote client is launched as a popup window. If your browser blocks popups and if you do not allow popups from your HMC, you will not be able launch the remote client.

  eCLipz HMC builds enforce model checking. The eCLipz build will not install on models codenamed RIOS (6578), Marlin (6792, 7315-C01) and yellowtail (8305, 7315-CO1). In addition, all models that shipped as 7315 are not supported for eCLipz. If the same model also shipped as 7310, then it is supported for eCLipz. Test labs must change their Machine Type to 7310 for supported models if you want the eCLipz build to load. For example, the Turquoise rack mount machine is shipped as both 7315-CR2 and 7310-CR2. To install the eCLipz build on a Turquoise, the Machine Type / Model must be 7310-CR2. Machines that have a Machine Type / Model of 7315-CR2 can be converted by re-flashing the BIOS and changing the model.. To check the current Machine Type / Model of your HMC, run the following command from the restricted shell: lshmc -v or lshmc -v | grep TM. The TM field will list the Machine Type / Model of your HMC. See the BIOS and Hardware Information link in this current release note.

  The HMC Readme information located on the Welcome page contains old information. This will be updated.

  Session cookies need to be enabled in order for ASMI to work when connected to the HMC remotely; the ASM proxy code saves session information and uses it.

  Using Internet Explorer:
  Select Tools -> Internet Options
  Select Privacy tab and select 'Advanced'.
  Check if 'Always allow session cookies' is selected. If not checked, check 'Override automatic cookie handling', and then check 'Always allow session cookies'.

  You can choose how you want to handle First-party Cookies and Third-party Cookies - block, prompt, or accept. Prompt is preferred, in which case you will be prompted every time a site tries to write cookies. While annoying, it is a safe thing to do; some sites need to be allowed to write cookies.

  Using Firefox:
  Tools -> Options
  Select Cookies Tab
  Check "Allow sites to set cookies".

  If you want to allow only specific sites, select 'Exceptions', and then add this HMC to allow cookies.

The following browsers have been tested.

Microsoft Internet Explorer

Firefox

• Firefox 3, 3.5.19 and 3.6.4 are no longer supported.
• Firefox 4, 5, 6, 7, 8, 9 and 10 are supported.

Installation instructions for HMC Version 7 upgrades, updates and corrective service can be found at these locations:

Installation methods for HMC Version 7 updates and fixes

Upgrading or restoring HMC Version 7

Instructions and images for upgrading via a remote network install can be found here (for all HMC releases):

HMC network installation images