Skip to main content
NetApp Knowledge Base

How to Verify If ONTAPI (ZAPI) Calls Are Still Being Processed in ONTAP with Trident

Views:
242
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

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+, useREST is set to true by default in the backend configuration. Trident will use REST API unless useREST is explicitly set to false in 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.

  • 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: UsingZAPIclient or references to XML/ONTAPI commands.
      • REST API use: UsingRESTclient or references to JSON/REST endpoints.
    • If only REST API entries are present, Trident is not processing ONTAPI calls.

  • 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.

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.