Hi David:
I have tested this on snv107 in a sparc machine. I found that the loop
back with isns of iscsi works well in my machine.
You can see as follows:
bash-3.2# uname -a
SunOS dmg240g 5.11 snv_107 sun4u sparc SUNW,Sun-Fire-V240
bash-3.2# iscsitadm show admin
iscsitadm:
Base Directory: Not set
CHAP Name: Not set
RADIUS Access: Not set
RADIUS Server: Not set
iSNS Access: Enabled
iSNS Server: 127.0.0.1
iSNS Server Status: Available
Fast Write ACK: Not set
bash-3.2# iscsitadm list target -v
Target: tgtd
iSCSI Name:
iqn.1986-03.com.sun:02:9a9b5064-30ba-c7a1-c74b-eb1d64c4b9ae.tgtd
Connections: 1
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:00144f6283be.4986c4d8
Alias: unknown
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 600144f0498e96e60000144f6283be00
VID: SUN
PID: SOLARIS
Type: disk
Size: 5.0G
Backing store: /dev/rdsk/c0t1d0s4
Status: online
bash-3.2# isnsadm list-node
iSCSI Name:
iqn.1986-03.com.sun:02:9a9b5064-30ba-c7a1-c74b-eb1d64c4b9ae.tgtd
<======we can see the target is now in isns server
Alias: tgtd
Type: Target
bash-3.2# iscsiadm list isns-server
iSNS Server IP Address: 127.0.0.1:3205
bash-3.2# iscsiadm modify discovery -i enable
bash-3.2# isnsadm list-node
iSCSI Name: iqn.1986-03.com.sun:02:9a9b5064-30ba-c7a1-c74b-eb1d64c4b9ae.tgtd
Alias: tgtd
Type: Target
iSCSI Name: iqn.1986-03.com.sun:01:00144f6283be.4986c4d8
<============now both the initiator and target are in the isns server
Alias: -
Type: Initiator
bash-3.2# iscsiadm list target -S
Target: iqn.1986-03.com.sun:02:9a9b5064-30ba-c7a1-c74b-eb1d64c4b9ae.tgtd
Alias: tgtd
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: SUN
Product: SOLARIS
OS Device Name: /dev/rdsk/c5t600144F0498E96E60000144F6283BE00d0s2
bash-3.2#
If it is convenient,I think that maybe you can try build 107. Or do you
have any special configuration?
Regards,
Bing
David Weibel wrote:
> Is iSCSI loopback with the initiator and target supported on the same
> system. I thought that was fixed a while back. I have a clean snv_104
> system installed. (We wanted to test the iSNS server and figured I would
> point the initiator and target at it to make sure things were working.)
>
> The initiator was configured with isns enabled and 127.0.0.1 for the
> isns server. iscsitadm was used to create a basic 1G target. Then I
> used iscsitadm to enable isns and point to 127.0.0.1. Both the initiator
> and target appear in the iSNS BUI. So I create a ds and dd with the
> initiator and target. I ran devfsadm -i iscsi and in the iscsiadm list target
> I can see the local target appearing but I never get a connection between
> the two of them. The logs show.
>
> ...
> ISNS SCN register failed
> NOTICE: iscsi connection failed to set socket optionTCP_NODELAY,
> SO_RCVBU or SO_SNDBUF.
> NOTICE: iscsi connection(4) unable to connect to target iqn....
> ...
>
> Just wondering...
>
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
