Hardware Management Console Readme

Firmware Limitation

• Virtual HMC appliance on Power is not supported on Power 9 with firmware FW930 until a future release. Attempts to install a virtual HMC appliance on FW930 will result in failure and upgrading to FW930 will cause an existing virtual HMC instance to fail to boot.
  
  

SPECIAL NOTE:  To avoid PTF/Service Pack install failures due to not enough free disk space in the root file system and false reports of E212E136, pro-actively install PTF MH01813(x86)/MH01814(ppc) before the fix listed in this readme.  PTF MH01813/MH01814 (located under the HMC V9R1M921 tier on FixCentral) must be reinstalled prior to any PTF or Service Pack update of V9R1 until V9R1M930 is installed.

Package information

Package name	Size	Checksum (sha1sum)	APAR#	PTF#
HMC_Update_V9R1M930_SP0_x86.iso	3594596352	a8ec8b2cd25a88e191551445a57ce110c723a568	MB04196	MH01810
Splash Panel information (or lshmc -V output)
"version= Version: 9  Release: 1  Service Pack: 930  HMC Build level 1904220700 MH01810 - HMC V9R1 M930  ","base_version=V9R1 "

Enhancements and new function

New Functions

• HMC GUI Enhancements
• Enhanced Quick Create Partition to support multiple partition creation.
  
• Provided options for a user to choose Physical IO, in case a match is not found on the system with the captured IO info (both system & partition templates).
  
• Provided VIOS license text acceptance from Manage VIOS view.
  
• Added a filter option to the Physical Volume, Physical IO table views and other tables where there are a large number of entries.
  
• Added Deferred/Activated firmware level as a selectable column in the dashboard view for systems.
  
• Added memory mode as a selectable column in the dashboard view of partition.
  
• Changed the Partition template wizard flow to show all the tabs through the state machine with appropriate messages instead of skipping certain pages.
  
• Enabled Browse option in Import templates after a failure in importing previous file.
  
• Provided option to remove or retain the group when the last group member is removed.
  
• Changed Task log pod to show only the latest “n” tasks. Filtering and more task details added in the Tasks Log page.
  
• Provided install option as part of partition template deploy and added a separate install menu option at partition level.
  
• UI will show system model description when hovering over the icon in the dashboard view
  
• Disabled “Bridge Internal Network” option for virtual networks corresponding to PVID of a load group
  
• Simplified adding virtual networks to load group by providing an option to directly add a network to a load group instead of going through Add Network Wizard

• Added support to show a managed system’s stealable processor and memory values
  
• Added support to show remaining non-IFL processors for hosting AIX or IBM i partitions
• HMC Security Enhancements
  
• TCP TimeStamp option has been disabled. It was reported as a possible vulnerability in security scan by Qualys (QID: 82063).
  
• Updated LDAP client on HMC to use TLSV1.2 when HMC is set to NIST mode.
  
• Enhancements based on ITSS  (IT Security Standard) requirements
  
  • Updated error message to be consistent when valid credentials are provided after multiple invalid logins are tried.
  • Updated HMC authentication to require that new passwords be a minimum of eight characters in length.
• Allow a managed system to concurrently be both the source and target of multiple migration operations
  
  • Allow two migration operations, one from server A to server B, and one from server B to server A, to be launched concurrently, and complete without error.
  • Allow three migration operations, one from server A to server B, one from server B to server C, and one from server C to server A, to be launched concurrently, and complete without error.
• HMC Logging Enhancements
  
  • Updated file permissions to protect logs against unauthorized access
• HMC Performance enhancements
  
  • Improved response time of Enhanced GUI dashboard login.
  • Improved response time for REST API’s for custom non-hmcsuperadmin users
  • Improved the launch time for Virtual NIC panel at partition level.
• Added PowerVM SR-IOV RoCE Support for the FC EC3L and EC3M (CCIN 2CEC) adapter.
  
• HMC Enhancement for managing PowerLC BMC systems 
  
  • Establishing concept of primary management console to prevent duplication and provide redundancy
  • Enhanced LED to show led status
  • Enhanced to collect and display system metrics: power usage, temps
  • Group Firmware Updates
• Default Idle session time out for new users created after updating to V9 R1 M930 will be 120 minutes. Value can be changed at the time of user creation or thereafter.
  
• Enhanced HMC to allow users to modify default session and idle timeouts for HMC users. The default values apply to newly created users.
  
• The option to change the HMC hardware clock has been removed. It is set to UTC by default to prevent double time changes during daylight savings time.
  

List of fixes

General fixes

• Fixed an issue that prevented managed system call home from working when the primary HMC could not be established in environments where frame (BPC) connections exist in either Connected or No Connection state resulting in HMC call home SRC E3326701.
  
• Fixed the Korean keyboard - "Won" sign (E 13 L1) issue.
  
• Fixed an issue where the Discover HMC Call Home list would show unsupported (lower version) HMC systems.
  
• Fixed an issue where users may not be able to log into the UI with "ERROR STATUS : 500 ERROR CODE : UNKNOWN INTERNAL ERROR." after encountering HMC file system errors from an abnormal shutdown of the HMC.
  
• Fixed an issue where LPM validation on a partition with partition mobility disabled did not return an error.
  
• Fixed the garbage characters issue caused by a conflict in selection of non-UTF-8 and UTF-8 locale between HMC and Browser locale
  
• Show warning popup when user tries to change HMC time, when BMC is enabled with NTP
  
• Fixed junk characters being displayed in dashboards such as "Console settings", "Console Management", etc. when non UTF-8 locale is set.
  
• Improved error message that occurs during partition activation from enhanced GUI due to network interruption in the absence of the profile.
  
• Fixed the null pointer exception SRC E3550701 with UIFramework when browser is closed while the task is starting.
  
• Fixed issue to show proper error message when sftp user password expires during backup process.
  
• SRC E35507B1 will proactively be reported when an ethernet interface media speed is set to auto negotiate and it negotiates only half duplex.
  
• Fixed an issue where HMC doesn't retain keyboard settings after updating HMC.
  
• Enhanced the command line parser to provide special handling of parameter values that start with "\-".  This allows parameter values that start with "-" to be input on any command by double escaping the value (for example, by typing "--vnetwork \\-100").
  
• Improved the enhanced UI error message for the failure in re-fetch of any resource (like ManagedSystem, LogicalPartition etc). The complete error message now is read as: " Unable to retrieve an equivalent object after the requested operation. Reason for failure: (the original error message). Note that this does not mean that the POST operation failed."
  
• Enhanced the Update Access Key console warning messages to make it clear that the latest server firmware may not be able to be loaded when the key expires.
  
• In 'All Partitions' view, the partition description field is populated now. The same is being populated in '/rest/api/uom/<MS UUID>/LogicalPartition/<LPAR UUID>/quick' REST API response.
  
• Removed bmc_versions from the valid attribute list for the lssyscfg -r sys command. User can use sp_version instead, for both BMC & FSP.
  
• Fixed an issue where PCM status is displayed incorrectly and not refreshed after an HMC update.
  
• Fixed an intermittent issue of new lpar disappearing shortly after being created which was caused by CEC going to No Connection state temporarily.
  
• Fixed an issue to increase the VIOS template’s default value for memory because it was too low to complete an install.
  
• Allow Idle Power Saver with max frequency on POWER9
  
• Changes in IE 11 caused the UI to show Japanese messages though English is set as preferred language. Updated UI to recognize this change in IE.
  
• Fixed the high CPU utilization alert call home SRCs E212E150 and E212E151 caused by unnecessary parallel execution of Java processes performing periodic transactions.
  
• Updated Help menu to point to POWER9 Knowledge Center documents
  
• Fixed network bridge creation failure in the absence of backing devices on VIOS, even though tagged virtual network is selected. Also updated to report RMC connection failures, if any.
  
• Fixed an issue that prevented the HMC GUI from accepting an LDAP primary or backup URI that contained a port number.
  
• Fixed to add failure specific error message to Task log instead of just a generic message for add VNIC failure.
  
• Fixed empty Negotiated-Speed field issue with SR-IOV Physical Port for 2-port 25 GB RoCE adapter
  
• Allowed the ability to add virtual networks to partitions on different virtual switches simultaneously from the UI
  
• Fixed Software Service Information transmissions failure for some partitions
  
• Fixed an issue where SRC E355095C is reported when firewall changes were done to all interfaces at once.
  
• Adjusted the threshold used for SRC E35A000D to prevent false reports.
• Fixed an issue that caused a deadlock that resulted in SRC E35A0018. The proxy error below may also be seen.
     The proxy server received an invalid response from an upstream server.
     The proxy server could not handle the request GET /ui/
     Reason: Error reading from remote server
  
• Fixed the reporting of E302F99C when running lslic to query sriov firmware levels when a system is in “No Connection” state.  This SRC has no impact and should be ignored.  Workaround is to resolve the cause of the “No Connection” state.
  

Web browser requirements

Learn about the requirements your web browser must meet to monitor and control the HMC.

