Skip to main content
NetApp Knowledge Base

Unified Manager cluster discovery stuck due to unresponsive Zapi calls

  1. Last updated
  2. Save as PDF
Views:
518
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Oncommand Unified Manager 9.5 and below
  • ActiveIQ Unified Manager 9.6 and above

Issue

  • Cluster discovery stuck for one cluster in UM
  • Extensive execution time and returned records for different ZAPI calls in foundation poll recordings under log_netappfoundation_xxxx_iterator_response_time.txt
  • Some of the known ZAPI calls exhibiting the behavior are:
  • job-schedule-get-iter
  • job-schedule-cron-get-iter
  • quota-report-iter
  • qtree-list-iter
  • snapmirror-history-get-iter
  • Example of error:
datasource, zapi, timestamp, max-records, iterations, total-clock-time, total-zapi-time, total-invocations, total-records, returned-records-list
xx.xx.xx.xx<Cluster_IP>, snapmirror-history-get-iter, Fri Dec 03 06:58:17 TRT 2021, 1000, 8216, 10052702, 9745756, 8216, 8215035, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000, 1000,
....
[truncated]

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.