iSCSI Protocol: Broadcom NetXtreme II® Network Adapter User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtremeII/English/iscsi.htm[9/5/2014 3:45:06 PM]
iSCSI Boot Parameters section, you have to boot the offload image. SuSE 10.x and SLES 11 do not support offload.
Troubleshooting iSCSI Boot
The following troubleshooting tips are useful for iSCSI boot.
Problem
: A system blue screen occurs when iSCSI boots Windows Server 2008 R2 through the adapter's NDIS path with the
initiator configured using a link-local IPv6 address and the target configured using a router-configured IPv6 address.
Solution
: This is a known Windows TCP/IP stack issue.
Problem
: The Broadcom iSCSI Crash Dump utility will not work properly to capture a memory dump when the link speed for
iSCSI boot is configured for 10 Mbps or 100 Mbps.
Solution
: The iSCSI Crash Dump utility is supported when the link speed for iSCSI boot is configured for 1 Gbps or 10 Gbps.
10 Mbps or 100 Mbps is not supported.
Problem
: An iSCSI target is not recognized as an installation target when you try to install Windows Server 2008 by using an
IPv6 connection.
Solution
: This is a known third-party issue. See Microsoft Knowledge Base KB 971443,
http://support.microsoft.com/kb/971443
.
Problem
: When switching iSCSI boot from the Microsoft standard path to Broadcom iSCSI offload, the booting fails to
complete.
Solution
: Install or upgrade the Broadcom Virtual Bus Device (VBD) driver to 5.0.x, along with the OIS driver, prior to
switching the iSCSI boot path.
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 Broadcom 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 Broadcom 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 Broadcom'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 T7.4 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\StartOverride] from 3 to 0.
Modify the registry key before toggling back from NDIS to HBA path in CCM.
NOTE: Microsoft recommends against this method.
Toggling the boot path from NDIS to HBA or vice versa
after installation is completed is not recommended.
Problem
: The Xen hypervisor will not start when booting from an iSCSI image created with the RHEL 5.4 Xen kernel.
Solution
: This is a known third-party issue. To work around this issue, disable the Xen hypervisor's EDD feature by editing
the grub.conf file in the boot/grub folder to add the
edd=off
switch to the end of the kernel line. For example,
kernel /xen.gz edd=off
.
Problem
: Unable to connect to an EqualLogic target using Windows Server 2008 and higher.
Solution
:
Add an exception to your firewall to allow ICMP echo requests.
Problem
: Installing Windows onto an iSCSI target via iSCSI boot fails when connecting to a 1 Gbps switch port.
Solution
: This is a limitation relating to adapters that use SFP+ as the physical connection. SFP+ defaults to 10 Gbps
operation and does not support autonegotiation.
