How To
Summary
The HMC can be used to query the current I/O firmware levels for a system and to update those firmware levels from a repository. The HMC does not have direct access to login to the partitions to perform I/O updates. It relies on the RMC infrastructure which is also used to DLPAR, service focal point, etc to provide this feature. On the partitions, the query and update process is done by the invscout command. Invscout will receive files from and send files back to the HMC via RMC.
Environment
Definititions of key terms used in this document
| Key Term | Definition |
|---|---|
| RMC | "Resource Monitoring and Control" subsystem within the AIX operating system, which is a feature that allows for monitoring and managing system resources on IBM Power Systems |
| invscout | Inventory Scout is a standard AIX utility that surveys AIX partitions for hardware and firmware information. |
| Microcode Survey Upload File (.mup) | A file with a list of the gathered microcode levels and the most recent levels available. |
| catalog.mic | Inventory database that contains information on all currently available microcode packages for devices. |
Always read the individual microcode documentation for devices on Fix Central for specific pre-requisites. The HMC will not warn if a device needs to be updated more than once, or that some devices need to be rmdeved or hot-plugged (power-cycled) after the update for their update to be complete. Do not use the HMC for devices with these requirements. The recommended way to update I/O is through the operating systems using the instructions in the individual microcode readme files, however, if the HMC will be used, the following known issues and limitations apply.
Known Issues and limitations
- Devices being updated must be assigned to a VIOS, AIX, or Linux partition in a running state.
- Invscout does not collect information on adapters that are shared (i.e. SRIOV in shared mode), assigned to hypervisor or IBMi.
- Server must be in Operating state and partitions must be active.
- An active RMC connection is required between the HMC and partitions.
- If using the “IBM Website” online repository from which to download firmware, reference the IBM Security Whitepaper regarding setting up output configuration and which IBM addresses and ports are used, specifically in the “Fix / Policy download Servers” section
- Concurrent I/O updates still result in a brief I/O outage of up to 40 seconds.
- The HMC can't update the Ethernet adapter which is used for RMC communication back to the HMC. The user must update these manually.
- The HMC doesn't know what adapters are redundant to each other nor in what order any of them should be updated. If all adapters are included in the update operation, all paths to storage devices could go down simultaneously and cause an outage.
Steps
1. Start the "Update I/O" firmware process on the HMC
2. Accept the license
3. Select the I/O firmware repository, for example the IBM Service Web Site or a Secure FTP site on the local network. From this repository, the HMC will download the catalog.mic file which will be used to compare with the information gathered from the partitions to determine which update actions are available.
4. HMC transfers the catalog.mic file to the LPAR and invscout surveys the partitions for currently installed microcode and device firmware on your system and will generate a report in the form of a file called hostname.mup.
5. Invscout will transfer the .mup files back to the HMC via RMC.
6. The HMC will use the .mup files to build a menu of I/O actions by partitions per device.
7. Review the "effect" and "suggested action" listed for each device.
- Use the information in the Effect column to determine whether the adapters or devices require you to shut down the adapter or take the device offline when you install the I/O adapter or device firmware updates.
- Use the information in the Suggested Action column to determine whether the HMC can manage the I/O adapters or devices listed in the table. If the Suggested Action column indicates Cannot Manage, you need to download and install the I/O adapter and device firmware fix through the operating system. Refer to the device readme to obtain the updates through the operating system.
8. Click the "trash can" icon to remove the devices from the list of devices to update and on which user does NOT want to take the reported "effect" action.
9. The rpm files (device microcode) are downloaded to the HMC from the repository for the device selected to be updated.
10. The appropriate rpm files are transferred to the partition for installation.
11. Invscout on the partition is used to install the rpm files.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB08","label":"Cognitive Systems"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSOQ2E","label":"Hardware Management Console V10"},"ARM Category":[{"code":"a8m50000000L2vzAAC","label":"Howto"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"POWER10","label":"IBM Power10"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}]},{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"POWER9","label":"IBM Power9"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}]}]
Was this topic helpful?
Document Information
Modified date:
24 June 2025
UID
ibm17182426