Hardware Management Console Readme For use with Version 10 Release 2 Maintenance 1030 (V10R2M1030) Updated: 07 May 2024 (C) Copyright International Business Machines Corp., 2024 All rights reserved. Contents These instructions contain the following information specific to the HMC V10 R2 M1030 code level * Contents <#descrip> * Terminology <#terminology> * HMC V10 R2 M1030 Recovery Media - For 7063 Hardware <#HMCppcrecovery> * Install/Upgrade Notes <#instnotes> * Network Install/Upgrade notes <#upgrade> * Enhancements and new function <#enhance> * General fixes <#fixes> * Command line changes <#command> * Performance and scale <#perf> * 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> * HMC Virtual Appliance (vHMC) <#vHMC> o Virtual HMC Installation for x86 hypervisors <#vhmcx86> o Virtual HMC for PowerVM LPARS <#vhmcpow> o General Virtual HMC notes <#vhmcgen> * 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 V10R2 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 V10 R2 M1030 Recovery Media - for 7063 Hardware This package represents the Recovery image that can be used to install HMC V10 R2 M1030 on the 7063 machine type. This Recovery image can be used to upgrade to HMC V10 R2 M1030 from minimum level of HMC V9R2 + MH01942(950.7) or HMC V10R1 + MF70431(1010.3). You can reference the Recovery image by APAR MB04371 and PTF MF70433. Package name Size Checksum (sha1sum) APAR# PTF# HMC_Recovery_V10R2M1030_ppc.iso 6330693632 812e986a473018ac16fd72df5af745198804bcb4 MB04371 MF70433 Splash Panel information (or lshmc -V output) After installing the Recovery package "version= Version: 10 Release: 2 Service Pack: 1030 HMC Build level 2211152246 ","base_version=V10R2 " Install/Upgrade Notes * The minimum HMC levels required to upgrade via DVD or USB, to HMC V10 R2 M1030 is HMC V9 R2. * Restoring a backup taken prior to 1041 then attempting to apply an earlier PTF will result in the HMC stopping at the emergency shell on reboot. After restoring a backup taken between V10R2M1030 and V10R2M1040 immediately apply 1041 or later. Network Install/Upgrade notes * The minimum HMC levels required to perform install or upgrade via network to HMC V10 R2 M1030 are: o HMC V9 R2 + Mandatory fix for vHMC on x86: MH01941 (9.2.950.7) + Mandatory fix for vHMC on PowerVM and 7063 Machine type: MH01942 (9.2.950.7) o HMC V10 R1 + Mandatory fix for vHMC on x86: MF70430 (10.1.1010.3) + Mandatory fix for vHMC on PowerVM and 7063 Machine type: MF70431 (10.1.1010.3) * Minimum memory supported for vHMC is 16GB and disk size should be 500GB. * HMC V10 R2 M1030 provides support for managing Power10, POWER9 & POWER8 processor-based systems. * Management of POWER7 and older servers is not supported by HMC V10. Attempts to manage POWER7 and older servers will result in a connection state of Version Mismatch and connection_error_code “Connection not allowed 0009-0008-00000000”. * HMC V10 R2 M1030 supports the following HMC models: o x86 : KVM, XEN, ESXi (6.0 / 6.5 / 7.0) o ppc64le : 7063-CR1, 7063-CR2, vHMC on PowerVM (POWER8, POWER9 & Power10 processor-based systems) * Starting with HMC V10 R1 M1010, 7042 models are not supported. * 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 use all the new features available in V10 HMC ensure all Virtual I/O Servers are at level 3.1.3, 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. * Starting with V10 R1 M1010, HMC supports HTTP2 protocol along with HTTP1.1. Users or applications using CURL as the REST client may see connection issues depending on the versions of curl being used. Suggest to use '--http1.1' as the CURL argument if it fails to connect by default over HTTP2. * Starting with V10 R1 M1010, http response status message is no longer present in the Rest API response (which was an optional field for earlier versions). REST API clients should depend on the status code instead of status message to validate the success/failure of the API. Enhancements and new function * A new dashboard designed for an enhanced user experience is available. Only the dashboard has a new experience and few panels have been consolidated for an enhanced user experience, most of the existing panels remain the same for this release. Groups in the new dashboard are referred to as tags. Users can learn more about the navigation options in the new dashboard compared with old dashboard using the "Learn about the HMC Interface" link in the login page of HMC and in the latest blog in the IBM Power Community . * New experience includes: o Quick left navigation using hamburger menu o Different drawers in header and detached help drawer o Drill down view to have a new header and categorized menu to launch different operations o New HMC settings to modify date, time, locale, NTP, welcome message and default console settings in a single view o Completely new tag management o Partition/Virtual IO Server/Systems tabular view presents a consolidated slide to access quick information o User can switch from new to old dashboard and vice-versa by clicking "User" icon at the top right corner of the dashboard and selecting "Switch to old dashboard/Switch to new dashboard" * Enhanced opening of the virtual terminal (VTerm) of the logical partition on the HMC GUI by removing dependency on JNLP applet due to its discontinuation since Java 11, eliminating the dependency on Java. * Enable IBM PowerSC agent with pre-defined security compliance profile on the HMC. This allows PowerSC Server to manage the HMC as one of the end points and monitor the basic security compliance of the managed HMC. * Enable secure boot support for ESXi and KVM (with RHEL 8, RHEL 9 and Ubuntu 20.04 as host) based vHMCs on x86_64 platform. The detailed steps have been captured in Readme shipped with the image bundle. Secure boot enabled image is different than non-secure boot image. * Support efficient cleanup for multi-mapped NPIV & SCSI adapter ports in VIOS for failed migration operations. * Enablement of remote code load (code update by remote support engineers) for Power Systems Firmware. Users can use the HMC CLI or the HMC GUI to start/stop the RSC (Remote Support Center secure connection) client and connect to the RSC support server. Users can also set an access code that is required for the remote support team to remotely connect to the local HMC. * Ability to view the SR-IOV adapter physical port MAC Address. * Supports Live Partition Mobility (LPM) of partitions configured with Virtual Persistent Memory (PMEM) volumes. * Enable update of Virtual IO Server (VIOS) via HMC GUI, REST API and HMC CLI. Provide the ability to import VIOS update images from remote NFS/SFTP server, IBM Website (Fix Central) or from attached USB device. Also provide option to save and manage the VIOS update images in HMC, which can be further used for updating other VIOSs. * Enable update of HMC with Program Temporary Fix (PTF) or Service Pack (SP) on the existing Base GA / Recovery release of HMC using HMC CLI and HMC GUI through the IBM website option. Provides the ability to list and import the updates directly from the IBM Fix Central website. * Support user selection of target mapping of migratable SR-IOV logical ports including specifying the target logical port capacity. Support VIOS label matching for vNIC backing devices. * Maintain SR-IOV adapter redundancy for both vNIC backing devices and migratable logical ports for LPM and RR operations. * Enable group-attribute based authentication and authorization as configured on the LDAP server for auto-managed LDAP users on the HMC. * Allow users to define NPIV capable FC adapter level selections within each VFC hosting VIOS. In order to achieve this, users are now allowed to define the group_tag attribute on FC ports on the respective VIOS via the HMC CLI interface. These predefined FC port group tag value helps Power server administrators have greater control over LPM and RR operations. * IBM i network boot support for iSCSI attached tape devices. * Unsecure protocols such as FTP will be disabled in a future HMC release. Back to top <#ibm-content> General fixes * Fixed an issue that prevents a user who does not have access to perform LPM/RR from attaching storage to a Remote Restart partition. * Fixed an issue that causes system plan creation to fail when the captured system has a Virtual Switch with a slash in the name and an additional VLAN id resulting in error: /Exception Occurred in java.lang.NumberFormatException:forInputString Line:76// //Exception Occurred - Message: For input string: """12" Cause: null// //The command mksysplan not successful due to unknown errors./ * Fixed an intermittent issue with Modify/View User panel which displays an obsolete panel with additional check boxes for: /"I am changing the password"// //"Force user to change the password at next login?"/ * Fixed an issue that prevented connection surveillance call home reporting for eBMC systems for SRCs such as B3030001, etc. * Fixed an issue that prevented HMC login or any Kerberos user. * Fixed a rare timing issue where updlic throws an error message - "/Unknown output type: from message (0x7f)/", even though the updlic command is still running. * Improved the performance of the *lshwres -r virtualio --rsubtype eth --level lpar -F * command by preventing it from making RMC calls to gather data when no attributes requiring that data were specified. * Fixed an issue that prevented call home from working successfully. Symptoms included test call home displaying attempts at trying additional IP addresses. * Fixed an issue where the system will be powered off disruptively when using the 'latestconcurrent' option on updlic if the latest level in the repository is the level already on the system * Fixed an issue that does not reflect MAC address if modified following a deploy failure and the user attempts to reconfigure it by moving back and forth in the physical IO tab of Deploy Partition Template. * Changed the default processor sharing mode for a full system (all resources) partition to be share always (dedicated donate) when the partition is activated on a server in a Power Enterprise Pool 2.0. * Increased timeout of firmware update from 2 to 4 hours to handle timeout issues that caused code update to fail. * Enabled Serbia (RS) or Montenegro (ME) country codes to be selected separately for call home customer information. Customers will need to manually select Serbia (RS) or Montenegro (ME) after applying this fix, otherwise callhome will continue to fall on the old value Serbia and Montenegro (CS). Security fix * Fixed Local File Inclusion issue found during fetching of help content URL. Command Line Changes * The following commands have been added to support importing and managing VIOS update images: *chviosupd*, *cpviosupd*, *lsviosupd*, and *rmviosupd*. * The *updvios *command has been added to update a VIOS. * The *chsysstate *command has been enhanced to support IBM i network boot for iSCSI attached tape devices. * The *lshwres *command has been enhanced to display the MAC address of SR-IOV physical ports. * A new option has been added to the *migrlpar*, *lslparmigr*, *rrstartlpar*, and *lsrrstartlpar *commands to specify requirements for maintaining SR-IOV adapter redundancy of a partition's migratable SR-IOV logical ports and virtual NIC backing devices during LPM and RR operations. * A new option has been added to the *migrlpar*, *lslparmigr*, *rrstartlpar*, and *lsrrstartlpar *commands to specify requirements for maintaining the port VLAN ID, allowed VLAN IDs, allowed MAC addresses and capacity configuration of a partition’s migratable SR-IOV logical ports during LPM and RR operations. * The *migrlpar*, *lslparmigr*, *rrstartlpar*, and *lsrrstartlpar *commands have been enhanced to support user-specified mappings of migratable SR-IOV logical ports during LPM and RR operations. * The *migrlpar *and *lslparmigr *commands have been enhanced to support the migration of partitions configured with persistent memory volumes. * The *migrlpar*, *lslparmigr*, *rrstartlpar*, *lsrrstartlpar*, *labelvios*, and *lslabelvios *commands have been enhanced to support use of VIOS Fibre Channel port labels for vFC adapter hosting for LPM and RR operations. * The *refdev *command has been enhanced to support use of VIOS Fibre Channel port labels when refreshing virtual FC adapter data. * The *migrlpar*, *lslparmigr*, *rrstartlpar*, *lsrrstartlpar*, *labelvios*, and *lslabelvios *commands have been enhanced to support grouping of VIOSs for virtual NIC hosting for LPM and RR operations. * The *lsupdhmc *command has been added to list available HMC updates from the IBM Fix Central website. * A new option has been added to the *updhmc *command to obtain the update image directly from the IBM Fix Central website. * The *chhmc *and *lshmc *commands have been enhanced to support the enablement of the PowerSC UI agent on the HMC. * The *getfile *command has been enhanced to get and deploy the PowerSC endpoint truststore file. * A new option has been added to the *chhmc *command to set the Kerberos authentication timeout. * The *chhmcldap *and *lshmcldap *commands have been enhanced to support LDAP group membership for automatically managed remotely authenticated LDAP users. * The *chrmtsupt *and *lsrmtsupt *commands have been added to manage remote support connections on the HMC. * The *chsacfg *and *lssacfg *commands have been enhanced to support email notifications for scheduled operations. Performance & Scale * With V10 R2 M1030, 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 Virtual HMC Appliance, please refer to - Installing the HMC virtual appliance Known issues and Limitations * When installing the FW1030 firmware to a system that previously was at a FW1020 level, you need to complete the upgrade then perform the upgrade again consecutively. This to ensure both the T (temporary, also known as current) and P (permanent, also known as backup) are equal. This was previously known as the "Accept" process that was performed automatically. This will be addressed in a newer release/PTF of the HMC to automatically do the accept. Improvements in FW1030.00 and higher to the eBMC will cause any IPL from a backup side that is at a FW1020 firmware level to fail. An AC power cycle would be required to recover from this condition. * When both Kerberos and LDAP user ids are the same in an auto managed user environment, once the user disables automanage mode, the user is still able to login with kerberos credentials via command line.. However, it fails to login from the GUI. The workaround is deleting auto managed users when disabling automanage mode. * Changes to Data Collection properties of a given Managed System is not synced between HMC GUI old & new dashboards * Delete Option is not available from Partition/VIOS Drill Down action menu, when navigating to General properties. As a work-around, the user can delete the Partition/VIOS using All Partitions/All VIOS main table action menu. * While deploying partition template, at the Configure SRIOV Logical Port Settings sub panel, configure window will close when OK is clicked, if none is selected for physical ports, instead of re-throwing the error message which is present for physical port combo-box. * A cross HMC LPM operation when the target HMC does not know the designated processor compatibility level of the migrating partition fails with "/HSCL9001 The operation has failed on the managed system./" * In a Multi Factor Authentication (MFA) configured HMC, log into HMC fails using any user if the MFA server is not responding. The MFA server state needs to be fixed to be able to login to HMC. * When a new system is connected to the HMC, its respective partitions and VIOSs are not always immediately listed in the HMC GUI. Workaround is to refresh the browser or click on the refresh icon in the table. * Update VIOS panel of the HMC GUI cannot be launched from the old Dashboard. * Guided setup wizard does not get launched automatically after fresh install from the new HMC GUI. Workaround is to manually launch the wizard from HMC Management -> HMC Settings -> HMC Actions drop down -> Launch guided setup wizard * Manage Users and Tasks window re-opens when closed by clicking 'X' at the top right corner of the respective window. Work around is to use close, cancel or exit option to close the panel instead of “X” at top right corner. * When Multi-Factor Authentication (MFA) is configured, logoff from the local HMC console can take a longer amount of time * Sometimes the old HMC GUI pop-ups are hidden as soon as the next button is clicked in the Firefox browser. This is a limitation of the Firefox browser due to certain security considerations for pop-ups. Default Firefox settings with disabled pop-up will solve this issue. * Currently, there is no option to resize the table columns in the new HMC GUI panels. * When multiple resources (systems/partitions) are selected & if there are no common actions, the batch action menu shows "/No action available/". * The search bar in the table is not visible after one or more partitions or systems are selected from the tabular views. * Remote Code Load option support is provided only to hscroot & hscpe users. * Currently, there is no option to Save User Preferences in the new dashboard. * In HMC M1020 and higher a new Event Notification field was introduced with 3 scheduled operations settings: o None o All scheduled operations o Failed scheduled operations The prior setting, if it was selected, of "All scheduled operations" is not persisted across updates to V10R1M1020 or greater nor upgrades to V10R2M1030. Instead the setting defaults to the None option. *Workaround:* Re-save the desired setting after update or upgrade to receive notifications of scheduled operations. * If the *chhmcencr *command has been used to remove any TLS 1.3 ciphers from the HMC Web user interface, those changes are lost when the HMC is updated or upgraded and will need to be made again after the HMC update or upgrade. * The reset of an expired password of a Kerberos user is not supported in multi-realm configuration setups since release V9 R2 950. When such users try to login using GUI, they will get message as Invalid credential. Upon login from CLI, users may see below or similar messages. /Password:// //Password expired. Change your password now.// //Current password:// //Current Password:// //Password change failed. Server message: Old password not accepted.// //Current Password:// //Password change failed. Server message: Old password not accepted.// //Current Password:// //New password:// //Retype new password:// //Password change failed. Server message: Old password not accepted./ *Circumvention**:* Change or reset the password first, then log into HMC. * When locally at the HMC console with virtual terminal windows open, clicking on the Systems hyperlink on the left navigation will cause the windows to close requiring the user to reopen the window(s). Best Practices * User sessions - The following best practices helps avoid performance degradation gradually over a period of time due to increased login sessions as well as security vulnerabilities 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 o 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 V10 R2 M1030 supports Google Chrome Version 107.0.5304.110 (Official Build) (64-bit). Mozilla Firefox HMC V10 R2 M1030 supports Mozilla Firefox 107.0.1 (64-bit). Safari HMC V10 R2 M1030 supports Safari Version 16.1 (18614.2.9.1.12). Microsoft Edge HMC V10 R2 M1030 supports Version 107.0.1418.62 (Official build) (64-bit). Clearing the Browser Cache *In Microsoft Edge * 1. Open Microsoft Edge, 2. Select Menu (3 dots icon on top right corner of the browser) 3. Click on Settings 4. On the left panel, under Settings, click on "Privacy, search & services". 5. Under Clear browsing data, click on "Choose what to clear". 6. Select "Cookies and other site data" and "Cached images and files" check box 7. Click on “Clear now” button. * * 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. Microsoft Edge 1. Open Microsoft Edge 2. Select Menu (3 dots icon on top right corner of the browser). 3. Click on Settings  Cookies and site permissions. 4. Under “Cookies and data stored” click on “Manage and delete cookies and site data”. 5. Turn on “Allow sites to save and read cookie data (recommended)” to unblock 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 107.0.5304.110. * Firefox Version 107.0.1 * Microsoft Edge Version 107.0.1418.62 * Safari Version 16.1 (18614.2.9.1.12 Installing HMC in the OpenPower Environment, 7063 Machine type Setup and cabling of the 7063-CR1: https://www.ibm.com/docs/en/power10?topic=rack-cabling-mounted-7063-cr1-hmc Setup and cabling of the 7063-CR2: https://www.ibm.com/docs/en/power10?topic=rack-cabling-mounted-7063-cr2-hmc Pre-installation considerations, cabling, and configuration of a new 7063-CR2 Power HMC: https://www.ibm.com/support/pages/node/6485099 The 7063-CR1 and 7063-CR2 uses a BMC based service processor that provides remote management capability: https://www.ibm.com/support/knowledgecenter/POWER9/p9eih/p9eih_openbmc_kickoff.htm The most current version of the install procedure for the HMC is here: * 7063-CR1 :https://www.ibm.com/docs/en/power10?topic=rack-configuring-7063-cr1-hmc * 7063-CR2 : https://www.ibm.com/docs/en/power10?topic=rack-configuring-7063-cr2-hmc Upgrading the 7063 HMC from Version V9R2 or V10R1M1010 to V10R2M1030 https://www.ibm.com/support/pages/node/6845980 *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 * Download of the Power Hardware Management Virtual Appliance (vHMC) install images for x86 hypervisors 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-VHX in order to download 5765-VHX from the ESS site. Upgrade of 5765-HMW to 5765-VHX is supported. Check the Upgrade Notes section above for further details. 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 for BIOS firmware are o VMWARE ESXi 6.5 or higher o KVM on Ubuntu 18.04 & 20.04 LTS, Red Hat RHEL8 and RHEL9 o Xen 4.2 or higher on SLES 12, Ubuntu 20.04 LTS * The supported hypervisors for x86 for secure boot EFI firmware are o VMWARE ESXi 7.0 and 7.0.2 o KVM on Ubuntu 20.04 LTS, Red Hat RHEL8 and RHEL9 * 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 for x86 hypervisors are available at the Entitled Systems Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss . Entitlement for Product ID 5765-VHX 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_SHA256_V10R2M1030.tgz 6452509963 8383b9428baaaf9d72c67b398d01d92b8cc330fa vHMC_UEFI_KVM_V10R2M1030.tgz 6265919957 ff1087aa61ab1d1ddf57829a9fc48ae29a3f1195 vHMC_UEFI_ESX7_0_V10R2M1030.tgz 6450727659 113edf01cbcc265ee00e8261c3b7217a60d7241b VHMC_KVM_V10R2M1030_x86.tgz 6287949550 0e050092b592c72bcee6532de0d1d9f021fbf3dd VHMC_XEN_V10R2M1030.tgz 6267875359 339cbfcf7a3f97d56472b77768412295443775a9 Installation methods for vHMC on x86 hypervisors https://www.ibm.com/docs/en/power10/000V-HMC?topic=appliance-installing-hmc-virtual-x86 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-VHP in order to download 5765-VHP from the ESS site. Upgrade of 5765-HMB to 5765-VHP is supported. Check the Upgrade Notes section above for further details. 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 and Power10 servers, HMC Virtual Appliance for PowerVM can run in Power8 and Power9 compatibility modes 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, POWER9 or Power10 server that is enabled for little endian support. Minimum System Firmware 860 recommended for Power8 servers * You cannot manage the server that hosts the HMC virtual appliance. * You cannot manage the server that hosts another HMC virtual appliance which is managing the server that hosts this HMC virtual appliance. For example, HMC virtual appliance A is running on server A and HMC virtual appliance B is running on server B. HMC virtual appliance A cannot manage server B and HMC virtual appliance B cannot manage server A at the same time. One of the HMC virtual appliance can manage the other server, but both HMC virtual appliance cannot manage each other at the same time. * For HMC virtual appliances that are created on PowerVM, enable LargeSend on the NetworkBridge of the corresponding virtual network for better network bandwidth to the HMC virtual appliance. *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-VHP 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_V10R2M1030_1.iso 6330693632 812e986a473018ac16fd72df5af745198804bcb4 Installation of vHMC for LPARs: https://www.ibm.com/docs/en/power10/000V-HMC?topic=appliance-installing-hmc-virtual-power 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 Wed Nov 30 05:26:08 UTC 2022 *FC ???????? *DS Hardware Management Console *TM V587-fa5 *SE 2d11d0f *MN IBM *PN N/A *SZ 7761043456 *OS Embedded Operating Systems *NA 9.3.XXX.YYY *FC ???????? *DS Platform Firmware *RM V10R2.1030.0 *UVMID 587f:a52d:125a:1d0f " * 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. 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>