Quote Originally Posted by To-M
1. Set up volume replication and start the replication task on the primary system.
2. On both systems, create a new target with exactly the same name and assign the LUN by clicking on the "+" button.
3. In the GUI menu, SETUP -> Network, configure bonding using eth0 and eth1.
4. Connect the cable from eth0 to the first network switch and the cable from eth1 to the second one.
5. Do the same as above on the secondary system.
6. On both systems, configure the virtual IP on the bond and select it as an auxiliary interface.
7. Select eth2 as the auxiliary on both systems (it there must be 2 auxiliary interfaces selected on every system).
8. In Function: Failover configuration: on the primary, enable primary mode and on the secondary, enable the secondary accordingly.
9. Select one failover task and click on Apply in function failover tasks on primary system.
10. Click on Start, in Function: failover manager on the primary system.
11. Check the status in Function: Failover status; all must be OK and in Task status, the destination volume must be consistent.
12. Please (either connect or log on?) connect log on to the mirror target with iSCSI initiator using the virtual IP.
13. Create a partition and format the iSCSI disk.
14. Test the Failover function by clicking on Manual Failover in Function: Failover Manager on the primary system.
15. Afterwards, the secondary system must show "active" mode in the node status in Function: Failover status.
16. In order to test Failback, please click on "Sync volumes" in Function: Failover manager on the secondary system.
17. Once both systems are in sync, the Failback button will be activated. Please check Task Status in Function: Failover status on the secondary system; it must show both volumes as consistent.
18. Click on the Failback button in Function: Failover manager on the secondary system.
19. Afterwards, the primary system is back in active mode and ready for failover.
Hello,

I used the above guide to setup autofailover, but everytime I try to enable a task on the primary node it says "Most probably there has been an error when connecting to the other node, or one of the selected tasks does not have a counterpart (a reverse task) on the other node. Please check the secondary node address and make sure you have configured appropriate reverse tasks."

eth4+5 are in bonding mode, eth3 is the auxiliary interface for replication and heartbeat. the bond (eth4+5) do have a public ip address, eth3 a private (10.0.0.x). Pinging between both servers using the private address and also the replication do work fine. What could be the problem?

Thanks