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

Appendix D
iSCSI Software Interface Driver Statistics
iSCSI Software Interface Driver Statistics
107
Table D-1 Software Interface Driver Statistics
iscsiutil Statistic CL Description of Field
Software Interface Driver Global
Interface Statistics
Number of connection opens I The number of TCP connection opens
initiated. The statistic is incremented when a
call to open a connection is made.
Number of connection closes I The number of TCP connection closes
initiated. The statistic is incremented when a
call to close a connection is made.
Software Interface Driver
Connection Statistics
Number of times the login failed I/T The number of login failures due to incorrect
text / key values and formatting. If this is a
transient problem at the target end, the
initiator would recover on a successive retry
attempt.
Number of exception status class
values returned by target
D The number of iSCSI login phase failure. The
reasons for login failure can be determined by
looking at the STM/syslog.log logs to find
more detailed information. The class of login
failures enumerated here consists of
interoperability (potential protocol violations)
issues between the host and the target.
Number of PDU headers with
Protocol errors received by
initiator
T The number of login failures due to protocol
violations by the target. The protocol
violation occurs when a target sends a PDU
login response header and the initiator
determines that the response is not protocol
compliant.
Number of times iswd daemon
failed to open a connection
D/C The number of times the iswd daemon failed
to open a connection to the requested target.
The failure can be the result of resource
allocation failures, incorrect target
configuration, or network infrastructure
problems.The exact reason for the failed will
be logged in syslog.log.
Number of failures to send a
login command due to kernel
memory allocation failure
D The number of attempts to send the Login
command that failed due to memory
allocation failures. The upper level driver
recovery may retry the session open, resulting
in a re-attempt to send the Login command. If
the memory allocation request succeeds, the
Login command will transmit successfully.