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

Appendix C

Diagnostic Messages

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.