Skip to main content
NetApp Knowledge Base

vserver in pending-setup because same vserver name exist

Views:
292
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster
  • DR replication

Issue

A newly created vserver may stay in pending-setup state 

cluster-1::> metrocluster  vserver  show -vserver vserver-1 -instance

               Cluster Name: cluster-1
                    Vserver: vserver-1
            Partner Vserver: vserver-1-mc
        Configuration State: pending-setup
          Corrective Action: Vserver with the same name exists on the partner cluster.                                                                   To fix the problem, rename the Vserver "vserver-1".
Creation Time on the source: -
             Is out of sync: -
  configuration Resume Time: -

 

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.