One quick test. Can ping the group ip with eth2.   Recent versions of 
debian/ubuntu fail that test.  So I could nvr get that path 2 work. If u down 
eth1 eth2 usually starts 2 work. So it's likely something with standard 
routing. 

Also Equallogic has a white paper on setting up OIS with debian. Might want to 
use current tar ball vs dkpg version. Might b a little stale. 

-don
Sent from my iPhone


On Jul 8, 2010, at 6:56 PM, Laurent <[email protected]> wrote:

> Hello,
> Thank you for the work. This is my 1st post here.
> 
> Under a Debian OS, i try to acces by two different paths an Equallogic
> PS 6000.
> 
> On the server i configured two NICs
> 
> eth1      Link encap:Ethernet  HWaddr b8:ac:6f:12:38:c9
>          inet adr:192.168.15.11  Bcast:192.168.15.255  Masque:
> 255.255.255.0
> 
> eth2      Link encap:Ethernet  HWaddr b8:ac:6f:12:38:cb
>          inet adr:192.168.15.12  Bcast:192.168.15.255  Masque:
> 255.255.255.0
> On the same vlan than the SAN
> 
> First, the discovery works fine:
> 
> iscsiadm -m discovery -t st -I eth1 -I eth2 -p 192.168.15.1 -P 1  -o
> delete -o new
>    Target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb
>        Portal: 192.168.15.1:3260,1
>           Iface Name: eth2
>           Iface Name: eth1
> 
> With EQL, there is only one IP address for the portal, regardless of
> how many times i have to access it.
> 
> I try to connect via the two nics:
> 
> First one:
> #iscsiadm -m node --targetname iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb -I eth1 --portal
> 192.168.15.1:3260,13 --login
> Logging in to [iface: eth1, target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb, portal:
> 192.168.15.1,3260]
> Logging in to [iface: eth1, target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb, portal:
> 192.168.15.1,3260]
> Login to [iface: eth1, target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb, portal:
> 192.168.15.1,3260]: successful
> #
> 
> All is fine with the first one.
> ls /dev/sdb
> /dev/sdb
> mount /dev/sdb /media/testDB/
> 
> Jul  9 00:42:10 sx1 kernel: [ 3318.053517] scsi 9:0:0:0: Direct-
> Access     EQLOGIC  100E-00          4.3  PQ: 0 ANSI: 5
> Jul  9 00:42:10 sx1 kernel: [ 3318.057042] sd 9:0:0:0: [sdb] 209725440
> 512-byte hardware sectors (107379 MB)
> Jul  9 00:42:10 sx1 kernel: [ 3318.057042] sd 9:0:0:0: [sdb] Write
> Protect is off
> Jul  9 00:42:10 sx1 kernel: [ 3318.057379] sd 9:0:0:0: [sdb] Write
> cache: disabled, read cache: enabled, doesn't support DPO or FUA
> Jul  9 00:42:10 sx1 kernel: [ 3318.057734] sd 9:0:0:0: [sdb] 209725440
> 512-byte hardware sectors (107379 MB)
> Jul  9 00:42:10 sx1 kernel: [ 3318.058035] sd 9:0:0:0: [sdb] Write
> Protect is off
> Jul  9 00:42:10 sx1 kernel: [ 3318.059480] sd 9:0:0:0: [sdb] Write
> cache: disabled, read cache: enabled, doesn't support DPO or FUA
> Jul  9 00:42:10 sx1 kernel: [ 3318.059527]  sdb: unknown partition
> table
> Jul  9 00:42:10 sx1 kernel: [ 3318.060635] sd 9:0:0:0: [sdb] Attached
> SCSI disk
> Jul  9 00:42:10 sx1 kernel: [ 3318.060686] sd 9:0:0:0: Attached scsi
> generic sg3 type 0
> Jul  9 00:43:51 sx1 kernel: [ 3419.896300] kjournald starting.  Commit
> interval 5 seconds
> Jul  9 00:43:51 sx1 kernel: [ 3419.915116] EXT3 FS on sdb, internal
> journal
> Jul  9 00:43:51 sx1 kernel: [ 3419.915116] EXT3-fs: recovery complete.
> Jul  9 00:43:51 sx1 kernel: [ 3419.915396] EXT3-fs: mounted filesystem
> with ordered data mode.
> 
> 
> 
> With eth2,, nothing happens.
> iscsiadm -m node --targetname iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb -I eth2 --portal
> 192.168.15.1:3260,13 --login
> Logging in to [iface: eth2, target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb, portal:
> 192.168.15.1,3260]
> Logging in to [iface: eth2, target: iqn.2001-05.com.equallogic:
> 0-8a0906-0dd652407-00e000e7b254c345-testdeb, portal:
> 192.168.15.1,3260]
> iscsiadm: Could not login to [iface: eth2, target: iqn.
> 2001-05.com.equallogic:0-8a0906-0dd652407-00e000e7b254c345-testdeb,
> portal: 192.168.15.1,3260]:
> iscsiadm: initiator reported error (8 - connection timed out)
> 
> I don't have any log line
> 
> Is anyone an idea of what could happen ?
> 
> Thank you very much, i am stuck
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "open-iscsi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/open-iscsi?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to