New FLRT Feature – HMC host recommendations
esupport 060000D5Y9 Visits (2149)
The IBM Fix Level Recommendation Tool (FLRT) has added a new feature to our Power Systems recommendations report that allows Power Systems administrators to specify the Hardware Management Console (HMC) host system to allow them to receive more accurate fix level recommendations. FLRT continues to provide Power Systems administrators information about the recommended levels for their systems. FLRT has provided recommended levels for the HMC software associated to your Power System for many years, however, as the variety of options for running an HMC has increased, the recommendations have not always been as clear regarding the recommended levels for different types of hosts.
Hardware Management Console hosts
Currently, Power Systems support four different type of HMC hosts:
For additional information about each type of host and the HMC software supported by that host, refer to the Power code matrix for HMC hardware.
When you have installed your HMC on some types of physical hosts, that host may not support the latest levels of HMC software. In order to get accurate recommendations, specifying the HMC host will allow FLRT to identify what HMC software versions are supported on your specific host.
Specifying an HMC host in FLRT
Specifying an HMC host is optional for all FLRT Power Systems recommendations reports. There are multiple ways to specify the host.
Using the FLRT Power systems report web interface
To specify your HMC host as part of a Power Systems recommendation report, access FLRT at http
The selection is optional, but the drop down will show all hosts that are supported by that version of HMC software. You can select one HMC host option and submit the report.
The report will include the HMC host selected as part of the report.
The recommendations will only include levels that are supported by the HMC host you specified. In other words, if your HMC host only supports some of the available versions of HMC software, the highest recommended level will be the highest level supported by the specified HMC host.
The HMC report now also displays the fixes available for both your current HMC version and any fixes available for any recommended updates or upgrades.
In some instances, in order to upgrade your HMC software, you may need to update to an intermediate release of HMC software. These details are documented in Recommended Fixes – HMC Code Upgrades which is linked in the notes of all HMC recommendations. Additionally, all HMC recommendations include the new FLRT version timeline feature which shows a graphical representation of the update and upgrade path. For more details about this feature, you can read our blog.
As always, FLRT recommends levels based on information from the Power Systems development and support teams; there may be newer versions of HMC software that are available that have not met the criteria for being recommended either based on the amount of time since they have been released or the number of customer systems that have installed that level.
Using the FLRT Power Systems report programmatic interface
The FLRT Power systems reports can also be accessed programmatically. For more information about using FLRT in this way, please refer to our blog Programmatic Use of FLRT. The HMC host information can be specified as part of the programmatic request. Note that because the HMC host is an optional parameter, existing FLRT programmatic calls do not need to be modified to include it.
To specify the HMC host, add the parameter p0.hmchost= to the URL, for example:
The format of the HMC host is straightforward as well, for physical HMC hosts, the format is the machine type and model separated by a dash such as 7063-CR1 or 7042-CR9. For virtual HMC hosts, the format is similar, but the two options are VIRT-X86 and VIRT-PWR.
The response for the HMC host information is very similar regardless of whether the return format is text, XML or JSON. An additional section is added to the report showing the HMC host value selected. For example (in JSON):
"name": "HMC Host Servers",
"nickname": "HMC Host",
As always, we value your feedback! Please use our feedback tool to submit a feature request, bug report, or suggestion directly to the developers at: http
You may also follow us on Twitter @IBMSysESupp for the latest updates.
The FLRT and FLRTVC team
John Goodson is an IT Architect for Electronic Support in Austin, TX. John has designed numerous support sites in his 17 years at IBM including the IBM Support Portal and IBM Call Home Web.
Joel Ruiz is an IBM Electronic Support developer in Austin, TX. He developed FLRTVC and the FLRT Beta website and welcomes your feedback.
Morgan Tong joined IBM in 1998. During his 17+ years with IBM, he has worked in many of the IBM divisions and product teams as a software engineer.
Ron Theriault is the primary developer of FLRT and some other support tools. He has spent many years in academia, developing software on various Unix/Posix platforms, and has been using Java since 1995.
Laurie Kruger is a project manager with IBM Electronic Support. She monitors several IBM Electronic Support twitter accounts and various feedback mechanisms and looks forward to your input.