Fujitsu iRMC Redfish Endpoints for Storage missing in newer Firmware

Troubleshooting
1

(Checkmk 2.3.0p26, redfish 2.3.75, but that’s not really relevant to the problem.)

I noticed that for a Fujitsu iRMC, monitored via Redfish, suddenly the checks for storage and drive were missing. I compared different iRMCs in the monitoring and noticed the following:

  • Monitoring checks redfish_storage and redfish_drives work for iRMC boards with active managment controller firmware “3.60P&3.51” or “3.60P&3.69”
  • These checks do not work anymore with newer firmware “3.60P&3.87”
    (Firmware can be found in raw agent output or in GUI in details for Service “Firmware health” behind “This resource is enabled”.)

It turns out, Fujitsu does not list this information anymore in newer firmware versions.

  • Redfish query, which systems exist:
curl -k -u <user>:<password> https://<ip>/redfish/v1/Systems/0

...
  "Storage":{
    "@odata.id":"\/redfish\/v1\/Systems\/0\/Storage"
  },
...
  • Query of the present Storage systems returns empty list:
curl -k -u <user>:<password> https://<ip>/redfish/v1/Systems/0/Storage

{
  "@odata.id":"\/redfish\/v1\/Systems\/0\/Storage",
  "@odata.type":"#StorageCollection.StorageCollection",
  "Name":"Storage Collection",
  "Members":[
  ],
  "Members@odata.count":0,
  "Oem":{
  },
}

  • As there are no members, there are no endpoints to query for storage information.

  • Output with older firmware:

{
  "@odata.id":"\/redfish\/v1\/Systems\/0\/Storage",
  "@odata.type":"#StorageCollection.StorageCollection",
  "Name":"Storage Collection",
  "Members":[
    {
      "@odata.id":"\/redfish\/v1\/Systems\/0\/Storage\/0"
    }
  ],
  "Members@odata.count":1,
  "Oem":{
  },
}

And of course there you can query /redfish/v1/Systems/0/Storage/0 and /redfish/v1/Systems/0/Storage/0/Drives/0, redfish/v1/Systems/0/Storage/0/Drives/1, which in the newer firmware reuturns error output with “message”:“The requested URI does not refer to a valid resource.”

As the endpoints are missing, there’s nothing to fix in the redfish plugin. I’d just like to ask, if anyone can confirm this Fujitsu problem with version “3.60P&3.87”. And maybe, if someone might already have opened an issue at Fujitsu.

Kind regards,
Dirk.

2 Likes
2

Nice description of the problem.
One test what would be good to know is the following.
Inside the iRMC web interface the raid controller and the disks should also not be visible anymore.

If they are gone there, then it can also be a problem between raid controller firmware and iRMC firmware.

2 Likes
3

Wow, wouldn’t have thought this could be an issue. Thanks for your hint!

I checked, and indeed the raid controller is not shown in the iRMC web interface, either.

In the web interface I looked for version information and the 3.87 refers to the SDRR version, which according to the Fujitsu manual “Displays the version of information defining the sensor and threshold.”

Not quite sure when this is updated, but there’s hope: It seems to work with newer BIOS versions. It might still be an issue with the specific combination of SDRR version and BIOS, but at least that’s worth a try.

  • not working with BIOS V5.0.0.12 R1.63.0 for D3384-A1x
  • working with BIOS V5.0.0.14 R1.41.0 for D3384-B1x
    (Might also be an issue with A1x vs. B1x models, if that’s a model number, but an update should at least be worth a try.)

So I’ll recommend a BIOS update to the customer and hope it will help.

Thanks a lot for your input!

Kind regards,
Dirk.

4

Yeah this is also a problem with other vendors. Different firmware versions depend on one another and you don’t know it until it breaks.

1 Like