Skip to main content
NetApp Knowledge Base

How to identify the iSCSI software initiator node name (IQN) from a host operating system

  1. Last updated
  2. Save as PDF
Views:
14,085
Visibility:
Public
Votes:
7
Category:
iscsi-initiator-support-kit
Specialty:
san
Last Updated:

Applies to

  • SAN
  • FlexPod

Description

Every iSCSI node must have a node name. Node names typically take the iSCSI Qualified Name (IQN) format.  This standard is industry standard and required by NetApp.  The IQN-type designator is a logical name that is not linked to an IP address.

The following is an example format:

iqn.yyyymm.backward-naming-authority:unique-device-name

yyyy-mm is the month and year in which the naming authority acquired the domain name.

'backward-naming-authority' is the reverse domain name of the entity responsible for naming this device. An example reverse domain name is 'com.microsoft'.

'unique-device-name' is a free-format unique name for this device assigned by the naming authority.

The following example shows the iSCSI node name for an initiator that is an application server:

iqn.1991-05.com.microsoft:example

Note: Some initiators might provide variations on the preceding format.

An iSCSI initiator node name is used when associating an iSCSI host with a Data ONTAP initiator group (igroup) for the purpose of mapping a LUN to the host.

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.