HP SmartStart-Software - Manual (Page 23)

Troubleshooting 23
• The initiator's boot path information is not correct
• The target service is not running on the target server
• Target's firmware is outdated. Update to the latest firmware version
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
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:
The initiator is able to connect to and log in to the target and the system sees the disk, but you are unable
to install the OS.
Possible causes:
• The drivers are not being loaded in the right order during installation
• The target disk provided is not large enough
• The initiator is not configured with the correct LUN from which to boot (some targets start numbering
data devices at 1, not 0)
• The target is not configured to allow access to the specified LUN by the initiator