HP-UX iSCSI Software Initiator Support Guide (Edition 7)

9. Verify that the files listed in “iSCSI Software Initiator Components” (page 16), are installed in
the correct directories on the HP-UX system.
10. Verify that there are no kernel build errors (see step 5 for details).
11. If the problem is still not resolved, try installing the iSCSI Software Initiator again.
6.2 Troubleshooting Undetected Target Devices
1. Verify that all of the required patches or superseding patches for the iSCSI Software Initiator
have been installed. Review the HP-UX iSCSI Software Initiator Release Notes to obtain a list
of required patches.
2. If a target device cannot be seen from the HP-UX host, verify that the problem is not an
infrastructure connectivity issue by executing the /usr/sbin/ping command from the HP-UX
host, specifying the IP address or qualified domain name of the iSCSI target. If ping is not
successful, verify that the target device is available, powered on, and properly connected to
the network.
3. If the iSCSI discovery target does not appear to respond:
— Verify that the IP address or domain name of the discovery target was entered correctly
by executing: iscsiutil -p -D
— Verify that the iSCSI Name is valid.
The iSCSI Initiator Name or iSCSI Target Name is referred to as an iSCSI Name. The
iSCSI Software Initiator configures a default Initiator Name in the "iqn" format. If you
have changed the Initiator Name from its default using iscsiutil and the Initiator
Name is in an invalid format, iSCSI login negotiation could fail leaving target devices
inaccessible from the HP-UX host.
The iSCSI Software Initiator validates iSCSI Names. If a target reports a Target Name in
an "iqn", "eui" or "naa" format, but it does not comply with the iSCSI Name format rules,
or if a Target Name contains a prohibited character, iSCSI Login negotiation will fail and
the target will not be seen by the HP-UX host.
NOTE: The iSCSI Name format rules are detailed in “Configuring the iSCSI Software
Initiator” (page 19). Prohibited characters are described in section 6.2 of RFC 3722,
"String Profile for Internet Small Computer Systems Interface (iSCSI) Names". Consult RFC
3722 at: http://www.ietf.org/rfc/rfc3722.txt
The following characters MUST NOT be used in iSCSI names:
0000-002C; [ASCII CONTROL CHARACTERS and SPACE through , ]
002F; [ASCII / ]
003B-0040; [ASCII ; through @ ]
005B-0060; [ASCII [ through ‘ ]
007B-007F; [ASCII { through DEL]
You will need to work with the target vendor representative to correct an invalid Target
Name format.
— Verify that the fully qualified domain name, or the hostname, of the discovery target is
known (if used instead of IP address) using nslookup.
— Confirm the TCP port and Target Portal Group Tag are correct for the iSCSI discovery
target in question. The values entered, or used by default by the iSCSI Software Initiator,
can be seen by executing: iscsiutil -p -D
4. Verify that the steps listed in “Configuring the iSCSI Software Initiator” (page 19), have been
followed correctly and completed successfully.
6.2 Troubleshooting Undetected Target Devices 33