HP-UX iSCSI Software Initiator Support Guide, HP-UX 11i v1 and 11i v2, July 2005

Chapter 6
Troubleshooting
Troubleshooting Undetected Target Devices
65
4. Verify that the steps listed in “Configuring the iSCSI Software Initiator” on page 39, have been followed
correctly and completed successfully.
5. Issue the iscsiutil -sG command and look at the following statistics:
Number of Discovery session open failures
If there is a non-zero value for this statistic, determine the cause of failure by either looking at the
message logged in the /var/adm/syslog/syslog.log file or by monitoring the EMS/STM log files. The
most common cause for failure would be an incorrect configuration of the components of the iSCSI
target address:
<ip-address>, <tcp-port> and <portal-grp-tag> or an iSCSI Login Negotiation failure.
Number of Normal session open failures
If there is a non-zero value for this statistic, determine the cause of failure by either looking at the
message logged in the /var/adm/syslog/syslog.log file or by monitoring the EMS/STM log files. The
most common cause for failure would be an incorrect configuration of the authentication and digest
methods. Refer to Appendix A, “Login Key Configuration,” on page 81, for configuration steps.
Number of SCSI INQUIRY commands issued that failed
If there is a non-zero value for this statistic, determine the cause of failure by either looking at the
message logged in the /var/adm/syslog/syslog.log file or by monitoring the EMS/STM log file. Some
of the causes for failure are:
The iSCSI session and/or connection is not in an online state, resulting in the SCSI Inquiry
command not being sent to the target.
The target device terminated the SCSI Inquiry command with a Check Condition, Busy, or
Reservation Conflict status.
The target device did not respond to the SCSI Inquiry command sent by the initiator within a
stipulated amount of time.
The target failed to execute the SCSI Inquiry command.
—The SCSI Inquiry command could not be issued due to memory resource constraints.
Review the detailed "Cause and Action" messages logged in the EMS/STM log file and take the
necessary action.
6. Target devices will not be seen if there are iSCSI Login Negotiation failures. Some of the causes for
login failures are; protocol violation by the target, initiator login errors, or lack of memory on the initiator.
Determine the cause of login failures by either looking at the message logged in the
/var/adm/syslog/syslog.log file or by monitoring the EMS/STM log file.
The detailed “Cause and Action messages logged in the EMS/STM log file provide guidance on the
necessary action to take. If EMS/STM is not set up and the only source of message logging is syslog.log,
review the Appendix , “Diagnostic Messages,” on page 96, to determine the action to be taken.
7. iSCSI uses ext_bus instances from the same pool as Fibre Channel and Parallel SCSI. HP-UX is limited
to 256 total allocations of ext_bus instances. The addition of iSCSI busses is a use of this resource. If you
see the “Attempt to allocate more than the maximum number of sessions” message in the
/var/adm/syslog/syslog.log file, the number of targets attached to the HP-UX system may need to be