Update drive firmware
Updating the tape drive firmware ensures that it is at the appropriate level for the user. This typically means updating drives to the latest level of firmware with all the latest features and fixes. However, it is possible to install firmware levels that are earlier than the version that the drive is running thus back leveling the code to an earlier version.
To avoid disrupting the host, control path drives are updated when they are restarted. All other drives are updated when the drive is unloaded. The control path drives need to be manually restarted to start using the uploaded firmware level.
If an automatic restart was not executed after the firmware update completes in the case of
control path drives, the drives are put in the resetRequired state. This alerts the
user that a restart is required before the code levels will be applied.
The Content-Length HTTP header is required for this request when sent by using
REST over SCSI so that the library can ensure that all the data is transferred properly.
Request syntax
POST /v1/tasks
{"type": "updateDriveFirmware", "location":"drive_F<f>C<c>R<r>"}
Content-Type:
application/octet-stream
Content-Length: <length of
file>
<drive firmware image file
data>
Updates the firmware of a drive with specified location.
POST /v1/tasks
{"type": "updateDriveFirmware", "sn": <serial number>}
Content-Type:
application/octet-stream
Content-Length: <length of
file>
<drive firmware image file
data>
Updates the firmware of a drive with specified serial number.
Request body parameters
drive firmware image file data(octet-stream)-
The contents of the drive firmware image file.
type(string, required)-
The task type to run. In this case,
updateDriveFirmware. location(string, optional)-
The location of the drive to update.
sn(string, optional)-
The globally unique serial number of the drive.
Example
> POST /v1/tasks [{"type": "updateDriveFirmware", "location": "drive_F2C4R2"}]
Content-Type: application/octet-stream
Content-Length: 4068268556
<drive firmware image file data>HTTP/1.1 201 Created
Location: /v1/tasks/42
Content-Type: application/json
Content-Length: 10
{"ID": 42}
Error handling
- Returns
500 Internal Server Errorif the file is invalid. - Returns
400 Bad Requestif the REST request header does not include the content type ofapplication/octet-streamwith a description that explains it is required.