packet drops on the ethernet

[a.mir]

T1 link from a hub site to a remote site, i can ping the serial interface from the hub site to remote site's serial all day long with no packet drops, but packets are being dropped at the ethernet interface on the remote site. Ethernet interface looks pretty clean.Any help would be appreciated.

[Kevin Dorrell]

Are these input drops or output drops? The reasons for each are different. Perhaps you could post a show int E0/0 and a show ip int E0/0 for the remote Ethernet. A show run int E0/0 would be useful too.

Kevin Dorrell

Luxembourg

[a.mir]

Below is the sh int, which seems to be clean, if i a have consistant ping going from the the hub site to remote ethernet thats when i have two replies and two drops on a consistant basis.

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0008.e890.07c0 (bia 0009.e8b0.06c0)

Description: Midland, TX - Local Network

Internet address is 38.27.3.254/22

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 5/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 21:02:24

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1989000 bits/sec, 316 packets/sec

5 minute output rate 784000 bits/sec, 293 packets/sec

10242150 packets input, 2914110713 bytes

Received 96351 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

9286678 packets output, 3409231295 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

[Richard Burts]

I have seen a situation where you would get a consistent reply, miss, reply, miss, on and on when the remote device thinks that there are two paths to the return address in the routing table but only one of the paths really works.

Perhaps you can post the output of show ip route from the remote router.

And are you pinging from the router itself, or from a PC connected to the router?

It might be helpful if you would post the output of doing a trace from the remote router to the address that is the source of your pings.

HTH

Rick