Hardware Management Console Readme For use with Version 9 Release 2 Maintenance 950 (V9 R2 M950) Updated: 04 March 2021 (C) Copyright International Business Machines Corp., 2021 All rights reserved. Contents These instructions contain the following information specific to the HMC V9 R2 M950 code level * Contents <#descrip> * Terminology <#terminology> * HMC V9 R2 M950 Recovery Media - for 7063 Machine Type <#HMCppcrecovery> * Upgrade notes <#upgrade> * Enhancements and new function <#enhance> * General and Security fixes <#fixes> * Command line changes <#command> * Performance and Scale <#scale> * Known issues and limitations <#known> * Best Practices <#best> * Web browser requirements <#browser> o Clearing the Browser Cache <#cache> o Other Web Browser Considerations <#otherweb> o BMC Browser Requirements <#bmcconsider> * Installing HMC in the OpenPower Environment, 7063 Machine type <#installHMCppc> * Virtual HMC Installation for x86 hypervisors <#vhmc> * Virtual HMC for PowerVM LPARS <#vhmcppc> * General Virtual HMC notes <#vhmcnotes> * National Language Support (Supported languages) <#nls> * Copyright and Trademark Information <#copyright> Terminology *x86* - This term is used to reference the Intel hypervisors (KVM, VMWare, Xen) on which Virtual HMC can be installed. *Note: HMC V9R2 release for x86 is not supported on bare metal (7042 hardware appliances).* *ppc64 or ppc64le* - describes the Linux code that is compiled to run on Power-based servers or LPARS (Logical Partitions). HMC V9 R2 M950 Recovery Media - for 7063 Hardware This package represents the Recovery image that can be used to install HMC V9 R2 M950 on the 7063 machine type. This Recovery image can be used to upgrade to HMC V9 R2 M950 from minimum level of HMC V9R1 + MH01857/MH01858. You can reference the Recovery image by APAR MB04261 and PTF MH01870. Package name Size Checksum (sha1sum) APAR# PTF# HMC_Recovery_ V9R2M950_1_ppc.iso 5056612352 f6ae8b4d4a51fba65fb6115bc12b13190fdff0ec MB04261 MH01870 Splash Panel information (or lshmc -V output) After installing the Recovery package "version= Version: 9 Release: 2 Service Pack: 950 HMC Build level 2010230054 ","base_version=V9R2 " The updated version of this readme is available in Fix Central : https://www-945.ibm.com/support/fixcentral/ Upgrade notes * The minimum HMC levels required for the upgrade to HMC V9 R2 M950 are: o HMC V9 R1 + *Mandatory fix *for vHMC on x86: MH01857 + *Mandatory fix* for vHMC on PowerVM and 7063 Machine type: MH01858 o The mandatory fix requirement: + Ensures that once the HMC is upgraded to the 950 version, all CECs and BPCs connect to the HMC. Without the fix, all CECs and BPCs will go to "Failed Authentication" state. + Includes fix for PCM database incompatibility issues while upgrading to 950. + User MUST run Save Upgrade Data after installing mandatory fix and prior to upgrading. Refer to https://www.ibm.com/support/pages/node/6409986 * HMC V9 R M950 supports POWER7 servers with the following minimum firmware levels: o FW730_146 (730.A0) o FW740_156 (740.90) o FW760_087 (760.50) o FW770_098 (770.50) o FW780_068 (780.21) * HMC V9 R M950 continues to provide support for 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 will result in a connection state of Version Mismatch and connection_error_code “Connection not allowed 0009-0008-00000000”. * Transport protocol TLSv1.1 support is removed from all HMC communication channels o Verify that all remote browsers, scripts and programs that interface with HMC REST APIs or web browser (including HA programs, AIX Live Kernel Update, etc) are enabled for TLS 1.2. * HMC V9 R2 M950 supports the following HMC models: o x86 : KVM, XEN, ESXi (6.0 / 6.5) o ppc64le : 7063-CR1, vHMC on PowerVM (Power 8 & Power 9 systems) * HMC V9 R2 M950 does _not_ support 7042 models. * 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 i.e., 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) should 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. * V9 R2 does not support HMC user profile names that are all numeric (i.e. user "123456"). Any existing hmc user profiles with numeric ids are deleted on upgrade. This issue is under investigation. * HMC V9 network installation images and installation instructions can be found here: https://www.ibm.com/support/pages/node/687979 Enhancements and new function * VIOS Maintenance and backup-restore: o New option in the HMC to validate the readiness of the VIOS for maintenance operations. o Validate all the clients using the VIOS for multi-path/redundancy setup for network & storage and provide appropriate message to the user. o Provide an HMC option to initiate a VIOS IO configuration backup (using viosbr) and store the configuration backup in the HMC file system. The saved configuration backup file can be restored on the VIOS at a later time. Similarly, provide an HMC option to initiate a VIOS full backup (using backupios) and store it in theHMC file system. HMC also provides an option to manage the backup files. * Enablement for the CMC Enterprise Pools 2.0 app to be able to identify Linux partition OS types as RHEL, SLES, or other Linux. * Enablement for dedicated processor partition support for Enterprise Pools 2.0. * Enhancement to support Partition Virtual serial number, which is a unique serial number that can be assigned to each partition. * Enhancement to assign platform keystore space for each partition. Platform keystore space will be provided by Hypervisor and can be configured at a partition level for use by Operating System. * Increase number of threads per migration operation to 8 for improved LPM performance * The following cipher suites and protocols have been disabled in all crypto policy levels. o DH with parameters < 1024 bits o RSA with key size < 1024 bits o Camellia o ARIA o SEED o IDEA o Integrity-only cipher suites o TLS CBC mode cipher suites using SHA-384 HMAC o AES-CCM8 o All ECC curves incompatible with TLS 1.3, including secp256k1 o IKEv1 o DSA key authentication is disabled. * Perfomance improvements: o Support for managing 2000 partitions per HMC o Performance enhancements in Virtual Storage and Virtual Network Topology diagrams o Performance improvements for Partition Virtual Storage operations o Performance enhancements specific to systems being managed by 2 HMCs * Linux support for Hybrid Network Virtualization * New options for adding and removing certificates from HMC truststore * GUI Enhancements o Ability to dynamically add/remove (DLPAR) virtual SCSI/virtual FC adapters from Virtual IO server/client partitions. o Performance improvements for launching vaadin panels and loading action menus o Reference codes in System and Partition Gallery views Back to top <#ibm-content> General fixes * Limit new managed resource role and task role names to 47 characters. * Added additional validation for the -h parameter on the *chhmc -c syslog -s add *command to return an error if a comma-separated list of host names is specified. * Fixed an issue where a UI DLPAR memory operation times out at 30 minutes even when the command timeout is greater than 30 and the command is still running. The UI task reports message /REST0255 An internal error occurred/. * Fixed an issue that ignored the -w option of the chhwres memory remove command for IBM i partitions. * Fixed an issue on Memory tab of IBM i partitions where the Options panel is not enabled. * Enabled hover text to display the complete name for VIOS names longer than 13 characters in the VIOS And Adapters tab of the Add Virtual Network wizard. * Fix to prevent call home of SRC E2FF1801. * Fix to prevent E212E13A against /hmcdump from reporting when getupgfiles is executed due to increased disk1.img size * Fixed an issue that caused Save Current Configuration to generate a saved profile named profile_0 where the number incremented each time rather than the specified profile name. This issue only impacts partitions that have Remote Restart enabled but have a configuration error that causes Local Storage Update Failed. * Fixed an issue with profiles of migration incapable partitions where the Specify MAC Address Restrictions option is neither reflected nor able to be set while editing SR-IOV logical ports. * Fixed a CEC periodically going to Incomplete state with NovaLink co-management * Fixed the recovery behavior for CPU DLPAR remove errors to rollback to the original values for virtual processors. * Fix to long running pedbg execution collecting the sosreport. * Fixed a UI issue where renaming a vSwitch did not take effect when there was only a change to the case (upper case to lower or vice-versa) of the characters * Fixed an issue with installios not using the user specified image name while installing VIOS from NFS server when multiple files existed in the directory. * Fixed an issue where additional vlan remains in the last valid configuration of VIOS even though a virtual network that is an additional vlan on existing trunk adapter is deleted. This issue also impacts the last * activated profile when automatically save configuration to profile is enabled. * Fix to prevent call home of SRCs E23D040A and E2FF4500. * Fixed gaps in the PCM data not showing up in the dashboard when run for a few days in a scaleup environment and improved response time of the Aggregated metrics API * Fix to prevent the secondary HMC to take over as primary during daily 'primary arbitration' scheduled task if a repair operation is running. * Fixed an intermittent issue where the partition storage diagram cannot be viewed due to some stale entry in the Storage Information * Fixed an issue with the REST call "/rest/api/uom/ManagedSystem?hwinventory=true" that does not return the results of the PowerSupplies and FANs XML on the first attempt. * Fixed a NullPointerException while creating a sysplan resulting in error /Exception Occurred in com.ibm.inventory.VSPPComponent:setPartitionProfiles/ * Fix to prevent power off of the managed system when a system dump is currently being performed so the dump won’t be invalidated. * Fixed an issue where BMC events would get re-reported by the HMC. * Fix to the actions menu options based on selection in VNIC Tab of Edit Partition Template. * Fix to display an error message for VIOS RMC state busy while viewing the license during Deploy System Template. * Fix to block the user from modifying the backing device type while the partition template is opened in view mode. * Fix for a failed partition migration operation without error message resulting in LPM in the other direction error of/HSCL8012 The partition named was not found/ * Fixed an issue that caused a Power enterprise pool to show an incorrect number of unreturned processors or unreturned memory for the pool after a server in the pool that was unreachable from the master HMC came back up. This issue only occurs if the server had unreturned resources before it came back up, and those unreturned resources were able to be automatically reclaimed when the server came back up. * Fix to discover a newly added interface in vhmc on PowerVM without requiring a reboot. * Large Send attribute issue in network bridges using Deploy System Template has been fixed. * Persistence issue of link aggregation configuration in network configuration tab of Deploy System Template has been fixed. * Fix for accurate values of a system's stealable proc/memory resources. * Fix lock timeout problem for cross HMC concurrent bi-directional partition migration operations. * Fixed a problem of failed migration operations hitting the error message /"//HSCLA319 The partition's virtual Fibre Channel client adapter xx cannot be hosted by the existing Virtual I/O Servers (VIOSs) on the destination managed system. Set up the necessary VIOS host on the destination managed system, then try this operation again./" * User is not allowed to performing Deploy System Template on a CEC with "Power off on last LPAR Shutdown" setting enabled. * Fix for handling code update when one FSP times out during a firmware update operation while the other FSP completes. * Fixed an issue where the last character of a 9 character SRN event was stripped off. * Fixed an issue while trying to view the Manage Inbound Connectivity panel when a system was connected using IPV6. * Fix to prevent network traffic from the HMC attempting to contact IBM servers even when the HMC is not set as a callhome server. Security fixes * Addressed tomcat vulnerability: CVE-2020-9484 * Addressed a problem in the authentication flows to avoid thread hung/idle state during access server calls. Command line changes * The following new commands have been added to support partition virtual serial numbers: *lsvsn*, *rmvsn*, *xfervsn*. * The following existing commands have been enhanced to support partition virtual serial numbers: *chsyscfg*, *lscod*, *lssyscfg*, *mksyscfg*. * The following commands have been enhanced to support partition keystores: *chsyscfg*, *lssyscfg*, *mksyscfg*, *rstprofdata*. * A new option has been added to the *lslparmigr *command to display memory requirements for a partition to be migrated as well as available memory on a destination managed system. * Enhanced the *lslparmigr -r msp* and *lslparmigr –r lpar* commands to display MSP thread information. * The *chsysstate *command to power off a managed system has been changed to fail if the managed system is currently offloading a dump to the HMC. To override this new behavior and power off the managed system anyway, specify the *--force* option on the command. * New options have been added to the *chled *and *lsled *commands to support identify LEDs. * New options have been added to the *chled *command to run an LED lamp test. * The *chhmc *command no longer allows the SSH protocol version to be set to 1, Kerberos weak encryption to be set to on, or the legacy anonymous cipher mode for the HMC chatlet interface (port 9920) to be enabled. * A new option has been added to the *chsvc *command to automatically add the required certificates to the HMC's truststore when the cloud connector encounters a non-trusted certificate chain when connecting to cloud endpoints. * The *chhmccert *command has been enhanced to support adding and removing certificates to and from the HMC's truststore, and the *lshmccert *command has been enhanced to list the trusted certificates added to the HMC's truststore. * The *chhmcfs *and *lshmcfs *commands have been enhanced to support the /data file system and to support the /var/hsc/log file system as the separate file system that it now is (/var/hsc/log is no longer in the /var file system). Prior to this enhancement, these commands included the /var/hsc/log file system with the /var file system. * New options have been added to the *chsacfg *and *lssacfg *commands to configure and display connection monitoring settings. * New options have been added to the *chsvcevent *command to add a comment to a serviceable event when closing it. * The *lssvceventfile *command has been added to list the contents of a file associated with a serviceable event. * * Back to top <#ibm-content> Performance and Scale * With V9 R2 M950 or later, a single HMC can manage up to 48 systems & 2000 partitions across the systems being managed by HMC with minimum requirements as below o 16GB memory for 1 - 500 partitions o 32 GB memory for 500 - 2000 partitions * For maximum number of systems and partitions when HMC is used in combination with CMC, PowerVC, VM HA/DR, please refer to the corresponding product documentation. For other configuration requirements for Version 9 Virtual HMC Appliance, please refer to - Installing the HMC virtual appliance. Known issues and Limitations * Navigating the enhanced UI when managing systems and partitions can result in message: /Proxy Error/ /The proxy server received an invalid response from an upstream server. / /The proxy server could not handle the request GET /ui/sfp/. / /Reason: Error reading from remote server/ An upcoming fix is planned to be delivered soon. In the interim, refer to the proxy error techdoc for more information. * Any user installed certificate must have key size of 2048 bit or higher. If the certificate of key size 1024 bits was installed the HMC web server and 5250 console will fail to start after the upgrade. * HMC V9 R2 does not support HMC user profile names that are all numeric (i.e. user "123456"). Any existing HMC user profiles with numeric ids are deleted on upgrade. * The System Virtual NICs task shows no vnics configured even when vnics exist * When user runs getupgfiles, an SRC E212E13A might be observed due to increased size of the installation image files * Occasional Out of Memory Exception during Virtual I/O Server Installation when user logs out or the session expires * Proxy time out issue when multiple mappings are created or deleted as part of single POST operation for the same RR partition * Accessibility: In some panels, navigating to different input fields by TAB key doesn't work * "/Internal error/" message is observed, on removing stand alone vSCSI client adapter from inactive AIX partition * During LPM, the state of the LPAR is shown as "Migrating - Running" or "Migrating - Not Activated", whereas PCM shows the state as just "Running" or "Not Activated". * Customer may observe multiple heapdumps and javacores if there is any OutOfMemory for a service. It can result into triggering of SRC "E332FFFF" multiple times. * Occasionally, during lpar activation, command execution becomes very slow affecting HMC performance * A failure occurs during a pool (CPU/Memory) update operation that prevents adding the resource to the server * REST API error messages are not translated to the language of the browser or HMC. * /Error launching task/ message is thrown in Partition virtual storage topology diagram page * Occasionally, user shall see that System level Hardware Virtualized IO tab takes more time to launch * In SRIOV Logical port advanced settings, Promiscuous Mode field is missing in add VIOS wizard * During partition deployment, user will not see the configured client slot id for SCSI adapters when Remote Slot ID is configured to next available ID. * Launching UI task might show errors for a server (General Settings, Processor, Memory,I/O, Virtual Networks, Virtual NICs) in some specific scenarios with running Linux Partitions post LPM operation. Remove the system connection and add it back as a workaround. * The validation fails for IPV6 address in the NetBoot wizard, when the user enters the prefix along with IPV6 address. The user can provide an IPV6 address in Unicast Addressing excluding the prefix as a workaround. * Automatic installation of HMC using Activation Engine fails to process the configuration file. If the installation using activation engine presents you with a license to accept, then there is a possibility that the Activation Engine ISO image deployed cannot be mounted. Try to install again by rebooting the partition. * Remote Restart operation fails when tried with REST Job. Circumvention is to use HMC CLI for Remote restart. This issue will impact older PowerVC versions which do not support V9R2 HMC. * On older POWER7 server models that have HEA but do not support SRIOV, the user is unable to launch the Hardware Virtualized IO tab for a partition. Circumvention: Use CLI or profile edits to view or modify the partition HEA configuration. * HMC is not accessible remotely after user deletes one of the network bonds. User can select one interface name for the default gateway instead of selecting 'any' . Circumvention is to use local console to when deleting a bond interface that is used for remote access. * Throttling may not be started/adjusted/stopped on a server in an EP 2.0 pool when that server is managed by 2 HMCs and the state of the server on one of the HMCs is not in Standby or Operating state. The workaround is to fix the bad server state on the HMC. Best Practices * User sessions - The following best practices helps avoid performance degradations gradually over a period of time due to increased login sessions as well as security vulnarabilities such as unauthorized access to the active HMC sessions. o It is a best practice to logoff from HMC UI and then close the browser tab instead of directly closing the tab * Set Idle session timeout for all the users and not leave the timeout as '0' which leaves it as no timeout. Web browser requirements Learn about the requirements your web browser must meet to monitor and control the HMC. 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 HMC V9 R2 M950 supports Google Chrome Version Version 86.0.4240.111 (Official Build) (64-bit). Safari HMC V9 R2 M950 supports Safari Version 14.0 / Version 13.0.5 (14608.5.12) Microsoft Internet Explorer HMC V9 R2 M950 supports Internet Explorer 11.1082.18362.0 / Version 11.57 Mozilla Firefox HMC V9 R2 M950 supports Mozilla Firefox 82.0.1 (64-bit). Safari HMC V9 R2 M950 supports Safari Version 14.0 / Version 13.0.5 (14608.5.12) 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 *menu*button 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 "t*he 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. BMC Browser requirements To access local console in OpenPower environment required the following browser requirements with JRE Plugin Version 8 U144 * Google Chrome Version 60 * Firefox Version 52.1.2 * Internet Explorer Version 11 * Safari Version 10.1.2 Installing HMC in the OpenPower Environment, 7063 Machine type Setup and cabling of the 7063-CR1: https://www.ibm.com/support/knowledgecenter/POWER9/p9hai/p9hai_cabling7063.htm The 7063-CR1 uses a BMC based service processor that provides remote management capability: https://www.ibm.com/support/knowledgecenter/POWER9/p9eih/p9eih_kickoff.htm The most current version of the install procedure for the HMC is here: https://www.ibm.com/support/knowledgecenter/POWER9/p9hai/p9hai_configure7063.htm *Note*: Use of an external USB 3.0 DVD device on the 7063-CR1 will require use of a y-cable connected to 2 USB ports in order to power the device properly. Virtual HMC Installation for x86 hypervisors *Installation Images * 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-HMV or 5765-HMW in order to download 5765-HMW from the ESS site. Upgrade of 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 . 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 o VMWARE ESXi 6.0 or higher o KVM on Red Hat RHEL7 or higher o 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. *Notice*: 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 . Entitlement for Product ID 5765-HMW is needed to download from the ESS site. Fixes, mandatory fixes and service packs for this product are common to the Power Hardware Management Console Appliance (HMC) and will be available from Fix Central site. Package name Size Checksum (sha1sum) VHMC_ESX_SHA1_V9R2M950.tgz 5353695713 652bd464f80b2d060b9986f71b0b91cb7176b28b VHMC_ESX_SHA256_V9R2M950.tgz 5353695744 e0fce6471a7ec2005482339d8d0f2e128f91679d VHMC_KVM_V9R2M950_x86.tgz 5161997919 d54ae78e172521ddbef9690450ce403f6ee47a94 VHMC_XEN_V9R2M950.tgz 5162039792 879de3e3b24050b057ea445f3a0069be3e18d135 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-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 and Power9 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. *Notice*: 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 . Entitlement for Product ID 5765-HMB is needed to download from the ESS site. Fixes, mandatory fixes and service packs for this product are common to the Power Hardware Management Console Appliance (HMC) and will be available from Fix Central site. Package name Size Checksum (sha1sum) VHMC_PPC_LPAR_V9R2M950_1.iso 5056612352 f6ae8b4d4a51fba65fb6115bc12b13190fdff0ec Installation of vHMC for LPARs: http://www.ibm.com/support/knowledgecenter/POWER8/p8hai/p8hai_vhmc_pvm.htm Back to top <#ibm-content> 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: o From the current HMC version (e.g. HMC V8.860.0), upgrade to HMC V9 R2 M950 o When the upgrade is complete the HMC is now at a new version but still has a 160GB disk. o Perform a Critical Console Data backup, excluding network information and store the backup to a remote location. o Deploy the new HMC V9 R2 M950 image which uses a 500GB disk. o After the HMC boots up with the 500GB disk, restore the Critical Console data. National Language Support (Supported languages) *Languages* *Locales* English en_US,en_AU,en_BE,en_BE@preeuro,en_CA,en_GB,en_GB@euro,en_HK,en_IE,en_IE@preeuro,en_IN,en_NZ,en_PH,en_PK,en_SG,en_ZA Catalan ca_ES, ca_ES@preeuro German de_DE, de_DE@preeuro, de_CH, de_AT, de_AT@preeuro, de_LU, de_LU@preeuro French fr_FR, fr_FR.UTF-8, fr_CH, fr_CA, fr_BE, fr_BE@preeuro, fr_LU, fr_LU@preeuro Italian it_IT, it_IT@preeuro, it_CH Spanish es_ES, es_ES@preeuro, es_AR, es_BO, es_CL, es_CO, es_CR, es_DO, es_EC,es_SV, es_GT, es_HN, es_MX, es_NI, es_PA, es_PY,es_PE, es_PR, es_US, es_UY,es_VE Brazilian Portuguese pt_BR Portugal Portuguese pt_PT, pt_PT@preeuro Polish pl_PL, pl_PL.UTF-8, pl_PL@euro,pl_PL@preeuro Japanese Ja_JP Simplified Chinese zh_CN, zh_SG Traditional Chinese zh_TW, zh_HK Korean ko_KR Hungarian hu_HU, hu_HU.UTF-8,hu_HU@euro,hu_HU@preeuro Dutch nl_NL, nl_NL@preeuro, nl_BE, nl_BE@preeuro Russian ru_RU Czech cs_CZ, cs_CZ.UTF-8,cs_CZ@euro,cs_CZ@preeuro Slovakian sk_SK, sk_SK.UTF-8,sk_SK@euro,sk_SK@preeuro Copyright and Trademark Information http://www.ibm.com/legal/copytrade.shtml Notices This information was developed for products and services offered in the US. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: /IBM Director of Licensing// //IBM Corporation// //North Castle Drive, MD-NC119// //Armonk, NY 10504-1785// //US/ For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: /Intellectual Property Licensing// //Legal and Intellectual Property Law// //IBM Japan Ltd.// //19-21, Nihonbashi-Hakozakicho, Chuo-ku// //Tokyo 103-8510, Japan/ INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: /IBM Director of Licensing// //IBM Corporation// //North Castle Drive, MD-NC119// //Armonk, NY 10504-1785// //US/ Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. If you are viewing this information in softcopy, the photographs and color illustrations may not appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml . Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft is a trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Back to top <#ibm-content>