Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
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

Views:
290
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
om
Last Updated:

Applies to

  • OCUM 7.2P1
  • ONTAP 9.1P11 CLUSTER-MODE

Issue

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 (DataSourceErrorException.java:230) - 10.10.198.51 [Internal error] - vserver_peer key field 'peer_vserver_uuid' may not be null. ([Device name 10.10.126.50]: 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

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support