Packet loss problem

Packet loss problem

Post by Steve Pfist » Fri, 07 Jan 2000 04:00:00



I've got a packet loss problem I can't seem to figure out. On the
network in question, I've got several test scripts running. Each is
doing a hundred pings from a different point on the network every five
minutes to another host on the network (at least one hop away). No
matter where I start from or ping to, I see some amount of packet
loss, perhaps 5-10 packets in an hour. That's not a lot, I know, but I
don't see why we should be seeing any, except on rare occasions.

One segment of this network has two different subnets assigned to it,
so that traffic between the subnets has to go through the router at
the common FastEthernet interface. I know this isn't ideal, but it's
part of a workaround for another problem we can't seem to solve any
other way.

Whenever a large amount of traffic (hundreds of megs) passes through
the router (from the FastEthernet port to an Ethernet port, or into
the FastEthernet and back out again), the packet loss shown by the
ping scripts increases dramatically, sometimes reaching as high as
12-15% in a single set of 100 pings.

On the router that has the two different subnets out one FastEthernet
port (a 2621 with a 1-port Ethernet card), none of the interfaces are
showing any input or output drops. The 'show buffers' command shows
some failures, but these aren't increasing terribly much over time.
There are quite a few collisions on the Ethernet port, usually
totalling about 6-9% of packets output. In times of high traffic,
throughput for other data streams is noticably reduced. In the output
of 'show process cpu,' the totals at the top seem kind of high (to me
at least), for example, five seconds: 38%/16%; one minute: 22%; five
minutes: 20%. The other figures in the list below that don't really
seem to change much from more idle times.

The problem actually was worse, and adding 'ip route-cache
same-interface' to the FastEthernet port made things a little better,
but the problem is still there.

Do we need a new router? Maybe more memory for the current one (it
seems to usually have 800k - 1.2mb free at any one time)? Do we need
to tune the buffer settings?

Thanks!

--Steve

 
 
 

Packet loss problem

Post by Tony Ra » Fri, 07 Jan 2000 04:00:00


I think you are expecting too much.  The loads you show on the CPU are
not high.  The number of collisions is a function of the load at the
ethernet interface and it goes up much more quickly than the increase in
data flow at the ethernet interface.

You also need to be careful when going from a fast port to a slower
port.  If you are using fast switching, the faster port can over stuff
the slower port and this will result in lost or corrupted packets.  You
might want to implement weighted fair queuing to prevent packet
corruption - make sure the output buffer on the slower port is larger
than the input buffer on the faster port.

--Tony


> I've got a packet loss problem I can't seem to figure out. On the
> network in question, I've got several test scripts running. Each is
> doing a hundred pings from a different point on the network every five
> minutes to another host on the network (at least one hop away). No
> matter where I start from or ping to, I see some amount of packet
> loss, perhaps 5-10 packets in an hour. That's not a lot, I know, but I
> don't see why we should be seeing any, except on rare occasions.

> One segment of this network has two different subnets assigned to it,
> so that traffic between the subnets has to go through the router at
> the common FastEthernet interface. I know this isn't ideal, but it's
> part of a workaround for another problem we can't seem to solve any
> other way.

> Whenever a large amount of traffic (hundreds of megs) passes through
> the router (from the FastEthernet port to an Ethernet port, or into
> the FastEthernet and back out again), the packet loss shown by the
> ping scripts increases dramatically, sometimes reaching as high as
> 12-15% in a single set of 100 pings.

> On the router that has the two different subnets out one FastEthernet
> port (a 2621 with a 1-port Ethernet card), none of the interfaces are
> showing any input or output drops. The 'show buffers' command shows
> some failures, but these aren't increasing terribly much over time.
> There are quite a few collisions on the Ethernet port, usually
> totalling about 6-9% of packets output. In times of high traffic,
> throughput for other data streams is noticably reduced. In the output
> of 'show process cpu,' the totals at the top seem kind of high (to me
> at least), for example, five seconds: 38%/16%; one minute: 22%; five
> minutes: 20%. The other figures in the list below that don't really
> seem to change much from more idle times.

> The problem actually was worse, and adding 'ip route-cache
> same-interface' to the FastEthernet port made things a little better,
> but the problem is still there.

> Do we need a new router? Maybe more memory for the current one (it
> seems to usually have 800k - 1.2mb free at any one time)? Do we need
> to tune the buffer settings?

> Thanks!

> --Steve


 
 
 

Packet loss problem

Post by Steve Pfist » Fri, 14 Jan 2000 04:00:00


I've got some more information on this problem...

The major part of this network is several Cisco routers connected to a
Catalyst 3516 Ethernet switch. All of the routers have little or no
input or output errors, which do not increase much over time. The
switch, however, shows many input errors on almost all ports that are
in use. These increase quite a bit over time (one increases 4000-5000
errors an hour). Most are frame errors. One port that's connected to a
Sun workstation shows no input errors, but many output errors. What
might be causing this?

 
 
 

Packet loss problem

Post by Hansang Ba » Fri, 14 Jan 2000 04:00:00



>I've got some more information on this problem...
>The major part of this network is several Cisco routers connected to a
>Catalyst 3516 Ethernet switch. All of the routers have little or no
>input or output errors, which do not increase much over time. The
>switch, however, shows many input errors on almost all ports that are
>in use. These increase quite a bit over time (one increases 4000-5000
>errors an hour). Most are frame errors. One port that's connected to a
>Sun workstation shows no input errors, but many output errors. What
>might be causing this?

1.  Old firmware.
2.  auto negotiation not working
3.  speed negotiation not working
4.  bad wiring
5.  Stupid 3C905B NIC on the other side.

*********** Remove the REMOVE if emailing me directly **************
Due to the volume of email that I receive, I may not not be able to  
reply to emails sent to my account.  Please post a followup instead.
********************************************************************
Hansang Bae        Director of Network Operations, Eastern Region  

Specializing in Network Design/Troubleshooting and Protocol Analysis
********************************************************************

 
 
 

1. strange packet loss problem

Hi!

I have quite a strange packet loss problem. Routers are like this:

   atm                     atm   fe                ge
A                                B                        C
xxx.yyy.zzz.26       .25   .34                .35

if i ping from A address xxx.yyy.zzz.25 or .34 there is no packet loss.
If i ping .35 i get about 25% packet loss
but if i ping from other side. .35, .34 and .25 give no packet loss and
.26 about 25%
can anybody explain this? I assume there is somekind of switch between B
and C but i have no access to this.
all error counters in A's atm port and in atm switch remain zero.

thanks in advance,

mart

2. Argh, local mail being routed through SmartRelay

3. 3640 to 2611 packet-loss problem

4. quake 1.06 freezing?

5. Your inputs required on a packet loss problem

6. Portable HardDisk Solution? ...

7. Reported Packet Loss Problem with Toshiba PCX1100 Cable Modems

8. Databasing with Frontpage 2000

9. Sporadic Packet Loss Problem

10. Cogeco@HOME more packet loss problems.

11. Comcast@Home packet loss problem fixed (Baltimore)

12. The Packet Loss Problem with Telocity in the NY/NJ Area

13. Packet loss problem