[j-nsp] J2320 CoS and QoS

[Nick Ryce]

Hi Arda,

Thats great.  I was looking at using this but was not sure if the CoS settings would override the MF classifier but looking at the config it makes sense now.

Nick

From: Arda Balkanay [mailto:ardabalkanay at gmail.com]
Sent: 27 April 2010 11:15
To: Nick Ryce
Subject: Re: [j-nsp] J2320 CoS and QoS

you can use multifield (MF) classifiers by matching source-destination characteristics of the traffic with a firewall filter and assign that traffic to a specific forwarding class.

firewall family inet filter MF-TEST
term T1 {
    from {
        <anything to match traffic>
    }
    then {
        forwarding-class expedited-forwarding;
        accept;
    }
}

use the firewall filter in interface
interfaces ge-0/0/0
unit 0 {
    ...
    family inet {
        filter {
            input MF-TEST

        }
        address ...
    }
}

you already have schedulers per forwarding class...
so matching backup traffic and assigning it to best-effort might help in your case.

Cheers
Arda


On Tue, Apr 27, 2010 at 9:28 AM, Nick Ryce <Nick.Ryce at lumison.net<mailto:Nick.Ryce at lumison.net>> 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<mailto: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.