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

5 Management
This chapter contains information on:
• “ioscan” (page 27)
• “The iscsiutil tool” (page 28)
• “iscsiutil Command Utilization” (page 28)
• “iSCSI Transport Statistics” (page 30)
• “Diagnostic Messages” (page 30)
• “iSCSI Software Initiator Daemons” (page 30)
• “iSCSI Software Initiator Name Resolution Daemon (iscsi_resolvd)” (page 30)
• “iSCSI Challenge-Handshake Authentication Protocol Daemon (iradd)” (page 30)
• “iSCSI Service Location Protocol Daemon (islpd)” (page 31)
5.1 System Administration Manager (SAM) and System Management
Homepage (SMH)
NOTE: For detailed information about SAM, see Using System Administration Manager (SAM).
This document can be viewed or downloaded at http://www.docs.hp.com, or a hard copy can
be ordered from HP. Note that SAM has been deprecated in 11i v3. System Management
Homepage (SMH) is the new tool replacing it.
SAM supports the following iSCSI functionality:
• Recognition of the iSCSI Software Initiator
• Inclusion and removal of the iSCSI Software Initiator in the /stand/system file
The HP-UX iSCSI Software Initiator may be included in the HP-UX kernel and is configurable
through SAM. System Administrators can add/remove iSCSI Software Initiator components
(iscsi, isw) from the kernel using SAM -> Kernel Configuration -> Modules.
• Storage Management
Storage accessible by the HP-UX iSCSI Software Initiator can be managed using the HP-UX
SAM tool. All storage and alternate paths in different subnets are accessible and configurable
through SAM in a manner similar to the access and configuration of existing storage.
NOTE: Addition and deletion of static iSCSI targets is not supported with the current version of
SAM and SMH.
5.2 ioscan
After the iSCSI Software Initiator is installed, a virtual node will appear in the ioscan output. This
virtual node will appear as follows:
iscsi 0 64000/0x0 iscsi CLAIMED VIRTBUS iSCSI Virtual Root
The iscsi element number in the hardware path is assigned by the I/O subsystem, and can be of
any value.
When data is available for valid iSCSI targets, the output of the ioscan command for iSCSI targets
will be similar to the following example:
Class I H/W Path Driver S/W State H/W Type Description
============================================================================ iscsi 0 64000/0x0
iscsi CLAIMED VIRTBUS iSCSI Virtual Root escsi_ctlr 0 64000/0x0/0x0 isvctlr CLAIMED
INTERFACE iSCSI Virtual Controller tgtpath 17 64000/0x0/0x0.0x2 estp CLAIMED TGT_PATH
iscsi target served by isvctlr driver lunpath 40 64000/0x0/0x0.0x2.0x4000000000000000 eslpt
CLAIMED LUN_PATH LUN path for disk43
5.1 System Administration Manager (SAM) and System Management Homepage (SMH) 27