Installation guide

Booting from SAN with QLogic QLA40xx and Microsoft Initiator
147
Miscellaneous Planning and Procedures
Booting from SAN with QLogic QLA40xx and Microsoft Initiator
The following procedure for booting from SAN with a QLogic iSCSI
adapter with Microsoft Initiator Service is illustrated using a VNX
series or CLARiiON CX series storage system. Booting with a QLogic
iSCSI adapter with Microsoft Initiator Service can also be done on a
Symmetrix storage array. For more information, refer to Symmetrix
LUN Masking documentation.
The important concept is understanding the adapter’s iqn name, its
relationship to persistent binding in a SAN environment, and how
the Microsoft Initiator Service changes the iqn name.
IMPORTANT
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 QLA40xx and Microsoft Initiator follows the
same setup configuration as boot from SAN with the QLogic QLA40xx iSCSI
adapter.
IMPORTANT
At this point, only connect the adapter that will be used to boot.
Remaining adapter(s) can be connected after the Windows
operating system is installed. Failing to do so could result in a blue
screen during the installation process. Best practice recommends
having only the LUN you will be booting from presented to the
host. This will ease the process of selecting the correct boot LUN
during the adapter 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 adapter will be
iqn.1991-05.com.microsoft:test.workgroup.