Update file device details
Update the administrative contact for a system and its physical location. The overall name of the system can also be changed, which is effectively the cluster name.
If the cluster is a Unified system or if the name is changed, it will take longer for the call to return.
Changing the cluster name will trigger creation of a new self-signed SSL/TLS certificate for the HTTPS management server and (if present) for the embedded SMU. However, if the system has a custom certificate it will not be affected, but you may want to consider updating it to match the new domain name.
HTTP request syntax (URI)
PATCH <base_URI>/v8/storage/file-devices
Parameters
Name | Type | Required | Values | Description |
contact | BODY | N | string | New cluster contact details. |
fileOnly | BODY | N | boolean | Whether to update only the file component of a Unified system. Default is False. |
name | BODY | N | string | New name for cluster. |
location | BODY | N | string | New cluster location. |
Return codes
Code | Data | Description |
204 | No Data | File device details successfully updated. |
400 | Error Message | Missing or invalid request contents. |
403 | Error Message | Operation forbidden by access level. |
500 | Error message | Error associated with the storage system. |
Any HTTP status code other than 204 indicates that the API did not complete successfully.
Request example
curl -vk -H "X-Api-Key: zrxvSDAv9x.RIP4gkmKarG3beF.or.4Tc2im7oeqYN88C9XPGHxbXC" https://172.17.11.11:8444/v8/storage/file-devices -X PATCH -d '{"contact":"trevor", "location":"comms room"}'
Response example
HTTP/1.1 204 No Content