How to Change the Software Open iSCSI IQN in XenServer
book
Article ID: CTX131761
calendar_today
Updated On:
Description
This article contains information about how to identify and change the software iSCSI initiator IQN.
By default a random IQN is generated when you install XenServer (formerly Citrix Hypervisor). The IQN is a requirement when running iSCSI to identify the XenServer host on the iSCSI network.
It is necessary to change the software iSCSI initiator IQN on XenServer if you do not want the default value or if you require a customized IQN.
Note: Ensure that you install hotfix XS82ECU1033 on your Citrix Hypervisor 8.2 Cumulative Update 1 host before starting this process. This hotfix resolves an issue seen when setting the IQN. This issue is still present in earlier, out-of-support versions of Citrix Hypervisor and XenServer.
Instructions
To identify the current IQN and change it in the database and file, complete the following procedure.
- If you are using Citrix Hypervisor 8.2 CU 1, ensure that hotfix XS82ECU1033 is applied to your pool before beginning.
- Ensure that there are no running virtual machines on the current storage repository (SR) that is configured with software open-iscsi initiator.
Note: Connections might be interrupted and the Windows Blue Screen(BSoD) errors or Stop errors might appear on the virtual machines. Therefore, ensure that the virtual machines are not running. - Open XenCenter and from the pool select the XenServer for which you want to change the IQN. Note the current IQN.

- Select the Console tab for XenServer.
- Run the following command to find the XenServer UUID:
xe host-list

- Run the following command to set a new IQN in the XenServer database:
xe host-param-set iscsi_iqn=<iqn> uuid=<host uuid> - Select the General tab in XenServer and verify that the IQN has changed.

Issue/Introduction
This article contains information about how to identify and change the software iSCSI initiator IQN.
Additional Information
The following are some guidelines for troubleshooting:
- Ensure you have connectivity to the SAN and the appropriate access set to allow the XenServer host to the SAN/LUN.
- Ensure you have a NIC/Network dedicated to iSCSI storage on a separate subnet than management or virtual machine network.
Was this article helpful?
thumb_up
Yes
thumb_down
No