iSCSI Failure when Secondary Node Down

We followed instructions on"Step-by-Step Guide to Synchronous Volume Replication (Block Based) with Fail-over over a LAN (withunicast) Supported by Open-E DSS", it works.

Fail-over when primary node down also working. However a strange issue happened when secondary node down.

Below are steps to reproduce our problem.
1. both primary and secondary node is up. iSCSI node status are "primary/active" and "secondary/passive".
2. we intentionally turn secondary node off.
3. after some time, iSCSI virtual ip longer can be ping.
4. check node status in primary node become suspend.
5. iSCSI storage not working..

step to resume:
1. turn secondary node on.
2. in primary node, stop fail-over manager.
3. in primary node, start replication tasks.
4. in primary node, start fail-over manger.

Any hints on what's happen?

Fai

Open a support call pronto. Tech support is excellent and they will be able to resolve this.

I had an issue where my autofailover was working fine, even when I shut the secondary off. But when the secondary came backup I lost my virtual IP. After a lot of work with the Open-E support folks and Todd Maxwell, they discovered that one of my bonded replication connections was flaky and causing the issue. Once I removed the flaky connection then everything started working great.

Issue resolved.

This is my mistake that used secondary node ip in "Ping node IP". It work perfectly after I modify Ping node IP to another server.