Users Guide

10–iSCSI Protocol
iSCSI Boot
129 BC0054508-00 M
Troubleshooting iSCSI Boot
The following troubleshooting tips are useful for iSCSI boot.
Problem: The Marvell iSCSI Crash Dump utility will not work properly to capture a
memory dump when the link speed for iSCSI boot is configured for 10Mbps or
100Mbps.
Solution: The iSCSI Crash Dump utility is supported when the link speed for
iSCSI boot is configured for 1Gbps or 10Gbps. 10Mbps and 100Mbps are not
supported.
Problem: When switching iSCSI boot from the Microsoft standard path to Marvell
iSCSI offload, the booting fails to complete.
Solution: Prior to switching the iSCSI boot path, install or upgrade the Marvell
Virtual Bus Device (VBD) driver to and OIS driver to the latest versions.
Problem: The iSCSI configuration utility will not run.
Solution: Ensure that the iSCSI Boot firmware is installed in the NVRAM.
Problem: A system blue screen occurs when installing the Marvell drivers through
Windows Plug-and-Play (PnP).
Solution: Install the drivers through the Setup installer.
Problem: For static IP configuration when switching from Layer 2 iSCSI boot to
Marvell iSCSI Host Bus Adapter, you 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 Marvell’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 Layer 2 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: iSCSI-Offload boot from SAN fails to boot after installation.
Solution: Follow the instructions in “Linux” on page 299.