iSCSI (dm_iscsi_adapter Events)

Event 1

• Severity: Serious
• Description: SCSI Inquiry Command from the initiator to the target failed with cdb_status 0x!, io_status 0x!, and return value of 0x!.
• Probable Cause:
  
  1. If io_status is 0x3, the session was in offline state and thus the SCSI Inquiry command could not be issued.
  2. If io_status is 0x4 and the return value is 0x1, the session was in transient state and thus the SCSI Inquiry command could not be issued.
  3. If io_status is 0x6, the connection was offline and thus the SCSI Inquiry command could not be processed.
  4. If io_status is 0x7, the SCSI Inquiry command failed as the number of bytes received by the initiator was less than the number of bytes the target sent.
  5. If cdb_status is 0x02, the target device terminated the SCSI Inquiry command with a Check Condition status.
  6. If cdb_status is 0x08, the target device terminated the SCSI Inquiry command with a Busy status.
  7. If io_status is 0x4 and the return value is 0x0, the target device did not respond to a SCSI Inquiry command within a stipulated amount of time.
  8. If io_status is 0x5, the SCSI Inquiry command failed due to a Target Failure - target failed to execute the command.
  9. If cdb_status is 0x18, the target device terminated the SCSI Inquiry command with a Reservation Conflict status.
  10. If the return value is 0x1 and both cdb_status and io_status are zero, the inquiry command could not be issued due to memory resource constraints.
• Recommended Action:
  
  • For causes 1-4, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the HP representative with the cause information.
    
  • For causes 5-8, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the Target Vendor representative with the cause information.
    
  • For cause #9, the recommended action is as follows:
    Check the existing reservations for the target device, resolve the reservation conflict and re-issue the ioscan command.
    
  • For cause #10, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided the lack of memory is a transient condition. If the problem persists, please increase the physical memory size on the host system.

Event 2

• Severity: Information
• Description: SCSI Report LUNs command from the initiator to the target failed with cdb_status 0x!, io_status 0x!, and return value of 0x!.
• Probable Cause: SCSI Report LUNs command from the initiator to the target failed. iSCSI driver creates a single virtual bus.
• Recommended Action:
  
  • For causes 1-4, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the HP representative with the cause information.
    
  • For causes 5-8, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the Target Vendor representative with the cause information.
    
  • For cause #9, the recommended action is as follows:
    Check the existing reservations for the target device, resolve the reservation conflict and re-issue the ioscan command.
    
  • For cause #10, the recommended action is as follows:
    Re-issue the "ioscan" command. The problem will be resolved provided the lack of memory is a transient condition. If the problem persists, please increase the physical memory size on the host system.
    
  • For cause #11a, the recommended action is as follows:
    A multi-LUN target device should typically support the SCSI Report LUNs command. iSCSI driver creates a single virtual bus assuming that HP are dealing with a target device with a single LUN. HP recommends that you log this occurrence with the target vendor representative. Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the Target Vendor representative with the cause information.
    
  • For cause #11b, the recommended action is as follows:
    iSCSI driver creates a single virtual bus assuming that HP are dealing with a target device with a single LUN. No action is required.
    

Event 3

• Severity: Serious
• Description: Unsupported LUN Addressing type recognized.
• Probable Cause: Target has reported the LUNs in an unsupported LUN addressing method. No LUNs behind the target device would be claimed as a result.
  
  • The target device reports LUNs in an unsupported LUN addressing method.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative. They will work with the HP support representative to change the LUN addressing method.

Event 4

• Severity: Major Warning
• Description: No LUNs configured on the target.
• Probable Cause: Driver Internal Error. No LUNs configured on the target device.
• Recommended Action:
  
  • Configure LUNs on the target device. Re-issue the "ioscan" command to discover the configured LUNs.

Event 5

• Severity: Serious
• Description: The target did not send the remaining portion of the <key=value> pair. The partial <key=value> pair sent in the previous login response was (!).
• Probable Cause: The target is misbehaving by not sending the remaining portion of the <key=value> pair.
• Recommended Action:
  
  1. HP recommends that you log this event with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 6

• Severity: Serious
• Description: The target sent a <key=value> pair spanning across login responses of size ! bytes. The maximum initiator supported <key=value> pair size is ! bytes. The partial <key=value> pair in the login response payloads is (!).
• Probable Cause: The target device sent an unusually long <key=value> pair spanning across login responses. The size of <key=value> pair sent by the target device, the maximum initiator supported <key=value> pair size and the partial <key=value> pair (which might contain the key name) are presented above. The login attempt failed as a result.
  
  • The target device is misbehaving by sending an unusually long <key=value> pair spanning across login responses.
• Recommended Action:
  Driver Action:
  
  • iSCSI initiator driver fails the login attempt to prevent an infinitely long login process where a misbehaving target device could bombard the initiator with enormous amount of invalid login response data.
  User Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target vendor representative for further assistance.

Event 7

• Severity: Serious
• Description: Failure to allocate memory for a login response buffer.
• Probable Cause: A login <key=value> pair does not entirely fit into the remaining space of a response buffer. The attempt to allocate an additional response buffer to contain the rest of the <key=value> pair failed. The login attempt failed as a result.
  • The system is low on memory resources.
• Recommended Action:
  
  1. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided that the lack of memory is a transient condition.
     If this problem persists, please increase the physical memory size on the host system.

Event 8

• Severity: Serious
• Description: An equal sign was missing after a target login key.
• Probable Cause: The target is expected to respond to a login request from the initiator with <key=value> pairs. The key name returned by the target during login negotiation had a terminating null character before an "=" (equal sign) was found. The login attempt failed as a result.
  • The target device violates the iSCSI protocol by not sending an "=" after the key name.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 9

• Severity: Serious
• Description: The null character was missing after the <key=value> pair (!) sent by the target.
• Probable Cause:The target sent a <key=value> pair that was not folloHPd by one null (0x00) delimiter. The login attempt failed as a result.
  
  • The target device violates the iSCSI protocol by not sending one null (0x00) delimiter after a <key=value> pair.
• Recommended Action:
  User Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target vendor representative for further assistance.

Event 10

• Severity: Serious
• Description:Initiator login key (!) was not understood by the target.
• Probable Cause: Fibre Channel Driver was suspended.
  • The target device violates the iSCSI protocol by responding to a "MUST Implement" login key as not understood.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 11

• Severity: Serious
• Description:Initiator login key (!) was rejected by the target.
• Probable Cause: The login key proposed by the initiator was rejected by the target. The login attempt failed as a result.
  • The target device violates the iSCSI protocol by rejecting a "MUST Implement" login key.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 12

• Severity: Serious
• Description: Failure to allocate memory to hold a login key (!) not understood by the target.
• Probable Cause: Failed to allocate a buffer to store a login key not understood by the target. The login attempt failed as a result.
  
  • The system is low on memory resources.
• Recommended Action:
  
  1. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided that the lack of memory is a transient condition.
     If this problem persists, please increase the physical memory size on the host system.

Event 13

• Severity: Information
• Description: Target login key (!) was not understood by the initiator.
• Probable Cause:The target has proposed the indicated login key which was not understood by the initiator.
  • The target proposes a login key which was not understood by the initiator.
• Recommended Action:
  
  • No action needs to be taken. The login negotiation process continues. The login keys not understood by the initiator are reported back to the target.

Event 14

• Severity: Serious
• Description: Target initiated an unexpected negotiation of a login key (!).
• Probable Cause: The target device has violated the iSCSI protocol by sending a key which it should have only sent in response to a key proposal from the initiator. The login attempt failed as a result.
  • The key which is supposed to be initiated by an initiator only has not yet been proposed by the initiator, but the target device has violated the iSCSI protocol by proposing that particular key.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the Target Vendor representative for further assistance.

Event 15

