[j-nsp] Finding drops
Saku Ytti
saku at ytti.fi
Wed Jan 23 10:23:48 EST 2019
On Wed, 23 Jan 2019 at 17:01, Jason Lixfeld <jason-jnsp at lixfeld.ca> wrote:
> Now that I’m looking at the right box, yes! More importantly, on et-0/0/2 @ mx1:
>
> Input errors:
> Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 14594154
> …
>
> 85405847+14594154 = 100000001
> Queue counters: Queued packets Transmitted packets Dropped packets
> 0 100000097 76644521 23355576
> 3 1348 1348 0
Have you changed class-of-service config from standard? My first guess
would be that queue0 depth is insufficient, but even that is bit odd
as you have same rate ingress and egress, so no queueing should occur,
unless someone other interface is competing for same egress as well.
--
++ytti
More information about the juniper-nsp
mailing list