Visit Open-E website
Results 1 to 2 of 2

Thread: Best Practice DSS7/Active-Active mpio w/ XenServer 6.2

  1. #1

    Default Best Practice DSS7/Active-Active mpio w/ XenServer 6.2

    Hello Sirs,

    I have some conceptional Questions regarding an Active-Active Setup in conjunction with XenServer 6.2. I use 2 Supermicro Storages with DSS7 against a bunch of XenServer 6.2 Hypervisors:

    Here is my Config:

    node-a:

    eth0 192.168.1.90 (Management)
    eth1 192.168.25.220 (Hostport Switch 1)
    eth2 192.168.26.220 (Hostport Switch 2)
    eth3 -unused-
    eth4 192.168.24.1 (bond0)
    eth5 192.168.24.1 (bond0)
    bond0: 192.168.24.1 (back2back replication)

    Virtual IP's for target0 on node-a: 192.168.81.100, 192.168.91.100

    node-b:

    eth0 192.168.1.91 (Management)
    eth1 192.168.25.221 (Hostport Switch 1)
    eth2 192.168.26.221 (Hostport Switch 2)
    eth3 -unused-
    eth4 192.168.24.2 (bond0)
    eth5 192.168.24.2 (bond0)
    bond0: 192.168.24.2 (back2back replication)

    Virtual IP's for target1 on node-b: 192.168.82.100, 192.168.92.100

    --------------

    XenServer Configuration (n>=1: Xen Server Index):

    eth0 192.168.1.10n (Management)
    eth1 192.168.25.10n (Hostport Switch 1), Alias IPs: 192.168.81.10n, 192.168.82.10n
    eth2 192.168.26.10n (Hostport Switch 2), Alias IPs: 192.168.91.10n, 192.168.92.10n

    --------------

    I used the XenServer primary IP's on the Hostport as Pingnode and have setup Alias IP's so the XenServer's can reach the Virtual IP's of the SAN.

    Now, when I add an SR (Storage Repository) in Xen, I enter 192.168.81.100 to reach mirrorset0. I can connect it to the Pool, but what scares me is that I XenCenter (as well as multipath -ll) shows me 5 active mpio pathes to the open-e mirror0, but I think I should only have two. It's both Virtual IP's (which I think is correct, as well as the "physical" IP's of the Hostports as well as the Management Network, that are valid pathes to the Volume. What I could do was following the Hint from some tutorials and block the Communication of the XenServer Hosts and the open-e Nodes with iptables. OK, that works, but I still have 4 pathes left (2x Virtual IP, 2x Physical IP). Is this good? From my understanding the Failover Functionality only works through the Virtual IP's (so arp-tricking works to instantly re-route the traffic to the backup-node). But having the physical ip's of the Hostports in my mpio pathlist doesn't seem right, because I bypass the Failover logic somehow. I fear splitbrain problem when a Failover occurs.

    This boils to few simple questions:

    - Is it wise to have the Xen Hosts have IP's from the Hostports IP Range of the open-e?
    - Is it wise to use the Xen Hosts as ping-nodes?
    - Is it wise to have more then 2 mpio path (or as many as you have virtual ips) when using a iscsi Volume with Failover enabled?
    - Shouldn't there be a setting to tell mpio on the open-e's to only announce Virtual IP's when in Failover mode, and not ALL local NIC's it sees?

    so long,
    thanks in advance..

  2. #2
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    - Is it wise to have the Xen Hosts have IP's from the Hostports IP Range of the open-e?
    Use IPTables and block all uneeded paths. Only connect to the VIP. - Is it wise to use the Xen Hosts as ping-nodes?
    A better choice would be switches or routers. - Is it wise to have more then 2 mpio path (or as many as you have virtual ips) when using a iscsi Volume with Failover enabled?
    MPIO should match the same amount of VIP. - Shouldn't there be a setting to tell mpio on the open-e's to only announce Virtual IP's when in Failover mode, and not ALL local NIC's it sees?
    Targets are broadcast on all IPs. You may use allow/deny rules to block connections on the storage side.

Posting Permissions

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