iScsi Auto Failover

[Ahead-IT]

Works perfect over 10Gbit ethernet, incl. fallback en return to primary system. Congratulations, asking for this for over 2 years !!

Connection: SyncSource
Total size to replicate: 614400 MB
Remain to replicate: 542078 MB
Speed (avg): 248084 kB/s (216540 kB/s)
Time left: 0:37:17
Source info:
Logical volume: lv0000
Consistency: Consistent
Destination info:
Logical volume: lv0000
Consistency: Inconsistent
IP address: 192.168.50.221

[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

[pfeifferl]

We will have a DSS Demo-CD version ready very soon, ETA 2 weeks. DSS LITE will not have this feature.

When will this new demo cd with auto failover be available?

[Sh-J]

Dear pfeifferl,

There is no ETA yet for the new demo CD. But it should be ready in a short periode of time.

Regards,
SJ

[pfeifferl]

Dear pfeifferl,

There is no ETA yet for the new demo CD. But it should be ready in a short periode of time.

Regards,
SJ

Weeks ago there was ETA 2 week. And know "no ETA"?? Hmmm ...

[To-M]

We decided to wait until the latest release of DSS which was released on 11-17-08, hopefully we will have this before Monday of next week.

[pfeifferl]

OK, great

[ottl05]

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.

and on the host I must set the virtual IP for the target-server?

Could I use more Virtual IPs ? For each nic in a subnet (subnet1-LAN, subnet2-for vm)?

and with the actual release I could select more than one iscsi-target for autofailover?

[ottl05]

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.

Auto Failover Quick Start Guide:

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.

must the targetname be exactly the same? at the moment on storage1 it is like
"iqn.2008-04:storage1.target0" and on storage2 like
"iqn.2008-05:storage2.target0"

both have the same alias-name.

Could I assign the LUN on the slave storage (it´s the replication target)?

[To-M]

Q. On the host I must set the virtual IP for the target-server?

A. Host must connect to the Virtual IP Address that you have setup.

Q. Could I use more Virtual IPs ? For each nic in a subnet (subnet1-LAN, subnet2-for vm)?

A. You can setup more Virtual IP's for each NIC but only per NIC assignment.

Note
Virtual IP needs to be unique within its network environment and the same on both nodes (Primary and Secondary).
Changes to virtual IP settings can be done only when failover configuration is not active.

Note
Virtual IP can be in a different subnetwork than the node IPs, e.g. 192.168.2.1 as opposed to 192.168.1.1 and 192.168.1.2.

Q. With the actual release I could select more than one iscsi-target for autofailover?

A. Most recent release DSS 5.0_49 build 3277 allows for more then one iSCSI - Target Auto Failover.

Q. Must the targetname be exactly the same? at the moment on storage1 it is like
"iqn.2008-04:storage1.target0" and on storage2 like
"iqn.2008-05:storage2.target0"

A. Both the Primary and Secondary must have the same Target Name and Lun# and SCSI ID.