HP NC382i Integrated Dual Port PCI Express Gigabit Server Adapter - Manual (Page 19)

Installation and configuration 19
Troubleshooting
Known issues
Known issues for Microsoft iSCSI Initiator boot installation
• If you do not select an Adapter Service Name by highlighting it during initial Microsoft Initiator boot
setup, the setup continues without an error but does not select an NDIS driver for booting. The
deployed system will display a stop error or Blue Screen of Death (BSoD) on boot prior to the first
splash screen.
• Multipath I/O (MPIO) is not supported for failover for boot filesystem because MPIO drivers cannot
be added during an install phase. MPIO can be used on devices created later.
• The iSCSI host name is derived from the InitiatorName that is set by the HP iSCSI BIOS and should
not be used in the GUI.
Known issues for F6 installation
The HP Windows_F6 Diskette 1 must not be inserted in the A:\ drive until after F6 prompts for the
diskette. Failure to wait for the prompt will cause the F6 installer to fail reading the second diskette.
Using a diagnostic monitor for troubleshooting
If the client is not able to boot from the target server and the problem is not discernable from the
immediately available information, you may need to use a network monitor that is capable of parsing the
iSCSI protocol to troubleshoot the information.
If the iSCSI target is software running on a server, you may be able to run a software network monitor
such as Ethereal directly on the target system. Otherwise, you may need to configure a network switch
with port mirroring and direct the mirrored packets to a port where either a hardware or software network
monitor can be attached.
Target connection problems
Symptoms:
The initiator is unable to make a connection to the target.
Possible causes:
• The initiator and target are not connected to the same network
• The initiator and target are not in the same VLAN (if any)
• The IP configurations for the initiator and target are not correct
• The initiator's boot path information is not correct
• The target service is not running on the target server
Target login problems
Symptoms: