How to Verify If ONTAPI (ZAPI) Calls Are Still Being Processed in ONTAP with Trident
Applies to
- NetApp ONTAP 9.14.1 and newer (including 9.16.1P11)
- NetApp Trident (24.06 and later)
Answer
- Beginning with Trident 24.06 and ONTAP 9.15.1+,
useRESTis set totrueby default in the backend configuration. Trident will use REST API unlessuseRESTis explicitly set tofalsein the backend. - Checking the ONTAPI status via ONTAP CLI and monitoring Trident logs will confirm whether ONTAPI calls are still being processed.
Additional Information
In addition you can determine if ONTAPI (ZAPI) calls are still being processedby ONTAP or Trident, follow these steps:
- Check ONTAPI Service Status in ONTAP:
- Run the CLI command: "
cluster::> system services web ontapi show" - If ONTAPI Suspended is true, ONTAPI calls are not being processed (service is disabled). If false, ONTAPI is still enabled.
- Run the CLI command: "
- Monitor ONTAPI Call Activity:
- ONTAPI is automatically disabled after 30 days of inactivity (no ONTAPI calls detected)
- If ONTAPI is disabled, any ONTAPI request will return HTTP status code 200 with a message stating ONTAPI has been suspended due to inactivity.
- Check Trident Logs for API Call Type:
- Use the command to gatherTrident logs :
"tridentctl logs -n trident" - Look for log entries:
- ZAPI/ONTAPI use:
UsingZAPIclientor references to XML/ONTAPI commands. - REST API use:
UsingRESTclientor references to JSON/REST endpoints.
- ZAPI/ONTAPI use:
- If only REST API entries are present, Trident is not processing ONTAPI calls.
- Use the command to gatherTrident logs :
- Check ONTAP System Logs for ONTAPI Calls:
-
- Run the command : "
vserver services web show -vserver <svm_name>" - Review for ONTAPI call activity related to your SVM.
- Run the command : "
