Extended ping time out after 20 counts

mohamed-khadr · ‎09-07-2004

All,

Iam pinging a remote notes server from my desktop. after successful 20-25 counts, it time outs for 1 or 2 times, then it resume again. I checked the config on both sides. I also notice the rspond time is very high.

Any idea what's wrong?

Thanks,

mohamed

Reply from 10.160.156.200: bytes=32 time=48ms TTL=124

Reply from 10.160.156.200: bytes=32 time=51ms TTL=124

Reply from 10.160.156.200: bytes=32 time=122ms TTL=124

Reply from 10.160.156.200: bytes=32 time=95ms TTL=124

Reply from 10.160.156.200: bytes=32 time=113ms TTL=124

Reply from 10.160.156.200: bytes=32 time=255ms TTL=124

Request timed out.

Reply from 10.160.156.200: bytes=32 time=53ms TTL=124

Reply from 10.160.156.200: bytes=32 time=56ms TTL=124

Request timed out.

Reply from 10.160.156.200: bytes=32 time=54ms TTL=124

Reply from 10.160.156.200: bytes=32 time=211ms TTL=124

Reply from 10.160.156.200: bytes=32 time=299ms TTL=124

Reply from 10.160.156.200: bytes=32 time=88ms TTL=124

Reply from 10.160.156.200: bytes=32 time=578ms TTL=124

Reply from 10.160.156.200: bytes=32 time=86ms TTL=124

Reply from 10.160.156.200: bytes=32 time=459ms TTL=124

Reply from 10.160.156.200: bytes=32 time=185ms TTL=124

Reply from 10.160.156.200: bytes=32 time=183ms TTL=124

Reply from 10.160.156.200: bytes=32 time=204ms TTL=124

Reply from 10.160.156.200: bytes=32 time=289ms TTL=124

Reply from 10.160.156.200: bytes=32 time=75ms TTL=124

Reply from 10.160.156.200: bytes=32 time=172ms TTL=124

Reply from 10.160.156.200: bytes=32 time=69ms TTL=124

Reply from 10.160.156.200: bytes=32 time=186ms TTL=124

Reply from 10.160.156.200: bytes=32 time=172ms TTL=124

Reply from 10.160.156.200: bytes=32 time=236ms TTL=124

Reply from 10.160.156.200: bytes=32 time=195ms TTL=124

Reply from 10.160.156.200: bytes=32 time=124ms TTL=124

Reply from 10.160.156.200: bytes=32 time=225ms TTL=124

Reply from 10.160.156.200: bytes=32 time=144ms TTL=124

Reply from 10.160.156.200: bytes=32 time=237ms TTL=124

Reply from 10.160.156.200: bytes=32 time=135ms TTL=124

Reply from 10.160.156.200: bytes=32 time=66ms TTL=124

Reply from 10.160.156.200: bytes=32 time=49ms TTL=124

Reply from 10.160.156.200: bytes=32 time=167ms TTL=124

Reply from 10.160.156.200: bytes=32 time=52ms TTL=124

Reply from 10.160.156.200: bytes=32 time=57ms TTL=124

Reply from 10.160.156.200: bytes=32 time=54ms TTL=124

Reply from 10.160.156.200: bytes=32 time=90ms TTL=124

Reply from 10.160.156.200: bytes=32 time=112ms TTL=124

Reply from 10.160.156.200: bytes=32 time=236ms TTL=124

Reply from 10.160.156.200: bytes=32 time=51ms TTL=124

Reply from 10.160.156.200: bytes=32 time=180ms TTL=124

Reply from 10.160.156.200: bytes=32 time=330ms TTL=124

Reply from 10.160.156.200: bytes=32 time=214ms TTL=124

Reply from 10.160.156.200: bytes=32 time=226ms TTL=124

Reply from 10.160.156.200: bytes=32 time=196ms TTL=124

Reply from 10.160.156.200: bytes=32 time=183ms TTL=124

Reply from 10.160.156.200: bytes=32 time=110ms TTL=124

Reply from 10.160.156.200: bytes=32 time=221ms TTL=124

Reply from 10.160.156.200: bytes=32 time=500ms TTL=124

Reply from 10.160.156.200: bytes=32 time=419ms TTL=124

Reply from 10.160.156.200: bytes=32 time=242ms TTL=124

Reply from 10.160.156.200: bytes=32 time=552ms TTL=124

Reply from 10.160.156.200: bytes=32 time=299ms TTL=124

Reply from 10.160.156.200: bytes=32 time=228ms TTL=124

Reply from 10.160.156.200: bytes=32 time=53ms TTL=124

Request timed out.

Reply from 10.160.156.200: bytes=32 time=54ms TTL=124

Reply from 10.160.156.200: bytes=32 time=57ms TTL=124

Ping statistics for 10.160.156.200:

Packets: Sent = 76, Received = 71, Lost = 5 (6% loss),

Approximate round trip times in milli-seconds:

Minimum = 48ms, Maximum = 578ms, Average = 176ms

Control-C

^C

C:\>

