Installation guide
2
Booting from SAN with QLogic QLA4010 and Microsoft Initiator
2-11
Planning, Miscellaneous Procedures, and Troubleshooting
Booting from SAN with QLogic QLA4010 and Microsoft Initiator
The following procedure for Booting from SAN with a QLogic iSCSI
HBA with Microsoft Initiator Service is illustrated using a CLARiiON
CX series storage array. Booting with a QLogic iSCSI HBA with
Microsoft Initiator Service can also be done on a Symmetrix storage
array. You will need to refer to Symmetrix Lun Masking
documentation. The important concept is understanding the HBA’s
iqn name, its relationship to persistant binding in a SAN
environment, and how the Microsoft Initiator Service changes the iqn
name. Failing to change the iqn name before installing the Windows
Operating System will cause the host to blue screen for an
inaccessible boot device when the Microsoft Initiator Service changes
the iqn name after being installed.
Note: Booting from SAN with QLA4010 and Microsoft Initiator follows the
same setup configuration as boot from SAN with the QLogic QLA4010 iSCSI
HBA.
Important At this point, only connect the HBA that will be used to boot.
Remaining HBA(s) can be connected after the Windows Operating
System has been installed. Failing to do so could result in a blue
screen during the installation process. Best practice recommends
having only the lun that you will be booting from presented to the
host. This will ease the process of selecting the correct boot lun
during the HBA configuration and during the O/S installation.
Remaining luns can be added after the installation.
1. The first step is to know what you are going to name your server
and how that translates into an iqn name. Microsoft Initiator uses
the following naming convention:
iqn.1991-05.com.microsoft
:servername.domainname. Therefore, if the server name is to be
“test”, and the domain name is “workgroup” then the name the
Initiator will use to rename the HBA will be
iqn.1991-05.com.microsoft:test.workgroup
2. On the host, go into the QLogic BIOS and change the iqn name to
iqn.1991-05.com.microsoft:servername. (If networking is
configured during installation, set the iqn name to
iqn.1991-05.com.microsoft :servername.domainname).