White Papers

APIs
18 Updating Firmware using OpenManage Enterprise APIs
Attribute Name T
y
pe Description
DeviceName Strin
g
Name of the device
FirmwareStatus Strin
g
Indicates if firmware is compliant or not
ComplianceStatus Strin
g
Indicates the compliance status
DeviceT
y
peId Inte
g
er Numeric value for the device t
y
pe such as server
(
1000
)
RebootRequired Boolean Indicates if a reboot is required to make the device
compliant.
Link Link to the component compliance report, identifying the
software components on the device and if they match up
a
g
ainst the catalo
g
.
Example: Response Payload (OpenManage Enterprise 3.1 and later):
{
{"@odata.context":
"/api/$metadata#Collection(UpdateService.ComponentComplianceReport)",
"@odata.count": 3,
"value": [
{
"@odata.type": "#UpdateService.ComponentComplianceReport",
"@odata.id":
"/api/UpdateService/Baselines(6)/DeviceComplianceReports(1)/ComponentComplianceR
eports(3)",
"Id": 3,
"DeviceId": 10867,
"ServiceTag": "7T2W1V1",
"DeviceModel": "PowerEdgeT320",
"DeviceTypeName": "SERVER",
"DeviceName": "idrac-7T2W1V1",
"FirmwareStatus": "NonCompliant",
"ComplianceStatus": "CRITICAL",
"DeviceTypeId": 1000,
"RebootRequired": true,
"DeviceFirmwareUpdateCapable": true,
"DeviceUserFirmwareUpdateCapable": true,
“ComponentComplianceReports": [
{
"@odata.type": "#UpdateService.ComponentComplianceReport",
"Id": 35,
"Version": "16.01.08",
"CurrentVersion": "0",
"Path": "FOLDER03532998M/2/T320_Drivers-for-OS-
Deployment_Application_1HPN9_WN64_16.01.08_A00.EXE",
"Name": "OS Drivers Pack",
"Criticality": "Optional",
"UniqueIdentifier": "1HPN9LW64769c0bf7ebf2f62442730b81c55c0605",
"TargetIdentifier": "18981",
"UpdateAction": "UPGRADE",