White Papers
APIs
20 Updating Firmware using OpenManage Enterprise APIs
"@odata.id":
"/api/UpdateService/Baselines(6)/DeviceComplianceReports(1)",
"Id": 1,
"DeviceId": 25013,
"ServiceTag": "B5JLMN2",
"DeviceModel": "PowerEdge C6420",
"DeviceTypeName": "SERVER",
"DeviceName": "idrac-B5JLMN2",
"FirmwareStatus": "Non-Compliant",
"ComplianceStatus": "CRITICAL",
"DeviceTypeId": 1000,
"RebootRequired": true,
"ComponentComplianceReports@odata.navigationLink":
"/api/UpdateService/Baselines(6)/DeviceComplianceReports(1)/ComponentComplianceR
eports"
}
]
}
Note: In OME 3.0, the user must drill down further to check compliance at the component level using
the navigation link in the response above. See link highlighted in bold font and used in subsequent
calls.
GET /api/UpdateService/Baselines(9)/DeviceComplianceReports(9523)/ComponentComplianceReports
Description: This method returns the component level compliance report for a particular baseline
Result Codes:
HTTP Response
Code
Description
200 View the compliance report at the component level
Privilege: VIEW
Response:
Attribute Name T
y
pe Description
Version Strin
g
Version of the component as available in the catalo
g
CurrentVersion Strin
g
Current version of the component
Path Strin
g
Relative path of the DUP file for this component
Name Strin
g
User readable name for the component
Criticalit
y
Strin
g
Indicates the ur
g
enc
y
of the update for the component
UniqueIdentifier Strin
g
Unique id of the component
Tar
g
etIdentifier Strin
g
Shorter tar
g
et identifier of the component
UpdateAction Strin
g
Indicates if the component is up
g
raded or down
g
raded