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

Appendix C

Diagnostic Messages

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,” on

page 96.

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,” on page 96 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.