Re: MIDRANGE-L Digest V4 #735

[Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>]

One time I was having trouble connecting to another server on our WAN, and
Pings were showing exactly 50% drops.  That is, every other ping was timing out.

So, what I did what increase the time to wait for the response on the Ping 
command
to like 10 seconds, and I actually saw that I was receiving every single ping, 
just
very slowly.

So why did I initially see every other ping?  The timing.  Pings wait 1 second 
as
the default before timing out.  So, it would send a ping, wait one second for a
response, state it timed out, send the second ping, wait... and receive the 
response from the first ping!  It would report this as the second ping, then it
would send the third ping, time out, send the 4th ping, and receive the response
to the third ping... 

So, when you test ping put in a longer wait time.  5 seconds should be plenty
(5000ms).  On an AS400:
ping '172.22.28.1' WAITTIME(5)

On a PC:
ping -w 5000 172.22.28.1

You should find that your response times are over 1000ms, which is 1 second,
which is the default wait time for the ping replies (sometimes called Pongs).

Regards,

Jim Langston


> On Wed, 11 Jul 2001, Hatzenbeler, Tim wrote:
> 
> > We have an overworked as/400.  And we have a new one on order, but I was
> > wondering if anyone has an idea for a Band-Aid?
> >
> > Problem.  If I ping a workstation during peak usage I will only get 2 of 5
> > successful hits...
> >
> > Is there a way to grant more timeslices/priority to the IP services job,
> to
> > prevent this problem?  And if so, what job would I change?
> >
> > Thanks, tim
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---