Is it a bug or a feature that the solaris iscsi initiator isn't able
to connect to an iscsi target on the same machine, using either
the 127.0.0.1 localhost address or the machine's own ip address?
(I was trying to debug a problem with format and disk labels, and
needed a blank disk; I thought I could use an iscsi disk so that I
don't have to install additional hardware)
I'm trying the following:
On the "target node", a box with ip address 172.20.0.11:
[b]
iscsitadm modify admin -d /data/iscsi
iscsitadm create target -z 2G disk
iscsitadm list target -v
Target: disk
iSCSI Name:
iqn.1986-03.com.sun:02:fd97496c-f4e6-c33c-aaca-a6b9e197c531.disk
Connections: 0
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 01000008c7aa83b800002a00455c48ef
VID: SUN
PID: SOLARIS
Type: disk
Size: 2.0G
Status: online
[/b]
Now, on the same box, the following fails:
[b]
iscsiadm modify discovery -s enable
iscsiadm add static-config
iqn.1986-03.com.sun:02:fd97496c-f4e6-c33c-aaca-a6b9e197c531.disk,172.20.0.11
[/b]
127.0.0.1 instead of the machine's own ip address doesn't work either.
The "iscsiadm add static-config" hangs for ~ a minute before it returns,
without reporting an error on stdout/stderr. No new (i)scsi disk is available.
/var/adm/messages contains this error message:
Nov 16 12:26:08 tiger2 iscsi: [ID 409607 kern.warning] WARNING: iscsi
connection(5) login failed - failed to receive login response - timeout
When I use the same "iscsiadm add static-config " command on
a remote machine, it works just fine.
Why does this work when the initiator is on a remote machine,
but doen't when target and initiator are on the same machine?
AFAICT, the iscsi target daemon iscsitgtd is accepting the
connection from the kernel iscsi module, processes the login
request sent from the kernel iscsi module and sends back a
login reply, but the reply isn't seen by the kernel iscsi module.
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
