Unified Manager cluster discovery stuck due to unresponsive Zapi calls
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:
- snapmirror-history-get-iter
job-schedule-get-iter
job-schedule-cron-get-iter
quota-report-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]