After adding or updating hardware or software that might impact the Networking stack e.g. Network Drivers, OS service packs etc., you must re-run the iscsibcg.exe with /verify /fix command line options. See instructions here: Upgrading/Installing Network Drivers, OS Service Packs, or New Hardware.
After setting up the system for iSCSI Boot with two ports connected to a target and successfully booting the system, if you later try to boot the system with only one port connected to the target, Microsoft Initiator will reboot the system. Port 1 must have link and connection to the target to be able to successfully boot the system. The system will not boot with only Port 0 connected. This is a known Microsoft Initiator limitation.
In a Windows* installation, if you move the iSCSI adapter to a PCI slot other than the one that it was in when the drivers and MS ISCSI Boot Initiator were installed, then a System Error (Blue Screen) occurs during the middle of the Windows Splash Screen. The error code is 0x0000007B. This issue goes away if you return the adapter to its original PCI slot. We recommend not moving the adapter to a different slot once an iSCSI target has been established. This is a known OS issue.
If you have to move the adapter to another slot, then you can install a new adapter to another slot and setup that adapter for iSCSI Boot and then remove the previous adapter.
If the driver for the device in use for iSCSI Boot is uninstalled via Device Manager, Windows will blue screen on reboot and the OS will have to be re-installed. This is a known Windows issue.
A workaround for this issue is to change the following registry value to "0":
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IOATDMA\Start
Only change the registry value if iSCSI Boot is enabled and if you want I/OAT offloading. A blue screen will occur if this setting is changed to "0" when iSCSI Boot is not enabled. It must be set back to "3" if iSCSI Boot is disabled or a blue screen will occur on reboot.
If you are using two Intel® PRO/1000 PT Server Adapters in two PCI Express x8 slots of a rack mounted Xeon system, Windows installation can be done only via a local HDD procedure.
iSCSI Boot installation on an Intel EM64T platform can only be done via Local Disk Installation.
Teaming is not supported with iSCSI Boot. Creating a team using the primary and secondary iSCSI adapters and selecting that team during the Microsoft initiator installation may fail with constant reboots. Do not select a team for iSCSI Boot, even if it is available for selection during initiator installation.
For load balancing and failover support, you can use MSFT MPIO instead. Check the Microsoft Initiator User Guide on how to setup MPIO.
Linux Channel Bonding has basic compatibility issues with iSCSI Boot and should not be used.
Last modified on 4/10/07 11:50a Revision 22