7–iSCSI Configuration
Open-iSCSI and Boot from SAN Considerations
106
AH0054602-00 A
192.168.25.100:3260,1
iqn.2003-04.com.sanblaze:virtualun.virtualun.target-05000002
6.
To log into the iSCSI target, issue the following command:
#
iscsiadm -m node -p 192.168.25.100 -T iqn.2003-
04.com.sanblaze:virtualun.virtualun.target-05000007 -l
Logging in to [iface: qedi.00:0e:1e:c4:e1:6c,
target:iqn.2003-04.com.sanblaze:virtualun.virtualun.target-05000007,
portal:192.168.25.100,3260] (multiple)
Login to [iface: qedi.00:0e:1e:c4:e1:6c, target:iqn.2003-
04.com.sanblaze:virtualun.virtualun.target-05000007,
portal:192.168.25.100,3260] successful.
7.
To verify that the iSCSI session was created, issue the following command:
#
iscsiadm -m session
qedi: [297] 192.168.25.100:3260,1
iqn.2003-04.com.sanblaze:virtualun.virtualun.target-05000007 (non-flash)
8.
To check for iSCSI devices, issue the
iscsiadm
command:
#
iscsiadm -m session -P3
...
************************
Attached SCSI devices:
************************
Host Number: 59 State: running
scsi59 Channel 00 Id 0 Lun: 0
Attached scsi disk sdb State: running scsi59 Channel 00 Id 0 Lun: 1
Attached scsi disk sdc State: running scsi59 Channel 00 Id 0 Lun: 2
Attached scsi disk sdd State: running scsi59 Channel 00 Id 0 Lun: 3
Attached scsi disk sde State: running scsi59 Channel 00 Id 0 Lun: 4
Attached scsi disk sdf State: running
For advanced target configurations, refer to the Open-iSCSI README at:
https://github.com/open-iscsi/open-iscsi/blob/master/README
Open-iSCSI and Boot from SAN Considerations
In current distributions (for example, RHEL 6/7 and SLE 11/12) the inbox iSCSI
user space utility (Open-iSCSI tools) lacks support for qedi iSCSI transport and
cannot perform user space-initiated iSCSI functionality. During boot from SAN
installation, you can update the qedi driver using a driver update disk (DUD).
However, no interface or process exists to update userspace inbox utilities, which
causes the iSCSI target login and boot from SAN installation to fail.