iSCSI Boot with Microsoft MPIO4 June 2007 · Filed in Explanation
There’s a small gotcha when using Microsoft’s iSCSI initiator and MPIO driver to do iSCSI multipathing: the Microsoft initiator and MPIO driver will overwrite the IQN of the iSCSI HBA. Obviously, this could cause problems where access control to iSCSI LUNs is based on initiator IQN.
As pointed out in this Qlogic support document (check the “Additional Notes” section at the bottom of the page), installation of the Microsoft iSCSI initiator will overwrite the IQN of the HBA with a Microsoft-generated IQN, like “1991-05.com.microsoft:servername.domain.com” or similar.
In environments where access to LUNs is controlled in part or in whole by initiator IQN, this is a problem. One such environment is NetApp iSCSI SANs, where initiator groups (or “igroups”) control access to LUNs based on the IQNs of the initiators. To work around this, you’ll want to add the original IQNs of the HBAs (before the installation of the Microsoft iSCSI initiator) as well as the Microsoft IQN in the igroups for the LUNs that should be visible to that server. Otherwise, you could lose access to the LUN after installation of the Microsoft initiator.
(By the way, in case you’re wondering why one would install the Microsoft iSCSI initiator when you’ve already got HBAs, there’s a good reason—to get multipath support.)Tags: Interoperability · NetApp · Networking · Storage · Windows · iSCSI Previous Post: Data ONTAP Upgrade Next Post: Why is Microsoft Fighting so Hard?