Re: [storage-discuss] iSCSI troubleshooting
David, Many thanks for taking the time to write up your notes publishing them on your web site/blog. These will be invaluable in trouble-shooting any difficulties in setting up the iScsi initiator on Solaris. The notes look like more than 20 minutes work to me! You must be a fast worker! Best Regards Nigel Smith 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
Thanks for all the advice. Configuring as a static target worked just fine in the end I wish I would have saw this sooner. I'm starting to wonder if there is something really busted in the Solaris iSCSI initiator SendTargets handling with the latest patches. I recently got done helping another guy in Europe. http://groups.google.com/group/comp.unix.solaris/browse_thread/thread/e14b16b24d94c64d/a4b77e511c758b73?lnk=gstq=+Pb+to+discover+my+iSCSI+targets+from+a+Solaris+10+Netra+X1+++rnum=2#a4b77e511c758b73 Anyway...Here are some random notes I composed on configuring the Solaris iSCSI Initiator, for the first time. They are a little different than the Solaris Administration Guides document. It's more correct in its assumptions that things will work. These notes assume things won't work. I will add to them when I have more time. http://weibeltech.com/?p=146 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
On 8/31/07, Ben Middleton [EMAIL PROTECTED] wrote: Ok - I disabled the iscsi-initiator service, but on re-running iscsiadm modify discovery --sendtargets enable, the system panics. The server isn't accesisble from here - and has come up in maintenance mode - so I'll have to try again on Monday. No remote console access from here either. Yikes! Anyway you can make the core files available? Thanks, - Ryan -- UNIX Administrator http://prefetch.net ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
[storage-discuss] iSCSI troubleshooting
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
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
