Hardware Management Console Readme For use with Version 10 Release 3 Maintenance 1050 (V10R3M1050) Updated: 28 August 2024 (C) Copyright International Business Machines Corp., 2024 All rights reserved. Contents These instructions contain the following information specific to the HMC V10 R3 M1050 code level * Contents <#descrip> * Terminology <#terminology> * HMC V10 R3 M1050 Recovery Media - For 7063 Hardware <#HMCppcrecovery> * Install/Upgrade Notes <#instnotes> * Future Support Notes <#future> * Enhancements and new function <#enhance> * General fixes <#fixes> * Command line changes <#command> * Performance and Scale <#perform> * 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 V10R3 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 R3 M1050 Recovery Media - for 7063 Hardware This package represents the Recovery image that can be used to install HMC V10 R3 M1050 on the 7063 machine type. This Recovery image can be used to upgrade to HMC V10 R3 M1050 from a minimum level of HMC V10R1. You can reference the Recovery image by APAR MB04432 and PTF MF71420. Package name Size Checksum (sha1sum) APAR# PTF# HMC_Recovery_V10R3M1050_ppc.iso 6671360000 110ba815405e095c2c206026d44e05d583687696 MB04432 MF71420 Splash Panel information (or lshmc -V output) After installing the Recovery package "version= Version: 10 Release: 3 Service Pack: 1050 HMC Build level 2310272020 ","base_version=V10R3 " Install/Upgrade Notes * The minimum HMC level required to perform install or upgrade to HMC V10 R3 M1050 is HMC V10 R1. * To install or upgrade *via the network* to HMC V10 R3 M1050, the following is _required_: o Mandatory fix for vHMC on x86: MF70430 (10.1.1010.3) o Mandatory fix for vHMC on PowerVM and 7063 Machine type: MF70431 (10.1.1010.3) o *Note*: PTF MF70430/MF70431 can be installed on top of HMC V10R1M1010 base level or any subsequent service packs with or without additional fixes but *must* be the LAST PTF installed prior to upgrading to V10R3 via network install images. * Minimum memory supported for vHMC is 16GB and disk size should be 500GB. * HMC V10 R3 M1050 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 R3 M1050 supports the following HMC models: o x86: KVM, XEN, ESXi (6.5 / 7.0 / 7.0.2) 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. If the partitions are using TLS for RMC communication, then the RSCT version should be 3.3.2.0 which is the default version available in AIX7.3 TL2. * 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 using '--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. Future Support Notes * Access to the old dashboard will be removed in a future release. * Support for the FTP option, which is unsecure, will be removed from all HMC interfaces in a future release. SFTP/NFS should be used instead. * Rest API access via port 12443 will be disabled in a future release. Use port 443 instead for accessing HMC Rest API’s. Enhancements and new function * Server Management support for FW1050. * Support for Additional Memory Region Sizes: Support for 1 GB, 2 GB and 4 GB memory region sizes for Power10 servers. * New Encryption level for vTPM 2.0: Support for the new vTPM 2.0 Power10 version 2 encryption level. * Support for new PCIe Gen4 IO Expansion Drawer and IO adapters * Added the ability to perform upgrade of a Virtual IO Server (VIOS) via GUI, REST API and command line using ISO files imported from a remote NFS/SFTP server or from an attached USB device. Also added support to import, list and manage VIOS images using the REST API, in addition to existing GUI and CLI. * New and improved User Experience and usability enhancements for o Performance and Capacity Monitoring o Live Partition Mobility (LPM), including the ability to select and migrate multiple partitions from the GUI o Rest API has been enhanced to support multiple partition migration o HMC update, including the ability to apply multiple updates in one flow when using the IBM website option o Dumps o LEDs * Added the ability to perform Remote Restart for partitions that have virtual Persistent Memory (vPMEM) volumes, along with enablement for Disaster Recovery operations using VM Recovery Manager. * Added the ability to configure IPv6 for Enterprise BMC and VMI (Virtualization Management Interface) connections. * Support for custom key management for Linux dynamic key secure boot. * Support for RMC communication using TLS over port 12601: Two new RMC communication modes have been added: o tls_preferred: use TLS over port 12601 if supported by the partition or HMC being communicated with, otherwise use legacy TCP/UDP over port 657. Note that selecting this mode can impact performance if the partition or HMC being communicated with does not support TLS. o tls_exclusive: use TLS over port 12601 only The communication modes are configured using the *chpsm *command. * Security: o Notification is now sent when HMC-to-HMC communication on port 9920 fails due to an HMC FCS certificate mismatch. o HMC settings “Login suspend time” and “Maximum login attempts” which apply to GUI sessions now also apply to SSH and REST sessions. o Support has been added to the HMC command line for configuring the SSH timeout, which is the maximum amount of time that an SSH session can remain idle or inactive before it is closed. * Performance and Capacity Monitoring (PCM) now computes processor usage with and without idle cycles separately, and a toggle has been added to the PCM Processor usage page to select whether processor usage is to be displayed with or without idle cycles included. The command "*chhmc -c pcmprocusage -s modify --deductidle on/off*" no longer has any impact on how processor usage is computed. * Partition core usage pushed to the Cloud Management Console (CMC) for use in the Capacity Monitoring (CM) app is now calculated without deducting idle cycles. Therefore, core usage shown in the CMC CM app will now match core usage shown in the CMC Enterprise Pools 2.0 app. Back to top <#ibm-content> General fixes * Fixed an issue that caused the VIOS Create Virtual Fibre Channel adapter GUI task to fail with the error "/REST000B The URL presented to the Management Console REST Web Services is not valid/". * Corrected the values shown in the Storage I/O usage column on the Usage page of the Systems and Partitions tables in the new GUI dashboard. * Fixed an issue with PCM energy metric sample collection for eBMC-based managed systems that caused SRC E3550046 to be called home. * Fixed an issue causing the interpolation line and shading to be missing from Performance and Capacity Monitoring (PCM) graphs for some intervals such as last month, when accessing Performance and Capacity Monitoring GUI from old dashboard, * Fixed an issue that can cause a shared processor pool name to be changed after a server firmware update. * Fixed an issue preventing a partition from being set as a time reference partition on a managed system that does not support Live Partition Mobility but does support time reference. Disabled unused HMC port 5023. * Fixed a timing issue that caused SRC E3D46FFF to be called home due to a call home failure that occurred because the Electronic Service Agent was not fully activated. * Fixed an issue that caused SRC E3D45070 to be reported and called home during a Transmit Service Information operation due to a specified Product Engineering file being rotated or deleted during the operation. * Fixed an issue causing firmware updates for Open Power systems to always fail with the error "/HSCF0276E Failure during readiness check operation against target/". * Fixed an issue that causes the Update Access Key (UAK) to be resent to an Enterprise BMC based managed system every time the HMC performs a UAK check even though the UAK has not expired. * Fixed a rare timing issue on HMC boot that caused SRC E3550046 to be called home. * Fixed an issue preventing HMC-to-HMC communication on port 9920 when the HMCs are on different subnets. * Fixed an issue where the HCNID associated with a migratable SR-IOV adapter is changed every time a partition profile with that migratable SR-IOV adapter is activated or applied. With this fix, the same HCNID will be used every time, preventing duplicate network bondings from being created and preventing the creation of a new resource with a new MAC address. * Reduced the time the partition dump restart operation will wait for a blocking operation to complete. Now the dump restart operation will return a busy error if it must wait more than one minute for a blocking operation to complete. * Fixed an issue that caused a Power Enterprise Pool 1.0 Mobile CoD pool processor or memory CoD code with a bad sequence number to be ignored and no error to be reported back to the user. * Fixed an issue for a Power Enterprise Pool 1.0 with no memory that causes the error "/HSCL9119 The Mobile CoD memory activation code for the Power enterprise pool was not entered because a permanent to Mobile CoD memory conversion code for a server could not be entered/" to be returned every time a pool create, update, or recover operation is performed. Also fixed an issue for a Power Enterprise Pool 1.0 with no processors that causes the error "/HSCL9118 The Mobile CoD processor activation code for the Power enterprise pool was not entered because a permanent to Mobile CoD processor9 conversion code for a server could not be entered/" to be returned every time a pool create, update, or recover operation is performed. * Improved the error message displayed by the installios command when only the name of the directory on the HMC that contains the ISO image to install is specified as the source of the installation images (-d) instead of the entire path, including the file name, of the ISO image. * When an Enterprise BMC-based managed system is powered off, its VMI IP address is no longer added to the list of removed IP addresses used for DHCP auto-discovery. Note that this change has no functional impact since VMI IP addresses are not auto discovered via DHCP. * Changed the error message that was received when activating a partition with vNIC adapters when the SR-IOV adapter logical port limit on the physical port has already been reached. The original error message "/HSCL2521 There was a failure in the management console repository/" has been replaced by an error message indicating the limit has been reached. * Fixed a rare issue causing notifications in the GUI Notifications slide in window to show a blank Reference ID and Source and a date of "/Invalid Date, Invalid Date/". * Fixed an issue that always caused a Linux partition running in the Power10 processor compatibility mode to fail remote restart or disaster recovery validation on a POWER9 processor-based destination system. * Fixed an issue that called home failure SRC (E3D46FFF) for a problem that is closed or duplicated in the backend. * Added the missing *-t io* option to the *lslic *help text and man page. Command Line Changes * The following commands have been enhanced to support Linux dynamic key secure boot: *chsyscfg*, *lssyscfg*, and *mksyscfg*. * The following commands have been enhanced to support the new vTPM 2.0 encryption level Power10 version 2: *chsyscfg*, *lssyscfg*, and *mksyscfg*. The original vTPM 2.0 encryption level value has been deprecated and renamed from *Power10* to *Power10v1*. The *Power10* value will still be accepted by the *mksyscfg *and *chsyscfg *commands. Support for the *Power10 *value will be removed in a future release. * The following commands have been enhanced to support remote restart of partitions configured with virtual persistent memory volumes: *lsrrstartlpar *and *rrstartlpar*. * Added the *upgvios *command to upgrade a VIOS. * The following commands have been enhanced to support RMC communication using TLS over port 12601: *chpsm *and *lspsm*. * New options have been added to the *chsysconn *command to configure IPv6 for the Virtualization Management Interface (VMI) for an Enterprise BMC-based managed system. * The following *chhmcusr -t* default and *lshmcusr -t* default command attributes have been deprecated and renamed: *max_webui_login_attempts* has been renamed to *max_login_attempts*, and *webui_login_suspend_time* has been renamed to *login_suspend_time*. The original attribute names will still be accepted by the *chhmcusr *command and will still be output by the *lshmcusr *command when the -F option is used. Support for the original attribute names will be removed in a future release. These attribute settings now apply to SSH and REST API sessions in addition to GUI sessions. * A new option has been added to the *chhmc *command to configure the SSH timeout, which is the maximum amount of time that an SSH session can remain idle or inactive before it is closed. The SSH timeout setting has been added to the *lshmc -r* command output. * Added support for SSH keys to the *cpfile *command. * Changed the *getupgfiles *command to always require the –r option. * Added the system name to the*lsdump -h* command output. * Deprecated the command *chhmc -c pcmprocusage -s modify --deductidle on/off* since it no longer has any impact. Also deprecated the*lshmc –p *command. Both commands will be removed in a future release. Performance & Scale * With V10 R3 M1050, 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 * Dates, times, and numbers on the GUI Performance dashboard are shown in the format based on the HMC language instead of the browser language. * The entire ENZ0 PCIe Gen4 I/O expansion drawer will be powered off when an Exchange FRU or repair of the Lightpipe Assembly is performed. * When performing a partition migration validation operation on the GUI, when the vNIC or SR-IOV mappings are edited, those mappings may disappear from the GUI when submitted for validation again. * If the managed system has generated SRC B158BA2A, this SRC does not show any description on the Serviceable Events page. 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 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 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 R3 M1050 supports Google Chrome Version 107.0.5304.110 (Official Build) (64-bit). Mozilla Firefox MC V10 R3 M1050 supports Mozilla Firefox 107.0.1 (64-bit). Safari HMC V10 R3 M1050 supports Safari Version 16.1 (18614.2.9.1.12). Microsoft Edge HMC V10 R3 M1050 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 HMC from Version V10R1M1010 or V10R2M1030 to V10R3M1050 https://www.ibm.com/support/pages/node/7074590 *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_V10R3M1050.tgz 6693726968 db4df64ea32baa0c2a9fc26aa5ae9aee9a4b8be0 vHMC_UEFI_KVM_V10R3M1050.tgz 6484653617 db34892f038333bc56e384d66d0ed6c28b907219 vHMC_UEFI_ESX7_0_V10R3M1050.tgz 6680254154 e0a03566002afe5eb3844d155dacbb550629c216 VHMC_KVM_V10R3M1050_x86.tgz 6497388624 bbcd49401068f6a7f319dd6d8e4157204271ca1c VHMC_XEN_V10R3M1050.tgz 6497293270 8f15e60829ba0ff6d8f49f747f4b60848e0fedf2 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_V10R3M1050_1.iso 6671360000 110ba815405e095c2c206026d44e05d583687696 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 Tue Nov 14 15:34:19 UTC 2023 *FC ???????? *DS Hardware Management Console *TM V9e7-f7b *SE 1e4170a *MN IBM *PN N/A *SZ 15632326656 *OS Embedded Operating Systems *NA 9.1.2.3 *FC ???????? *DS Platform Firmware *RM V10R3.1050.0 *UVMID 9e7f:7b1e:4c4c:170a " * 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 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>