Authors:  Sasi Thumati(sasi.thumati@in.ibm.com), Bhupathiraju Jyothi Prasanna(bprasann@in.ibm.com)

INTRODUCTION:

I/O devices such as network adapters, storage controllers, Fibre Channel cards, and other peripheral hardware play a critical role in ensuring smooth data flow and system performance. These devices rely on embedded software known as microcode (or firmware) to function correctly.

Microcode (also known as firmware) is the low-level software embedded in hardware devices like I/O adapters, storage controllers, and network cards. Updating microcode ensures devices run efficiently, securely, and are compatible with the latest OS (Operating system),  and platform features

Microcode updates are essential maintenance tasks that involve upgrading this embedded software to a newer version provided by the hardware vendor. These updates are not just routine they are strategic actions that can significantly impact system reliability, performance, and security.

This document provides step-by-step guidance for installing I/O device microcode updates using Legacy IO(Input/Output) Firmware and Automated Platform Updates  via Hardware Management Console (HMC).

Before proceeding, ensure the following prerequisites are met:

Prerequisites

• Supported Partition Types: Updates can only be performed  through VIOS(Virtual I/O Server), AIX, , or Linux partitions.
• Device Assignment: Devices targeted for update must be assigned to an active partition.
• Server State: The server must be in an Operating state, and the relevant partitions must be active.
• RMC Connectivity: A valid Remote Management and Control (RMC) connection must be active between the HMC and the partitions.
• Firmware Catalog Availability: The catalog of I/O device firmware must be accessible either:
• Online via the IBM Website repository, or Locally from a pre-downloaded source

IO adapter update Via Update I/O firmware

Section 1: Navigating to Update IO Firmware  HMC

To locate the Update IO Firmware  feature in the HMC:
Select the desired system, then click on the Firmware section. Here, you will find options to Update IO firmware feature, as illustrated in Figure 1.

Figure 1:

Section 2. Accept the License 

Once you select the option it will redirect to License Agreement as shown in Figure 2.

Figure 2:

Section 3: Choose the Source Files

In this step, you can choose the source location for the update files from a variety of available options, as illustrated in Figure 3. These options allow you to specify where the update packages will be retrieved from before proceeding with the firmware update process.

Figure 3:

Section 4: Choose Logical Devices for Updates.

Once Source File is selected it will check the adapter current Microcode level and display if any updated is needed as shown in Figure 4 and 5
Figure 4:


Figure 5:

Note: If user what to skip any IO adapter Firmware update they can select delete icon to skip the update.

And if adapter is already at latest Microcode Firmware level it will display as No action under suggested action as shown in Figure 5.

Section 5: Applying the Update.

Once User selected the adapter he want to update then he can click Next as shown in Figure 5, And it will get navigated to update page. Once Microcode update is available it will update the adapter as shown in Figure 6.

Figure 6:

And during IO device update devices may Experience a brief disruption while updates are in progress.Once Microcode Update was successful on IO adapter it will be shown as displayed in Figure 7.
Figure 7:


IO adapter update Via Automated Platform Updates in HMC

FUNCTIONALITY AND BEHAVIOUR

1. Automated Platform Updates is a feature within the HMC (Hardware Management Console) that provides an open-access interface for I/O adapter firmware.

2. This interface enables HMC users to perform microcode updates.

•  I/O adapter firmware associated with partitions
•  SR-IOV adapter firmware

These updates are typically can be carried out as part of routine maintenance.

• Adapters associated with AIX, Linux, or IBM i partitions are not updated via this feature.
• Use existing HMC interfaces to update firmware for these adapters.

Section 1.1: Navigating to Automated Platform Updates in HMC

To locate the Automated Platform Updates feature in the HMC:

Select the desired system, then click on the Firmware section. Here, you will find options to update the system firmware, VIOS, and adapter microcode levels.
This interface represents the newly introduced Automated Platform Updates feature, as illustrated in Figure 1.1.

Figure 1.1:

Section 2.1. Accept the License 

Once you select the option it will redirect to License Agreement as shown in Figure 2.1.

Figure 2.1:

Section 3.1: System Readiness Check

Next, the system performs a readiness check to validate the environment before proceeding. This includes verifying the system status and identifying the number of VIOS instances present, as illustrated in Figure 3.1.
Figure 3.1:

At this stage, end users are presented with two options for handling update files, as shown in Figure 3.1:

1.     Import Files to the HMC Filesystem
This option allows users to import the update files directly into the HMC filesystem and immediately proceed with the update. The process is performed "on the fly," combining file import and code update in a single step.

2.     Import Files Only
This option is ideal for users who prefer to import the update files in advance and initiate the update at a later time, once the system is ready.

Section 4.1: Selecting Target Levels

In this step, you can choose the source location for the update files from a variety of available options, as illustrated in Figure 4.1. These options allow you to specify where the update packages will be retrieved from before proceeding with the firmware update process.

Figure 4.1:

Source File Location Methods
To proceed with the update, users must choose a method for sourcing the firmware update files. Based on the current firmware levels (as identified in Section 1.1), the following options are available as shown in Figure 4.1:

• IBM Service Website
  Retrieve the required firmware update or upgrade directly from the IBM service website and apply it to the system.
  
• SFTP Method
  Download the necessary firmware packages from IBM Fix Central to a remote FTP-enabled system. Then, use the SFTP method to perform the update by providing the appropriate login credentials and file path on the remote server.
  
• HMC Filesystem
  Download the firmware files directly to the HMC filesystem. This method supports updates for system firmware, VIOS, and I/O adapters.
  
• NFS Server
  Use a remote NFS server as a mount point to access the firmware files and perform the update from there.
  

Figure 4.1:

Section 5.1: Performing I/O Adapter Updates.

Once Source Files location is updated it will fetch Current IO adapter Firmware Level and if any adapter update is available it will show the available Firmware level to update.

NOTE: If user want to skip the update he can use Do Not Update option also. As shown in Figure5.1 and 6.1.

Figure 5.1:

Figure 6.1

Section 6.1: Apply Updates.

Once user select the IO adapter to update it will re-direct to Apply Updates, First it will import the files and once Import files got successful then it will apply the Updates as Shown in Figure 7.1.
Figure 7.1

Section 7.1: Update Successful.

Once Microcode Update is done it will show updated FW levels as Level is most current as shown in Figure8.1.

Figure 8.1:

Conclusion:

This tutorial explained 2 Methods to update IO adapter microcode Firmware update. Unlike software patches, microcode updates directly affect how hardware behaves, making them crucial for maintaining optimal system health.

Contacting the PowerVM Team

Have questions for the PowerVM team or want to learn more?  Follow our discussion group on LinkedIn IBM PowerVM or IBM Community Discussions