Failover configuration synchronization on both nodes take long time

[Gr-R]

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

[cloudtech]

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.

[Gr-R]

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.

[cloudtech]

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

[cloudtech]

Hi Gr-R,

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

[Gr-R]

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.