Broadcom iSCSI Boot for HP FlexFabric Adapters User Guide
Table Of Contents
- Broadcom iSCSI Boot for HP FlexFabric Adapters User Guide
- Abstract
- Notice
- Contents
- Introduction
- Setup
- iSCSI boot setup
- Configuring the iSCSI target
- Configuring iSCSI boot parameters
- Preparing the iSCSI boot image
- Booting
- Other iSCSI boot considerations
- iSCSI offload in Windows server
- iSCSI boot setup
- Troubleshooting
- Boot fails when switching to Broadcom iSCSI offload
- Broadcom iSCSI Crash Dump utility does not capture a memory dump
- HBA offload miniport BXOIS does not load
- Inbox driver does not update
- Installing Windows on an iSCSI target fails
- IP address conflict
- iSCSI target is not recognized as an installation target
- iSCSI configuration utility does not run
- NDIS miniports with Code 31 yellow-bang after L2 iSCSI boot installation
- System blue screen appears after setting iSCSI boot LUN to 255
- System blue screen occurs when installing through Windows Plug-and-Play
- System blue screen occurs when iSCSI boots Windows 2008 R2
- Frequently asked questions
- Event notifications
- Regulatory compliance notices
- Support and other resources
- Acronyms and abbreviations
- Documentation feedback
- Index
Troubleshooting 30
IP address conflict
Symptom: For static IP configurations, an IP address conflict message appears when switching from Layer 2
iSCSI boot to Broadcom iSCSI HBA.
Action: Change the IP address of the network property in the OS.
iSCSI target is not recognized as an installation target
Possible cause: An iSCSI target is not recognized as an installation target during a Windows Server 2008
installation through an IPv6 connection.
Action: No action is required. This is a known third-party issue. For more information, see the article
KB971443 on the Microsoft website (http://support.microsoft.com/).
iSCSI configuration utility does not run
Symptom: The iSCSI configuration utility does not run.
Action: Be sure that the iSCSI Boot firmware is installed in the NVRAM.
NDIS miniports with Code 31 yellow-bang after L2
iSCSI boot installation
Symptom: NDIS miniports with Code 31 yellow-bang after L2 iSCSI boot installation.
Action: Run the T7.8 or later installer.
System blue screen appears after setting iSCSI boot
LUN to 255
Possible cause: After configuring the iSCSI boot LUN to 255, a system blue screen appears when performing
iSCSI boot.
Action: Configure a LUN value from 0 to 254. Although Broadcom iSCSI supports a LUN range from 0 to
255, the Microsoft iSCSI software initiator does not support a LUN of 255.
System blue screen occurs when installing through
Windows Plug-and-Play
Possible cause: A system blue screen occurs when installing the Broadcom drivers through Windows
Plug-and-Play.
Action: Install the drivers through the Setup installer.