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

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

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

Quote:

---

Communication via:
eth2 unknown
eth0 unknown

---

double check subnet masks, on the communication links.

can the nodes ping each other?

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

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

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.

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.

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

Hi Gr-R,

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

I suspect there was an issue in writing the initial config files for the failover service.
I have seen that happen once or twice..... sometimes its as simple as resetting the files. This can be done by de-selecting the failover services, and clicking apply, then re-selecting them, and clicking apply. Then re-enable failover.