iScsi Auto Failover

[To-L]

Hi enealDC

The Ping node is used for the failover connection management. It could be anything with an IP address that is close to the servers. The servers will ping the ping node to ensure the servers and the path are up and running.

The Aux connection does not need to be on the same subnet as the ping node

[juelz]

Sorry, but I didnt get around with my problem. When trying to assign a iSCSI task to a Failover task it always 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."

What could be the problem?

Both servers are connected through crossover. IP of the primary host is 10.0.0.30 and IP of the secondary host is 10.0.0.31.

Thanks!

[To-L]

Hi juelz

Did you enter the correct mirror IP address for primary and secondary server?
CONFIGURATION -> Volume Manager -> Vol. replication -> Function: Mirror server IP

On all 4 NIC's have you enabled
Use this network interface to communicate between the nodes.
in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection.

[juelz]

Hi juelz

Did you enter the correct mirror IP address for primary and secondary server?
CONFIGURATION -> Volume Manager -> Vol. replication -> Function: Mirror server IP

On all 4 NIC's have you enabled
Use this network interface to communicate between the nodes.
in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection.

Hi,

replication works perfectly. The status on both volumes is "consistent".

I enabled the "Auxiliary connection" for all NIC's, but I still get the error.
On the primary host it says:

Global status
  	Service running 	inactive
  	Node status 	inactive
  	Ping node 	ok
Communication via:
  	bond0 	unknown
  	eth3 	unknown
  	eth0 	unknown
  	eth1 	unknown
  	eth2 	unknown