Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
El 29/04/2008, a las 20:15, Mike Christie escribió: Santi Saez wrote: El 29/04/2008, a las 19:42, Mike Christie escribió: Dear Mike!! Are you doing iscsi boot? Or did you start the iscsi service, try to stop it then try to restart it and one of the steps had errors? No, the server isn't booting from SAN. I'm starting iscsi service manually, restarting the service I get the same error :-/ doh, oh yeah, I forgot you are using centos. That is expected for service restarts. Dear Mike, I have make some test with latest Open-iSCSI version open- iscsi-2.0-869, and now I get new error: Apr 30 11:47:35 vz-09 kernel: iscsi: registered transport (tcp) Apr 30 11:47:39 vz-09 kernel: scsi1 : iSCSI Initiator over TCP/IP Apr 30 11:47:39 vz-09 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 30 11:47:39 vz-09 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 30 11:47:39 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 30 11:47:39 vz-09 kernel: sdb: Write Protect is off Apr 30 11:47:39 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 30 11:47:39 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 30 11:47:39 vz-09 kernel: sdb: Write Protect is off Apr 30 11:47:39 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 30 11:47:40 vz-09 iscsid: received iferror -38 Apr 30 11:47:40 vz-09 last message repeated 4 times Apr 30 11:47:40 vz-09 iscsid: connection1:0 is operational now Apr 30 11:47:43 vz-09 udevd-event[2871]: wait_for_sysfs: waiting for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ioerr_cnt' failed Apr 30 11:47:51 vz-09 iscsid: Nop-out timedout after 5 seconds on connection 1:0 state (3). Dropping session. Apr 30 11:47:54 vz-09 iscsid: received iferror -38 Apr 30 11:47:54 vz-09 last message repeated 4 times Apr 30 11:47:54 vz-09 iscsid: connection1:0 is operational after recovery (1 attempts) Apr 30 11:48:04 vz-09 iscsid: Nop-out timedout after 5 seconds on connection 1:0 state (3). Dropping session. Apr 30 11:48:07 vz-09 iscsid: received iferror -38 Apr 30 11:48:07 vz-09 last message repeated 4 times Apr 30 11:48:07 vz-09 iscsid: connection1:0 is operational after recovery (1 attempts) What means received iferror -38 ?? Running the same kernel 2.6.18-53.1.14.el5PAE on a CentOS 5.1 i686 box. Regards, -- Santi Saez Hostalia Internet S.L.U. http://www.hostalia.com --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
El 29/04/2008, a las 18:23, Mike Christie escribió: Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 29 10:24:41 vz-10 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ ioerr_cnt' failed Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on Dear Srs, The problem has been solved disabling Jumbo Frames in the Infortrend target. Linux has Jumbo Frames enabled with 9000 bytes MTU, and the switch has this feature enabled.. very curious :-/ Regards, -- Santi Saez --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
Dear Srs, The problem has been solved disabling Jumbo Frames in the Infortrend target. Linux has Jumbo Frames enabled with 9000 bytes MTU, and the switch has this feature enabled.. very curious :-/ What is the model/name of the switch? Maybe the manufacturer web-site has a firmware update with the fix for this? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Problems with Open-iSCSI and Infortrend A16E-G2130-4
Dear Srs, I'm getting this error when trying to connect to a Infortrend A16E- G2130-4 storage vía iSCSI. Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 29 10:24:41 vz-10 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ ioerr_cnt' failed Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:25:10 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:25:36 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:25:39 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:26:05 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:26:09 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:26:34 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:26:38 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:27:03 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:27:07 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:27:32 vz-10 kernel: sdb:6sd 1:0:0:0: SCSI error: return code = 0x0002 Apr 29 10:27:32 vz-10 kernel: end_request: I/O error, dev sdb, sector 0 Apr 29 10:27:32 vz-10 kernel: Buffer I/O error on device sdb, logical block 0 Apr 29 10:27:32 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:27:36 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:28:02 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:28:05 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) The problem appears to be related to udevd-event? The system is running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and iscsi- initiator-utils-6.2.0.865-0.8.el5. The iscsiadm holds on: [EMAIL PROTECTED]:~ # iscsiadm -m node --targetname iqn. 2002-10.com.infortrend:raid.sn7511631.10 -p 10.15.17.131 -l Login session [iface: default, target: iqn. 2002-10.com.infortrend:raid.sn7511631.10, portal: 10.15.17.131,3260] (..) It's a strange problem.. I have no errors with CentOS 4.6, what can be the problem? Thanks!! Regards, -- Santi Saez Hostalia Internet S.L.U. http://www.hostalia.com --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
Santi Saez wrote: Dear Srs, I'm getting this error when trying to connect to a Infortrend A16E- G2130-4 storage vía iSCSI. Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 29 10:24:41 vz-10 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ ioerr_cnt' failed Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:25:10 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:25:36 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:25:39 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:26:05 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:26:09 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:26:34 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:26:38 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:27:03 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:27:07 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:27:32 vz-10 kernel: sdb:6sd 1:0:0:0: SCSI error: return code = 0x0002 Apr 29 10:27:32 vz-10 kernel: end_request: I/O error, dev sdb, sector 0 Apr 29 10:27:32 vz-10 kernel: Buffer I/O error on device sdb, logical block 0 Apr 29 10:27:32 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:27:36 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 10:28:02 vz-10 iscsid: Nop-out timedout after 15 seconds on connection 1:0 state (3). Dropping session. Apr 29 10:28:05 vz-10 iscsid: connection1:0 is operational after recovery (2 attempts) The problem appears to be related to udevd-event? The system is running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and iscsi- initiator-utils-6.2.0.865-0.8.el5. The target does not like our nops. If you set node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0 It should fix that problem, but if you could check the target logs for something about a bad PDU or iSCSI protocol error or anything, we can see why this is causing problems. The iscsiadm holds on: [EMAIL PROTECTED]:~ # iscsiadm -m node --targetname iqn. 2002-10.com.infortrend:raid.sn7511631.10 -p 10.15.17.131 -l Login session [iface: default, target: iqn. 2002-10.com.infortrend:raid.sn7511631.10, portal: 10.15.17.131,3260] (..) It's a strange problem.. I have no errors with CentOS 4.6, what can be the problem? Thanks!! What are the settings for the PingTimeout, ActiveTimeout and IdleTimeout in /etc/iscsi.conf in the 4.6 installation? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
El 29/04/2008, a las 18:23, Mike Christie escribió: The problem appears to be related to udevd-event? The system is running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and iscsi- initiator-utils-6.2.0.865-0.8.el5. The target does not like our nops. If you set node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0 It should fix that problem, but if you could check the target logs for something about a bad PDU or iSCSI protocol error or anything, we can see why this is causing problems. Dear Mike, I get the same error changing those values at /etc/iscsi/iscsi.conf file and with iscsiadm: # tail -f -n0 -q /var/log/* 2 /dev/null Apr 29 19:28:12 vz-09 iscsid: iSCSI logger with pid=3450 started! Apr 29 19:28:12 vz-09 kernel: scsi2 : iSCSI Initiator over TCP/IP Apr 29 19:28:12 vz-09 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 29 19:28:12 vz-09 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 29 19:28:13 vz-09 iscsid: transport class version 2.0-724. iscsid version 2.0-865 Apr 29 19:28:13 vz-09 iscsid: iSCSI daemon with pid=3451 started! Apr 29 19:28:13 vz-09 iscsid: Could not read data from db. Using default and currently negotiated values Apr 29 19:28:13 vz-09 iscsid: connection2:0 is operational now Apr 29 19:28:16 vz-09 udevd-event[3470]: wait_for_sysfs: waiting for '/sys/devices/platform/host2/session2/target2:0:0/2:0:0:0/ ioerr_cnt' failed Apr 29 19:28:16 vz-09 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 19:29:02 vz-09 kernel: sdb:6 connection2:0: iscsi: detected conn error (1011) Apr 29 19:29:03 vz-09 iscsid: Kernel reported iSCSI connection 2:0 error (1011) state (3) Apr 29 19:29:06 vz-09 kernel: iscsi: host reset succeeded Apr 29 19:29:06 vz-09 iscsid: connection2:0 is operational after recovery (2 attempts) (..) What are the settings for the PingTimeout, ActiveTimeout and IdleTimeout in /etc/iscsi.conf in the 4.6 installation? PingTimeout = default ActiveTimeout = default IdleTimeout = default Not changed, we're using default values.. This's the output of the iSCSI config: # iscsiadm -m node --targetname iqn. 2002-10.com.infortrend:raid.sn7511631.00 node.name = iqn.2002-10.com.infortrend:raid.sn7511631.00 node.tpgt = 1 node.startup = automatic iface.hwaddress = default iface.iscsi_ifacename = default iface.net_ifacename = default iface.transport_name = tcp node.discovery_address = 10.15.17.130 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 = 10 node.session.err_timeo.reset_timeout = 30 node.session.iscsi.FastAbort = No 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.15.17.130 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.active_timeout = 5 node.conn[0].timeo.idle_timeout = 60 node.conn[0].timeo.ping_timeout = 5 node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0 node.conn[0].iscsi.MaxRecvDataSegmentLength = 131072 node.conn[0].iscsi.HeaderDigest = None,CRC32C node.conn[0].iscsi.IFMarker = No node.conn[0].iscsi.OFMarker = No Regards!! -- Santi Saez Hostalia Internet S.L.U. http://www.hostalia.com --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
Santi Saez wrote: El 29/04/2008, a las 18:23, Mike Christie escribió: The problem appears to be related to udevd-event? The system is running CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, and iscsi- initiator-utils-6.2.0.865-0.8.el5. The target does not like our nops. If you set node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0 It should fix that problem, but if you could check the target logs for something about a bad PDU or iSCSI protocol error or anything, we can see why this is causing problems. Dear Mike, I get the same error changing those values at /etc/iscsi/iscsi.conf file and with iscsiadm: Not exactly the same error :) # tail -f -n0 -q /var/log/* 2 /dev/null Apr 29 19:28:12 vz-09 iscsid: iSCSI logger with pid=3450 started! Apr 29 19:28:12 vz-09 kernel: scsi2 : iSCSI Initiator over TCP/IP Apr 29 19:28:12 vz-09 kernel: Vendor: IFT Model: A16E- G2130-4 Rev: 361F Apr 29 19:28:12 vz-09 kernel: Type: Direct- Access ANSI SCSI revision: 04 Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: 629145600 512-byte hdwr sectors (322123 MB) Apr 29 19:28:12 vz-09 kernel: sdb: Write Protect is off Apr 29 19:28:12 vz-09 kernel: SCSI device sdb: drive cache: write back Apr 29 19:28:13 vz-09 iscsid: transport class version 2.0-724. iscsid version 2.0-865 Apr 29 19:28:13 vz-09 iscsid: iSCSI daemon with pid=3451 started! Apr 29 19:28:13 vz-09 iscsid: Could not read data from db. Using default and currently negotiated values Are you doing iscsi boot? Or did you start the iscsi service, try to stop it then try to restart it and one of the steps had errors? Apr 29 19:28:13 vz-09 iscsid: connection2:0 is operational now Apr 29 19:28:16 vz-09 udevd-event[3470]: wait_for_sysfs: waiting for '/sys/devices/platform/host2/session2/target2:0:0/2:0:0:0/ ioerr_cnt' failed Apr 29 19:28:16 vz-09 iscsid: connection1:0 is operational after recovery (2 attempts) Apr 29 19:29:02 vz-09 kernel: sdb:6 connection2:0: iscsi: detected conn error (1011) Apr 29 19:29:03 vz-09 iscsid: Kernel reported iSCSI connection 2:0 error (1011) state (3) Apr 29 19:29:06 vz-09 kernel: iscsi: host reset succeeded Apr 29 19:29:06 vz-09 iscsid: connection2:0 is operational after recovery (2 attempts) For some reason all IO after the inquiry/report_luns does not seem to be getting to the target, or the target is not processing them. Does the inforterend box have multiple cards/hbas/ports? Does it require any ACL type of setup? Do you have to tell it to allow certain initiators? Are there any errors in the target logs? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Problems with Open-iSCSI and Infortrend A16E-G2130-4
El 29/04/2008, a las 19:42, Mike Christie escribió: Dear Mike!! Are you doing iscsi boot? Or did you start the iscsi service, try to stop it then try to restart it and one of the steps had errors? No, the server isn't booting from SAN. I'm starting iscsi service manually, restarting the service I get the same error :-/ For some reason all IO after the inquiry/report_luns does not seem to be getting to the target, or the target is not processing them. Does the inforterend box have multiple cards/hbas/ports? Does it require any ACL type of setup? Do you have to tell it to allow certain initiators? Are there any errors in the target logs? The target is a Infortrend A16E-G2130-4 box, with 4 iSCSI interfaces. I have tested enabling/disabling CHAP authentication getting the same error. I have one partition and it's lun mapped to the first ethernet interface, I connect from the Open-iSCSI box to this interface.. I have tried with all interfaces, changing LUN, SCSI ID numbers, etc.. Maybe the problem is in the Infortrend target.. because of I have connected with the same config, CentOS 5.1 some days ago.. Regards, -- Santi Saez --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
