Skip to main content
NetApp Knowledge Base

What is the maximum length of a iSCSI iqn name

Views:
947
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
san
Last Updated:

 

Applies to

ONTAP 9

Answer

  • When you attempt to add an initiator to an igroup, the following error message might be reported:


    ::> igroup add -vserver svm31 -igroup test -initiator iqn.1992-08.com.netapp:sn.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    Error: command failed: Initiator "iqn.1992-08.com.netapp:sn.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" too long (need 223     or fewer characters).

  • However, when you attempt to modify iSCSI target iqn of NetApp controller, a different alert is seen:


    ::> iscsi modify -vserver future -target-name     iqn.1992-    08.com.netapp:sn.f4a0d654ca1b11e5b6cd00a09830e2f8@xxxxxxxxxxxxxxxx#s_:vs.7

    Error: "iqn.1992-08.com.netapp:sn.f4a0d654ca1b11e5b6cd00a09830e2f8@xxxxxxxxxxx" is an invalid value for field "-target-name
       <text (size 1..128)>"

  • According to RFC3270, 'Each iSCSI node, whether an initiator or target, MUST have an iSCSI name. Initiators and targets MUST support the receipt of iSCSI names of up to the maximum length of 223 bytes.'
  • A valid iqn name length must not be more than 223 bytes.
  • However, for NetApp, the maximum IQN name length is 128 characters. When modifying the NetApp iSCSI target IQN, a valid value should be less than 128.

Additional Information

 

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.