Skip to main content

Chassis Resources

Chassis resources are used to query the physical chassis, mainboard, fans, temperature, and power status of the device, as well as to set the fan mode, UID indicator LED, and overall power state.

Plain HTTP requests on this page support HTTP Basic Auth and session tokens. The token is carried in the `X-Xsrf-Token` request header, not in the request body. In the examples, replace `` with `http` or `https` according to the service configuration. The current backend registers only one chassis, with `ChassisId` set to `bmc`. Clients should also query the chassis resource collection first, then obtain the actual path from `Members[].@odata.id`.

1 Chassis Resource Collection

Query the list of chassis resources on the current device.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Request bodyNone
Success status code200 OK
Basic Auth Token ```bash title="Query the Chassis Resource Collection" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis' ``` ```bash title="Query the Chassis Resource Collection Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis' ```

Response Example

The following is a real response returned by a test device, with HTTP status code 200 OK. DateTime is the request time and changes with each query.

200 OK
{
"@odata.id": "/redfish/v1/Chassis",
"@odata.type": "#ComputerSystemCollection.ComputerSystemCollection",
"DateTime": "2026-08-04T16:39:32.575+08:00",
"Description": "The collection of Chassis resource instances",
"Members": [
{
"@odata.id": "/redfish/v1/Chassis/bmc"
}
],
"Members@odata.count": 1,
"Name": "Chassis Collection"
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the chassis resource collection.
@odata.typestringOData type of the chassis resource collection.
DateTimestringTime at which the server generated the response.
DescriptionstringDescription of the chassis resource collection.
MembersarrayList of chassis resource members.
Members[].@odata.idstringAccess path of a specific chassis resource.
Members@odata.countnumberNumber of chassis resources.
NamestringName of the chassis resource collection.

2 Chassis Status Resource

2.1 Query Chassis Status

Query the chassis model, dimensions, health status, power state, UID LED status, and OEM mainboard information.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}
Path parametersChassisId: chassis identifier, currently bmc
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Chassis Status" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc' ``` ```bash title="Query Chassis Status Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc' ```

Response Example

The following is an excerpt of the core fields from a real 200 OK response. The device serial number, version, power, and UID status depend on the actual device.

