Skip to main content
NetApp Knowledge Base

Luns sharing same Lun ID resulting in error while trying to add initiator to igroup

Views:
621
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • ONTAP 9.x
  • RHEL Host

Issue

  • Same LUN ID is showing for multiple LUN IDs.
  • cluster1::> lun mapping show
    Vserver    Path                                      Igroup   LUN ID  Protocol
    ---------- ----------------------------------------  -------  ------  --------
    svm1       /vol/iscsi1/iscsi1                        initgroup     0  iscsi
    svm1       /vol/iscsi1/lun0                          igroupA       0  iscsi
    svm1       /vol/iscsi1/lun_1                         igroupB       0  iscsi
     
    cluster1::> igroup show
    Vserver   Igroup       Protocol OS Type  Initiators
    --------- ------------ -------- -------- ------------------------------------
    svm1      initgroup  iscsi    vmware   iqn.1xxx-01.com.vmware:xxx
                                           iqn.1xxx-01.com.vmware:xxy
    svm1      igroupA    iscsi    windows  iqn.1991-05.com.microsoft:xxxx.demo.netapp.com
                                           iqn.1991-05.com.microsoft:snapctr.demo.netapp.com
    svm1      igroupB     iscsi    windows  -

     
  • In the above example, when we try to add any initiator to IgroupB, it fails.
  • When adding IQN iqn.1991-05.com.microsoft:xxxx.demo.netapp.com  to igroupB , it  fails. 

IniatorXXX Failed: You cannot add the node to an initiator group if the node is already present in another initiator group and both initiator groups share a LUN ID
 

 

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.