Skip to main content
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.
NetApp Knowledge Base

Left out peering entries on DR Cluster after deleting peering relationship on source vserver

Views:
225
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • Vserver peer
  • Migration to MetroCluster

Issue

After peering relationship was deleted on source vserver, left out entries remain on the DR Cluster and not able to delete with:
 
::> vserver peer delete -vserver vs1-mc -peer-vserver pvs1 -force true
you will see:
Error: command failed: This operation is not permitted on a Vserver that is configured as the destination of a MetroCluster Vserver relationship.

 

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