Skip to main content
NetApp Knowledge Base

Cluster added to OnCommand Unified Manager is stuck in discovery state due to vserver peering relationship's Peer State being stuck in an initializing state

Last Updated:

Applies to

  • Active IQ Unified Manager


Attempting to add a cluster to OCUM adds the cluster, but the cluster is still in a state of discovery after several hours. When checking the au.log the following error is found:

2018-06-14 19:08:28,236 ERROR [pool-3-thread-6087] c.o.s.a.f.d.BaseDataSource ( - [Internal error] - vserver_peer key field 'peer_vserver_uuid' may not be null. ([Device name]: vserver_peer key field 'peer_vserver_uuid' may not be null.) java.lang.NullPointerException: vserver_peer key field 'peer_vserver_uuid' 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.
Scan to view the article on your device