To access HMC through a remote browser in a Windows 7 environment, you must have a minimum/default of 1600x900 screen resolution.

HMC web browser support requires HTML 2.0, JavaScript 1.0, Java™ Virtual Machine (JVM), Java Runtime Environment (JRE) Version 8 U151, and cookie support in browsers that will connect to the HMC. Contact your support personnel to assist you in determining if your browser is configured with a Java Virtual Machine. The web browser must use HTTP 1.1. If you are using a proxy server, HTTP 1.1 must be enabled for the proxy connections. Additionally, pop-ups must be enabled for all HMCs addressed in the browser if running with pop-ups disabled.

The following browsers have been tested:

Google Chrome

This HMC version supports Google Chrome Version 73 (Official Build) (64-bit).

Safari

This HMC version supports Safari 11.1

Microsoft Internet Explorer

This HMC version supports Internet Explorer Version 11.0.9600.19326CO.

• If your browser is configured to use an Internet proxy, then local Internet addresses are included in the exception list. Consult your network administrator for more information. If you still need to use the proxy to get to the Hardware Management Console, enable Use HTTP 1.1 through proxy connections under the advanced tab in your Internet Options window.
  

• It is recommended to have:

• Browser security setting in internet zone. If you are running security mode in "Local intranet" mode, make sure you do not have any setting to detect intranet network; disable Compatibility view.
• Browser zoom setting to 100%.
  

• IE doesn't support Promise JS which is the base of the GUI Dashboard.  The UI will fail to update automatically and may show stale data.  To recover:
  o    Refresh the browser (F5)
  o    Logoff and re-login to HMC
  

Mozilla Firefox

This HMC version supports Mozilla Firefox Version 60.5 Extended Support Release (ESR) and Mozilla Firefox Version 60.6 Extended Support Release (ESR). Ensure that the JavaScript options to raise or lower windows and to move or resize existing windows are enabled. To enable these options, click the Content tab in the browser’s Options dialog, click Advanced next to the Enable JavaScript option, and then select the Raise or lower windows option and the Move or resize existing windows options. Use these options to easily switch between HMC tasks.  For more information about the latest Mozilla Firefox ESR levels, see Security Advisories for Firefox ESR.

Safari

This HMC version supports Safari Browser Version 12.0.3

Clearing the Browser Cache

In Microsoft Internet Explorer

1. Open the Browser
2. Select Tools
3. Select Internet Options
4. Under Browser History, select Delete
5. Check "Temporary Internet files and websites files" and "Cookies and website data"
6. Click on Delete

In Mozilla Firefox

1. In the top-right corner of the browser window click the menubutton
    Choose History, and then Clear Recent History.
    In time range to clear, select "Everything"
    In the Details section, select "Cookies" and "Cache"
    Click on "Clear now"
2. In the top-right corner of the browser window click the menu button
    Choose Options > Advanced > Network >
    In "Offline Web Content and User Data" section click on "Clear Now"

In Google Chrome

1. In the top-right corner of the browser window, click the Chrome menu
    Choose History.
    Click the button Clear browsing data. A dialog will appear.
    From the drop-down menu, select "the beginning of time."
    Check the boxes "Cookies, site, and plug-in data" and "Cache"
    Click the button Clear browsing data.
2. Open the following URL with the Chrome browser: chrome://appcache-internals/
    If there is an entry related to the target hmc, click the corresponding “Remove” link

Other web browser considerations

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

Internet Explorer

1. Click Tools > Internet Options.
2. Click the Privacy tab and select Advanced.
3. Determine whether Always allow session cookies is checked.
4. If not checked, select Override automatic cookie handling and Always allow session cookies.
5. For the First-party Cookies and Third-party Cookies, choose block, prompt, or accept. Prompt is preferred, in which case you are prompted every time a site tries to write cookies. Some sites need to be allowed to write cookies.

Mozilla Firefox

1. Click Tools > Options.
2. Click the Cookies Tab.
3. Select Allow sites to set cookies.
   If you want to allow only specific sites, select Exceptions, and add the HMC to allow access.

Installation

Virtual HMC Installation for x86 hypervisors

Installation Images 

Download of the Power Hardware Management Virtual Appliance (vHMC) install images are available at the Entitled Systems Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss .  You must be entitled to Product ID 5765-HMW or 5765-HMV in order to download 5765-HMW from the ESS site.

Upgrade of 5765-HMV to 5765-HMW is supported.

Fixes, mandatory fixes and service packs for the vHMC are common to the Power Hardware management console (HMC) and will be available at IBM Fix Central.