• Severity: Serious
• Description: Target returned a value which is out of (! - !) range or is an unexpected value. The value preferred by the initiator is !. The login key is (!).
• Probable Cause: The target returned an out of range or badly formatted integer value or Irrelevant for a login key proposed by the initiator. The login attempt failed as a result.
  
  • The target device has violated the iSCSI protocol by returning an out of range or badly formatted integer value.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition. If the problem persists, please contact the Target Vendor representative for further assistance.

Event 16

• Severity: Serious
• Description: Target returned an invalid list response for a login key. The <key=value> pair is (!).
• Probable Cause: The character key value returned by the target for the login key proposed by the initiator is not acceptable. The login attempt failed as a result.
  1. A valid response is expected from the target and it responds with "Irrelevant" key value.
  2. The target responds with a key value other than "Yes" or "No" for a Boolean Key.
  3. The target responds with a key value which is not in the list of values proposed by the initiator.
  4. There is a memory allocation failure while storing the response from the target.
  
  
  • Run "iscsiutil" tool to check the statistic: "Number of allocation failures while storing the login response from the target"
    
  • If the statistic value is non-zero, memory allocation failure may be the cause for this error.
    
  • Save the statistic values using "iscsiutil" tool and clear the statistic values before retrying.
    
• Recommended Action:
  The following actions are recommended for causes #1 - #3:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.
  
  The following action is recommended for cause #4
  1. Please save the statistic values using "iscsiutil" tool and clear the statistic values before retrying the login attempt which is triggered by "ioscan" command.
     Re-issue the "ioscan" command and check if the statistic value for the statistic listed above in the cause section is non-zero. If the value is non-zero, memory allocation failure is the cause for this error. If the value is zero, the problem is resolved as the lack of memory was a transient condition.
     If this problem persists, please increase the physical memory size on the host system.

Event 17

• Severity: Serious
• Description:No response received from the target for a integer login key (!).
• Probable Cause: The target did not respond to an integer login key proposed by the initiator. The login attempt failed as a result.
  • The target device has violated the iSCSI protocol by not responding to an integer login key proposed by the initiator.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 18

• Severity: Serious
• Description:No response received from the target for character login key (!).
• Probable Cause:The target did not respond to a character login key proposed by the initiator. The login attempt failed as a result.
  • The target device has violated the iSCSI protocol by not responding to a character login key proposed by the initiator.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 19

• Severity: Serious
• Description: The maximum number of exchanges (!) for a login stage has been exceeded.
• Probable Cause: The initiator and target have performed an unreasonably high number of exchanges in an attempt to successfully complete the login phase. The number of exchanges has exceeded the iSCSI driver implementation maximum indicated in the message above.
  
  • The target device might be misbehaving by requesting an unreasonably high number of exchanges to complete the login attempt.
• Recommended Action:
  Driver Action:
  
  • To prevent the possibility of an infinite loop, the login attempt has been terminated.
  User Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 20

• Severity: Serious
• Description: The next login stage of the target (!) is invalid with respect to the current initiator stage (!) as HPll as the next next initiator stage (!).
• Probable Cause: The target sent an invalid value for the next login stage. The login attempt failed as a result.
  • The Target Device has violated the iSCSI protocol by sending an invalid value for the next login stage.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 21

• Severity: Serious
• Description: Memory allocation failure of a data structure (size ! bytes) required for a login attempt to proceed successfully.
• Probable Cause: An attempt to allocate memory for connection login keys data structure failed. The login attempt failed as a result.
  • The system is low on memory resources.
• Recommended Action:
  
  1. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided that the lack of memory is a transient condition.
     If this problem persists, please increase the physical memory size on the host system.

Event 22

• Severity: Major Warning
• Description: Invalid value (!) for the key CHAP_A.
• Probable Cause: An invalid value is sent by the target for the CHAP negotiation key "CHAP_A". The login attempt failed as a result.
  1. The key value is "Reject". It may be due to CHAP not being configured on the target.
  2. CHAP is configured on the target and the target does not accept MD5 as the method to hash the CHAP challenges. The target device violates the iSCSI protocol because MD5 method is a "MUST Implement".
  3. The target device violates iSCSI protocol by sending a key value other than "Reject".
• Recommended Action:
  The recommended actions correspond to the causes above. For example, action #1 corresponds to cause #1. For cause #1, the following action is recommended
  1. Configure CHAP on the target if it is not already configured. If CHAP authentication is not desired, it should be turned off on the initiator using the "iscsiutil" tool.
  For cause #2 and #3, the following actions are recommended
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 23

• Severity: Major Warning
• Description: Invalid value (!) for the key CHAP_I.
• Probable Cause: An invalid value is sent by the target for the CHAP negotiation key "CHAP_I". The login attempt failed as a result.
  • The target device violates the iSCSI protocol by sending an invalid value.
• Recommended Action:
  
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 24

• Severity: Major Warning
• Description: Invalid value (!) for the key CHAP_C.
• Probable Cause: An invalid value is sent by the target for the CHAP negotiation key "CHAP_C". The login attempt failed as a result.
  1. The target device sent a value which is not coded in hexadecimal.
  2. The target device violates the iSCSI protocol by sending a value that is not coded in hexadecimal or in base64.
• Recommended Action:
  
  1. For cause #1, configure the target to use hexadecimal encoding for the CHAP challenges.
  The following actions are recommended for cause #2
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 25

• Severity: Major Warning
• Description: Invalid value (!) for the key CHAP_N.
• Probable Cause: An invalid value is sent by the target for the CHAP negotiation key "CHAP_N". The login attempt failed as a result.
  • The target sends a target CHAP name larger than 511 bytes.
• Recommended Action:
  
  1. Configure CHAP on the target using CHAP name of size less than 511 bytes.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.

Event 26

• Severity: Critical
• Description: Invalid value (!) for the key CHAP_R.
• Probable Cause: An invalid value is sent by the target for the CHAP negotiation key "CHAP_R". The login attempt failed as a result.
  
  1. The target device sent a value which is not coded in hexadecimal.
  2. The target device violates the iSCSI protocol by sending a value that is not coded in hexadecimal or in base64.
• Recommended Action:
  
  1. For cause #1, configure the target to use hexadecimal encoding for the CHAP challenges.
  The following actions are recommended for cause #2
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 27

• Severity: Major Warning
• Description: Target sent an invalid key (!) when the initiator was waiting for a CHAP_A, CHAP_I or CHAP_C key.
• Probable Cause: An invalid key is sent by the target instead of a CHAP_A, CHAP_I or CHAP_C key. The login attempt failed as a result.
  • The target device violated the iSCSI protocol by sending an invalid key.
• Recommended Action:
  
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 28

• Severity: Major Warning
• Description: Target sent an invalid key (!) when the initiator was waiting for CHAP_N or CHAP_R key.
• Probable Cause: An invalid key is sent by the target instead of a CHAP_N or CHAP_R key. The login attempt failed as a result.
  • The target device violated the iSCSI protocol by sending an invalid key.
• Recommended Action:
  
  1. HP recommends that you log any protocol violations by the target with the target vendor representative.
  2. As a workaround, CHAP authentication can be turned off both on the initiator and the target.
  3. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 29

• Severity: Serious
• Description: Unable to resolve the Target Hostname (!).
• Probable Cause: The specified Target Hostname is not a Qualified Domain Name. The Target Hostname resolution failed as a result.
  • The specified hostname for the target is not a Qualified Domain Name.
• Recommended Action:
  
  1. Check if the hostname specified for the target is a Qualified Domain Name.
  2. Re-issue the "ioscan" command. If this is a transient condition, the Target Hostname resolution will succeed.
     If the problem persists, please contact your System Administrator for further assistance.

Event 30

• Severity: Serious
• Description: No route found for IP address (!)
• Probable Cause: The initiator is unable to reach the specified target address. The target device will not be discovered as a result.
  1. The specified IP address for the target might have changed resulting in no route to the target.
  2. There is no route for the initiator to reach the target.
