Skip to main content
NetApp Knowledge Base

OCUM fails to monitor a cluster having an empty failover group

  1. Last updated
  2. Save as PDF
Views:
266
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
legacy
Last Updated:

Applies to

  • OnCommand Unified Manager (OCUM) 9.5
  • ONTAP 9
  • Cluster has an empty failover group

Issue

  • OCUM fails to discover the cluster with the description "Cluster discovery failed. Rediscover the cluster after resolving the issue.".
  • The following java.lang.NullPointerException can be seen in au.log.

ERROR [pool-3-thread-2] c.o.s.a.f.d.BaseDataSource (AggregatedDataSourceErrorsException.java:152) -      Error 1 out of 1: <CLUSTER_MGMT_IP> [Internal error] - Internal error (Internal Error) java.lang.NullPointerException: network_failover_group_network_port_relationship key field 'network_port_name' may not be null.
    at com.onaro.sanscreen.acquisition.schema.KeyBase$KeyIDs.<init>(KeyBase.java:183) ~[au-package-common.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.schema.KeyBase$KeyIDs.<init>(KeyBase.java:163) ~[au-package-common.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.schema.KeyBase.<init>(KeyBase.java:17) ~[au-package-common.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.model.ModelKeyBase.<init>(ModelKeyBase.java:21) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.model.cmode.CModeNetworkFailoverGroupNetworkPortRelationship$NetworkFailoverGroupNetworkPortRelationshipKey.<init>(CModeNetworkFailoverGroupNetworkPortRelationship.java:49) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.model.cmode.CModeNetworkFailoverGroupNetworkPortRelationship.<init>(CModeNetworkFailoverGroupNetworkPortRelationship.java:37) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.model.cmode.CModeCluster.createNetworkFailoverGroupNetworkPortRelationship(CModeCluster.java:619) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.NetworkFailoverGroupBuilder.buildIterInstance(NetworkFailoverGroupBuilder.java:47) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.NetworkFailoverGroupBuilder.buildIterInstance(NetworkFailoverGroupBuilder.java:16) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.IterBuilderBaseImpl.buildModel(IterBuilderBaseImpl.java:178) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.CallableBuilder.call(CallableBuilder.java:59) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.CallableBuilder.call(CallableBuilder.java:15) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    ... 4 more
Wrapped by: com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Internal error
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.builders.zapi.cmode.netappfoundation.ClusterBuilder.executeAndBuild(ClusterBuilder.java:233) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.NetAppOCIEDataSource.doFoundation(NetAppOCIEDataSource.java:154) ~[au-datasource-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.netappfoundation.datasource.NetAppFoundationPackage.pollNow(NetAppFoundationPackage.java:199) ~[au-package-netappfoundation.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:263) [au-framework.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:687) [au-framework.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.SchedulerTask.runLogic(SchedulerTask.java:91) [au-framework.jar:9.5.0-2019.04.J145]
    at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.Scheduler$LogicWrapper.run(Scheduler.java:271) [au-framework.jar:9.5.0-2019.04.J145]
    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) [?:?]

 

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.