Skip to main content

POST – Multipart HTTP Push update for firmware

This operation can perform an update of installed software component(s) by pushing a software image file to the URI referenced by UpdateService.MultipartHttpPushUri property. In XCC3 redfish service, the UpdateService.MultipartHttpPushUri property value is “/redfish/v1/UpdateService/update”.

Request URL​

POST https://<BMC_IPADDR>/redfish/v1/UpdateService/update

Request body​

The HTTP POST operation shall provide authentication with the sufficient privilege to access the UpdateService resource.

Response​

FieldTypeDescription

Id

String

The created task ID.

Name

String

Task name.

Description

String

This resource represents a task for a Redfish implementation.

TaskMonitor

String

The URI of the Task Monitor for this task.

StartTime

String

The date-time stamp that the task was last started.

TaskState

String

The state of the task.

Messages

Array

This is an array of messages associated with the task.

PercentComplete

Integer

Task completion in percent.

HidePayload

Boolean

Indicates Payload object is hidden and not returned on GET.

Note
The client may optionally include HTTP multipart form data in the POST body to specify the image file name as RFC2388 specified. XCC3 checks this header and verity the size is supported for firmware updates, and returns code 413 when file size is too large. If the client uploads multiple files in a POST request, it returns code 400 with an error message indicating the format is not supported.

Multipart HTTP push update may be rejected with code 503 when Http Push update is in progress, and vice versa.

Status code​

HTTP Status CodeError Message ID
202Accepted
400BadRequest, ActionParamMissing, ActionParamTypeError, ActionParamFormatError
413RequestEntityTooLarge
500InternalError
503ServiceUnavailable