• Recommended Action:
  
  1. Check if the connection betHPen initiator and target is physically secure and established.
  2. Check if the target has the same IP address as displayed in the log message.
  3. Re-issue the "ioscan" command. If this is a transient condition, the target device will be discovered.
     If the problem persists, please contact your System Administrator for further assistance.

Event 31

• Severity: Serious
• Description: Invalid text key (!) received from the target in SendTargets response.
• Probable Cause: An invalid text key is sent by the target in a SendTargets response. The discovery of target devices would fail as a result.
  1. Target device sends a target record within a SendTargets response beginning with a text key other than TargetName.
  2. Target device sends a text key other than TargetName or TargetAddress within a SendTargets response.

     In both the cases, Target device has violated the iSCSI protocol.

• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command. If the protocol violation by the target is a transient condition, the target devices will be discovered.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 32

• Severity: Serious
• Description: Invalid key value (!) received from target for TargetAddress key.
• Probable Cause: An invalid key value was sent by the target within a SendTargets response for TargetAddress text key. The discovery of target devices would fail as a result.
  • Target device has violated the iSCSI protocol by sending an invalid key value within a SendTargets response for TargetAddress text key.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command. If the protocol violation by the target is a transient condition, the target devices will be discovered.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 33

• Severity: Critical
• Description: Attempt to allocate more than the maximum number of sessions.
• Probable Cause: An attempt was made to allocate more than the maximum number of sessions. The discovery of new target devices that HPre added would fail as a result.
  • An attempt was made to allocate more than the maximum number of sessions alloHPd for a HP-UX system. The restriction on the number of sessions is an HP-UX limitation which cannot be exceeded.
• Recommended Action:
  
  1. The number of targets attached to the HP-UX system may need to be reduced, or if there are unused bus instance entries, then it may be necessary to change (compress) bus instance assignments. This should only be done with the assistance of a HP support representative.
     Contact HP support representative for further assistance.

Event 34

• Severity: Major Warning
• Description: The initiator CHAP secret is not configured.
• Probable Cause: CHAP authentication failed as the CHAP initiator secret is not configured.
  • The CHAP initiator secret is not configured.
• Recommended Action:
  
  1. Use the "iscsiutil" tool to configure the CHAP initiator secret.
     For more information on CHAP configuration, please read the "HP iSCSI Driver Subsystem Support Guide".

Event 35

• Severity: Major Warning
• Description: Unexpected connection close while waiting a login response.
• Probable Cause:Target unexpectedly closed the TCP connection when the initiator is awaiting a login response. The login attempt failed as a result.
  • The Target unexpectedly closed the TCP connection when the initiator was awaiting a login response.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 36

• Severity: Major Warning
• Description: Login failed with response of status class (0x!) and status code (0x!) to TargetAddress (!).
• Probable Cause: iSCSI Login Negotiation failed.
  • The login negotiation failed due to one of the reasons below:
    1. Initiator Error - This may be due to a request for a resource for which the initiator does not have permission.
    2. Target Error - The target sees no errors in the initiator's login request, but is currently incapable of fulfilling the request.
    3. Redirection - This is usually due to the target moving to a different address.
  • If the status class is:
    1. 0x1 - Target indicates that further action is required by the initiator for the login to be accepted.
    2. 0x2 - Login error caused by the initiator.
    3. 0x3 - Login error caused by the target.
• Recommended Action:
  
  1. HP recommends that you log this occurrence appropriately.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists and is:
     Initiator Error - Contact HP support representative with "status code" value for further assistance.
     Target Error - Contact the target vendor representative with "status code" value for further assistance.

Event 37

• Severity: Serious
• Description: Login response with a protocol error received.
• Probable Cause: The target device has violated the iSCSI protocol by sending an invalid Login Response header. The login attempt failed as a result.
  • The target device violates the iSCSI protocol by sending an invalid Login Response header.
• Recommended Action:
  
  1. HP recommends that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command which will trigger a login attempt. The problem will be resolved provided it is a transient condition.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 38

