Skip to main content
NetApp Knowledge Base

Active IQ Unified Manager's discovery operation for a newly added cluster fails

Views:
364
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

ActiveIQ Unified Manager (UM) 9.7

Issue

  • An error appears in the UM web interface when you try to add a cluster for the first time

failed to discover, please rediscover

  • The following error appears in the au.log when UM acquisition fails to parse the recording data file into XML files:

2020-11-24 01:50:31,456 INFO  [pool-3-thread-5] c.o.s.a.d.n.p.PartialPollContext (PartialPollContext.java:300) - <IP> Full Poll completed.
2020-11-24 01:50:31,456 ERROR [pool-3-thread-5] c.o.s.a.f.d.BaseDataSource (DataSourceErrorException.java:241) - <IP> [All devices failed] - 0 out of 1 devices acquired successfully. (0 out of 1 devices acquired successfully.) com.onaro.sanscreen.acquisition.framework.datasource.AggregatedDataSourceErrorsException: 0 out of 1 devices acquired successfully.
 at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.ClusterBuilder.<init>(ClusterBuilder.java:79) ~[au-datasource-netappfoundation.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.NetAppOCIEDataSource.doFoundation(NetAppOCIEDataSource.java:150) ~[au-datasource-netappfoundation.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.netappfoundation.datasource.NetAppFoundationPackage.pollNow(NetAppFoundationPackage.java:199) ~[au-package-netappfoundation.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:264) [au-framework.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:691) [au-framework.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.SchedulerTask.runLogic(SchedulerTask.java:91) [au-framework.jar:9.7.0-2020.03.J3229]
 at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.Scheduler$LogicWrapper.run(Scheduler.java:271) [au-framework.jar:9.7.0-2020.03.J3229]
 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
 at java.base/java.lang.Thread.run(Thread.java:834) [?:?]

  • The error also appears in the sample log root\log_netappfoundation_<ip>_<date>_sample.log
  • It may also contain an additional line like the following:

2020-12-09 12:20:04,367 ERROR  [pool-3-thread-5] c.o.s.a.f.d.BaseDataSource (AggredatedDataSourceErrorsException.java:152) -  Error 1 out of 1:IP of cluster [Internal error] - Internal error  (Internal Error) java.lang.NullPointerException: Network_failover_group_network_port_relationship key field "network_port_name' may not be null

 

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.