Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
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:
252
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

 

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