[j-nsp] mpls traffic priority when P router

[Craig Pierantozzi]

You can also use a Behavior Aggregate classifier to 
classify on ingress and rewrite on egress.  You do 
this in the 'class-of-service' section and you 
set up your forwarding classes and schedulers and then
classify using EXP bits.  You can use the default which
is:

user at R1> show class-of-service classifier type exp
Classifier: exp-default, Code point type: exp, Index: 7
  Code point         Forwarding class                    Loss priority
  000                best-effort                         low
  001                best-effort                         high
  010                expedited-forwarding                low
  011                expedited-forwarding                high
  100                assured-forwarding                  low
  101                assured-forwarding                  high
  110                network-control                     low
  111                network-control                     high

...or set up your own custom classifier.

http://www.juniper.net/techpubs/software/junos/junos70/swconfig70-interfaces/html/cos-config10.html

-Craig

* Thus spake Andrew Ramsey (akramsey at juniper.net):

> Hi Hristo,
> 
> You could create a filter that matched on MPLS exp bits.
> 
> Dig in here and see if it helps:
> 
> lab at M20-R27# set firewall family mpls filter ?      
> Possible completions:
>   <filter-name>        Filter name
>   match-mpls           Filter name
> 
> Andy
> 
> > -----Original Message-----
> > From: juniper-nsp-bounces at puck.nether.net 
> > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> > Hristo Todorov
> > Sent: Wednesday, March 23, 2005 12:30 PM
> > To: juniper-nsp at puck.nether.net
> > Subject: [j-nsp] mpls traffic priority when P router
> > 
> > 
> > Hello Everybody.
> > 
> > I have the following setup
> > 
> > CE----PE1--------P--------PE2-----CE
> >      Cisco    Juniper    Cisco
> >      7200      M5         7200
> > 
> > 
> > Here M5 is P and connecton between P and PE2 is limited. I 
> > have normal traffic and mpls traffic. I need to give priority 
> > to mpls traffic leaving the router and leave the rest as is.
> >  
> > The mpls is configured with ldp on the cisco side
> > 
> > mpls label protocol ldp
> > mpls ldp logging neighbor-changes
> > no mpls traffic-eng auto-bw timers frequency 0
> > tag-switching tdp router-id Loopback0 force
> > 
> > Problem is i dont seem to be able to classify the traffic 
> > with the filter. I matched the ips for the l2transport route 
> > on the ciscos  mpls l2transport route x.x.x.x 200 
> > but the counter does not seem to count. So i'm not matching 
> > traffic. I also don't have options to match mpls as a protocol.
> > 
> > The following direction is needed PE1  via ge unit , PE2 via atm unit.
> > 
> > Sheduler and Scheduler maps for the forwaring-class that need 
> > to set priority are already set. 
> > Thanks for your time.
> > 
> > -- 
> > Cyberly yours,
> > Hristo Todorov
> > NOC Operator
> > Orbitel, Inc.
> > tel.: +359 2 400 4860, +359 2 400 4737 
> > fax: +359 2 400 4744
> > 
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net 
> > http://puck.nether.net/mailman/listinfo/junipe> r-nsp
> > 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp