Skip to main content
NetApp Knowledge Base

Apply failed for Object: igroup Method: baseline. Reason: Cannot create initiator group X because the initiator is a member of the initiator group Y with conflicting ostype

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

 

Applies to

  • MetroCluster
  • ONTAP 9

Issue

The configurations state of a Vserver in a MetroCluster is marked as degraded due to an ostype conflict from an initiator in an igroup belonging to the Vserver.

            Cluster : clusterA
            Vserver : vserver1
    Partner Vserver : vserver1-mc
Configuration State : degraded
      Stream Status : operation-failed
  Corrective Action : Resynchronize the configuration using "metrocluster vserver resync" command. Contact technical support for assistance if configuration-state does not change to healthy.
...
      Failed Reason : Apply failed for Object: igroup Method: baseline. Reason: Cannot create initiator group "igroup_windows" because the initiator "initiator1" is a member of the initiator group "igroup_vmware" with conflicting ostype "vmware".

 

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.