Redfish Device Enablement (RDE) support

HPE iLO implements the Platform Level Data Model for Redfish Device Enablement (PLDM for RDE) DMTF standard. In this section the term RDE is a shortcut for PLDM for RDE. The term RDE capable device refers to a physical device (i.e. storage controller) implementing PLDM for RDE.

RDE enables management controllers (i.e. iLO) to present a Redfish-conformant data model, without the need of embedding specific code related to the vendor, family or model device. When PLDM for RDE is implemented in both the management controller and the device, the former acts as a request forwarder (pass-through) between the Redfish client and the device.

In the detail, RDE capable management controllers and devices may use the Management Component Transfer Protocol (MCTP) to exchange Redfish encoded messages. By default, HPE iLO enables MCTP globally as well as on all possible device slots. Refer to the iLO user guide for managing MCTP from the GUI (System Information --> Device Inventory --> Discovery).

MCTP management with Redfish

For troubleshooting or other reasons, you may want to disable or factory reset the MCTP.

Retrieve MCTP status

The following example retrieves the MCTP global status and the status of slot 5.

GET /redfish/v1/Chassis/1/?$select=Oem/Hpe/MCTPEnabledOnServer

GET /redfish/v1/Chassis/1/devices/5/?$select=MCTPProtocolDisabled

Disable the MCTP globally

POST /redfish/v1/Chassis/1/Actions/Oem/Hpe/HpeServerChassis.DisableMCTPOnServer/

{}

{
    "error": {
        "code": "iLO.0.10.ExtendedInfo",
        "message": "See @Message.ExtendedInfo for more information.",
        "@Message.ExtendedInfo": [
            {
                "MessageId": "Base.1.12.Success"
            }
        ]
    }
}

Disable the MCTP on a specific slot

PATCH: /redfish/v1/Chassis/{{ChassisId}}/devices/{{slotId}}/

{
    "MCTPProtocolDisabled": true
}

{
    "error": {
        "code": "iLO.0.10.ExtendedInfo",
        "message": "See @Message.ExtendedInfo for more information.",
        "@Message.ExtendedInfo": [
            {
                "MessageId": "Base.1.12.Success"
            }
        ]
    }
}

MCTP factory reset

In order to globally re-enable the MCTP and all the specific slots, a MCTP factory reset is required.

POST /redfish/v1/Chassis/1/Actions/Oem/Hpe/HpeServerChassis.FactoryResetMCTP

{}

{
    "error": {
        "code": "iLO.0.10.ExtendedInfo",
        "message": "See @Message.ExtendedInfo for more information.",
        "@Message.ExtendedInfo": [
            {
                "MessageId": "Base.1.12.Success"
            }
        ]
    }
}

iLO RDE URIs and corresponding HTTP methods

The following table lists the Redfish URIs enabled by iLO for RDE capable devices. Cells contain the list of iLO generations supporting operations, or a dash character ("-") if the operation is not applicable or not supported. Refer to the iLO 5 changelog file and look for string RDE support changes to get the first firmware version implementing RDE operations. iLO 6 implements all mentioned operations since version 1.05.

RDE capable device schema file locations

Redfish responses from RDE enabled devices depend on the schema versions that are supported by each device. They may vary across device vendors, families and models. The schema files describing RDE capable devices are not stored in iLO and usually not in the device. However, their location is in the Link response header property of HEAD requests.

These schema files can be obtained using iLOrest tool.

Controller schema file location of an RDE capable storage controller

ilorest rawhead /redfish/v1/Systems/1/Storage/DE07C000 2>/dev/null | jq '.Link'

https://redfish.dmtf.org/schemas/Storage.v1_13_0.json

Volume schema file location of an RDE capable logical volumes

ilorest rawhead /redfish/v1/Systems/1/Storage/DE07C000/Volumes 2>/dev/null | jq -r '.Link'

https://redfish.dmtf.org/schemas/VolumeCollection.json

Network port schema file location of an RDE capable network adapter

ilorest rawhead /redfish/v1/Chassis/1/NetworkAdapters/DE080000/NetworkPorts 2>/dev/null | jq '.Link'

http://redfish.dmtf.org/schemas/v1/NetworkPortCollection.json

For more detail concerning PLDM for RDE, refer to the DMTF RDE specification.