I have a lot of spiky traffic hitting a particular queue and much of
it is being dropped. I want to find out exactly what that traffic is.
I would guess that some variation of monitor traffic interface would
do the trick, but what is the best way to structure that if there is a
lot of traffic and
-
boun...@puck.nether.net] On Behalf Of John Neiberger
Sent: Thursday, May 24, 2012 5:16 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Troubleshooting output queue drops
I have a lot of spiky traffic hitting a particular queue and much of it is
being
dropped. I want to find out exactly
On Thu, May 24, 2012 at 8:01 AM, Per Granath per.gran...@gcc.com.cy wrote:
Well, this gentleman: http://mccltd.net/blog/?p=1199 has looked at that, so:
monitor traffic interface ge-1/0/0 no-resolve matching (ip and (ip[1]
0xfc) 2 == 20)
would give you DSCP with AF22.
But wont this only
On Thu, May 24, 2012 at 8:01 AM, Per Granath per.gran...@gcc.com.cy
wrote:
Well, this gentleman: http://mccltd.net/blog/?p=1199 has looked at that,
so:
monitor traffic interface ge-1/0/0 no-resolve matching (ip and (ip[1]
0xfc) 2 == 20)
would give you DSCP with AF22.
But wont
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Troubleshooting output queue drops
I have a lot of spiky traffic hitting a particular queue and much of it
is being
dropped. I want to find out exactly what that traffic is.
I would guess that some variation of monitor traffic interface would
do
On (2012-05-24 15:34 +), Per Granath wrote:
That's right. You would need to look at port mirroring, or sampling.
Mirroring over GRE directly to your linux tshark box is quick to set up and
really simply. Excellent feature indeed.
Only problem is, in JNPR you cannot send L2 traffic over
6 matches
Mail list logo
