API Guide

Table 28. HTTP response code (continued)
Code Description or response object
500 Internal Server error / timeout
For OMIVV-Specific error codes, see OMIVV-Specific error codes on page 112.
Example Response:
{
"reportType": "HOST",
"clusterReport":NULL,
"hostReports":
{
"host": {
"id": "{Host ID}",
"href": "",
"objectType": "Host",
"hostip": "{Host IPv4 or FQDN}",
"hostName": "",
"managementIP": "{iDRAC IP}",
"serviceTag": "{Host Service Tag}",
"model": "{Server model name}",
"systemId": "{System ID}"
},
"applicableComponents": [
{
"componentType": "{Component Type}",
"packageId": "{Package ID}",
"component": "{Component Name}",
"currentVersion": "{Current installed componet verson}",
"availableVersion": "{Available component version}",
"criticality": "{Importance of component update}",
"updateAction": "{Component update status}",
"scheduled": {Component update job scheduled},
"rebootRequired": {Host reboot required (True or False)},
"releaseDate": "{Component release date and month}"
},
]
}
}
For more information, see Response body on page 96.
Create cluster level firmware inventory report
Description: Creates the cluster-level firmware inventory report. You can create vSAN and vSphere cluster level firmware
inventory reports.
Use the bundle ID received from the /Services/RepositoryManagementService/RepositoryData?
repoProfileID={repoProfileID}&systemId={systemId}&bundleId={bundleId} API.
Use the system ID received from the /Services/ConsoleService/Clusters/{cluster-id} API.
Command or URL: /Services/UpdateService/FWReport
Method: POST
Authorization: Bearer authentication
Request Body:
{
"reportType":"{CLUSTER}",
"clusterID":"{Cluster ID}",
"bundleAssociation":[
{
"systemId":"{System ID}",
60
Firmware inventory management