File storage failure cases

Incorrect cluster IP address of the HNAS system provided in the HTTP Request header. To provide the correct IP address, see Acquiring the correct admin EVS IP address. Also, you may have mistakenly used the SMU IP address in the HTTP request header. If so, change it to the Admin EVS IP address.

Incorrect credential for the HNAS storage system provided in the HTTP Request header. To validate the HNAS storage system credentials being used in the HTTP request, see Authenticating with the REST API server. Also, you may have mistakenly used the SMU credentials in the HTTP request header. If so, change them to the HNAS cluster credentials.

Wrong REST Server API mode. If the REST server is running in legacy mode, some of the API calls mentioned in this document may not work, and others may return less information than is expected. Make sure that the output from the rest-server-status command indicates that the REST Server mode is native, and that the server is running. See “Enabling Native REST API” Section for more details.

REST server fails to start when switching modes. When switching between legacy and native modes, the REST server may sometimes fail to start, this is usually due to the legacy REST server(s) not shutting down instantaneously and holding onto the TCP port. The native REST server is not able to start as the TCP port is not available for it to bind to. Waiting for 30 seconds and retrying the start request again will normally fix this issue. This is more likely to happen on a cluster, as the REST server needs to be stopped on all nodes before it can be restarted in the new mode.