ESXi Host Reporting Stale SPP Version After HPE Firmware Update
search cancel

ESXi Host Reporting Stale SPP Version After HPE Firmware Update

book

Article ID: 430117

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Following the HPE Service Pack for ProLiant (SPP) update, reporting discrepancy may occur. While the HPE iLO correctly displays the newly installed SPP version (e.g., 2024.09.00.00.01), querying the ESXi host locally via the HPE RESTful Interface Tool (ilorest) returns a stale version (e.g., 2023.09.00.00.01)

  • This mismatch can cause compliance audits, automated monitoring scripts, and vCenter hardware status plugins to flag the host as non-compliant or outdated, despite the firmware being successfully applied at the hardware level.    
  • To verify if the ilorest VIB is installed, establish an SSH connection to the ESXi host, log in as "root" and execute the following command:: 
    esxcli software vib list

         Note: When querying the installed VIBs, the package will be listed specifically as ilorest.

Environment

VMware vSphere ESXI

Cause

  • When an SPP is applied, the updated baseline version string is written to the iLO firmware and system ROM. However, the ServerOtherInfo attribute within the BIOS—which is read by the local OS and ilorest utility—can occasionally fail to synchronize or refresh its cached string during the update process. As a result, the ESXi host continues to read and report the stale SMBIOS/BIOS attribute from the previous baseline.

Resolution

To resolve this issue, manually override the stale BIOS string using the ilorest command-line utility directly from the ESXi host shell, commit the changes, and reboot the host.

         Note: While the examples below use a 2023 to 2024 SPP update scenario, this methodology applies to any SPP version mismatch.

 

  1. Verify the Current Stale Version: Ensure SSH is enabled on the ESXi host via vCenter (Configure > Services > SSH)  Login as "root user" and execute following command to check the current SPP baseline cached in the BIOS: 
    /opt/ilorest/bin/ilorest.sh -- nologo -- nocache get ServerOtherInfo -- select Bios

     

    Sample Output: 

    [root@ :~ ] /opt/ilorest/bin/ilorest.sh -- nologo -- nocache get ServerOtherInfo -- select Bios
Discovering data ... Done
ServerOtherInfo=2023.09.00.00.01

Expected Output (showing the stale version): ServerOtherInfo=2023.09.00.00.01

     

  2. Stage and Commit the Correct SPP Version:  Use the set command to override the ServerotherInfo attribute with the correct SPP version currently reflected in your iLO interface.  Replace the version number below with your specific target version 
    /opt/ilorest/bin/ilorest.sh -- nologo set ServerOtherInfo=2024.09.00.00.01 -- select Bios -- commit

    Note: The -- commit flag ensures the staged changes are written to the system ROM 

  3. Reboot the ESXi Host: This ensures the BIOS changes are applied and exposed to the ESXi operating system
    1. Place the ESXi host into Maintenance Mode via vCenter Webclient or through ILO
    2. Reboot the Host


  4. Verify the Resolution: Once the host is back online, reconnect via SSH and run the initial query command again to ensure the cache has been updated successfully:  
    /opt/ilorest/bin/ilorest.sh -- nologo -- nocache get ServerOtherInfo -- select Bios

    Sample Output: 

    [root@ :~ ] /opt/ilorest/bin/ilorest.sh -- nologo -- nocache get ServerOtherInfo -- select Bios
Discovering data ... Done
ServerOtherInfo=2024.09.00.00.01

 

 

 

   

Powered by Wolken Software