Monitoring NS204i Gen11 RAID Status with ilorest

[rotero]

I have a ProLiant DL380 Gen11 with an NS204i-u boot device. I need to periodically query the health of the NS204's RAID-1 so I can alert users when the RAID is degraded. I'm using the ilorest program to interact with the iLO 6 controller's Redfish API to achieve this.

First, I looked for the NS204 with the Storage and StorageController types, but it does not appear there:

ilorest --nologo get --select Storage.

ilorest --nologo get --select StorageController.

I do find the NS204 within the Volumes type alongside the volumes that are configured on the MR416i controllers. Then I use a filter to isolate the results that have the attribute "Name=NS Volume" like so:

ilorest --nologo get --select Volume. --filter "Name=NS Volume" --json
[
  {
    "@odata.etag": "W/\"5291d1d7\"",
    "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Volumes/1",
    "@odata.type": "#Volume.v1_4_0.Volume",
    "BlockSizeBytes": 512,
    "CapacityBytes": 480036519936,
    "DisplayName": "VD_1",
    "Encrypted": false,
    "Id": "1",
    "Identifiers": [
      {
        "DurableName": "0050434707000001",
        "DurableNameFormat": "EUI"
      }
    ],
    "Links": {
      "DedicatedSpareDrives": [],
      "DedicatedSpareDrives@odata.count": 0,
      "Drives": [
        {
          "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Drives/1"
        },
        {
          "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Drives/2"
        }
      ],
      "Drives@odata.count": 2
    },
    "LogicalUnitNumber": 1,
    "Name": "NS Volume",
    "Operations": [],
    "OptimumIOSizeBytes": 131072,
    "RAIDType": "RAID1",
    "ReadCachePolicy": "Off",
    "Status": {
      "Health": "OK",
      "State": "Enabled"
    },
    "StripSizeBytes": 131072,
    "VolumeUsage": "Data",
    "WriteCachePolicy": "Off"
  },
  {
    "@odata.etag": "W/\"5291d1d7\"",
    "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Volumes/1",
    "@odata.type": "#Volume.v1_4_0.Volume",
    "BlockSizeBytes": 512,
    "CapacityBytes": 480036519936,
    "DisplayName": "VD_1",
    "Encrypted": false,
    "Id": "1",
    "Identifiers": [
      {
        "DurableName": "0050434707000001",
        "DurableNameFormat": "EUI"
      }
    ],
    "Links": {
      "DedicatedSpareDrives": [],
      "DedicatedSpareDrives@odata.count": 0,
      "Drives": [
        {
          "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Drives/1"
        },
        {
          "@odata.id": "/redfish/v1/Systems/1/Storage/DE00B000/Drives/2"
        }
      ],
      "Drives@odata.count": 2
    },
    "LogicalUnitNumber": 1,
    "Name": "NS Volume",
    "Operations": [],
    "OptimumIOSizeBytes": 131072,
    "RAIDType": "RAID1",
    "ReadCachePolicy": "Off",
    "Status": {
      "Health": "OK",
      "State": "Enabled"
    },
    "StripSizeBytes": 131072,
    "VolumeUsage": "Data",
    "WriteCachePolicy": "Off"
  }
]

This leads me to a few questions:

• Why does the same volume appear twice in the response?
• Is it appropriate to use the Status > Health attribute to indicate whether the RAID is consistent or degraded? What other values besides OK might appear in this field?
• Can we rely on the Name attribute to always be NS Volume, or is there a better way to identify the NS204i RAID volume? (Filtering on the name seems fragile to me.)

[ngnear]

Hi There,

Thank you for reaching out.

We understand the concern, however for us to check in detail, we would require certain logs.

It would be helpful if you can log a Support Ticket with us on our HPE Support Center for further isolation. https://support.hpe.com/connect/s/?language=en_US

Good luck

[rotero]

I submitted case number 5377306685.

[ngnear]

Thank you for logging the case.

An HPE Engineer shall assist you further with 5377306685.
Meanwhile, we shall be closing 5377252133.

Good luck.