HP Broadcom iSCSI Boot for NC37xx/NC380x Adapters User Guide

Troubleshooting 21
Target login problems
Symptoms:
The iSCSI initiator is able to connect to the target but is unable to log in successfully.
Possible causes:
• The initiator is not configured with the right target name
• The initiator is not configured with the right target IP address
• The initiator is not configured with the right initiator name
• The initiator and target are not configured for the same authentication method
• The initiator and target are using CHAP or Mutual CHAP authentication so they may not be
configured with matching user name and secret(s)
• If the target implements some form of Access Control Lists (ACL), the target may not be configured to
allow it on the initiator
Boot problems
Symptoms:
The initiator is able to connect to and log in to the target, but the system does not attempt to boot from the
iSCSI disk.
Possible causes:
• Verify the Standard Boot Order (IPL) list and Boot Controller Order list is configured correctly in
RBSU according to the Configure the server for iSCSI boot section.
• Option ROM space is limited. If too many option ROMs are enabled the boot may fail due to lack of
space. In this case it is necessary to disable PXE on other adapters, disable the Smart Array
Controller, physically remove the hard drives, and so on.
• Verify the Option ROM configuration setting "Boot to iSCSI" is set to Enabled.
LUN access problems
Symptoms:
The initiator is able to connect to and log in to the target, but the system doesn't see a disk present (it
attempts to boot from an internal disk or PXE).
Possible causes:
• The initiator is not configured with the correct LUN from which to boot (Some targets start numbering
at 1 instead of 0)
• The target is not configured to allow access to the specified LUN by the initiator
OS problems
Symptoms: