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

Diagnostic Messages
» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

The HP-UX iSCSI Software Initiator works with HP-UX Event Monitoring Services (EMS) and the Support Tools Manager (STM). By default, the iSCSI Software Initiator 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 Initiator.

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

The messages that can be logged to the syslog.log file are defined at 8 levels. By default, messages with numerical values less than or equal to LVL_ERR (Level 3) will be logged. See Table C-1 “Logging Levels for the syslog.log File” below, for detailed descriptions of logging levels.

Table C-1 Logging Levels for the syslog.log File

Logging Level

Level
Number

Description

LVL_PANIC

       0

The system is unusable and a panic will follow. The message will provide additional data about the panic.

LVL_ALERT

       1

The system has entered a state that requires an action by the administrator. The message describes the condition, and the action that must be taken

LVL_CRIT

       2

A critical event has occurred. The system is still usable. The message will provide additional details about the event.

LVL_ERR

       3

An error condition has occurred. The system is still usable. The message will provide additional details about the error.

LVL_WARN

       4An event has occurred that may indicate some future action is necessary. The system is still usable, and the current system operation has not been affected. The message will provide additional details about the warning.

LVL_NOTE

       5

An event has occurred that fits the normal profile of operation, however, the event is called out so that it may be viewed in the context of other things occurring in the system. The system is still usable, and the current system operation has not been affected. The message will provide additional details about the noted event.

LVL_INFO

       6

An informational message regarding some unusual, but acceptable, event that occurred during system operation. The system is usable, and the information can be ignored. The message will provide additional details.

LVL_DEBUG

       7

A debug message used internally by the HP lab to assist in debugging an exception event. Customers should not attempt to interpret messages at this level.

 

To change the level of event logging, execute the following command:

iscsiutil [/dev/iscsi] -b <dbg_level>

where dbg_level is one of the level numbers listed in Table C-1 “Logging Levels for the syslog.log File”.

Logging of events is always turned on. By default, messages at the LVL_ERR and lower levels are displayed in the syslog.log file. Level zero reporting cannot be turned off.

The messages detailed in the following “Message Descriptions” section, may be generated when the iSCSI Software Initiator 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.

Message Descriptions

  1. ISCSI_LOG_SCSI_INQ_FAILED                                    LVL_ERR
    "SCSI Inquiry Command from the initiator to the target failed \n"
    "with cdb_status 0x%x, io_status 0x%x and return value of 0x%x."
    There is something wrong with the target nexus. An interpretation of the status
    is necessary to determine what has happened.
  2. ISCSI_LOG_REPORTLUNS_FAILED                                  LVL_DEBUG
    "SCSI Report LUNs Command from the initiator to the target \n"
    "failed with cdb_status 0x%x, io_status 0x%x and return value of 0x%x."
    Either the target does not support the REPORT_LUNS SCSI command,or there is
    something wrong with the target nexus. An interpretation of the status is
    necessary to determine what has happened.
  3. ISCSI_LOG_INV_LUN_ADDR_TYPE                                  LVL_ERR
    "Unsupported LUN Addressing type recognized."
    The target has attempted to use invalid LUN addressing.
  4. ISCSI_LOG_NO_LUNS_CONFIGURED                                 LVL_WARN
    "No LUNs configured on the target."
    There are no LUNs configured on the target. Please configure some LUNs and
    re-issue the "ioscan" command.
  5. ISCSI_LOG_PROTOCOL_MISSING_TGT_KEY_PART                      LVL_ERR
    "The target did not send the remaining portion of the <key=value> \n"
    "pair. The partial <key=value> pair sent in the previous login response \n"
    "was (%s)."
    A login key returned by the target is incomplete and, as such, cannot be
    processed. The specific target login key is included. This information should be
    provided to HP for analysis.
  6. ISCSI_LOG_PROTOCOL_KEY_ACROSS_TOO_LONG                       LVL_ERR
    "The target device sent a <key=value> pair spanning across login \n"
    "responses of size %d bytes. The maximum initiator supported <key=value> \n"
    "pair size is %d bytes. The partial <key=value> pair in the login response \n"
    "payload is (%s)."
    A target login key was returned and the key is defined across responses and is
    too long. The size of the target key and the specific target key name are
    included. This information should be provided to the support team for analysis.
  7. ISCSI_LOG_PROTOCOL_ALLOC_ACROSS_FAIL                         LVL_ERR
    "Failure to allocate memory for a login response buffer."
    A login key does not completely fit into the remaining space of a response
    buffer. It was necessary to attempt allocation of an additional response buffer
    to contain the rest of the login key. The allocation of the additional buffer
    failed.
  8. ISCSI_LOG_PROTOCOL_NO_EQUAL_AFTER_NAME                       LVL_ERR
    "An equal sign was missing after a target login key \n"
    "(%s)."
    The target login key that is specified, was received, and a terminating null
    character was
    found, before an equal sign was identified. This information should be provided
    to the support team for analysis.
  9. ISCSI_LOG_PROTOCOL_NO_0_AFTER_VAL                            LVL_ERR
    "The null character was missing after the <key=value> pair \n"
    "(%s) sent by the target."
    The target login key that is specified was received, and a second equal character
    was found, before a null character was identified. This information should be
    provided to the support team for analysis.
  10. ISCSI_LOG_PROTOCOL_INIT_KEY_NOTUNDERSTD                      LVL_ERR
    "Initiator login key (%s) was not understood by \n"
    "the target."
    The initiator login key supplied to the target was not recognized or understood
    by the iSCSI target.This information should be provided to the support team for
    analysis.
  11. ISCSI_LOG_PROTOCOL_INIT_KEY_REJECTED                        LVL_ERR
    "Initiator login key (%s) was rejected by the target."
    The initiator login key supplied to the iSCSI target was recognized by the
    iSCSItarget and
    then rejected. This information should be provided to the supportteam for
    analysis.
  12. ISCSI_LOG_PROTOCOL_NOTUNDER_ALLOC_FAIL                      LVL_ERR
    "Failure to allocate memory to hold a login key (%s) \n"
    "not understood by the target."
    An attempt to allocate a buffer failed. The buffer was to be used internally by
    the iSCSI Software Initiator to hold an initiator login key that had not yet been
    recognized by the target.
  13. ISCSI_LOG_PROTOCOL_TGT_KEY_NOTUNDERSTD                      LVL_INFO
    "Target login key (%s) was not understood by \n"
    "the initiator."
    The target sent the specified login key (which was not recognized by the
    initiator). This information should be provided to the target vendor for
    resolution. The initiator will respond to the target in the next login text PDU
    with a "not understood" indicator.
  14. ISCSI_LOG_PROTOCOL_UNEXPT_TGT_INIT_NEGO                     LVL_ERR
    "Target initiated an unexpected negotiation of a \n"
    "login key (%s)."
    This is a case of the target violating the iSCSI protocol by wrongly proposing a
    key which it should have only responded to in response to that particular key
    being proposed from an initiator. This case would occur if a particular key which
    is to be proposed by an initiator only, has not been proposed yet, but the target
    goes ahead and proposes that particular key.
  15. ISCSI_LOG_PROTOCOL_BAD_IKEY_VAL                             LVL_ERR
    "Target returned a value (%d) which is out of (%d - %d) \n"
    "range or is an unexpected value. The value proposed \n"
    "by the initiator is %d. The login key is (%s)."
    The target returned a numerical key value which is either out of range or is an
    unexpected value. The login failed as a result of the protocol violation. In the
    case of an unexpected value, the protocol violation could be because the value
    does not comply with the result function for that key. If the result function is
    Minimum, the value responded should be less than or equal to the value proposed
    by the initiator. If the result function is Maximum, the value responded should
    be greater than or equal to the value proposed by the initiator.
  16. ISCSI_LOG_PROTOCOL_BAD_CKEY_VAL                             LVL_ERR
    "Target returned an invalid list response for a login key. \n"
    "The <key=value> pair is (%s). The value proposed by the \n"
    "initiator is (%s)."
    The target returned a string key value that is invalid. The login failed as a
    result of protocol violation. This could be because the value does not comply
    with the result function for that key. If the result function is Boolean "AND",
    the value responded by the target should be the boolean "AND" of the initiator
    proposed value and the value selected by the target.
  17. ISCSI_LOG_PROTOCOL_IKEY_NO_RSP                              LVL_ERR
    "No response received from the target for integer \n"
    "login key (%s)."
    The target failed to respond to or recognize, a numerical key. The login failed
    as a result of the protocol violation.
  18. ISCSI_LOG_PROTOCOL_CKEY_NO_RSP                              LVL_ERR
    "No response received from the target for character \n"
    "login key (%s)."
    The target failed to respond to or recognize, a string key. The login failed as a
    result of the protocol violation.
  19. ISCSI_LOG_PROTOCOL_TOO_MANY_LOGIN_EXCH                      LVL_ERR
    "The maximum number of exchanges (%d) for a login stage has been \n"
    "exceeded."
    The initiator and target have performed exchanges in an attempt to successfully
    complete the login phase. The number of exchanges has exceeded the HP-UX
    implementation maximum indicated in the message. To prevent the possibility of an
    infinite loop, the login attempt has been terminated.
  20. ISCSI_LOG_PROTOCOL_BAD_TGT_NSG                              LVL_ERR
    "The next login stage of the target (%d) is invalid with \n"
    "respect to the current initiator stage (%d) as well as the next \n"
    "initiator stage (%d)."
    The target returned a value for the next login stage that is invalid. The login
    failed as a result of the protocol violation. This information should be
    presented to the target vendor for resolution.
  21. ISCSI_LOG_PROTOCOL_ALLOC_KEYS_CB                            LVL_ERR
    "Memory allocation failure of a data structure (size %d bytes) \n"
    "required for a login attempt to proceed successfully."
    An attempt to allocate a connection key structure has failed. The login failed as
    a result. This could be a transient condition. The login can be retried by the
    application. A recommendation is to monitor the statistics using the iscsiutil
    tool for allocation failures. Allocation failures are typically a symptom of
    insufficient memory.
  22. ISCSI_LOG_PROTOCOL_BAD_CHAP_A_VAL                           LVL_WARN
    "Invalid value (%s) for the key CHAP_A."
    An invalid value was returned by the target for the CHAP negotiation key
    "CHAP_A".
  23. ISCSI_LOG_PROTOCOL_BAD_CHAP_I_VAL                           LVL_WARN
    "Invalid value (%s) for the key CHAP_I."
    An invalid value was returned by the target for the CHAP negotiation key
    "CHAP_I".
  24. ISCSI_LOG_PROTOCOL_BAD_CHAP_C_VAL                           LVL_WARN
    "Invalid value (%s) for the key CHAP_C."
    An invalid value was returned by the target for the CHAP negotiation key
    "CHAP_C".
  25. ISCSI_LOG_PROTOCOL_BAD_CHAP_N_VAL                           LVL_WARN
    "Invalid value (%s) for the key CHAP_N."
    An invalid value was returned by the target for the CHAP negotiation key
    "CHAP_N".
  26. ISCSI_LOG_PROTOCOL_BAD_CHAP_R_VAL                           LVL_WARN
    "Invalid value (%s) for the key CHAP_R."
    An invalid value was returned by the target for the CHAP negotiation key
    "CHAP_R".
  27. ISCSI_LOG_PROTOCOL_BAD_CHAP_AIC                             LVL_WARN
    "Target sent an invalid key (%s) when the initiator was \n"
    "waiting for CHAP_A, CHAP_I or CHAP_C key."
    An invalid value was returned by the target instead of a CHAP_A, CHAP_I or CHAP_C
    key.
  28. ISCSI_LOG_PROTOCOL_BAD_CHAP_NR                              LVL_WARN
    "Target sent an invalid key (%s) when the initiator was \n"
    "waiting for a CHAP_N or CHAP_R key."
    An invalid value was returned by the target instead of a CHAP_N or CHAP_R key.
  29. ISCSI_LOG_SSN_RESOLV_FAIL                                   LVL_ERR
    "Unable to resolve the Target Hostname (%s)."
    The specified Hostname is not a Qualified Domain Name. This will cause the target
    port
    hostname resolution to fail. Check if the hostname specified for the target port
    is a Qualified
    Domain Name. If the problem persists, please contact your network administrator
    for further assistance.
  30. ISCSI_LOG_SSN_ROUTE_FAIL                                    LVL_ERR
    "No route found for IP address (%s)."
    The initiator is not able to reach the specified target address. The specified IP
    address for the target is changed resulting in no route to the target. Check if
    the connection between initiator and target is physically secure and established.
    Check if the target has the same IP address as displayed in the log message. If
    the problem persists, please contact your network administrator for further
    assistance.
  31. ISCSI_LOG_INCOR_KEY                                         LVL_ERR
    "Invalid text key (%s) received from the target in \n"
    "SendTargets response."
    An invalid text key was received from the target in response to a SendTargets
    request. The login failed as a result of this protocol violation. This
    information should be presented to the target vendor for resolution.
  32. ISCSI_LOG_INCOR_TGT_ADDR                                    LVL_ERR
    "Invalid key value (%s) received from the target for \n"
    "TargetAddress key."
    The specified invalid key value was received from the target for
    theTargetAddress. The login failed as a result of this protocol violation. The
    information should be presented to the target vendor for resolution.
  33. ISCSI_LOG_MAX_SSNS_OVERFLOW                                 LVL_CRIT
    "Attempt to allocate more than the maximum number of sessions."
    An attempt was made to allocate more than the maximum number of sessions. This is
    an HP-UX limitation that cannot be exceeded. The number of targets attached to
    the initiator may need to be reduced, or if there are unused ext_bus entries, it
    may be necessary to reassign (compress) ext_bus assignments. This should only be
    done with the assistance of HP support.
  34. ISCSI_LOG_LOGIN_NO_CHAP_SECRET                              LVL_WARN
    "The initiator CHAP secret is not configured."
    CHAP authentication failed as the CHAP initiator secret is not configured. Use
    the iscsiutil command to configure the CHAP initiator secret.
  35. ISCSI_LOG_BAD_ISCSI_NAME                                    LVL_ERR
    Initiator received an iSCSI name from a target that was in an invalid format. The
    target cannot be recognized by the iSCSI initiator as a result.
  36. ISCSI_LOG_INCOR_KEY_REDI                                    LVL_ERR
    "Invalid text key (%s) received from the target in"
    "a login redirection response."
    A key that wasn’t a TargetAddress key was received
    while processing a login redirection request.
  37. ISCSI_LOG_TEMP_REDIRECT_REQUESTED                           LVL_INFO
    "Login response with status code (0x%x) to"
    "TargetAddress %s indicated a"
    "temporary redirection request to %s."
    During login,an iSCSI target device requested
    the initiator to perform a temporary login redirection
    to a new TargetAddress.
  38. ISCSI_LOG_PERM_REDIRECT_REQUESTED                           LVL_INFO
    "Login response with status code (0x%x) to"
    "TargetAddress %s indicated a"
    "permanent redirection request to %s."
    During login,an iSCSI target device requested the
    initiator to perform a permanent login redirection
    to a new TargetAddress.
  39. ISCSI_LOG_REDIRECT_OCCURRED                                 LVL_INFO
    "Login to TargetAddress %s was redirected"
    "successfully to %s."
    The target requested the login to be redirected to a
    new target address. The request was granted and the
    redirected login succeeded.
  40. ISCSI_LOG_INCOR_TGT_ADDR_REDI                               LVL_ERR
    "Invalid key value (%s) received from the target for\n"
    "TargetAddress key."
    An invalid key value was sent by the target within a
    login redirection response for TargetAddress text key.
    The discovery of target devices would fail as a result.




Appendix C Diagnostic
Messages

                 
              		
                 
              


Appendix D iSCSI
Software Interface Driver Statistics