NIC Health and State Fields Returned as Null on HPE DL380 Gen11 Using iLOrest

[jungho]

Hello everyone,

I'm using an HPE DL380 Gen11 server and attempting to retrieve NIC status information via the following iLOrest command:

ilorest list --select NetworkAdapter. --json

However, when I review the output, the Health and State fields under Status are returned as null. Below is a shortened example of the JSON response:

[

  {

    "@Redfish.Settings":{...},

    "@odata.context": "/redfish/v1/$metadata#NetworkAdapter.NetworkAdapter",

    "@odata.id": "/redfish/v1/Chassis/1/NetworkAdapters/DA000000",

    "Controllers": {...}

    "Id": "DA000000",

    "Location": {...},

    "Manufacturer": "Broadcom",

    "Model": "BCM 5719 1Gb 4p BASE-T OCP Adptr",

    "Name": "BCM 5719 1Gb 4p BASE-T OCP Adptr",

    "Oem":{...}

    "PartNumber": "BCM95719N1905HC",

    "Ports":{...}

    "SerialNumber": {...},

    "Status": {

      "Health": null,

      "State": null

    }

  },

  {

    "@Redfish.Settings": {},

    "@odata.context": "/redfish/v1/$metadata#NetworkAdapter.NetworkAdapter",

    "@odata.etag": "W/\"1B6D48B0\"",

    "@odata.id": "/redfish/v1/Chassis/1/NetworkAdapters/DA000001",

    "@odata.type": "#NetworkAdapter.v1_9_0.NetworkAdapter",

    "Controllers": {...}

    "Id": "DA000001",

    "Location":{...}

    "Manufacturer": "",

    "Model": "Broadcom NetXtreme 5719 Quad Port Gigabit PCIe Adapter - NIC",

    "Name": "Broadcom NetXtreme 5719 Quad Port Gigabit PCIe Adapter - NIC",

    "Oem": {...}

    "PartNumber": "",

    "Ports":{...}

    "SerialNumber": {...},

    "Status": {

      "Health": null,

      "State": null

    }

  }

]

I’d like to understand why these fields are showing up as null. Is this expected behavior on the DL380 Gen11 with the Broadcom 5719 NICs, or is there a particular setting or firmware update required so that valid status information (e.g., Health and State) is populated?

Any guidance or suggestions to resolve this would be greatly appreciated.

Thank you!

[Moderator edit: Erased the confidential info.]

[Rama2]

The command is fetching the details, but the Health State is null.

1. Verify that the AMS (Agentless Management Service) is updated to the latest version.
2. Ensure the driver is at the recommended levels.
3. If all components are at the recommended levels, raise a support ticket with HPE. will review the logs and provide the Plan of Action (POA).