Visit Open-E website
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Failover configuration synchronization on both nodes take long time

  1. #1

    Default Failover configuration synchronization on both nodes take long time

    Hello,

    I have setup volume replication with failover over a lan with iSCSI on two open-e DSS v6 servers. The volume replication seems fine. In the last step, after I start the failover service, it just says the Configuration of both nodes is in progress ... please wait. I've wait over 10 hours. Not sure the status now. Is there a problem and how to check it? Thanks.

    Primary node:

    Failover status
    Global status
    Service running inactive
    Node status inactive
    Ping node group status unknown
    Individual ping node status:
    IP: 192.168.2.4 ok
    Failover services:
    iSCSI on
    NFS off
    Communication via:
    eth2 unknown
    eth0 unknown
    Task status
    [iSCSI] vol01 rep running

  2. #2

    Default

    This should take no more then a 10sec to 1min - something is wrong on the setup or other - you using any VLANs?
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3

    Default

    Yes, I am using VLAN to separate the 3 network I have. Any problem? Thanks.

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

    Default

    Communication via:
    eth2 unknown
    eth0 unknown
    double check subnet masks, on the communication links.

    can the nodes ping each other?

  5. #5

    Default

    The nodes can ping each other on all networks. I have double checked the Virtual IP and Auxiliary connections on both servers, I don't see any problem.

    Primary node Network settings:
    Interface 1: eth0 IP:192.168.3.207/255.255.255.0 (replication network)
    Interface 2: eth1 IP:192.168.1.207/255.255.255.0 (management network)
    Interface 3: eth2 IP:192.168.2.207/255.255.255.0 (Storage network)


    Secondary node Network settings:
    Interface 1: eth0 IP:192.168.3.208/255.255.255.0
    Interface 2: eth1 IP:192.168.1.208/255.255.255.0
    Interface 3: eth2 IP:192.168.2.208/255.255.255.0

    Virtual IP Settings:
    IP address: 192.168.100.100
    Netmask: 255.255.255.0
    Broadcast: 192.168.100.255

    Auxiliary connection:
    Primary node: 192.168.2.208
    Secondary node: 192.168.2.207

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

    Default

    as silly as it sounds.....
    disable failover, and re-apply that its iSCSI failover only, and re-enable it.

  7. #7

    Default

    I disable the failover and re-enable it. Now the status changed to starting failover service(it's over 10 mins). Also, there's an even in primary node shows the failover completed. The primary node service is degraded and Communication links are failed. The failover status in secondary node are same as before. Maybe I need to wait a bit longer?

    Info
    Starting failover service on both nodes ... please wait.

    2011/08/10 17:03:11 Failover: Primary node: This node took over all resources - failover completed. Status is now active.

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

    Default

    degraded is normal , while sync is reached.
    can you give some screen shots from both nodes ?
    If you can PM me logs, or link me to them, that can help too.

    If I have time tomorrow, perhaps I can take a look at your systems via team viewer or something similar.

  9. #9

    Default

    I will send you the screenshot and logs when it's ready. Thanks.

  10. #10

    Default

    Hi Gr-R,

    I have re-installed the SAN servers, now the failover is working fine. Thank you.

Posting Permissions

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