It also occurred to me just now that you might want to add -c 10000 or
similar to end the ping command after a certain point.
When you kill it with ctrl+c you can have a false drop reported because
you might have killed it in between a request and reply.
------ Original Message ------
From: "Adam Moffett" <[email protected]>
To: [email protected]
Sent: 1/29/2018 12:25:18 PM
Subject: Re: [AFMUG] Failover / Recovery Time Testing?
Maybe it's obvious, but this method ought to be fairly accurate IF the
time from one ping to another is very consistent. I don't know the
specific cause of the cases where the command is unable to satisfy the
request for 1 ping per .001 second. Obviously if that cause leads to
variance from one ping to another then the accuracy suffers.
Even if you don't get 1 ping per ms, you might be able to estimate as:
(pings transmitted / time = time per ping)
and
(failover time = time per ping * (pings transmitted - pings received))
