NetApp_Ontap Probe is missing information VServers and Volumes

Document created by Richard_Little Employee on Jun 22, 2017
Version 1Show Document
  • View in full screen mode

Document ID:  TEC1961237
Last Modified Date:  06/22/2017



We noticed that the NetApp_Ontap Probe (v1.12) is not collecting information VServers and Volumes. 

the following is seen in the netapp_ontap.log 

  • Jun 19 17:34:29:034 [Data Collector - 0, netapp_ontap] exception in getting value of voulme_max_size and fixed_volume
  • Jun 19 17:34:29:643 [Data Collector - 0, netapp_ontap] buildDisk - Error occured while populating data for folderId DISKnull
  • Jun 19 17:34:29:643 [Data Collector - 0, netapp_ontap] java.lang.NullPointerException
  • at
  • at
  • at
  • at
  • at
  • at
  • at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(
  • at com.nimsoft.probe.common.ctd.ProbeDataCollector.executeSessionUpdateInventory(
  • at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(
  • at
  • at java.util.concurrent.Executors$
  • at java.util.concurrent.FutureTask.runAndReset(
  • at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
  • at java.util.concurrent.ScheduledThreadPoolExecutor$
  • at java.util.concurrent.ThreadPoolExecutor.runWorker(
  • at java.util.concurrent.ThreadPoolExecutor$
  • at



NetApp Metro Cluster
NetApp_Ontap Probe v1.12



Currently the NetApp_ontap probe does not support Netapp Metro Cluster



There is no workaround at present.

Please raise an idea on the user community to request the netapp metro cluster be certified for a future release of the probe.