done.

dump1 has been sent

On May 8, 6:48 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> hissing_sid wrote:
> > Just looked at the trace myself. I can see it trying to contact LUN 00
> > but I do not have that configured on my target. I am using LUN 01
>
> > That is why is it failing. When I change my Target LUN to 00 it
> > works.....
>
> > So, how or where is the initiator deciding on the LUN? Is it
>
> The scsi layer will send a inquiry to lun0 to get some info about the
> target and start off the device discovery process. It would then
> normally send a report luns command to discover all the devices.
>
> Your target might be operating as expected and need some special flags
> in the scsi layer. Attach your trace to 
> herehttp://groups-beta.google.com/group/open-iscsi/files
> so we can see what is going on.
>
> > configured or should it find it from the Target?
> > Thanks for your help so far, I feel I am getting somewhere now!
>
> > On May 8, 6:27 pm, hissing_sid <dopey...@gmail.com> wrote:
> >> I have a dump. How should I get it to you?
>
> >> On May 8, 5:52 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
>
> >>> hissing_sid wrote:
> >>>> All sorted. Definitely running only open-iscsi now.
> >>> Ok ignore the request to use iscsi-initiator-utils.
> >>>> Still broken though
> >>>> Loading iSCSI transport class v2.0-870.
> >>>> iscsi: registered transport (tcp)
> >>>> iscsi: registered transport (iser)
> >>>> scsi6 : iSCSI Initiator over TCP/IP
> >>>>  connection1:0: detected conn error (1011)
> >>>>  session1: host reset succeeded
> >>>>  connection1:0: detected conn error (1011)
> >>>>  session1: host reset succeeded
> >>>> scsi 6:0:0:0: Device offlined - not ready after error recovery
> >>> Can you get a ethereal/wireshark trace?
> >>>>> On May 8, 5:08 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
> >>>>>> hissing_sid wrote:
> >>>>>>> Hi,
> >>>>>>> I am running an initiator on FC9 64-bit (Linux
> >>>>>>> 2.6.27.21-78.2.41.fc9.x86_64 #1 SMP) connecting to a NexSan SATA boy
> >>>>>>> over 1GB ethernet with iSCSI.
> >>>>>>> I am running open-iscsi 2.0-870.
> >>>>>> Are you using a open-iscsi.org release or fedora iscsi-initiator-utils 
> >>>>>> one?
> >>>>>>> When I try to connect I get a conn error (1011)  and I am struggling
> >>>>>>> to know where to go next. The NexSan has no errors. Can someone give
> >>>>>>> me pointer on where to go next to try and get this working. I have
> >>>>>>> another machine running FC8 32-bit (Linux 2.6.26.8-57.fc8 #1 SMP) and
> >>>>>>> that works just fine.
> >>>>>>> Any help please?
> >>>>>>> #iscsiadm -m session
> >>>>>>> tcp: [1] 10.52.145.121:3260,2 iqn.1999-02.com.nexsan:p1:sataboy:
> >>>>>>> 028a2347
> >>>>>>> Loading iSCSI transport class v2.0-870.
> >>>>>>> iscsi: registered transport (tcp)
> >>>>>>> iscsi: registered transport (iser)
> >>>>>>> scsi3 : iSCSI Initiator over TCP/IP
> >>>>>>>  connection1:0: detected conn error (1011)
> >>>>>>>  session1: host reset succeeded
> >>>>>> Looks like maybe the initial inquiry or repport luns that the scsi 
> >>>>>> layer
> >>>>>> sends is timing out. The iscsi layer probably tries to abort the 
> >>>>>> command
> >>>>>> and that fails so we try to drop the session (conn error 1011) then
> >>>>>> re-login. It looks like we log in at the iscsi level ok.
> >>>>>> I am not sure why this would happen. Let me do some digging. I think
> >>>>>> this might have come up before, but I did not see it.
> >>>>>>>  connection1:0: detected conn error (1011)
> >>>>>>>  session1: host reset succeeded
> >>>>>>> scsi 3:0:0:0: Device offlined - not ready after error recovery
> >>>>>>> #iscsiadm -m node -T iqn.1999-02.com.nexsan:p1:sataboy:028a2347 -p
> >>>>>>> 10.52.145.121
> >>>>>>> node.name = iqn.1999-02.com.nexsan:p1:sataboy:028a2347
> >>>>>>> node.tpgt = 2
> >>>>>>> node.startup = automatic
> >>>>>>> iface.hwaddress = default
> >>>>>>> iface.iscsi_ifacename = default
> >>>>>>> iface.net_ifacename = default
> >>>>>>> iface.transport_name = tcp
> >>>>>>> iface.initiatorname = <empty>
> >>>>>>> node.discovery_address = 10.52.145.121
> >>>>>>> node.discovery_port = 3260
> >>>>>>> node.discovery_type = send_targets
> >>>>>>> node.session.initial_cmdsn = 0
> >>>>>>> node.session.initial_login_retry_max = 4
> >>>>>>> node.session.cmds_max = 128
> >>>>>>> node.session.queue_depth = 32
> >>>>>>> node.session.auth.authmethod = None
> >>>>>>> node.session.auth.username = <empty>
> >>>>>>> node.session.auth.password = <empty>
> >>>>>>> node.session.auth.username_in = <empty>
> >>>>>>> node.session.auth.password_in = <empty>
> >>>>>>> node.session.timeo.replacement_timeout = 120
> >>>>>>> node.session.err_timeo.abort_timeout = 15
> >>>>>>> node.session.err_timeo.lu_reset_timeout = 30
> >>>>>>> node.session.err_timeo.host_reset_timeout = 60
> >>>>>>> node.session.iscsi.FastAbort = Yes
> >>>>>>> node.session.iscsi.InitialR2T = No
> >>>>>>> node.session.iscsi.ImmediateData = Yes
> >>>>>>> node.session.iscsi.FirstBurstLength = 262144
> >>>>>>> node.session.iscsi.MaxBurstLength = 16776192
> >>>>>>> node.session.iscsi.DefaultTime2Retain = 0
> >>>>>>> node.session.iscsi.DefaultTime2Wait = 2
> >>>>>>> node.session.iscsi.MaxConnections = 1
> >>>>>>> node.session.iscsi.MaxOutstandingR2T = 1
> >>>>>>> node.session.iscsi.ERL = 0
> >>>>>>> node.conn[0].address = 10.52.145.121
> >>>>>>> node.conn[0].port = 3260
> >>>>>>> node.conn[0].startup = manual
> >>>>>>> node.conn[0].tcp.window_size = 524288
> >>>>>>> node.conn[0].tcp.type_of_service = 0
> >>>>>>> node.conn[0].timeo.logout_timeout = 15
> >>>>>>> node.conn[0].timeo.login_timeout = 15
> >>>>>>> node.conn[0].timeo.auth_timeout = 45
> >>>>>>> node.conn[0].timeo.noop_out_interval = 10
> >>>>>>> node.conn[0].timeo.noop_out_timeout = 15
> >>>>>>> node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072
> >>>>>>> node.conn[0].iscsi.HeaderDigest = None
> >>>>>>> node.conn[0].iscsi.DataDigest = None
> >>>>>>> node.conn[0].iscsi.IFMarker = No
> >>>>>>> node.conn[0].iscsi.OFMarker = No
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to