Hardware Management Console Readme
Version 9 Release 1 Maintenance
940 (V9 R1 M940) README
Updated: 21 April 2021
(C) Copyright International Business Machines Corp., 2020 All
rights reserved.
Contents
The information in this Readme
contains the fix list and other package information about the
Hardware Management Console.
Terminology
x86 - This term is used to reference the legacy HMC
that runs on x86/Intel/AMD hardware for both the 7042
Machine Type appliances and the Virtual HMC that can run on the
Intel hypervisors (KVM, VMWare, Xen).
ppc64 or ppc64le - describes the Linux code that is
compiled to run on Power-based servers or LPARS (Logical
Partitions)
DNS - Domain Name Server
GUI - Graphical user interface
vHMC - Virtual HMC. The HMC appliance that runs in
supported VM Hypervisors
PTF MH01836 HMC V9 R1.940.0 Service Pack - for 7042 Machine
Types or vHMC for x86 hypervisors (5765-HMW)
This package represents a service pack image that can be used to
update your V9 HMC to the HMC V9 R1.940.0 Service Pack. You
can also reference this package by PTF MH01836 and APAR
MB04224. This image should be installed on top of HMC
Version 9 Release 1 910.0 Recovery installation (PTF MH01733)
and V9R1M931 or later applied.
- Installation NOTE: This PTF can be installed on any
level of V9 (starting at V9R1 M910 with required PTF MH01813
installed). However, IBM recommends applying this PTF with
the following installation order:
First update to V9R1 M931, install pre-req PTF MH01853, then
update to V9R1M940. Updating directly from V9R1 921.x or
earlier may cause periodic transmit service transactions
such as Hardware inventory, Software inventory, and
Performance data to fail.
- HMC V9 R1.940 is the last planned release stream
to support 7042-CR7 and 7042-CR8 Machine Types.
- Service packs are cumulative and as such will include all
the fixes for the PTFs released up to and including the last
service pack(s) for this HMC version. Please read the
individual Readme files for each PTF to see the list of
fixes.
- New systems arriving from manufacturing ship at the latest
available firmware. The HMC should be updated to the
latest available HMC code to be compatible, otherwise the
system may show Incomplete state.
Package information
| Package name |
Size |
Checksum (sha1sum) |
APAR# |
PTF# |
| HMC_Update_V9R1M940_x86.iso |
4045574144
|
8b5e55aeaae39ba711d61ee99927fa3c2d81073e
|
MB04224 |
MH01836 |
| Splash Panel information (or lshmc -V
output) |
"version= Version: 9
Release: 1
Service Pack: 940
HMC Build level 1911021524
MH01836 - HMC V9R1 M940
","base_version=V9R1
"
|
PTF MH01837 HMC V9 R1.940.0 Service Pack - for 7063 Machine
Types or vHMC for PowerVM (5765-HMB)
This package represents a service pack image that can be used
to update your V9 HMC to the HMC V9 R1.940.0 Service
Pack. You can also reference this package PTF MH01837
and APAR MB04225. This image can be installed on top of
HMC Version 9 Release 910.0 Recovery installation (PTF
MH01735) and V9R1M931 or later applied.
- Installation NOTE: This PTF can be installed on
any level of V9 (starting at V9R1 M910 with required PTF
MH01814 installed). However, IBM recommends applying this
PTF with the following installation order:
First update to V9R1 M931, install pre-req PTF MH01854,
then update to V9R1M940. Updating directly from V9R1
M921.x or earlier may cause periodic transmit service
transactions such as Hardware inventory, Software
inventory, and Performance data to fail.
- Service packs are cumulative and as such will include
all the fixes for the PTFs released up to and including
the last service pack(s) for this HMC version.
Please read the individual Readme files for each PTF to
see the list of fixes.
- New systems arriving from manufacturing ship at the
latest available firmware. The HMC should be updated
to the latest available HMC code to be compatible,
otherwise the system may show Incomplete state.
Package information
| Package name |
Size |
Checksum (sha1sum) |
APAR# |
PTF# |
| HMC_Update_V9R1M940_ppc.iso |
4042715136 |
2eb053313d95650de254e3d838128aaabddb66cb
|
MB04225 |
MH01837 |
| Splash Panel information (or lshmc -V
output) |
"version= Version: 9
Release: 1
Service Pack: 940
HMC Build level 1911021524
MH01837 - HMC V9R1 M940
"," base_version=V9R1
"
|
EOS of x86
- HMC V9 R1 is the last release to support the 7042-CR7
and CR8 machine types. HMC V9R2 will support 7042-CR9, the
7063 machine types and Virtual HMC Appliances (x86/ppc64le)
only.
Note: iFixes and Service packs on top of V9 R1 M940 will be
supported on 7042 machine types.
Enhancements and new function
New Function
- Security Enhancements
- The ls/chhmcencr commands have been updated to provide
SSH key exchange algorithm management.
- Security update to the pedbg command.
- New option scope(sub/one) HMC Manage LDAP panel
- The user will be asked to change the HMC password during
their first login on a new HMC installed and shipped with
HMC V9 R1 940.
- The Bash library has been updated to address a security
vulnerability.
- Injection of IBM i License Keys from HMC via CLI
- Enhancements to support virtual persistent memory
enablement
- HMC GUI/CLI/Rest API support for adding/assigning/removing
virtual persistent memory volumes
- Ability to get e-mail notifications for scheduled
operations.
- Show warning dialog when user session is about to expire due
to idle timeout
- Provide an option to specify user-defined name for HMC
critical console backup
- Ability to configure the maximum number of invalid Web UI
login attempts for HMC users
- Ability to configure UseDNS attribute of SSH configuration
- Ability to assign SR-IOV logical ports to an IBM i partition
with restricted I/O mode enabled.
- HMC automatic update of custom resource roles
- Provide auto access addition/removal for custom users
creating/deleting partitions
- In-band authentication using RSA token code when
multi-factor authentication is configured on the HMC.
- User Mode NX (Nutanix Xtreme) accelerator enablement for
PowerVM. This provides lower latency and higher performance
exploitation of the hardware accelerator engines.
- Support for providing more information about the status of
each sub-step of a partition migration operation in order to
figure out at what step a partition migration operation
failed.
- Hybrid Network Virtualization (HNV) : HNV allows partitions
with SR-IOV logical ports to be migrated by creating a backup
device (virtual Ethernet or virtual NIC) for each SR-IOV
logical port and removing/adding the SRIOV logical port
during Live Partition Mobility (LPM) or Simplified Remote
Restart (SRR).
- Note: The new Migratable option for Hybrid Network
Virtualization is provided as an unsupported technology
preview only and is not intended for production deployments.
List of fixes
General fixes
- Fixed an issue with the UI Shared Storage Pool freespace
information showing incorrect description/value.
- Changed both the enhanced GUI task that sets the keylock
property on partitions and the chsysstate -r lpar -o chkey
command to require the Modify Partitions (ChangeLPARProperty)
user task instead of the Set Partition Keylock Position
(SetLPARKeylockPosition) user task. With this change
users with the hmcoperator task role can now set the keylock
property on partitions. Deprecated the Set Partition
Keylock Position user task. Also changed both the
enhanced GUI task that activates a partition with the keylock
position or IPL source override and the chsysstate -r lpar -o
on command with either the -k or -i parameters to require the
Modify Partitions user task in addition to the Activate
Partition (ActivateLPAR) user task. With this change
users with the hmcoperator task role can still activate a
partition and override its keylock position or IPL source.
- Fixed a problem where E212E122 may be incorrectly reported
against /mnt/nimol during a VIOS installation when the image
is mounted via USB.
- Fixed an issue with lsperfmon showing incorrect values for
name, mtms, and ltmEnabled.
- Fixed an issue with simplified remote restart that cause
activation of the LPAR on the target using the UI to fail
until the cleanup has been run on the source. Errors
include HSCL9010 and HSCL05A7.
- Fixed an issue where the HMC GUI task recorder may log a
successful complete for a Power Enterprise Pool task that
failed.
- Fixed a timing issue that caused LKU to fail. This happens
rarely when the lpar got deleted and within same second
another lpar created and they both should get the same
partition id.
- A red graph for the flat storage utilization trend caused a
wrong interpretation of being a warning. It’s now replaced
with a blue graph plot.
- Fixed an issue where an HMC upgraded from older releases may
not be able to change certain call home settings such as a
call home proxy password due to incorrect file ownership.
- Fixed an issue on the UI Licensed Capabilities panel where
the "IBMi 5250 Application Capability" setting
incorrectly showed the "IBM i capability" value instead of the
IBM i 5250 application capability value.
- Fixed an issue where the new title of the pinned item
reverts to the default title upon relogin.
- Fixed an issue where using the UI to activate a partition
when two or more managed systems have the same name may fail
with HSCL8012.
- Fixed an issue that always caused the lsiotopo -r slot
command to fail with an unknown error for POWER7+ servers.
- The Title of the column 3 in the Adapter View of virtual
network panel will now correctly display 'Port VLAN ID'
instead of 'VLAN ID'
- Fixed issues in handling network bonds such as: selection of
bond0 as the interface for the default route; selection for
RMC communication in chpsm/lspsm; not including the bond
interface in the ip address list used by partition RMC and HMC
FCS communications. Symptoms include inactive
partition RMC connections to HMCs configured with bond and
E3325009 being reported by a peer HMC.
- Fixed generic SRC messages such as "Licensed Internal Code
failure..." in the customer email notification to show the
Knowledge Center Message Response text.
- Display a more meaningful message when a migration operation
is aborted with HSCL365C reason code "04101025" indicating a
possible cause of target system running out of non-IFL
processors.
- Display server name in the task log instead of server uuid
for VIOS activation.
- Fixed an issue causing the GUI to become inaccessible when
an x86 HMC is upgraded from release V8 to V9 and then migrated
to Power HMC.
- Provided the following command "runsig -s 700" to be run as
hscpe. This is a workaround for Linux rpm hangs that could
cause HMC installation, pedbg collection and code update tasks
to hang. A permanent fix is planned for a future PTF or
Service Pack.
- Fixed email notification issue when SMTP server sends two
line responses.
- Fixed a problem where activate of a profile that contains
one or more VNIC devices created prior to support for VNIC
failover (FW840) may fail. Symptoms include error
HSCL05E9 and the VNIC may show a minimum capacity of 0%.
- Fixed multiple issues in Deploy System Template related to
assignment of both dedicated mode SR-IOV capable cards and
shared mode SR-IOV Logical Ports in Virtual I/O Servers.
- Fixed btmp log rotation issue that was consuming unnecessary
disk space and that can cause a E212E134 to be reported.
- Fixed an issue with migration of data from x86 HMC to
another x86/ppc64le HMC. Both the source and target HMC must
be at V9R1.940 or later to use saveupgdata/rstupgdata commands
to migrate data from one HMC to another.
- Fixed an issue where restore profile data did not restore
the SR-IOV physical port "Maximum SR-IOV logical port options"
for RoCE adapter. Attempting to activate current
configuration after the restore failed with error:
HSCL12E7 The operation cannot be completed because it will
cause the maximum number of RoCE logical ports on SR-IOV
adapter 2 physical port 1 to be exceeded.RoCE logical port
limit exceeded. Note that the user must still set the
adapter to shared mode prior to restore for this fix restore
shared mode settings.
- Updated error recovery timeouts and handling when messages
fail to transmit between two consoles connected to the same
managed server to eliminate the reporting of SRC E3325009 when
communication should be working. SRC E3325009 may still
be reported if port 9920 is blocked between the HMCs or if
name resolution is inconsistent for the HMC hostname and IP
address in the environment.
- Fixed an issue when activating a partition may result in
multiple pop-up messages:
Error launching task. Unable to process request, retry
after some time.
Your session has expired. Please close your browser and
logon again.
Security fixes
- Addressed libtiff vulnerabilities: CVE-2018-18661,
CVE-2018-18557, CVE-2018-17101, CVE-2018-17100, CVE-2018-12900,
CVE-2018-10963, CVE-2018-10779, CVE-2018-8905, CVE-2018-7456,
CVE-2016-3186
- Addressed libssh2 vulnerabilities: CVE-2019-3858,
CVE-2019-3861
- Addressed openssl vulnerabilities: CVE-2019-1559,
CVE-2018-0734
- Addressed httpd vulnerabilities: CVE-2019-0220, CVE-2019-0217
- Addressed openssh vulnerability: CVE-2018-15473
Command Line Changes
- The following commands have been enhanced to support virtual
persistent memory: chhwres, lshwres, lssyscfg.
- The following commands have been enhanced to support Hybrid
Network Virtualization: chsyscfg, lssyscfg, mksyscfg,
chhwres, lshwres, migrlpar, rrstartlpar.
- Note : The new Migratable option for Hybrid Network
Virtualization is provided as an unsupported technology
preview only and is not intended for production deployments.
- The following commands have been enhanced to support User Mode
NX (Nutanix Xtreme) accelerator enablement: chhwres, lshwres,
lssyscfg.
- The chlickey command has been added to add license
key information to a running IBM i partition.
- Added a new option to the migrlpar command to display
the steps that are completed during a validation or a migration
operation if the operation fails.
- The chpwrmgmt and lspwrmgmt commands have
been updated to support the power management modes for POWER9
servers.
- Added a new option to the viosvrcmd command to
specify a custom timeout value.
- Added frame support to the chprimhmc and lsprimhmc
commands.
- Added progress messages to the following commands: bkconsdata,
getupgfiles, rstupgdata, saveupgdata, updhmc.
- New options have been added to the chhmcencr and lshmcencr
commands to configure and display SSH key exchange
algorithms for the HMC.
- New options have been added to the bkconsdata command
to allow the user to specify the name of the backup file.
- The chaccfg and lsaccfg commands have been
enhanced to support automatic updates of custom managed resource
roles.
- The chhmcusr and lshmcusr commands have been
enhanced to set and display the default HMC user setting for the
maximum number of Web UI login attempts allowed.
- A new option has been added to the getfile command to
get and deploy a Baseboard Management Controller (BMC) CA
certificate file on the HMC.
- The chbmccert and lsbmccert commands have
been added to manage BMC certificates on the HMC.
- The chproxy and lsproxy commands have been
deprecated. The chsacfg and lssacfg commands can be used
instead.
- Added SFTP support and the ability to call home dumps to the cpdump
command.
- The chhmc and lshmc commands have been
enhanced to set and display the sshd UseDNS setting.
Syntax: chhmc -c ssh -s modify --sshusedns
{enable|disable}
An HMC reboot or restart of SSH is required.
Known issues and Limitations
- Concurrent Maintenance operation on Houston adapters fails
when migratable virtual function is assigned to an AIX partition
- When HMC is set as Co-Management Master for the first time,
any LPAR operation such as Shutdown / Activation, is not updated
in the gallery view. As workaround, change to any other view and
then again to gallery view.
- On the "Shared Storage Pool Cluster" view, the user will see
that the tier page will show some text in English regardless of
the locale setting.
- LPM validation button gets disabled (greyed out) when there is
an SR-IOV mapping failure at destination. It does not get
enabled even if "Override vNIC configuration" is selected.
- The disk size will be shown as 0 GB from Cluster->SSP
details-> tier details->LU details page. This happens when
the user uses one of the legacy panels (which are accessible
from System -> "Manage VIOS") to carve out a LU there, and
then use enhanced UI to attach it to a partition.
- When the last Virtual Optical device is removed, it continues
to be listed soon after unload media file operation. Manual
refresh of the browser page will clear the virtual optical
device from the list.
- The Repair option is enabled on the problem-actions menu and
leads to a blank page for LC systems although the operation is
not supported on these platforms.
- After hitting a configuration error during create network
bridge with fail-over option using the Add Virtual Network
wizard, the error message is not cleared automatically if the
configuration is corrected and operation is tried again. To
workaround the issue, close the wizard and relaunch the UI and
select the single VIOS for the operation.
- Add VIOS button in VIOS tab of Edit System Template doesn't
update the Total count automatically when a new VIOS is added.
- Group partition LPM of migratable virtual function may fail
with error HSCLB602 and HSCLAF17.
- Force option for DLPAR remove I/O adapter is not displayed on
GUI for IBMi partitions.
- GUI might display an error while trying to view the source
server after a remote restart operation when migratable VFs are
configured. To circumvent the problem, run the rebuild
command for the managed server.
- Modify Virtual Network Bridge window may not work properly for
enable failover operation on some versions of Safari.
- When pmem volumes are assigned to a partition, running chhwres
to remove memory results in an inappropriate error message.
Actual cause is the partition has one or more persistent memory
volumes assigned.
- Enabled automatic collection of LPM FFDC data, without the
need to run the command "migrdbg -o e" .
- FRU exchange procedure might fail when multiple FRUs are
selected.
- When performing cross HMC concurrent bidirectional multiple
single migration operations, one or two migration operations may
sometimes fail with the error message: "HSCL3202 Failed to
acquire lock because of timeout."
- When a LC system with expired password is connected to HMC,
HMC will not be manage the server and perform any operations on
the server. To work around the problem log in to the
- BMC GUI and change the expired password through that GUI prior
to connecting it to the HMC.
- Deploy Partition Template may fail with an error message
saying that there are no VIOS available on the CEC when one of
VIOS is in non-operational state.
- After a fresh install of the HMC, the first attempt to save
change and exit from the Change Network Settings will
appear to hang on the busy dialog. The settings are
successfully saved but the user must click the X to close the
window, log off or reboot to clear the task.
- HMC may fail to boot with error 1901 when cabled to a Juniper
switch. Circumvention is to remove the ethernet cable,
reboot, then recable after the HMC is booted.
- Attempting to edit, copy or deploy a template created at HMC
level earlier than V9 R1 940, may fail with error "REST0001
Failed to unmarshal input payload. Premature end of file"
or "HSCL0602 Partition with the same ID is already defined in
the managed system". To circumvent the issue, use the
export template option from Templates and OS Images View and
import the template again.
Installation
Installation NOTE: This PTF
can be installed on any level of V9 (starting at 910 with required
PTF MH01813 installed). However, IBM recommends applying this PTF
with the following installation order:
- First update to V9R1 M931, install pre-req PTF
MH01853/MH01854, then update to V9R1M940. Updating directly
from V9R1 M921.x or earlier may cause periodic transmit
service transactions such as Hardware inventory, Software
inventory, and Performance data to fail. Installation
instructions for HMC Version 9 upgrades and corrective service
can be found at these locations:
Upgrading
or restoring HMC Version 9
Updating,
upgrading, and migrating your HMC machine code
Instructions and images for upgrading via a remote network
install can be found here:
HMC
V9 network installation images and installation instructions
Web browser requirements
Learn about the requirements your web browser must meet to monitor
and control the HMC.
To access HMC through a remote browser in a Windows 7 environment,
you must have a minimum/default of 1600x900 screen resolution.
HMC web browser support requires HTML 2.0, JavaScript 1.0, Java™
Virtual Machine (JVM), Java Runtime Environment (JRE) Version 8
U151, and cookie support in browsers that will connect to the HMC.
Contact your support personnel to assist you in determining if
your browser is configured with a Java Virtual Machine. The web
browser must use HTTP 1.1. If you are using a proxy server, HTTP
1.1 must be enabled for the proxy connections. Additionally,
pop-ups must be enabled for all HMCs addressed in the browser if
running with pop-ups disabled.
The following browsers have been tested:
Google Chrome
This HMC version supports Google Chrome Version 73 (Official
Build) (64-bit).
Safari
This HMC version supports Safari 11.1
Mozilla Firefox
This HMC version supports Mozilla Firefox Version 60.5 Extended
Support Release (ESR) and Mozilla Firefox Version 60.6 Extended
Support Release (ESR). Ensure that the JavaScript options to raise
or lower windows and to move or resize existing windows are
enabled. To enable these options, click the Content tab in the
browser’s Options dialog, click Advanced next to the Enable
JavaScript option, and then select the Raise or lower windows
option and the Move or resize existing windows options. Use these
options to easily switch between HMC tasks. For more
information about the latest Mozilla Firefox ESR levels, see
Security
Advisories for Firefox ESR.
Safari
This HMC version supports Safari Browser Version 12.0.3
Clearing the Browser Cache
In Microsoft Internet Explorer
- Open the Browser
- Select Tools
- Select Internet Options
- Under Browser History, select Delete
- Check "Temporary Internet files and websites files"
and "Cookies and website data"
- Click on Delete
In Mozilla Firefox
1. In the top-right corner of the browser window click the
menubutton
Choose
History, and then
Clear
Recent History.
In time range to clear, select "
Everything"
In the Details section, select "
Cookies"
and "
Cache"
Click on "
Clear now"
2. In the top-right corner of the browser window click the menu
button
Choose
Options > Advanced > Network
>
In "
Offline Web Content and User Data"
section click on "
Clear Now"
In Google Chrome
1. In the top-right corner of the browser window, click the
Chrome menu
Choose
History.
Click the button
Clear browsing data. A
dialog will appear.
From the drop-down menu, select "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.
Mozilla Firefox
- Click Tools > Options.
- Click the Cookies Tab.
- Select Allow sites to set cookies.
If you want to allow only specific sites, select Exceptions,
and add the HMC to allow access.
Virtual HMC Installation for x86 hypervisors
Installation Images
Download of the Power Hardware Management Virtual Appliance (vHMC)
install images are available at the Entitled Systems Support site
(ESS):
http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. You must be entitled to Product ID 5765-HMW or 5765-HMV in
order to download 5765-HMW from the ESS site.
Upgrade of 5765-HMV to 5765-HMW is supported.
Fixes, mandatory fixes and service packs for the vHMC are common
to the Power Hardware management console (HMC) and will be
available at IBM
Fix Central.
The splash panel information (lshmc -V output) for the vHMC will
be the same as for the HMC recovery DVD that is documented in the
above description section.
Installation guidance for installing the vHMC into your hypervisor
is found in the
IBM
Knowledge Center. Installation procedures may vary depending
on the operating system you use and the hypervisor you use.
A feature of the vHMC is the activation engine which allows you to
preconfigure the HMC Console by passing configuration information
to the HMC at the first boot of the HMC, when using these images.
Please look at the on-line Knowledge Center documentation on using
the
Activation
Engine feature.
Notes for the Virtual Appliance for x86 hypervisors
- The supported hypervisors for x86 are
- VMWARE ESXi 6.0 or 6.5
- KVM on Red Hat RHEL7 or higher
- Xen 4.2 or higher on SLES 12
- There are now two images for the VMWare ESXi Server, one is
for ESXi 6.0 and the other for ESXi 6.5. This is due to
differences in the encoding of the OVA images. SHA1 for ESXi
6.0 , SHA256 for ESXi 6.5.
- The processor on the systems hosting vHMC for x86 must have
either Intel VT-x or AMD-V Hardware Virtualization enabled.
Installation methods for vHMC on x86 hypervisors
http://www.ibm.com/support/knowledgecenter/POWER8/p8hai/p8hai_installvhmc.htm
After the upgrade, install the mandatory fix using the
instructions at
Installation
methods for HMC Version 8 fixes
Virtual HMC for PowerVM LPARS
Installation Images
Download of the Power Hardware Management Virtual Appliance (vHMC)
install images are available at the Entitled Systems Support site
(ESS):
http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. You must be entitled to Product ID 5765-HMA or 5765-HMB in order
to download 5765-HMB from the ESS site.
Upgrade of 5765-HMA to 5765-HMB is supported.
Fixes, mandatory fixes and service packs for the vHMC are common
to the Power Hardware management console (HMC) and are available
at IBM Fix Central.
The splash panel information (lshmc -V output) for the vHMC will
be the same as for the HMC recovery DVD that is documented in the
above description section for the 7063 Machine type.
Installation guidance for installing the vHMC into your hypervisor
are found in the Online Knowledge Center. Installation procedures
may vary depending on the operating system you use and the
hypervisor you use.
Notes for the Virtual Appliance for PowerVM :
- On Power9 servers, the HMC Virtual Appliance for PowerVM
must run in Power8 compatibility mode, for this release.
- The HMC Virtual Appliance for PowerVM does not
provide graphics adapter support for adapters assign to the
partition. Use a supported web browser to point to the HMC for
UI support.
- DLPAR operations such as memory and processor moves for HMCs
running in an LPAR are not supported.
- Inactive partition migration and Simplified Remote Restart
operations are supported.
- The virtual appliance for PowerVM requires a Power8 or
Power9 server that is enabled for little endian support.
Minimum System Firmware 860 recommended for Power8 servers.
- vHMC for PowerVM cannot manage the server it is hosted on.
Installation of vHMC for LPARs:
http://www.ibm.com/support/knowledgecenter/POWER8/p8hai/p8hai_vhmc_pvm.htm
Back to top
General Virtual HMC notes
- Virtual HMC Appliance can be deployed in your existing POWER
virtualized infrastructure. Virtual HMC Appliance supports
install into PowerVM LPARs.
- Call home of serviceable events with a failing MTMS of the
HMC itself is disabled. Those serviceable events should
be manually reported to IBM software support.
- To see if you are running on a virtual HMC use the lshmc -v
command. If it displays a UVMID field, then you are running in
a virtual machine.
Example:
lshmc -v
"vpd=*FC ????????
*VC 20.0
*N2 Thu Sep 14 15:02:44 UTC 2017
*FC ????????
*DS Hardware Management Console
*TM Vc87-f0a
*SE 7f61457
*MN IBM
*PN N/A
*SZ 8371892224
*OS Embedded Operating Systems
*NA 127.0.0.1
*FC ????????
*DS Platform Firmware
*RM V8R8.7.0.0
*UVMID c87f:0a7f:603a:1457
"
- When deploying a virtual HMC, if the mac address is not
specified, it will be generated by the hypervisor.
Network configuration on the HMC relies on the value of MAC
addresses. If you re-deploy a new virtual HMC and want to
restore critical console data previously taken on a virtual
HMC, ensure sure you are using the same MAC addresses.
- When using Activation Engine to setup NTP configuration, you
must specify the NTP version value.
- We recommend upgrading to the new image that uses 500GB by
following the steps below:
- From the current HMC version (e.g. HMC V8.860.0),
upgrade to HMC V9 R1 M910
- When the upgrade is complete the HMC is now at a new
version but still has a 160GB disk.
- Perform a Critical Console Data backup, excluding
network information and store the backup to a remote
location.
- Deploy the new HMC V9 R1 M910 image which uses a 500GB
disk.
- After the HMC boots up with the 500GB disk, restore the
Critical Console data.
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