ISP failure after 2-3 packet drops

[Deepak_K]

We are using one VOIP application over internet which is disconnecting after drop in 2-3 packet. For seamless connectivity we are looking for ISP failure if 2-3 packets are dropping.

We can configure path monitoring ( By default ping interval is 3sec and count is 5) . 

We want to know this path-monitoring will fail after 15 consecutive pings or how it is ?

In first interval if first two pings are successful and for rest three if there is no response so can we consider this three failed pings under 15 consecutive ping ?

all 5 pings in each interval should be require to fail to trigger the path monitor failure ?

[OtakarKlier]

Hello,

You have the timing correct, e.g. multiply the seconds by the count. For the second, not so much. If you want the failover to happen after 3 failures, then set the count to 3, all fields have to occur before the failover occurs. However this may still cause the voip call the drop since they are very sensitive to drops, failovers to other routes, etc.

Hope that helps.

[aleksandar.astardzhiev]

Hi @Deepak_K ,

- 3sec interval with 5 count means: It will mark path as down if 5 consecutive pings have timeout and it will wait for reply maximum 3sec before sending another ping request.

"We want to know this path-monitoring will fail after 15 consecutive pings or how it is ?"

No, not 15 consecutive pings. You can say it will detect path fail after 15 seconds (waiting all 5pings to fail = 3x5)

"all 5 pings in each interval should be require to fail to trigger the path monitor failure ?"

Yes. All 5ping needs to fail for path monitor to be considered down.

What I am not sure right now is when FW consider path-monitor up again...Eith on the first successful ping, or it needed the same count of successful replies as failing.