scottosan · ‎09-07-2004

The first thing I would check is that the speed/duplex is manually set to match the switch port and NIC on the server or even your desktop. Also try pinging from a switch or router to the server to insure it is not your desktop.

rjackson · ‎09-07-2004

This looks like a WAN circuit getting hit periodically by large routing updates or sap broadcasts.

Run your ping tests through several 3-4 periods of timeouts and time how far apart they are. See if it lines up with any of these examples;

Distance vector protocols such as IP Routing Information Protocol (RIP), Internetwork Packet Exchange (IPX) RIP, and Interior Gateway Routing Protocol (IGRP) send a full routing table at a fixed interval of time as described below:

The IP RIP routing protocol sends an update, by default, every 30 seconds.

The IPX RIP routing protocol sends an update every 60 seconds, per its default interval.

The IGRP routing protocol sends a routing table update, by default, every 90 seconds.

mohamed-khadr · ‎09-07-2004

Rich,

I run a capture on the line.The server is running on Netware, so there are sap updates.Iam running EIGRP on the network.I can ping from the local switch with no time outs, from the router,it's a different story. Extended ping of 100 or 200 start to time out after 75-80(that's the local router).

Regards,

mohAmed

mohamed-khadr · ‎09-07-2004

Scott,

Thanks for ur quick respond. I did check the speed&duplex on the switch port & the server NIC. They match. Also I can big from the switch no problem. But an extended ping on the router with 200 counts, the server time out after may be 75-80 count.Iam running EIGRP on the network.

Regards,

mohamed

spremkumar · ‎09-07-2004

hi

Afaiu from ur post ur getting rto when pinging u r remote nodes from ur local lan.

Whts the mode of connecitivity between u r location and the remote side ?r u doing any unequal cost load balancing using eigrp or any other sort of load balancing ??

If its an E1 connecting to u r remote side is that reliable always ?hv u cheked any drops or errors on tht ?since u r sure & have confirmed,cheked ur lan side do chek these points too..

regds

mohamed-khadr · ‎09-08-2004

It's a frame connection. From sub int to sub int ppp.No load balancing.

Here's a a ping result from 2 different connectin to same Notes server.

cisco45-1#ping

Protocol [ip]:

Target IP address: 10.160.156.202

Repeat count [5]: 200

Datagram size [100]:

Timeout in seconds [2]: 1

Extended commands [n]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 200, 100-byte ICMP Echos to 10.160.156.202, timeout is 1 seconds:

!..!..!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Success rate is 97 percent (195/200), round-trip min/avg/max = 48/63/564 ms

cisco45-1#

cisco45-1#trac 10.160.156.202

Type escape sequence to abort.

Tracing the route to 10.160.156.202

1 10.180.180.2 80 msec 72 msec 60 msec

2 10.160.156.202 56 msec 48 msec 60 msec

cisco45-1#

*****************************************************

SanJose2612#ping

Protocol [ip]:

Target IP address: 10.160.156.202

Repeat count [5]: 200

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 200, 100-byte ICMP Echos to 10.160.156.202, timeout is 2 seconds:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!.!.!.!.!.!.!.

!.!.!.!.!!!!!!!!!!!!!!!!!!!!!!!!!..!!!!!!!!!!!!!!!!!!!!!!!!!

Success rate is 93 percent (186/200), round-trip min/avg/max = 76/109/1719 ms

SanJose2612#trac 10.160.156.202

Type escape sequence to abort.

Tracing the route to 10.160.156.202

1 10.180.180.6 76 msec 80 msec 76 msec

2 10.160.156.202 76 msec 76 msec 81 msec

SanJose2612#

spremkumar · ‎09-08-2004

hi

To isolate the problem and possibilities to minimum have u tried pinging from these routers to the router where ur remote notes is placed ?

is that frame connecitivity thru without any drops ?did u chek tht connecitivity ?

if thts thru then u need to solely concentrate on the lan part.either ur local lan or remote lan.i would suggest u to ping ur routers ethernet,ur end wan ip and remote end wan ip while u r getting drops with the notes server.

with tht try pinging from the remote router to ur notes server and chek whether u r experincing any drops.

r u experincing this problem for the whole day or hows tht behaving (only in peak/working hrs and not getting any drops in offpeak hrs) ??

and also crosschek/confirm again whether ur ethernet port settings r same on both the sides on ur remote side router as well on ur notes server as already pointed out by earier posts..

regds

mohamed-khadr · ‎09-10-2004

All,

Thankx so much for ur inputs. It was a QoS issue. There was a frame-relay cir config on the sub int. to 256 but was not applied and the s. int. deffered to ONLY 64K(cap default limit). That cuz all the hysteria and panic.(I should 've read the config more carefully).

mohamed khadr

glen.grant · ‎09-09-2004

Think you need to traceroute the path then ping from each hop and see when the packet drops start . If you have a real busy line that you route across then 1 or 2 drops is not unusual . Somewhere along the path the drops will probably stop and you can concentrate on that area and look at interfaces and utilization etc........