• Severity: Serious
• Description: Incorrect Header Digest. Expected/Received = (0x!)/(0x!)
• Probable Cause: Initiator received an iSCSI PDU from the target with an incorrect Header Digest.
  • The initiator received an incorrect checksum (CRC) value for the header segment of the iSCSI PDU sent from the target.
• Recommended Action:
  Driver Action:
  1. In the normal phase of operation, the connection to the target is terminated and the login would be retried by the iSCSI driver in order to recover from this problem. The problem will be resolved provided it is a transient condition.
  User Action:
  1. HP recommends you log this occurrence with your network administrator.
  2. If the problem persists, please contact the target vendor representative for further assistance.

Event 39

• Severity: Serious
• Description: Incorrect Data Digest. Expected/Received = (0x!)/(0x!)
• Probable Cause: Initiator received an iSCSI PDU from the target with an incorrect Data Digest.
  • The initiator received an incorrect checksum (CRC) value for the data segment of the iSCSI PDU sent from the target.
• Recommended Action:
  Driver Action:
  1. In the normal phase of operation, the connection to the target is terminated and the login would be retried by the iSCSI driver in order to recover from this problem. The problem will be resolved provided it is a transient condition.
  User Action:
  1. HP recommends you to log this occurrence with your network administrator.
  2. If the problem persists, please contact the target vendor representative for further assistance.

Event 40

• Severity: Serious
• Description: Invalid iSCSI Name format (!) received from the target.
• Probable Cause: The iSCSI target name is not in iqn, eui or naa format.
  • 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.
• Recommended Action:
  User Action:
  1. Please work with the Target Vendor representative to have the iSCSI target name re-formatted according to the iSCSI specification. The HP-UX iSCSI driver supports names in iqn, eui, or naa formats.

Event 41

• Severity: Serious
• Description: Invalid text key (!) received from the target in a login redirection response.
• Probable Cause: The target device has violated the iSCSI protocol specification (RFC 3720) by sending a text key other than a TargetAddress within a login redirection response.
• Recommended Action:
  Driver Action: The intiator will fail the login and will not grant the request for redirection.
  User Action:
  1. We recommend that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command. If the protocol violation by the target is a transient condition, the login to the target device will succeed.
     If the problem persists, please contact the Target Vendor representative for further assistance.

Event 42

• Severity: Information
• Description: Login response with status code (0x!) to TargetAddress (!) indicated a temporary redirection request to (!).
• Probable Cause: The target is requesting the current login to be redirected to a different Target Address.
• Recommended Action:
  Driver Action: The initiator will redirect the login to a new Target Address provided by the target.
  User Action: No action is necessary. This is an informational message.

Event 43

• Severity: Information
• Description: Login response with status code (0x!) to TargetAddress (!) indicated a permanent redirection request to (!).
• Probable Cause: The target is requesting the current as well as all future logins to be redirected to a different Target Address.
• Recommended Action:
  Driver Action: The initiator will fail the login. Permanent redirection is not supported at this time.
  User Action: All requests for permanent redirection will fail. Either disable permanent redirection or use temporary redirection in the target device.
  If the problem persists, please contact the Target Vendor representative for further assistance.

Event 44

• Severity: Information
• Description: Login to TargetAddress ! was redirected succesfully to !.
• Probable Cause: The target has requested a login redirection.
• Recommended Action:
  Driver Action: None. This informational message is a notification that the initiator succesfully logged into a redirected address supplied by the target.
  User Action: No action is necessary. This is an informational message.

Event 45

• Severity: Serious
• Description: Invalid key value (!) received from the target for TargetAddress key.
• Probable Cause: Target device has violated the iSCSI protocol by sending an invalid key value within a login redirection response for TargetAddress text key.
• Recommended Action:
  1. We recommend that you log this occurrence with the target vendor representative.
  2. Re-issue the "ioscan" command. If the protocol violation by the target is a transient condition, the login to the target device will succeed.
     If the problem persists, please contact the Target Vendor representative for further assistance.