iScsi Auto Failover

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

[ottl05]

- I named the targets equal
- I set up the Virtual IPs on my NICs on both Systems
- the Auxilary is set on all NIC

the status on the primary:

Names  	Status
Global status
  	Service running 	inactive
  	Node status 	inactive
  	Ping node 	    ok
Communication via:
  	bond1 	unknown     (192.168.6... - replication)
  	eth2 	unknown    (192.168.10.... - iSCSI )
  	bond0 	unknown   (192.13.47.... LAN)

- the ping node: 192.13.47.xxx
- I entered the IPs from the replication bond as primary and secondary nodes.


but when I activate a iscsi-task for failover I´ll get an error:
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.

On the secondary I could not setup a replication task, because the Volumes are in target-mode.

So whats wrong?

[To-M]

Are both NIC's for the Replication and Targets have the Auxiliary connection enabled. This is in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection

Also check that the Volume Replication is completed successfully in Status > Tasks.

[ottl05]

Are both NIC's for the Replication and Targets have the Auxiliary connection enabled. This is in SETUP -> Network -> iSCSI Failover -> Function: Auxiliary connection

Also check that the Volume Replication is completed successfully in Status > Tasks.

the Auxiliary connection is activated on all NICs
the replication tasks are all completed successfully,

but still the same error.
when I activate the failover-function the information says:

Information
System has automatically selected interface bond0

bond0 are the nics to the LAN (192.13.47....)

as primary/secondary node I took the IPs from the replication bond (192.168.6....)

[To-M]

Email me and I will send you a step by step document. It looks as though the secondary has issues. Make sure you have the latest version that was just released this week.

[ottl05]

Email me and I will send you a step by step document. It looks as though the secondary has issues. Make sure you have the latest version that was just released this week.

email is underway

[enealDC]

What about the release that was just put up on the FTP server yesterday?

Build 3278. What does this fix?

[To-M]

There was a problem in updating messages in other languages than English and this update fixes the messages updating for the last build 3277. Also fixed problem with error message in Failover/Failback.

[juelz]

Hi,

To-M, can you send the same email, which you send to ottl05, to me? My email address is julian_joswig@web.de
I still experience problems with activating the failover task. I updated the software, but the problem still occurs.

Thanks!