Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

What are the Host IQN naming requirements for NetApp

Views:
358
Visibility:
Public
Votes:
1
Category:
flexpod-with-infrastructure-automation
Specialty:
san
Last Updated:

 

Applies to

SAN Environment 

iSCSI

Answer

  • Most Operating Systems (OS) will allow users to rename iSCSI Qualified Name's (IQN).
  • NetApp requires that IQNs match the IEEE standard in order to connect to the storage system.
  • Host IQNs can be renamed; however, in order to operate with NetApp controllers they must follow this standard.

The standard is as follows:

iqn.yyyy-mm.reverse_domain_name:any_friendly_name

For example, iqn.1991-05.com.microsoft:winclient1 OR iqn.1991-05.com.microsoft:winclient2

  • NetApp also supports the EUI-64 type IQN which takes the format - EUI.64bit_address

For example, eui.02004567A425678D

  • IQNs that do not conform to one of these standards will not work with NetApp.

For example, dashes are allowed in IQN names. Underscores are not allowed.

Additional Information

 

Scan to view the article on your device