[j-nsp] J2320 CoS and QoS

[Nick Ryce]

Duly noted.  As its just 1 source range and 1 destination range ( both of which are ranges for backup devices ) this should work fine.

Nick

-----Original Message-----
From: Richmond, Jeff [mailto:Jeff.Richmond at frontiercorp.com]
Sent: 27 April 2010 14:07
To: Nick Ryce
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] J2320 CoS and QoS

Nick, the correct terminology would be a Behavior Aggregate (which is what you are doing with the Classifier on the interface) or a MultiField Classifier (MFC), which is what you are proposing with a Src/Dst filter. These work just fine together, but just remember that an MFC is processed after the BA and therefore takes precedence over it if there is a conflicting value.

Regards,
-Jeff

On Apr 27, 2010, at 1:28 AM, Nick Ryce wrote:

> Hi Guys,
>
> Is it possible to mix CoS and QoS per interface on a 2320 running 9.4?
>
> Current CoS configured as follows:-
>
> class-of-service {
>    forwarding-classes {
>        queue 0 best-effort;
>        queue 1 expedited-forwarding;
>        queue 2 assured-forwarding;
>        queue 3 network-control;
>    }
>    interfaces {
>        ge-* {
>            scheduler-map cos-lumison;
>            unit * {
>                classifiers {
>                    dscp default;
>                }
>            }
>        }
>    }
>    scheduler-maps {
>        cos-lumison {
>            forwarding-class network-control scheduler nc-scheduler;
>            forwarding-class expedited-forwarding scheduler voice-scheduler;
>            forwarding-class best-effort scheduler data-scheduler;
>            forwarding-class assured-forwarding scheduler assured-scheduler;
>        }
>    }
>    schedulers {
>        voice-scheduler {
>            transmit-rate percent 60;
>            buffer-size percent 60;
>            priority strict-high;
>        }
>        data-scheduler {
>            transmit-rate percent 25;
>            buffer-size percent 25;
>            priority low;
>        }
>        nc-scheduler {
>            transmit-rate percent 5;
>            buffer-size percent 5;
>            priority high;
>        }
>        assured-scheduler {
>            transmit-rate percent 10;
>            buffer-size percent 10;
>            priority low;
>        }
>    }
> }
>
> Customer would also like to use qos to prioritise backup traffic from a source range to a destination range.  Is it possible to then use a filter to prioritise the traffic from source to destination?
>
> Many Thanks
>
> Nick
>
> --
> Nick Ryce
> Network Engineer
> Lumison
> 08451199999
>
> P.S. do you love Lumison?  Why not take a moment and vote for us?
> http://bit.ly/Vote_Lumison
>
>
>
> --
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender. Any
> offers or quotation of service are subject to formal specification.
> Errors and omissions excepted.  Please note that any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Lumison.
> Finally, the recipient should check this email and any attachments for the
> presence of viruses.  Lumison accept no liability for any
> damage caused by any virus transmitted by this email.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp


--

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender. Any
offers or quotation of service are subject to formal specification.
Errors and omissions excepted.  Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Lumison.
Finally, the recipient should check this email and any attachments for the
presence of viruses.  Lumison accept no liability for any
damage caused by any virus transmitted by this email.