200 OK · Excerpt of a Real Response
{
"@odata.id": "/redfish/v1/Chassis/bmc",
"@odata.type": "#Chassis.v1_22_0.Chassis",
"ChassisType": "Drawer",
"DepthMm": 421.3,
"EnvironmentalClass": "A2",
"HeightMm": 44.4,
"HotPluggable": false,
"Id": "bmc",
"IndicatorLED": "Off",
"Manufacturer": "Firefly",
"MaxPowerWatts": 450,
"MinPowerWatts": 150,
"Name": "Computer System Chassis",
"Oem": {
"Firefly": {
"Mainboard": {
"Manufacturer": "Firefly",
"ProductName": "CS-B1",
"SerialNumber": "21",
"ChassisShell": "1U",
"BoardName": "CS-B1",
"Version": "v1.0",
"Fullname": "1U:CS-B1:v1.0"
}
}
},
"PowerState": "On",
"SerialNumber": "21",
"Status": {
"Health": "OK",
"HealthRollup": "OK",
"State": "Enabled"
},
"ThermalDirection": "FrontToBack",
"UUID": "a29d0b37-1414-5d2b-99fa-e6804dd73440",
"Version": "v1.0",
"WeightKg": 8,
"WidthMm": 420
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the chassis resource.
@odata.typestringOData type of the chassis resource.
ChassisTypestringChassis type; the current response is Drawer.
DepthMmnumberChassis depth in millimeters.
EnvironmentalClassstringEnvironmental class applicable to the chassis.
HeightMmnumberChassis height in millimeters.
HotPluggablebooleanWhether the chassis supports hot-plugging.
IdstringChassis resource identifier.
IndicatorLEDstringCurrent UID LED status, such as Lit, Blinking, or Off.
ManufacturerstringChassis manufacturer.
MaxPowerWattsnumberMaximum chassis power in watts.
MinPowerWattsnumberMinimum chassis power in watts.
NamestringChassis resource name.
OemobjectOEM extension information for the chassis.
Oem.FireflyobjectFirefly OEM extension information.
Oem.Firefly.MainboardobjectFirefly mainboard information.
Oem.Firefly.Mainboard.ManufacturerstringMainboard manufacturer.
Oem.Firefly.Mainboard.ProductNamestringMainboard product name.
Oem.Firefly.Mainboard.SerialNumberstringMainboard serial number.
Oem.Firefly.Mainboard.ChassisShellstringChassis form factor.
Oem.Firefly.Mainboard.BoardNamestringMainboard name.
Oem.Firefly.Mainboard.VersionstringMainboard version.
Oem.Firefly.Mainboard.FullnamestringFull name composed of the chassis form factor, mainboard name, and version.
PowerStatestringCurrent overall power state.
SerialNumberstringChassis or device serial number.
StatusobjectChassis status information.
Status.HealthstringChassis health status.
Status.HealthRollupstringChassis rollup health status.
Status.StatestringChassis operational state.
ThermalDirectionstringChassis airflow direction.
UUIDstringUniversally unique identifier of the chassis.
VersionstringChassis hardware version.
WeightKgnumberChassis weight in kilograms.
WidthMmnumberChassis width in millimeters.

2.2 Query Mainboard Information

Query the model, serial number, version, and environmental specifications of the Firefly OEM extended mainboard.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/Oem/Firefly/Board
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Mainboard Information" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Oem/Firefly/Board' ``` ```bash title="Query Mainboard Information Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Oem/Firefly/Board' ```

Response Example

200 OK
{
"@odata.id": "/redfish/v1/Chassis/bmc/Oem/Firefly/Board",
"@odata.type": "#BoardInfo.v1_0_0.BoardInfo",
"Id": "BoardInfo",
"Name": "Oem Board Info",
"info": {
"Manufacturer": "Manufacturer",
"ProductName": "CS-B1",
"SerialNumber": "21",
"EnvironmentalClassOpt": {
"Degrees": "10°C-35°C",
"RelativeHumidity": "20%RH-80%RH",
"Specification": "SHRAE_A2"
},
"Oem": {
"ChassisShell": "1U",
"BoardName": "CS-B1",
"ProductName": "CS-B1",
"Version": "v1.0",
"Fullname": "1U:CS-B1:v1.0"
}
}
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the OEM mainboard resource.
@odata.typestringOData type of the OEM mainboard resource.
IdstringMainboard information resource identifier.
NamestringMainboard information resource name.
infoobjectDetailed mainboard information.
info.ManufacturerstringManufacturer information.
info.ProductNamestringMainboard product name.
info.SerialNumberstringMainboard serial number.
info.EnvironmentalClassOptobjectEnvironmental class options.
info.EnvironmentalClassOpt.DegreesstringAllowed ambient temperature range.
info.EnvironmentalClassOpt.RelativeHumiditystringAllowed relative humidity range.
info.EnvironmentalClassOpt.SpecificationstringApplicable environmental specification.
info.OemobjectMainboard OEM extension information.
info.Oem.ChassisShellstringChassis form factor.
info.Oem.BoardNamestringMainboard name.
info.Oem.ProductNamestringOEM product name.
info.Oem.VersionstringMainboard version.
info.Oem.FullnamestringFull mainboard name.

3 Fan Management Resources

3.1 Query Thermal and Fan Status

Query fan speed, speed-control mode, fan health status, and temperature sensor readings.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/Thermal
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Thermal and Fan Status" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Thermal' ``` ```bash title="Query Thermal and Fan Status Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Thermal' ```

Response Example

The following is an excerpt of the core fields from a real 200 OK response. The actual response contains 6 fan members; one member and one temperature sensor are shown here. Speeds and temperatures vary with the operating state of the device.

200 OK · Excerpt of a Real Response
{
"@odata.id": "/redfish/v1/Chassis/bmc/Thermal",
"@odata.type": "#Thermal.v1_7_1.Thermal",
"Fans": [
{
"MemberId": "5",
"Model": "server-fan",
"Name": "5",
"PhysicalContext": "Fan",
"ReadingUnits": "RPM",
"SensorNumber": 5,
"Reading": 6329,
"Oem": {
"Firefly": {
"FanMode": {
"Mode": "Balanced"
},
"SpeedRatio": 30,
"Position": "",
"SlotNumber": 5
}
},
"Status": {
"Health": "OK",
"HealthRollup": "OK",
"State": "Enabled"
}
}
],
"Fans@odata.count": 6,
"Id": "Thermal",
"Name": "Thermal",
"Temperatures": [
{
"PhysicalContext": "CPU",
"Name": "Weighted mean temperature",
"ReadingCelsius": 35,
"SensorNumber": 0,
"Status": {
"Health": "OK",
"HealthRollup": "OK",
"State": "Enabled"
}
}
],
"Temperatures@odata.count": 1
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the thermal resource.
@odata.typestringOData type of the thermal resource.
FansarrayList of fan members.
Fans[].MemberIdstringFan member identifier.
Fans[].ModelstringFan model.
Fans[].NamestringFan name.
Fans[].PhysicalContextstringPhysical component the sensor belongs to.
Fans[].ReadingUnitsstringFan reading unit; currently RPM.
Fans[].SensorNumbernumberFan sensor number.
Fans[].ReadingnumberCurrent fan speed.
Fans[].OemobjectFan OEM extension information.
Fans[].Oem.FireflyobjectFirefly fan extension information.
Fans[].Oem.Firefly.FanModeobjectFan speed-control mode information.
Fans[].Oem.Firefly.FanMode.ModestringCurrent fan mode.
Fans[].Oem.Firefly.SpeedRationumberFan speed ratio.
Fans[].Oem.Firefly.PositionstringFan position description.
Fans[].Oem.Firefly.SlotNumbernumberFan slot number.
Fans[].StatusobjectFan status information.
Fans[].Status.HealthstringFan health status.
Fans[].Status.HealthRollupstringFan rollup health status.
Fans[].Status.StatestringFan operational state.
Fans@odata.countnumberNumber of fan members.
IdstringThermal resource identifier.
NamestringThermal resource name.
TemperaturesarrayList of temperature sensors.
Temperatures[].PhysicalContextstringPhysical component the temperature sensor belongs to.
Temperatures[].NamestringTemperature sensor name.
Temperatures[].ReadingCelsiusnumberTemperature reading in degrees Celsius.
Temperatures[].SensorNumbernumberTemperature sensor number.
Temperatures[].StatusobjectTemperature sensor status information.
Temperatures[].Status.HealthstringTemperature sensor health status.
Temperatures[].Status.HealthRollupstringTemperature sensor rollup health status.
Temperatures[].Status.StatestringTemperature sensor operational state.
Temperatures@odata.countnumberNumber of temperature sensors.

3.2 Query Fan Mode Parameters

Query the parameters, values, and numeric ranges allowed when setting the fan mode.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/FanModeActionInfo
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Fan Mode Parameters" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/FanModeActionInfo' ``` ```bash title="Query Fan Mode Parameters Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/FanModeActionInfo' ```

Response Example

200 OK
{
"@odata.id": "/redfish/v1/Chassis/bmc/FanModeActionInfo",
"@odata.type": "#ActionInfo.v1_1_2.ActionInfo",
"Id": "ActionInfo",
"Name": "Action Info",
"Parameters": [
{
"DisallowedInput": false,
"AllowablePattern": "",
"DataType": "Number",
"Name": "FanCustLevel",
"Required": false,
"MinimumValue": 1,
"MaximumValue": 20
},
{
"DisallowedInput": false,
"AllowablePattern": "",
"AllowableValues": [
"Silent",
"Balanced",
"Powerful",
"Custom"
],
"DataType": "String",
"Name": "Mode",
"Required": false
}
]
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the fan mode ActionInfo resource.
@odata.typestringOData type of the ActionInfo resource.
IdstringActionInfo resource identifier.
NamestringActionInfo resource name.
ParametersarrayList of parameter definitions for the fan mode setting interface.
Parameters[].DisallowedInputbooleanWhether input is disallowed for this parameter.
Parameters[].AllowablePatternstringString pattern allowed for the parameter; an empty string means unrestricted.
Parameters[].AllowableValuesarrayList of values allowed for string parameters.
Parameters[].DataTypestringParameter data type.
Parameters[].NamestringParameter name, such as FanCustLevel or Mode.
Parameters[].RequiredbooleanWhether the parameter is required.
Parameters[].MinimumValuenumberMinimum value allowed for numeric parameters.
Parameters[].MaximumValuenumberMaximum value allowed for numeric parameters.

3.3 Set Fan Mode

This operation immediately changes the fan speed-control policy. During on-device verification the current mode was `Balanced`; the test only wrote the `Balanced` value back as-is and did not switch the fan mode.
ItemContent
MethodPOST
Path/redfish/v1/Chassis/{ChassisId}/Actions/FanMode.Setting
PrivilegeConfigureComponents
Request headersContent-Type: application/json
Success status code200 OK
ParameterTypeRequiredDescription
ModestringNoSilent, Balanced, Powerful, or Custom.
FanCustLevelnumberNoCustom level in the range 120; only used when Mode is Custom.
Basic Auth Token ```bash title="Set the Balanced Fan Mode" curl --request POST \ --user ':' \ --header 'Content-Type: application/json' \ --data '{ "Mode": "Balanced" }' \ '://:/redfish/v1/Chassis/bmc/Actions/FanMode.Setting' ``` ```bash title="Set the Balanced Fan Mode Using a Token" curl --request POST \ --header 'X-Xsrf-Token: ' \ --header 'Content-Type: application/json' \ --data '{ "Mode": "Balanced" }' \ '://:/redfish/v1/Chassis/bmc/Actions/FanMode.Setting' ```

Response Example

The following is the real response after writing the current fan mode Balanced back as-is, with HTTP status code 200 OK. Re-querying the Thermal resource after the request showed the fan mode was still Balanced.

200 OK
{
"@odata.type": "#Message.v1_1_1.Message",
"Timestamp": "1785833173",
"MessageId": "Base.1.11.0.Success",
"Message": "The request completed successfully.",
"MessageArgs": [],
"MessageSeverity": "OK",
"Severity": "",
"Oem": null,
"RelatedProperties": null,
"Resolution": "None"
}

Response Fields

FieldTypeDescription
@odata.typestringOData type of the Redfish message.
TimestampstringUnix timestamp string of the time the server generated the message.
MessageIdstringRedfish message identifier; Base.1.11.0.Success on success.
MessagestringDescription of the operation result.
MessageArgsarrayList of arguments used to format the message.
MessageSeveritystringMessage severity level; OK on success.
SeveritystringCompatibility severity field; an empty string in the current response.
Oemobject | nullOEM extension message; null in the current response.
RelatedPropertiesarray | nullProperty paths related to the message; null in the current response.
ResolutionstringSuggested follow-up action; None on success.
The `/redfish/v1/Chassis/bmc/Thermal/FanHistorySpeed` path found in older reference documentation is not registered in the current backend; an on-device request returns `404 Not Found`, so it is not treated as a usable API.

4 UID Management Resources

4.1 Query UID Setting Parameters

Query the status values supported by the UID indicator LED.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/Actions/IndicatorLEDActionInfo
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query UID Setting Parameters" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Actions/IndicatorLEDActionInfo' ``` ```bash title="Query UID Setting Parameters Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Actions/IndicatorLEDActionInfo' ```

Response Example

200 OK
{
"@odata.id": "/redfish/v1/Chassis/bmc/Actions/IndicatorLEDActionInfo",
"@odata.type": "#ActionInfo.v1_1_2.ActionInfo",
"Id": "ActionInfo",
"Name": "Action Info",
"Parameters": [
{
"DisallowedInput": false,
"AllowablePattern": "",
"AllowableValues": [
"Unknown",
"Lit",
"Blinking",
"Off"
],
"DataType": "String",
"Name": "IndicatorLED",
"Required": true
}
]
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the UID ActionInfo resource.
@odata.typestringOData type of the ActionInfo resource.
IdstringActionInfo resource identifier.
NamestringActionInfo resource name.
ParametersarrayList of parameter definitions for the UID indicator LED setting interface.
Parameters[].DisallowedInputbooleanWhether input is disallowed for this parameter.
Parameters[].AllowablePatternstringString pattern allowed for the parameter; an empty string means unrestricted.
Parameters[].AllowableValuesarrayList of status values allowed for the UID indicator LED.
Parameters[].DataTypestringParameter data type.
Parameters[].NamestringParameter name; currently IndicatorLED.
Parameters[].RequiredbooleanWhether the parameter is required.

IndicatorLED Values

ValueDescription
LitUID LED is steady on.
BlinkingUID LED is blinking.
OffUID LED is off.
UnknownUnknown state; returned by ActionInfo, not recommended for set operations.

4.2 Set the UID Indicator LED

This operation changes the chassis UID LED state. During on-device verification the UID LED was currently `Off`; the test only wrote the `Off` value back as-is and did not switch the indicator state.
ItemContent
MethodPOST
Path/redfish/v1/Chassis/{ChassisId}/Actions/IndicatorLED.Setting
PrivilegeConfigureComponents
Request headersContent-Type: application/json
Success status code200 OK
Basic Auth Token ```bash title="Turn Off the UID LED" curl --request POST \ --user ':' \ --header 'Content-Type: application/json' \ --data '{ "IndicatorLED": "Off" }' \ '://:/redfish/v1/Chassis/bmc/Actions/IndicatorLED.Setting' ``` ```bash title="Turn Off the UID LED Using a Token" curl --request POST \ --header 'X-Xsrf-Token: ' \ --header 'Content-Type: application/json' \ --data '{ "IndicatorLED": "Off" }' \ '://:/redfish/v1/Chassis/bmc/Actions/IndicatorLED.Setting' ```

Response Example

The following is the real response after writing the UID LED's current state Off back as-is, with HTTP status code 200 OK. Re-querying the chassis resource after the request showed IndicatorLED was still Off.

200 OK
{
"@odata.type": "#Message.v1_1_1.Message",
"Timestamp": "1785833173",
"MessageId": "Base.1.11.0.Success",
"Message": "The request completed successfully.",
"MessageArgs": [],
"MessageSeverity": "OK",
"Severity": "",
"Oem": null,
"RelatedProperties": null,
"Resolution": "None"
}

Response Fields

FieldTypeDescription
@odata.typestringOData type of the Redfish message.
TimestampstringUnix timestamp string of the time the server generated the message.
MessageIdstringRedfish message identifier; Base.1.11.0.Success on success.
MessagestringDescription of the operation result.
MessageArgsarrayList of arguments used to format the message.
MessageSeveritystringMessage severity level; OK on success.
SeveritystringCompatibility severity field; an empty string in the current response.
Oemobject | nullOEM extension message; null in the current response.
RelatedPropertiesarray | nullProperty paths related to the message; null in the current response.
ResolutionstringSuggested follow-up action; None on success.

5 Overall Power Management Resources

5.1 Query Chassis Power Information

Query chassis power control information and power supply unit status.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/Power
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Chassis Power Information" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Power' ``` ```bash title="Query Chassis Power Information Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Power' ```

Response Example

The following is an excerpt of the core fields from a real 200 OK response. The PSU status of the current test device is Absent, so several electrical readings are 0.

200 OK · Excerpt of a Real Response
{
"@odata.id": "/redfish/v1/Chassis/bmc/Power",
"@odata.type": "#Power_v1_7_1_Power",
"Id": "Power",
"Name": "Chassis Power",
"PowerControl": {
"PowerAllocatedWatts": 0,
"PowerAvailableWatts": 0,
"PowerCapacityWatts": 0,
"PowerConsumedWatts": 0,
"PowerRequestedWatts": 0
},
"PowerSupplies": [
{
"@odata.id": "/redfish/v1/Chassis/bmc/Power#/PowerSupplies/0",
"EfficiencyPercent": 0,
"LineInputVoltage": 0,
"MemberId": "0",
"Name": "PSU 1",
"Oem": {
"Firefly": {
"InputAmperage": 0,
"LineInputCurrent": 0,
"SlotNumber": 1,
"SlotName": "Top"
}
},
"PowerCapacityWatts": 0,
"PowerInputWatts": 0,
"PowerOutputWatts": 0,
"Status": {
"Health": "Warning",
"HealthRollup": "Warning",
"State": "Absent"
}
}
]
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the chassis power resource.
@odata.typestringOData type of the chassis power resource.
IdstringChassis power resource identifier.
NamestringChassis power resource name.
PowerControlobjectChassis power control information.
PowerControl.PowerAllocatedWattsnumberAllocated power in watts.
PowerControl.PowerAvailableWattsnumberAvailable power in watts.
PowerControl.PowerCapacityWattsnumberPower capacity in watts.
PowerControl.PowerConsumedWattsnumberCurrently consumed power in watts.
PowerControl.PowerRequestedWattsnumberRequested power in watts.
PowerSuppliesarrayList of power supply units.
PowerSupplies[].@odata.idstringPath of a specific power supply unit within this resource.
PowerSupplies[].EfficiencyPercentnumberPower conversion efficiency percentage.
PowerSupplies[].LineInputVoltagenumberInput voltage.
PowerSupplies[].MemberIdstringPower supply member identifier.
PowerSupplies[].NamestringPower supply unit name.
PowerSupplies[].OemobjectPower supply OEM extension information.
PowerSupplies[].Oem.FireflyobjectFirefly power supply extension information.
PowerSupplies[].Oem.Firefly.InputAmperagenumberInput amperage.
PowerSupplies[].Oem.Firefly.LineInputCurrentnumberLine input current.
PowerSupplies[].Oem.Firefly.SlotNumbernumberPower supply slot number.
PowerSupplies[].Oem.Firefly.SlotNamestringPower supply slot name.
PowerSupplies[].PowerCapacityWattsnumberRated power of the power supply unit in watts.
PowerSupplies[].PowerInputWattsnumberInput power of the power supply unit in watts.
PowerSupplies[].PowerOutputWattsnumberOutput power of the power supply unit in watts.
PowerSupplies[].StatusobjectPower supply status information.
PowerSupplies[].Status.HealthstringPower supply health status.
PowerSupplies[].Status.HealthRollupstringPower supply rollup health status.
PowerSupplies[].Status.StatestringPower supply operational or presence state.

5.2 Query Overall Power Setting Parameters

Query the status values supported by overall power operations.

Request

ItemContent
MethodGET
Path/redfish/v1/Chassis/{ChassisId}/Actions/PowerStateActionInfo
AuthenticationHTTP Basic Auth or X-Xsrf-Token
Success status code200 OK
Basic Auth Token ```bash title="Query Overall Power Setting Parameters" curl --user ':' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Actions/PowerStateActionInfo' ``` ```bash title="Query Overall Power Setting Parameters Using a Token" curl --header 'X-Xsrf-Token: ' \ --header 'Accept: application/json' \ '://:/redfish/v1/Chassis/bmc/Actions/PowerStateActionInfo' ```

Response Example

200 OK
{
"@odata.id": "/redfish/v1/Chassis/bmc/Actions/PowerStateActionInfo",
"@odata.type": "#ActionInfo.v1_1_2.ActionInfo",
"Id": "ActionInfo",
"Name": "Action Info",
"Parameters": [
{
"DisallowedInput": false,
"AllowablePattern": "",
"AllowableValues": [
"On",
"Off"
],
"DataType": "String",
"Name": "PowerState",
"Required": true
}
]
}

Response Fields

FieldTypeDescription
@odata.idstringAccess path of the overall power ActionInfo resource.
@odata.typestringOData type of the ActionInfo resource.
IdstringActionInfo resource identifier.
NamestringActionInfo resource name.
ParametersarrayList of parameter definitions for the overall power setting interface.
Parameters[].DisallowedInputbooleanWhether input is disallowed for this parameter.
Parameters[].AllowablePatternstringString pattern allowed for the parameter; an empty string means unrestricted.
Parameters[].AllowableValuesarrayList of status values allowed for overall power; currently On and Off.
Parameters[].DataTypestringParameter data type.
Parameters[].NamestringParameter name; currently PowerState.
Parameters[].RequiredbooleanWhether the parameter is required.

5.3 Set Overall Power State

This operation directly turns the device's overall power on or off and may cause service interruption or data loss. During on-device verification the device was currently `On`; the test only wrote the `On` value back as-is and did not perform an `Off` power-down operation.
ItemContent
MethodPOST
Path/redfish/v1/Chassis/{ChassisId}/Actions/PowerState.Setting
PrivilegeOemPowerControl
Request headersContent-Type: application/json
Success status code200 OK
ParameterTypeRequiredDescription
PowerStatestringYesOn means power on; Off means power off.
Basic Auth Token ```bash title="Set Overall Power On" curl --request POST \ --user ':' \ --header 'Content-Type: application/json' \ --data '{ "PowerState": "On" }' \ '://:/redfish/v1/Chassis/bmc/Actions/PowerState.Setting' ``` ```bash title="Set Overall Power On Using a Token" curl --request POST \ --header 'X-Xsrf-Token: ' \ --header 'Content-Type: application/json' \ --data '{ "PowerState": "On" }' \ '://:/redfish/v1/Chassis/bmc/Actions/PowerState.Setting' ```

Response Example

The following is the real response after writing the overall power's current state On back as-is, with HTTP status code 200 OK. Re-querying the chassis resource after the request showed PowerState was still On.

200 OK
{
"@odata.type": "#Message.v1_1_1.Message",
"Timestamp": "1785833173",
"MessageId": "Base.1.11.0.Success",
"Message": "The request completed successfully.",
"MessageArgs": [],
"MessageSeverity": "OK",
"Severity": "",
"Oem": null,
"RelatedProperties": null,
"Resolution": "None"
}

Response Fields

FieldTypeDescription
@odata.typestringOData type of the Redfish message.
TimestampstringUnix timestamp string of the time the server generated the message.
MessageIdstringRedfish message identifier; Base.1.11.0.Success on success.
MessagestringDescription of the operation result.
MessageArgsarrayList of arguments used to format the message.
MessageSeveritystringMessage severity level; OK on success.
SeveritystringCompatibility severity field; an empty string in the current response.
Oemobject | nullOEM extension message; null in the current response.
RelatedPropertiesarray | nullProperty paths related to the message; null in the current response.
ResolutionstringSuggested follow-up action; None on success.