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

D iSCSI Software Interface Driver Statistics
D.1 iSCSI Software Interface Driver Statistics
Statistics are maintained in the iSCSI Software Interface Driver (SWD). These statistics are explained
in Table 6: “Software Interface Driver Statistics” (page 53).
The Class column (CL) provides message classification. Messages can be informational (I), target
errors (T), transient driver errors (D), or connectivity problems (C).
Informational Messages are counters for driver events. They are not an indication of an error, but
should an error occur, they may provide some profiling information.
Target Errors are detected at the initiator and should be reported to HP and/or the target vendor.
Not all target errors are reported on the host side. It is the responsibility of the system administrator
to monitor any device specific logs for target issues.
Transient Driver Errors will typically occur when some resource, for example, memory, is in short
supply, or something is not configured correctly. The error is considered transient, because a retry
of the operation, or a correct re-configuration, would typically be successful. I/Os that experience
transient errors will be retried, so no data will be lost. Control operations such as an application
open, or a task management command, may not be retried (the determination to retry is left to the
application or to the administrator). If the system resource load is increased, a small value for a
transient driver error statistic may be an indication of problems . Larger values for the transient
driver error statistic will start to impact performance.
Connectivity Problems will typically be network or target availability problems. Connectivity
problems are transient in the sense that a network infrastructure engineer can resolve the problem
and I/O traffic will resume as before.
Table 6 Software Interface Driver Statistics
Description of FieldCLiscsiutil Statistic
Software Interface Driver Global Interface
Statistics
The number of TCP connection opens initiated. The statistic is
incremented when a call to open a connection is made.
INumber of connection opens
The number of TCP connection closes initiated. The statistic is
incremented when a call to close a connection is made.
INumber of connection closes
Software Interface Driver Connection
Statistics
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.
I/TNumber of times the login failed
The number of iSCSI login phase failure. The reasons for login
failure can be determined by looking at the STM/syslog.log
DNumber of exception status class values
returned by target
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.
The number of login failures due to protocol violations by the
target. The protocol violation occurs when a target sends a
TNumber of PDU headers with Protocol errors
received by initiator
PDU login response header and the initiator determines that
the response is not protocol compliant.
The number of times the iswd daemon failed to open a
connection to the requested target. The failure can be the result
D/CNumber of times iswd daemon failed to
open a connection
of resource allocation failures, incorrect target configuration,
or network infrastructure problems.The exact reason for the
failed will be logged in syslog.log.
D.1 iSCSI Software Interface Driver Statistics 53