Skip to main content
Hitachi Vantara Knowledge

Reboot cluster sequentially

Initiate a reboot of all nodes in a cluster, in sequence. All nodes will reboot one after the other, which should ensure that all virtual servers remain running while the cluster reboots. There will be short interruptions while the virtual servers migrate as the node they are running on reboots, and they migrate to another node. The API call returns after initiating the reboot request, and does not wait for the reboot to complete.

HTTP request syntax (URI)
POST <base_URI>/v8/storage/file-devices/reboot-sequential
Return codes
Code Data Description
204 No Data Sequential cluster reboot successfully requested.
403Error MessageOperation 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" -X POST
Response example
HTTP/1.1 204 No Content


  • Was this article helpful?