[j-nsp] Troubleshooting output queue drops

[Doug Hanks]

This won't work for transit traffic.

Thank you,

-- 
Doug Hanks - JNCIE-ENT #213,  JNCIE-SP #875
Sr. Systems Engineer
Juniper Networks



On 5/24/12 8:01 AM, "Per Granath" <per.granath at 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.
>
>
>
>> -----Original Message-----
>> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
>> bounces at puck.nether.net] On Behalf Of John Neiberger
>> Sent: Thursday, May 24, 2012 5:16 PM
>> To: juniper-nsp at 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 the
>> trick, but what is the best way to structure that if there is a lot of
>>traffic and I
>> just want to see some examples of what is being dropped in that queue?
>>Is
>> there a regexp that would help limit it by DSCP markings or by queue?
>> 
>> Thanks,
>> John
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp