VIP failover time

[regular123]

I have configured a critical service(ap-kal-pinglist) for the VIP redundant failover, default freq,maxfail and retry freq is 5,3,5, so I think the failover time is 5+5*3*2=35s.But the virtual-router's state changed from "master" to "backup" in around 5 secs after connection lost.

Anyone help me to understand it?

[Gilles Dufour]

normally the time for the service to go down is 3*5 = 15 seconds,

Once the service is down, failover should occur in 3 seconds.

Did you see the service going down faster than 15 sec ?

Check the log file and compare the timer.

You can also turn on 'logging subs keepalive level debug' to get more information about the keepalive and verify when it goes to dying and then down and when the mast failover after that

Regards,

Gilles.

[regular123]

Service sw1-up-down connect to e2 interface,going down in 15sec

Service sw2-up-down connect to e3 interface,going down in 4sec?

JAN 14 02:38:41 5/1 3857 NETMAN-2: Generic:LINK DOWN for e2

JAN 14 02:39:57 5/1 3858 NETMAN-2: Generic:LINK DOWN for e3

JAN 14 02:39:57 5/1 3859 VRRP-0: VrrpTx: Failed on Ipv4FindInterface

JAN 14 02:40:11 5/1 3860 NETMAN-2: Enterprise:Service Transition:sw2-up-down -> down

JAN 14 02:40:11 5/1 3861 NETMAN-2: Enterprise:Service Transition:sw1-up-down -> down

[Gilles Dufour]

e2 went down at 2:38:41

sw2 went down a5:2:40:11

So it is 90 sec to go down

e3 went down at 02:39:57

sw1 went down at 02:40:11

So it is 14 seconds [not 4 sec].

As you can see sw1 and sw2 went down at the same time.

The reason is that when e2 goes down, the CSS can stil reach sw2 via e3.

So everything looks good here.

Your services went down in 3*5 = 15 seconds as it is configured.

Regards,

Gilles.