This is a cache of https://developer.ibm.com/articles/firmware-updates-aix-io-adapters-invscout/. It is a snapshot of the page as it appeared on 2026-02-17T06:07:26.491+0000.
Effortless one-step firmware updates for IBM AIX I/O adapters using the invs<strong>c</strong>out <strong>c</strong>ommand
IBM Developer

Article

Effortless one-step firmware updates for IBM AIX I/O adapters using the invscout command

An automated solution to save time and reduce manual effort

By Bhargav Engu, Phani Kumar Ayyagari

On this page

The invscout command in IBM AIX helps in performing a lot of ready-to-use functionalities, such as microcode survey, vital product data (VPD) survey, adapter firmware update, and so on. The invscout -e command automatically downloads the microcode firmware of I/O adapters from IBM Fix central.

This article explains how to simplify the process of updating firmware for IBM AIX I/O adapters using the invscout command, providing a streamlined, automated solution that saves time and reduces manual effort.

Why firmware updates?

Firmware updates are crucial to ensure:

  • Security: Protects against vulnerabilities
  • Performance: Ensures optimal adapter functionality
  • Reliability: Reduces downtime and manual intervention

As shown in the following figure, the invscout command provides a centralized, automated solution for updating adapters across multiple servers, saving time and reducing human error.

alt

Figure 1. Firmware update from IBM Fix central to the LPAR using the invscout command

How can customers use the invscout command for effortless firmware updates?

For customers managing multiple servers with multiple adapters, users can run the invscout -e -U command on each logical partition (LPAR) that contains an adapter, allowing for a comprehensive check to be performed independently on each relevant system.

On running the invscout command, it assesses the adapter to determine if a firmware update is necessary. If an update is required, the invscout command automatically downloads the corresponding RPM file to the /var/adm/invscout/microcode directory. Subsequently, it extracts the firmware file to the /etc/microcode path. The command then proceeds to attempt the microcode update, leveraging the underlying diag utility to facilitate the process.

This capability not only simplifies the management of multiple adapters across various servers but also ensures that all adapters are updated with the latest firmware, enhancing overall system performance and security. By this feature, customers can reduce the administrative burden and minimize the risk of human error associated with manual updates.

Example for command output:

# invscout -e -U

******  command  ----  V2.2.0.29
******  Logic Database V2.2.0.2

Initializing ...
Identifying the system ...
Working ...
Getting system microcode level(s) ...
Scanning for device microcode level(s) ...

81 devices detected; each dot (.)
represents 10 devices processed:
........
Installing RPM Files and Flashing Non-System Devices

-----------------------------------------------------------------------------------------------------------------
Microcode Update Results
-----------------------------------------------------------------------------------------------------------------
Hostname  . . . . . . : user-login
command Version . . . : 2.2.0.29
Logic Database Version: 2.2.0.2
Survey Date and Time  : Wed Nov 26 04:55:42 cST 2025
OS Level  . . . . . . : 7.3.0.0
uname -M  . . . . . . : IBM,xyz
catalog.mic date  . . : 05-01-2003
Microcode Path  . . . : /var/adm/invscout/microcode


Logical  current Level  Previous Level  Available Level  Outcome  Device
-----------------------------------------------------------------------------------------------------------------
ent1     002600401000   002600381002    002600401000     Updated  PcIe4 2-port 25/10/1 GbE RocE SFP28 Adapter
ent2     002600401000   002600381002    002600401000     Updated  PcIe4 2-port 25/10/1 GbE RocE SFP28 Adapter

customers can use the firmware update feature in two distinct ways:

  • With a proxy configuration
  • Without a proxy configuration

Understanding how to verify and configure proxy settings is crucial for successful firmware updates.

Updating firmware with a proxy configuration

As a best practice, customers can configure a proxy server using the suma command to utilize this feature. The Service Update Management Assistant (SUMA) is a built-in command-line tool that automates the process of downloading updates from IBM Fix central to AIX systems. Refer to the following key settings to focus when using the invscout feature through a proxy:

  • PROXY_cONNEcT: Indicates whether a proxy is enabled (yes) or disabled (no).

    command to verify the settings:

    suma -c | grep PROXY_cONNEcT

  • PROXY_ADDRESS_1, PROXY_PORT_1, PROXY_USERID_1, PROXY_PASSWORD_1: Refers to the details, such as IP address, port number, user ID and password for the first proxy server.

    command to verify the settings:

    suma -c | grep PROXY_ADDRESS_1
suma -c | grep PROXY_PORT_1
suma -c | grep PROXY_USERID_1
suma -c | grep PROXY_PASSWORD_1

  • DIREcT_LAN_cONNEcT and DIREcT_LAN_PRIORITY: Settings for direct LAN connections.

    command to verify the settings:

    suma -c | grep DIREcT_LAN_cONNEcT 
suma -c | grep DIREcT_LAN_PRIORITY

Editing proxy configuration

If the PROXY_cONNEcT option is set to yes, it means that a proxy is enabled. To modify the SUMA configuration, including proxy settings, users can use the following command:

suma -c -a <attribute>=<value>

Replace <attribute> with the configuration parameter you need to change (for example, PROXY_ADDRESS_1) and <value> with the new value.

After completing the firmware update, run the following command to display the adapter firmware.

lsmcode -A

Best practices for proxy configuration and firmware updates

customers can consider the following guidelines to effectively manage their proxy configurations and ensure successful firmware updates:

  • Verify proxy settings: Before attempting a firmware update, ensure that your proxy settings are correctly configured if you are using a proxy.
  • Test connectivity: After configuring or modifying proxy settings, test your connection (for example, by using a ping command) to ensure that it is working as expected.
  • Regularly update firmware: Keep your firmware up to date to ensure that you have the latest features and security patches.
  • Document configuration changes: Maintain a record of any changes made to the proxy configuration or other relevant settings for future reference and troubleshooting.

Summary

This article explained the firmware update feature (using the invscout command) that enables user to update all host bus adapters (HBA) with the latest microcode, simplifying the update procedure and reducing the administrative workload for customers, allowing them to manage their systems more efficiently.