Slow failover (virtual ip takes long to recover)

[4Consult]

Hi guys,

I have the following config:

DDS1

eth0 172.10.10.1
eth1 172.10.11.1
eth2 172.10.12.1
eth3 172.10.13.1

DDS2

eth0 172.10.10.2
eth1 172.10.11.2
eth2 172.10.12.2
eth3 172.10.13.2

eth0 on both machines have a virtual ip: 10.10.10.10

All adapters are in auxilary mode.

When I unplug DDS1 it takes about 1 minute before I can ping 10.10.10.10. All virtual machines will hang. What's wrong in my config?

When I bring DDS1 back online ping falls away again for about 1 minute. I cannot get it to work proberly. Hope someone can help me.

[Robotbeat]

What are your advanced settings for autofailover?

BTW, 1 minute isn't really that long for remote storage. You should allow up to at least 180 seconds, usually (can be set in Windows registry).

[pfeifferl]

You should allow up to at least 180 seconds, usually (can be set in Windows registry).

Do you know more about this in Windows (Server 2008/Hyper-V)? Where can I find the registry key to extend the waiting/recovery time for iSCSI connection?

I think there are more MS users here, which will run into troubles with this vIP timeout ..

Thanks!

[RWolfrum]

The iSCSI connection seems to be a local disk for the os.
I think the registry key is

HKEY_LOCAL_MCHINE\SYSTEM\CurrentControlSet\service s\Disk
-> TimeOutValue

not sure if this value helps in the guest OS or in host OS.

regards,

Roland

[Robotbeat]

Here's an article for you about that registry setting:

http://publib.boulder.ibm.com/infoce...ut_198ovw.html