You hv to ask for it. It's not posted on website. It won't fix this issue. It just shows u how 2 set it up including mpio and persistent device names.
-don Sent from my iPhone On Jul 9, 2010, at 2:03 PM, Laurent HENRY <[email protected]> wrote: > Hi Don, you are right. > i can't ping from eth2 interface: > > #ping -I eth1 192.168.15.1 > PING 192.168.15.1 (192.168.15.1) from 192.168.15.11 eth1: 56(84) bytes of > data. > 64 bytes from 192.168.15.1: icmp_seq=1 ttl=255 time=0.192 ms > 64 bytes from 192.168.15.1: icmp_seq=2 ttl=255 time=0.118 ms > 64 bytes from 192.168.15.1: icmp_seq=3 ttl=255 time=0.114 ms > c^C > --- 192.168.15.1 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 1998ms > rtt min/avg/max/mdev = 0.114/0.141/0.192/0.037 ms > # ping -I eth2 192.168.15.1 > PING 192.168.15.1 (192.168.15.1) from 192.168.15.12 eth2: 56(84) bytes of > data. > From 192.168.15.12 icmp_seq=1 Destination Host Unreachable > From 192.168.15.12 icmp_seq=2 Destination Host Unreachable > From 192.168.15.12 icmp_seq=3 Destination Host Unreachable > ^C > --- 192.168.15.1 ping statistics --- > 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3018ms > > What is the problem with Debian ? Something wrong in the routing table ? > > Do you know where this paper can be found ? > > Le Friday 09 July 2010 19:50:47 Don Williams, vous avez écrit : >> 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. > > > > -- > Laurent HENRY > Administrateur Systèmes & Réseaux > Responsable du CRI/RSSI > EHESS - CRI > 54 Bd Raspail > 75006 Paris > Secrétariat du CRI: 01 49 54 23 08 > Tel: 01 49 54 23 61 -- 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.
