8–iSCSI Protocol
iSCSI Crash Dump
97
83840-546-00 E
Problem
: For static IP configuration when switching from Layer 2 iSCSI boot to
QLogic iSCSI HBA, then you will receive an IP address conflict.
Solution
: Change the IP address of the network property in the OS.
Problem
: After configuring the iSCSI boot LUN to 255, a system blue screen
appears when performing iSCSI boot.
Solution
: Although QLogic’s iSCSI solution supports a LUN range from 0 to 255,
the Microsoft iSCSI software initiator does not support a LUN of 255. Configure a
LUN value from 0 to 254.
Problem
: NDIS miniports with Code 31 yellow-bang after L2 iSCSI boot install.
Solution
: Run the latest version of the driver installer.
Problem
: Unable to update inbox driver if a non-inbox hardware ID present.
Solution
: Create a custom slipstream DVD image with supported drivers present
on the install media.
Problem
: In Windows Server 2012, toggling between iSCSI HBA offload mode
and iSCSI software initiator boot can leave the machine in a state where the HBA
offload miniport bxois will not load.
Solution
: Manually edit
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bxois\StartOver
ride] from 3 to 0.
Modify the registry key before toggling back from NDIS to HBA path in CCM.
Problem
: Installing Windows onto an iSCSI target through iSCSI boot fails when
connecting to a 1Gbps switch port.
Solution
: This is a limitation relating to adapters that use SFP+ as the physical
connection. SFP+ defaults to 10Gbps operation and does not support
autonegotiation.
iSCSI Crash Dump
If you will use the QLogic iSCSI Crash Dump utility, it is important to follow the
installation procedure to install the iSCSI Crash Dump driver. See
for more information.
NOTE
Microsoft recommends against this method. Toggling the boot path from
NDIS to HBA or vice versa after installation is completed is not
recommended.
Summary of Contents for FastLinQ 3400 Series
Page 286: ......