The splash panel information (lshmc -V output) for the vHMC will be the same as for the HMC recovery DVD that is documented in the above description section.

Installation guidance for installing the vHMC into your hypervisor is found in the IBM Knowledge Center. Installation procedures may vary depending on the operating system you use and the hypervisor you use.

A feature of the vHMC is the activation engine which allows you to preconfigure the HMC Console by passing configuration information to the HMC at the first boot of the HMC, when using these images. Please look at the on-line Knowledge Center documentation on using the Activation Engine feature.

Notes for the Virtual Appliance for  x86 hypervisors

• The supported hypervisors for x86 are
  
  • VMWARE ESXi 6.0 or higher
  • KVM on Red Hat RHEL7 or higher
  • Xen 4.2 or higher on SLES 12
• There are now two images for the VMWare ESXi Server, one is for ESXi 6.0 and the other for ESXi 6.5. This is due to differences in the encoding of the OVA images. SHA1 for ESXi 6.0 , SHA256 for ESXi 6.5
• The processor on the systems hosting vHMC for x86 must have either Intel VT-x or AMD-V Hardware Virtualization enabled.
  

Installation methods for vHMC on x86 hypervisors
http://www.ibm.com/support/knowledgecenter/POWER8/p8hai/p8hai_installvhmc.htm

After the upgrade, install the mandatory fix using the instructions at Installation methods for HMC Version 8 fixes

Virtual HMC for PowerVM LPARS

Installation Images 

Download of the Power Hardware Management Virtual Appliance (vHMC) install images are available at the Entitled Systems Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss . You must be entitled to Product ID 5765-HMA or 5765-HMB in order to download 5765-HMB from the ESS site.

Upgrade of 5765-HMA to 5765-HMB is supported.

Fixes, mandatory fixes and service packs for the vHMC are common to the Power Hardware management console (HMC) and are available at IBM Fix Central.

The splash panel information (lshmc -V output) for the vHMC will be the same as for the HMC recovery DVD that is documented in the above description section for the 7063 Machine type.

Installation guidance for installing the vHMC into your hypervisor are found in the Online Knowledge Center. Installation procedures may vary depending on the operating system you use and the hypervisor you use. 

Notes for the Virtual Appliance for PowerVM :

• On Power9 servers, the HMC Virtual Appliance for PowerVM must run in Power8 compatibility mode, for this release.
  
• The HMC Virtual Appliance for PowerVM   does not provide graphics adapter support for adapters assign to the partition. Use a supported web browser to point to the HMC for UI support.
  
• DLPAR operations such as memory and processor moves for HMCs running in an LPAR are not supported.
  
• Inactive partition migration and Simplified Remote Restart operations are supported.
  
• The virtual appliance for PowerVM requires a Power8 or Power9 server that is enabled for little endian support. Minimum System Firmware 860 recommended for Power8 servers.
• vHMC for PowerVM cannot manage the server it is hosted on.

Installation of vHMC for LPARs:
http://www.ibm.com/support/knowledgecenter/POWER8/p8hai/p8hai_vhmc_pvm.htm

Back to top

General Virtual HMC notes

• Virtual HMC Appliance can be deployed in your existing POWER virtualized infrastructure. Virtual HMC Appliance supports install into PowerVM LPARs.
• Call home of serviceable events with a failing MTMS of the HMC itself is disabled.  Those serviceable events should be manually reported to IBM software support.
• To see if you are running on a virtual HMC use the lshmc -v command. If it displays a UVMID field, then you are running in a virtual machine.
  

  Example:
  

  lshmc -v

  "vpd=*FC ????????
  *VC 20.0
  *N2 Thu Sep 14 15:02:44 UTC 2017
  *FC ????????
  *DS Hardware Management Console
  *TM Vc87-f0a
  *SE 7f61457
  *MN IBM
  *PN N/A
  *SZ 8371892224
  *OS Embedded Operating Systems
  *NA 127.0.0.1
  *FC ????????
  *DS Platform Firmware
  *RM V8R8.7.0.0
  *UVMID c87f:0a7f:603a:1457
  "

• When deploying a virtual HMC, if the mac address is not specified, it will be generated by the hypervisor.  Network configuration on the HMC relies on the value of MAC addresses. If you re-deploy a new virtual HMC and want to restore critical console data previously taken on a virtual HMC, ensure sure you are using the same MAC addresses.
• When using Activation Engine to setup NTP configuration, you must specify the NTP version value.
• We recommend upgrading to the new image that uses 500GB by following the steps below:
  
  • 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.