[storage-discuss] mds in a zone

[Selim Daoud]

hi all,
is the MDS in a zone a feasible option or not?

thanks

sd
___
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

[storage-discuss] iSCSI troubleshooting

[Ben Middleton]

Hi,

I'm having terrible problems with my Sol 10 11/06 x86 box getting iSCSI to 
work. The sun forum folk recommended posting here for a better response. The 
machine is patched with the latest iSCSI patches.

Steps I have run:

svcadm enable iscsi_initiator
iscsiadm add discovery-address 10.0.5.222:3260
iscsiadm modify discovery --sendtargets enable
devfsadm -Cv -i iscsi

Bascially, the final step fails to connect to the iSCSI target, giving the 
following message in the messages log:

Aug 31 14:24:17 myhost iscsi: [ID 286457 kern.notice] NOTICE: iscsi 
connection(9) unable to connect to target 
iqn.1991-05.com.microsoft:iscsistore-myhost-target (errno:145)

I can ping the machine fine and telnet to 10.0.5.222 on port 3260 without 
issue. I can't figure out why devfsadm isn't creating anything useful. Reboots 
don't help.

errno 145 points to a timeout in the connection. Where should I focus my 
attention to resolve this?

Incidentally, a similarly configured Sparc setup here works fine.

Many thanks,

Ben
 
 
This message posted from opensolaris.org
___
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Re: [storage-discuss] iSCSI troubleshooting

[Nigel Smith]

First off, you do not need to enable iscsi_initiator.
See David Weibel post here:
http://mail.opensolaris.org/pipermail/storage-discuss/2007-March/002484.html
..but that is probably not the cause of this problem.

What do you get from '# iscsiadm list target -v'

What exact variety of target are you using?  Something from Microsoft?

When you enable SendTargets discovery, the initiator should login to the target.
It looks like this is failing. 'devfsadm' will not do anything useful if the
login has failed.

You could try using Dtrace to see what is happening.
Again see David Weibel post here:
http://mail.opensolaris.org/pipermail/storage-discuss/2007-February/002391.html

Also it would be interesting to get an Ethernet capture with 'snoop',
while the initiator is trying to login,  make that capture file available
for us to take a look at.
See Jeff Wen's post here:
http://mail.opensolaris.org/pipermail/storage-discuss/2007-February/002398.html
and my post here:
http://mail.opensolaris.org/pipermail/storage-discuss/2007-February/002397.html

You can use WireShark or Ethereal to look at the capture file and it will 
decode the
iScsi protocol.

I always like to take a look at the source code to see what is generating the 
error
message. So I used OpenGrok to search the 'nwsc' project,
for the string unable to connect and found this:
http://src.opensolaris.org/source/xref/nwsc/src/sun_nws/iscsi/src/iscsi_login.c#1970
..which to me, looks like it is saying it cannot connect to the socket on the 
target,
when opening the TCP connection.
But you say that telnet can connect to port 3260, so that does not agree.
Thanks
Nigel Smith
 
 
This message posted from opensolaris.org
___
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss