[j-nsp] Juniper QoS (LLQ)

[Jeff Richmond]

Be aware though that COS is very router and interface specific, so while a generic example like this will work in most cases, it won't work in all. For example, with some PICs you cannot have more than one med-high+ priority:

[edit class-of-service interfaces]
  'ge-5/1/0'
    More than one scheduler is configured as "strict-high" or "high" or "medium-high" in SCHED-MAP for ge-5/1/0. Ifd ge-5/1/0 supports only one scheduler with "strict-high" or "high" or "medium-high".
error: configuration check-out failed

This is for an 8-port GE-IQ PIC in an M320, btw.

-Jeff


On Feb 4, 2011, at 9:22 AM, Matthew Tighe wrote:

> Depending on your hardware you can have up to 16 forwarding classes. I wrote
> a very basic 3 class example here (Network Control, Expedited Forwarding,
> and BE) to get you started. Network Control is your control plane protocols.
> There are a lot more options than what is here. I would recommend checking
> out the CoS documentation (
> http://www.juniper.net/techpubs/en_US/junos10.4/information-products/topic-collections/nce/qos-cos-overview/index.html)
> but
> the basic steps are:
> 
> 1. Create your forwarding classes
> 
> [edit class-of-service]
> set forwarding-class queue 0 BE
> set forwarding-class queue 2 EF
> set forwarding-class queue 3 NC
> 
> 2. Create the schedulers for each class
> 
> [edit class-of-service schedulers]
> 
> set sched-BE transmit-rate percent <XX>
> set sched-BE buffer-size percent <XX>
> set sched-BE priority low
> 
> set sched-EF transmit-rate percent <XX>
> set sched-EF buffer-size percent <XX>
> set sched-EF priority high
> 
> set sched-NC transmit-rate percent 5
> set sched-NC buffer-size percent 5
> set sched-NC priority strict-high
> 
> (5 percent is the default for network control on JunOS 10)
> 
> 3. Map the schedulers to each forwarding class:
> 
> [edit class-of-service scheduler-maps]
> 
> set sched-map-llq forwarding-class BE scheduler sched-BE
> set sched-map-llq forwarding-class EF scheduler sched-EF
> set sched-map-llq forwarding-class NC scheduler sched-NC
> 
> 4. Apply scheduler map to the interface:
> 
> [edit class-of-service interfaces]
> 
> set <interface> scheduler-map sched-map-llq
> 
> ---
> In your case you would create additional forwarding classes for each of your
> BE queues.
> 
> HTH,
> Matt
> 
> 
> On Mon, Jan 31, 2011 at 12:51 AM, Vlad Ion <vlad.thoth at gmail.com> wrote:
> 
>> Hi,
>> 
>> Can anyone lend a hand with a sample configuration of QoS on Juniper? I am
>> trying to have something really close to an existing Cisco deployment of
>> LLQ
>> with 1 PQ for VoIP and routing protocols (OSPF/IS-IS, BGP, LDP, RSVP), 3
>> CBWFQ classes (OAM, Services, IPSec VPNs) and a default class with
>> everything that was not included in the previous classes.
>> 
>> Thanks in advance,
>> Vlad
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> 
> 
> 
> 
> -- 
> Matthew Tighe
> matthew.e.tighe at gmail.com
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp