From: Church, Chuck (cchurch@wamnetgov.com)
Date: Mon Jul 05 2004 - 09:11:42 GMT-3
If you're not doing traffic shaping, it's possible that you tried to
exceed the port speed of that interface. I think that output queue
drops will show up in the PVC info like you've shown. Do a 'sh int' on
that physical int, and see if there's a similar number on the 'output
queue drops' section.
Chuck Church
Wam!Net Government Services - D&I Team
Lead Design Engineer
CCIE #8776, MCNE, MCSE
1210 N. Parker Rd.
Greenville, SC 29609
Office: 864-335-9473
Cell: 703-819-3495
cchurch@wamnetgov.com
PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.
com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Nick Tucker
Sent: Monday, July 05, 2004 3:53 AM
To: ccielab@groupstudy.com
Subject: Dropped packets in pvc
Pulled this from one of the networks we monitor here:
DLCI = xxx, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0.2
input pkts 20275664 output pkts 19938492 in bytes
1807487268
out bytes 2019670889 dropped pkts 26 in FECN pkts
0
in BECN pkts 0 out FECN pkts 0 out BECN pkts
0
in DE pkts 0 out DE pkts
0
out bcast pkts 5831592 out bcast bytes
468801450
pvc create time 41w3d, last time pvc status changed 01:15:43
My question is, listed above is dropped pkts 26.
Is there any other information that could be obtained as to the how/why
these packets were dropped?
It wasn't due to DE, as also listed above, there were no discard
eligables.
On another note, anyone else hear about the "incident" yesterday
afternoon with Accuring, et. all. in Newark.
Its made most of the night go by quickly tonite :)
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:47 GMT-3