Visit Open-E website
Results 1 to 2 of 2

Thread: VMWare iSCSI MPIO not working as expected in regards to paths.

  1. #1
    Join Date
    Sep 2010
    Location
    Albury, New South Wales, Australia, Earth
    Posts
    40

    Arrow VMWare iSCSI MPIO not working as expected in regards to paths.

    Hi all,

    I have 2 machines setup in a iSCSI failover, everything is working fine on the failover side of things, it's just the MPIO from VMWare I'm not quite sure how to set this up.

    Machine network is
    eth0 - VIP 10.1.5.1
    eth1 - VIP 10.1.5.2
    eth2 - VIP 10.1.5.3
    eth3 - VIP 10.1.5.4
    eth4 - Managment IP - xxx.xxx.xxx.xxx
    eth5 - Replication - 192.168.1.10

    eth0 - eth3 are meant to be the MPIO ip's but when I add 10.15.1.1 to the dynamic discovery on VMWare it only finds 2 paths to the storage box (I have dual dedicated nic's to iscsi in my vm host machines) when I was testing with IET on ubuntu on the same hardware VMWare would auto discover the other 3 nic's/paths and I would end up with 8 paths for each VM host.

    Do I have to manually add each IP to the VMWare iscsi initiator?

    Cheers
    Ad

  2. #2
    Join Date
    Aug 2009
    Location
    Lincoln, UK
    Posts
    42

    Default Different subnets

    Hi there,

    If I were you, I would seriously consider moving each MPIO path to a different subnet, since VMARE and OPEN-E will not know which adapter to send the traffic out on, since they all share the same subnet.

    We use different subnets and this works perfectly, albeit without Failover - since we don't have that configured.

    So your setup would become:

    eth0 - VIP 10.1.5.1/24
    eth1 - VIP 10.1.6.1/24
    eth2 - VIP 10.1.7.1/24
    eth3 - VIP 10.1.8.1/24

    Best regards

    TFZ
    If it can go wrong, it generally will!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •