iScsi Auto Failover

[To-M]

Auxiliary connection is additional connection used for the cluster communication and checking if second node is ok. Please set for both Public and Replication NIC's.

[juelz]

Auxiliary connection is additional connection used for the cluster communication and checking if second node is ok. Please set for both Public and Replication NIC's.

I did, but that doesn't change anything. I just can't select an iSCSI Task as a Failover Task.

[enealDC]

well with the multi-volume failover, then the limitations are manageable!

[ottl05]

We will have multi iSCSI Volume Replication in next release during the week of the 17th.

We do recognize the 4TB limitation and we are looking into this please allow us more time for the developers to research this and hopefully without additional cost.

I´ve got a question with the multi iSCSI Volume Replication. must all the iSCSI Volumes be assigned to the same target, or could the volumes be assigned to different targets for different subnets?

At the moment my network config looks like:

- nic1+nic2= bond0 (management and small NFS-share) 192.168.2. (our LAN)
- nic3 - iSCSI for two vmware-servers 192.168.3. (seperate subnet)
- nic4 -for major iSCSI-Target (for central fileserver) 192.168.10. (I want to activate auto-failover for this Target)
- nic5+nic6 = bond1 (replication) 192.168.6....

What must I change for auto-failover?

[To-L]

Hi ottl05

You do not need the same iSCSI target for the Auto Failover to work as long as your Virtual Ip address are on the same subnet as your host.

Use Nic 4 for the virtual IP
If Nic 5 & 6 are bonded and going from server to server that should be fine.

[enealDC]

Tom, what's the significance of the ping_node? There is still something not right about my understanding here and it relates to the requirement of the 2 aux connections.

I need to understand if the aux connections for both nodes in the cluster - must they all reside in the same subnet?

How does each node communicate with the ping_node? Is it through the aux connection? If so - then this means that all of a nodes interfaces they must be in the same subnet as the ping_node.

I ask this because no matter what I do, it always starts in a degraded mode (e.g. running on one Aux connection)

[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.

[zeki893]

For the iSCSI Auto Failover you will need 2 DSS modules only, there is no additional license fees for this. Below is a Quick Start guide for the Auto Failover.

so i just need another dss module? do i need to have the same level license as my original? 16tb module with 16tb addon license or do i just need a 16tb module and use the same license on it?