Visit Open-E website
Results 1 to 10 of 91

Thread: iScsi Auto Failover

Thread has average rating 4.00 / 5.00 based on 1 votes.
Thread has been visited 536801 times.

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default

    Hi deejay24

    In our test with VMware failover worked with out any problems
    Here is a link to another user using Hyper-V without issues as well
    http://forum.open-e.com/showthread.p...hlight=Hyper-V
    Check out his setup, it may help with you problem

  2. #2
    Join Date
    Oct 2008
    Posts
    69

    Default

    Hi,

    I read this How-To and i have one question, what is the IP to be used IP for the ISCSI Initiator? The one from bond0 or eth2 ?

    I'll implement this solution soon for a Vmware Server on Ubuntu 8.0.4 and two OpenE DSS (actually i have bond0 for iSCSI, bond1 for Public access on my SAN & Server).


    Thanks a lot for this great update.

    NSC

  3. #3

    Default

    Dear nsc,

    Use the bond IP address.

  4. #4
    Join Date
    Aug 2008
    Posts
    236

    Default

    I'm having a problem with failover. Everything seems to be working, it's just that it refuses to use the auxillary NIC and as such, the failover status is "degraded" Here is my NIC layout

    The first NIC is for management
    Second NIC is Cross over for replication
    Third NIC Unused
    Fourth NIc Unused
    Fifth NIC iSCSI-Path A
    Sixth NIC iSCSI-Path B


    I'm using MPIO and do not want to use bonded interfaces. So is it a requirement that all interfaces for failover have to be on the same subnet?

  5. #5

    Default

    The first NIC is for management
    Second NIC is Cross over for replication Third NIC Unused Fourth NIc Unused Fifth NIC iSCSI-Path A Sixth NIC iSCSI-Path B

    We recommend the replication be bonded - so for NIC 2 please bond with another available NIC that is Unused. We have thought about this in our development and we strongly support this only. If not bonded for the Replication then this will not be supported. This is for your benefit.

    We have not tested with MPIO with regards to the Virtual IP address but I believe you can use the other Unused NIC (4) to set the Virtual IP address and use with MPIO from the host side. NIC example for MPIO should be as follows:

    Must configure on server both network adapters to work in different subnets:
    for example:
    - adapter no1: Ip address: 192.168.2.220, NetMask: 255.255.255.0 (Virtual IP Address)
    - adapter no2: Ip address: 192.168.3.220, NetMask: 255.255.255.0 (Virtual IP Address)

    and the configuration of the client network adapters:
    - adapter no1: Ip address: 192.168.2.221, NetMask: 255.255.255.0
    - adapter no2: Ip address: 192.168.3.221, NetMask: 255.255.255.0
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  6. #6
    Join Date
    Aug 2008
    Posts
    236

    Default

    Thanks very much. Our MPIO is on the host side.

    What about this question: do all NICs for failover have to be on the same subnet? Or should all NICs be able to reach the ping node?

  7. #7

    Default

    Dear enealDC,

    The Virtual IP should be on the same subnet, as well as the ping node. And the Replication should be on its own subnet.

    Regards,
    SJ

Posting Permissions

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