Troubleshooting IBM Storage Scale native REST API

This topic describes the troubleshooting procedure that you might encounter while using IBM Storage Scale native REST API.

Common errors in IBM Storage Scale native REST API
Common errors that you might encounter while using IBM Storage Scale native REST API.
IBM Storage Scale native REST API logs
Troubleshoot issues in the IBM Storage Scale native REST API with the following logs.
Request IDs in IBM Storage Scale native REST API
Request IDs are used in the scalectl or the scaleadmd logs to track logs related to a particular client-initiated request.
Debugging the IBM Storage Scale native REST API issues
The IBM Storage Scale native REST API feature introduces a new trace class, grpc, with a maximum level of 6, is available for IO-daemon traces. You can set the new trace class through the normal mmtracectl --set option.
Debugging node identities issues
Node identities consist of X.509 Transport Layer Security (TLS) certificates and private key pairs.
Troubleshooting persistent reserve errors for IBM Storage Scale native REST API
IBM Storage Scale native REST API provides support to manage persistent reserve settings on a specified target disk. This support is required for troubleshooting persistent reserve errors during the creation of a network shared disk (NSD). In such cases, you might need to register or clear keys from a device to allow it to be used as an NSD.
Disabling and re-enabling IBM Storage Scale native REST API
You can disable the IBM Storage Scale native REST API feature and revert to the classic IBM Storage Scale infrastructure only if you encounter issues related to this feature. Also, you can re-enable this feature after the issue is resolved.

Parent topic: Troubleshooting