HPlogo HP-UX iSCSI Software Initiator Support Guide: HP-UX 11i v1 & 11i v2 > Appendix E iSCSI Software Interface Driver Diagnostic Messages

iSCSI Software Interface Driver Diagnostic Messages

» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

The HP-UX iSCSI Software Interface Driver works with HP-UX Event Monitoring Services (EMS) and the Support Tools Manager (STM). By default, the iSCSI Software Interface Driver logs all diagnostic messages to the STM log files. STM can be used to view the diagnostic messages logged in the STM log files.

EMS can be configured to automatically notify the system administrator when diagnostic messages are logged by the iSCSI Software Interface Driver.

In addition to logging all diagnostic messages to the STM log files, the iSCSI Software Interface Driver logs some of the diagnostic messages to the /var/adm/syslog/syslog.log file.

The messages listed below may be generated when the iSCSI Software Interface Driver is in use.

The first value in the first line of each message listing is defined in an iSCSI header file and can be used to reference a specific message. The second value is the level of the event.

The second entry in each message listing is the message string presented in C language format with print format characters present.

The third entry in each message listing is a brief description of the message.

It is necessary to have a familiarity with the iSCSI specification and the driver implementation to completely understand the messages. See Table C-1 “Logging Levels for the syslog.log File”, for a detailed explanation of logging levels.

  1.  ISW_LOG_CLOSED_ON_LOGIN                                  LVL_WARN
    "Unexpected connection close while awaiting a login response."
    An unexpected close of the TCP connection occurred while a login was being
    attempted. The login failed as a result.
  2.  ISW_LOG_BAD_STATUS_CLASS                                 LVL_WARN
    "Login failed with response of status class (0x%x) \n"
    "and status code (0x%x) to TargetAddress %s."
    A bad status class was returned in the login response buffer. The login failed as
    a result.
  3.  ISW_LOG_BAD_PROTO_HDR                                    LVL_ERR
    "Login response with a protocol error received."
    A protocol header violation from the target has occurred.
  4.  ISW_LOG_BAD_HDR_DIGEST                                   					LVL_ERR
    "Incorrect Header Digest. Expected/Received = (0x%x)/(0x%x)."
    The initiator received an incorrect checksum (CRC) value for the header segment 
    of the iSCSI PDU sent from the target.
  5.  ISW_LOG_BAD_DATA_DIGEST					                                  LVL_ERR
    "Incorrect Data Digest. Expected/Received = (0x%x)/(0x%x)."
    The initiator received an incorrect checksum (CRC) value for the data segment
    of the iSCSI PDU sent from the target.