iScsi Auto Failover

[Carterhoward]

Hey Todd,
I have a question, if the auto failover will be using a virtual IP address.
And I am currently use MPIO as per Shon (due to issues in the net Bonding)
What would the failover route be since there are two sub-nets in play with the MPIO?

Thanks, carter

[To-M]

We have not tested this mix but this should work as you can set a virtual IP address from each NIC.

[DerFux]

Hi there!

We have the up44 Vesion running with iSCSI failover installed (or activated).
We had to get an additional license Code but it is not working very well.
So we decided not to use it. (Our Harware/open-e supplier also recommended this).

In the up46 iSCSI failover is not available as you said.

We would like to use this function as well as to have the VMware certification.
(They said us that it will available in March (2008 ;-) ).

I do not expect it to be be available before autumn (both) - if it comes.

Regards
DerFux

[StefanS]

Trying to create an iSCSI-cluster with Version: 5.0.DB47000000.3117 wo do have the following problem:

setup - network - iSCSI Cluster

Secondary

Here we can create a Secondary Cluster Member but the status is always:
- Service running inactive
- Node status inactive
- Ping node disabled
- eth3 unknown
- com 1unknown

We are not able to add the reverse iSCSI Target to the Cluster Task (Button grayed)
- No task have been selected.
- In secondary mode start and stop action will be made only on this node.


Primary

Here we can create a Primary iSCSI Cluster Meber with following Status
- Service running inactive
- Node status inactive
- Ping node ok
- eth3 unknown
- com1 unknown

We are not able to add the reverse iSCSI Target to the Cluster Task

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.

- Info No task have been selected

Whats going wrong
- Both DSS do have an virtual IP with the same address
- there is an iSCSI Volumne successfully replicated
- both servers do have the iSCSI target with same name

regards Stefan

[To-M]

We just got certified with VMware for iSCSI yesterday so DerFux i hope this helps you.

[SuperSAN]

where you get the 47 from????

Open-E informed me that they have a new version but its in Beta testing. Maybe thats why you have issues.

I prefer to wait until the official release then judge.

I test the 44 with the failover it works fine but with few issues. And as I heared they will be fixed..

[DerFux]

Thx To-M, thats good news.

I suppose that is for the up46.

Tomorrow we will do an update on two machines
which are running the up44 (One primary - one secondary - manual failover).

Lets hope the best that the automatic failover will come soon as well.
The manual failover is working with VMware and linux.

Regards
DerFux

[ottl05]

so when will this update be available and how is the configuration for master/slave. will the slave-machine automatically pull the config from the master?

[robertdalco]

As Ottl05 says.

Can I buy this today? What do I specifically reference to make sure I get the version that supports iSCSI failover.

Robert

[To-M]

You will need to purchase the DSS product, NAS-R3 and iSCSI-R3 professional version will not have this feature. Please wait as we will not release until all has been passed by our QA department. We will not release it until then.