Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. nsp>
  3. juniper
output drops
cheechew at hotmail
Nov 20, 2002, 6:00 PM
Post #1 of 7 (3502 views)
Permalink
This is a multi-part message in MIME format.

------=_NextPart_000_0025_01C29144.C37FC710
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hello,

I am encountering output packet drop incresing from 'monitor interface'.

But according to juniper website, the explaination is as below.

"Drops--Number of packets dropped by the output queue of the I/O Manager =
ASIC. If the interface is saturated, this number increments once for =
every packet that is dropped by the ASIC's RED mechanism."

What should I do to eleminate this problem?

Regards


Interface: t3-0/0/1, Enabled, Link is Up
Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
Traffic statistics: Current =
delta
Input bytes: 5334956357 (14252600 bps) =
[0]
Output bytes: 10999204424 (29350408 bps) =
[7064]
Input packets: 14272467 (4663 pps) =
[0]
Output packets: 19847871 (6481 pps) =
[20]
Encapsulation statistics:
Input keepalives: 303 =
[0]
Output keepalives: 302 =
[0]
Error statistics:
Input errors: 0 =
[0]
Input drops: 0 =
[0]
Input framing errors: 0 =
[0]
Policed discards: 0 =
[0]
L3 incompletes: 0 =
[0]
L2 channel errors: 0 =
[0]
L2 mismatch timeouts: 0 =
[0]
Carrier transitions: 0 =
[0]
Output errors: 0 =
[0]
Output drops: 146730 =
[0]
Aged packets: 0 =
[0]
Active alarms : None
Active defects: None
DS3 statistics:
BPV 0 =
[0]
EXZ 0 =
[0]
LCV 0 =
[0]
PCV 0 =
[0]
CCV 0 =
[0]

------=_NextPart_000_0025_01C29144.C37FC710
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#fffbf0 background=3D"">
<DIV><FONT face=3D"Courier New" size=3D2><FONT size=3D2>
<P>Hello,</P>
<P>I am encountering output packet drop incresing from 'monitor =
interface'.</P>
<P>But according to juniper website, the explaination is as below.</P>
<P>"Drops--Number of packets dropped by the output queue of the I/O =
Manager=20
ASIC. If the interface is saturated, this number increments once for =
every=20
packet that is dropped by the ASIC's RED mechanism."</P>
<P>What should I do to eleminate this problem?</P>
<P>Regards</P></FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Interface: t3-0/0/1, Enabled, =
Link is=20
Up<BR>Encapsulation: Cisco-HDLC, Keepalives, Speed: T3<BR>Traffic=20
statistics:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Current delta<BR>&nbsp; Input=20
bytes:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5334956357 (14252600=20
bps)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Output=20
bytes:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
10999204424 (29350408=20
bps)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
[7064]<BR>&nbsp; Input=20
packets:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
14272467 (4663=20
pps)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Output=20
packets:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
19847871 (6481=20
pps)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[20]<BR>Encapsulation statistics:<BR>&nbsp; Input=20
keepalives:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
303&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Output=20
keepalives:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
302&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>Error statistics:<BR>&nbsp; Input=20
errors:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Input=20
drops:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Input framing=20
errors:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Policed=20
discards:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; L3=20
incompletes:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; L2 channel=20
errors:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; L2 mismatch=20
timeouts:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Carrier=20
transitions:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Output=20
errors:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Output=20
drops:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
146730&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp; Aged=20
packets:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>Active alarms : None<BR>Active defects: None<BR>DS3 =
statistics:<BR>&nbsp;=20
BPV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp;=20
EXZ&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp;=20
LCV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp;=20
PCV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]<BR>&nbsp;=20
CCV&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[0]</FONT></DIV></BODY></HTML>

------=_NextPart_000_0025_01C29144.C37FC710--
output drops [ In reply to ]
Chris.Hellberg at telecom
Nov 20, 2002, 6:04 PM
Post #2 of 7 (3430 views)
Permalink
Hunt down the Kazaa users on your network and show no mercy.

-----Original Message-----
From: Chee Chew [mailto:cheechew@hotmail.com]
Sent: Thursday, November 21, 2002 3:00 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] output drops


Hello,
I am encountering output packet drop incresing from 'monitor interface'.
But according to juniper website, the explaination is as below.
"Drops--Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism."
What should I do to eleminate this problem?
Regards

Interface: t3-0/0/1, Enabled, Link is Up
Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
Traffic statistics: Current delta
Input bytes: 5334956357 (14252600 bps) [0]
Output bytes: 10999204424 (29350408 bps) [7064]
Input packets: 14272467 (4663 pps) [0]
Output packets: 19847871 (6481 pps) [20]
Encapsulation statistics:
Input keepalives: 303 [0]
Output keepalives: 302 [0]
Error statistics:
Input errors: 0 [0]
Input drops: 0 [0]
Input framing errors: 0 [0]
Policed discards: 0 [0]
L3 incompletes: 0 [0]
L2 channel errors: 0 [0]
L2 mismatch timeouts: 0 [0]
Carrier transitions: 0 [0]
Output errors: 0 [0]
Output drops: 146730 [0]
Aged packets: 0 [0]
Active alarms : None
Active defects: None
DS3 statistics:
BPV 0 [0]
EXZ 0 [0]
LCV 0 [0]
PCV 0 [0]
CCV 0 [0]

------------------------------------------------------------------------------
"This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you."

------------------------------------------------------------------------------
output drops [ In reply to ]
cheechew at hotmail
Nov 20, 2002, 6:22 PM
Post #3 of 7 (3490 views)
Permalink
Chris, anything to do with Kazaa? The drop is happening even the interface
is not saturated. Do you know what is cause?


----- Original Message -----
From: "Chris Hellberg" <Chris.Hellberg@telecom.co.nz>
To: "Chee Chew" <cheechew@hotmail.com>; <juniper-nsp@puck.nether.net>
Sent: Thursday, November 21, 2002 10:04 AM
Subject: RE: [j-nsp] output drops


Hunt down the Kazaa users on your network and show no mercy.

-----Original Message-----
From: Chee Chew [mailto:cheechew@hotmail.com]
Sent: Thursday, November 21, 2002 3:00 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] output drops


Hello,
I am encountering output packet drop incresing from 'monitor interface'.
But according to juniper website, the explaination is as below.
"Drops--Number of packets dropped by the output queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism."
What should I do to eleminate this problem?
Regards

Interface: t3-0/0/1, Enabled, Link is Up
Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
Traffic statistics: Current delta
Input bytes: 5334956357 (14252600 bps) [0]
Output bytes: 10999204424 (29350408 bps) [7064]
Input packets: 14272467 (4663 pps) [0]
Output packets: 19847871 (6481 pps) [20]
Encapsulation statistics:
Input keepalives: 303 [0]
Output keepalives: 302 [0]
Error statistics:
Input errors: 0 [0]
Input drops: 0 [0]
Input framing errors: 0 [0]
Policed discards: 0 [0]
L3 incompletes: 0 [0]
L2 channel errors: 0 [0]
L2 mismatch timeouts: 0 [0]
Carrier transitions: 0 [0]
Output errors: 0 [0]
Output drops: 146730 [0]
Aged packets: 0 [0]
Active alarms : None
Active defects: None
DS3 statistics:
BPV 0 [0]
EXZ 0 [0]
LCV 0 [0]
PCV 0 [0]
CCV 0 [0]

----------------------------------------------------------------------------
--
"This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you."

----------------------------------------------------------------------------
--
output drops [ In reply to ]
clay at bloomcounty
Nov 20, 2002, 6:54 PM
Post #4 of 7 (3449 views)
Permalink
> ----- Original Message -----
> From: "Chris Hellberg" <Chris.Hellberg@telecom.co.nz>
> To: "Chee Chew" <cheechew@hotmail.com>; <juniper-nsp@puck.nether.net>
> Sent: Thursday, November 21, 2002 10:04 AM
> Subject: RE: [j-nsp] output drops
>
>
> Hunt down the Kazaa users on your network and show no mercy.

File sharing isn't forbidden on everyone's network. I think as
an ISP I'd lose plenty of customers with such a policy.

>
> -----Original Message-----
> From: Chee Chew [mailto:cheechew@hotmail.com]
> Sent: Thursday, November 21, 2002 3:00 PM
> To: juniper-nsp@puck.nether.net
> Subject: [j-nsp] output drops
>
>
> Hello,
> I am encountering output packet drop incresing from 'monitor interface'.
> But according to juniper website, the explaination is as below.
> "Drops--Number of packets dropped by the output queue of the I/O Manager
> ASIC. If the interface is saturated, this number increments once for every
> packet that is dropped by the ASIC's RED mechanism."
> What should I do to eleminate this problem?


> Interface: t3-0/0/1, Enabled, Link is Up
> Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
> Traffic statistics: Current delta
> Input bytes: 5334956357 (14252600 bps) [0]
> Output bytes: 10999204424 (29350408 bps) [7064]
> Input packets: 14272467 (4663 pps) [0]
> Output packets: 19847871 (6481 pps) [20]

The short answer is, you probably need more bandwidth. Is your
peak utilization close to the maximum 45mbit/sec this interface
can pass? Your utilization is already at 29Mbits in this case.

-c
output drops [ In reply to ]
dr at cluenet
Nov 20, 2002, 7:03 PM
Post #5 of 7 (3439 views)
Permalink
Hi Chee,

On Thu, Nov 21, 2002 at 10:22:45AM +0800, Chee Chew wrote:
> Chris, anything to do with Kazaa? The drop is happening even the interface
> is not saturated. Do you know what is cause?

Traffic can be VERY spiky, especially in these "low-speed" ranges.
So some drops are usual for this circuit utilization level (relative
and absolute).

In what time period were these 146730 drops measured?


Best regards,
Daniel
output drops [ In reply to ]
Chris.Hellberg at telecom
Nov 20, 2002, 7:06 PM
Post #6 of 7 (3543 views)
Permalink
look what happens when you don't put a ;)

;)

> -----Original Message-----
> From: Clayton Fiske [mailto:clay@bloomcounty.org]
> Sent: Thursday, November 21, 2002 3:54 PM
> To: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] output drops
>
>
> > ----- Original Message -----
> > From: "Chris Hellberg" <Chris.Hellberg@telecom.co.nz>
> > To: "Chee Chew" <cheechew@hotmail.com>;
> <juniper-nsp@puck.nether.net>
> > Sent: Thursday, November 21, 2002 10:04 AM
> > Subject: RE: [j-nsp] output drops
> >
> >
> > Hunt down the Kazaa users on your network and show no mercy.
>
> File sharing isn't forbidden on everyone's network. I think as
> an ISP I'd lose plenty of customers with such a policy.
>
> >
> > -----Original Message-----
> > From: Chee Chew [mailto:cheechew@hotmail.com]
> > Sent: Thursday, November 21, 2002 3:00 PM
> > To: juniper-nsp@puck.nether.net
> > Subject: [j-nsp] output drops
> >
> >
> > Hello,
> > I am encountering output packet drop incresing from
> 'monitor interface'.
> > But according to juniper website, the explaination is as below.
> > "Drops--Number of packets dropped by the output queue of
> the I/O Manager
> > ASIC. If the interface is saturated, this number increments
> once for every
> > packet that is dropped by the ASIC's RED mechanism."
> > What should I do to eleminate this problem?
>
>
> > Interface: t3-0/0/1, Enabled, Link is Up
> > Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
> > Traffic statistics:
> Current delta
> > Input bytes: 5334956357 (14252600 bps)
> [0]
> > Output bytes: 10999204424 (29350408 bps)
> [7064]
> > Input packets: 14272467 (4663 pps)
> [0]
> > Output packets: 19847871 (6481 pps)
> [20]
>
> The short answer is, you probably need more bandwidth. Is your
> peak utilization close to the maximum 45mbit/sec this interface
> can pass? Your utilization is already at 29Mbits in this case.
>
> -c
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>

------------------------------------------------------------------------------
"This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you."

------------------------------------------------------------------------------
output drops [ In reply to ]
gmartine at mafalda
Nov 22, 2002, 9:02 AM
Post #7 of 7 (3451 views)
Permalink
Do you have applied any rate limit (hardware based or software based) ?

--

"Peace cannot be kept by force. It can only be achieved by
understanding." Albert Einstein.


On Thu, 21 Nov 2002, Chee Chew wrote:

> Hello,
>
> I am encountering output packet drop incresing from 'monitor interface'.
>
> But according to juniper website, the explaination is as below.
>
> "Drops--Number of packets dropped by the output queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism."
>
> What should I do to eleminate this problem?
>
> Regards
>
>
> Interface: t3-0/0/1, Enabled, Link is Up
> Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
> Traffic statistics: Current delta
> Input bytes: 5334956357 (14252600 bps) [0]
> Output bytes: 10999204424 (29350408 bps) [7064]
> Input packets: 14272467 (4663 pps) [0]
> Output packets: 19847871 (6481 pps) [20]
> Encapsulation statistics:
> Input keepalives: 303 [0]
> Output keepalives: 302 [0]
> Error statistics:
> Input errors: 0 [0]
> Input drops: 0 [0]
> Input framing errors: 0 [0]
> Policed discards: 0 [0]
> L3 incompletes: 0 [0]
> L2 channel errors: 0 [0]
> L2 mismatch timeouts: 0 [0]
> Carrier transitions: 0 [0]
> Output errors: 0 [0]
> Output drops: 146730 [0]
> Aged packets: 0 [0]
> Active alarms : None
> Active defects: None
> DS3 statistics:
> BPV 0 [0]
> EXZ 0 [0]
> LCV 0 [0]
> PCV 0 [0]
> CCV 0 [0]
>

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal