HP-UX iSCSI Software Initiator Support Guide (Edition 7)

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. See Appendix A (page 39) for
configuration steps.
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/STMlog 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 Section C.1 (page 47), to determine the action
to be taken.
7. When authentication is desired, if some targets are not seen due to authentication failure:
• Verify that the iradd daemon is running (if Bi-Directional CHAP authentication is desired).
• Verify that the configuration steps in “Challenge-Handshake Authentication Protocol
(CHAP) Configuration” (page 22), are followed.
8. When SLP based discovery is used and some targets are not seen in spite of the iSCSI islpd
daemon starting successfully (as per the /etc/rc.log and
/var/adm/syslog/syslog.log files), please verify the SLP configuration on the iSCSI
target.
6.3 Troubleshooting issues with iswd daemon
The iswd daemon is involved in the connection management for the iSCSI Software Interface
Driver. This version of the iswd daemon uses a multi-process approach to establish and manage
TCP connections. The parent process sleeps in the kernel; whenever a TCP connection needs to be
opened, it carries the request to user space and passes it to the child process, which establishes
and manages all of the TCP connections.
CAUTION: The iswd deamon is required to access the iSCSI devices. To avoid upredictable
results, the deamon must not be terminated.
If a target device cannot be seen from the HP-UX host, verify that the iswd daemon is alive by
executing
# ps -ef | grep iswd
If the iswd daemon is not alive, restart the daemon and re-issue an ioscan by executing
# /opt/iscsi/bin/iswd
# /usr/sbin/ioscan -NH 64000
34 Troubleshooting