[c-nsp] IP precedence inside of a service policy

[Temkin, David]

Understood, and that helps ( I didn't realize I could set the IP TOS),
but that still leaves me with one burning question:

If I've got

Class-map match-all test1
  match ip tos 5
Class-map match-all test2
  match input-interface serial1/0

Policy-map NewMap
  class test1
    set ip precedence 5
  class test2
    priority 1000
  class class-default 
    bandwidth 20000
    set ip precedence 0
    random-detect prec-based


Will class test1 end up getting matched by the default class?  Everyone
has said no so far, and I'm inclined to believe that.  

So, how can I combine the ability to have dedicated QoS for certain
things while doing WRED (prec based) for everything else?  DSCP and
Precedence can be interchangeable (map to each other) - is there a
direct way to do that with the ToS byte?  Ie, does ToS byte X correspond
to precedence Y?



Thanks for any help...
-Dave



> -----Original Message-----
> From: Tantsura, Jeff [mailto:jeff.tantsura at capgemini.com] 
> Sent: Wednesday, August 25, 2004 5:52 AM
> To: Temkin, David
> Cc: cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] IP precedence inside of a service policy
> 
> 
> Take a look at
> 
> http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1829
> /products_
> feature_guide09186a00801a2c39.html
> 
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Temkin, David
> Sent: Wednesday, August 25, 2004 3:51 AM
> To: Glen Turner
> Cc: cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] IP precedence inside of a service policy
> 
> Hmm... My only issue is that there is no "input" interface as 
> it's locally generated (via xconnect) l2tpv3 traffic.  That 
> would work great for normal stuff though...
> 
> 
> > -----Original Message-----
> > From: Glen Turner [mailto:glen.turner at aarnet.edu.au]
> > Sent: Tuesday, August 24, 2004 8:20 PM
> > To: Temkin, David
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] IP precedence inside of a service policy
> >
> 
> > On Wed, 2004-08-25 at 04:05, Temkin, David wrote:
> > > This may sound silly, but if I'm applying the IP precedence
> > inside of
> > > a service policy but have a default class, how does it get
> > applied. 
> 
> > > Let's say I have:
> > >
> 
> > > !
> > > policy-map test
> > >   class test
> > >    set ip precedence 5
> > >   class test1
> > >    bandwidth 10000
> > >   class class-default
> > >    fair-queue
> > >    random-detect
> >
> 
> > I too have pondered this. My conclusion is that service policies are
> 
> > not recursive, so only one "class" clause is executed per packet.
> >
> 
> > However, you are allowed to have two service policies -- 
> one on input
> 
> > and one on output. So to re-work your example:
> >
> 
> >   class-map CS5
> >    match ip dscp cs5
> >
> 
> >   policy-map IN
> >    class TEST
> >     set ip dscp cs5
> >    class class-default
> >     set ip dscp default
> >
> 
> >   policy-map OUT
> >    class CS5
> >     bandwidth 10000
> >    class class-default
> >     fair-queue
> >     random-detect
> >
> 
> > I'm open to correction, as Cisco's documentation is rather poor, but
> 
> > this seems to fit the DiffServ QoS model that the Modular QoS is
> 
> > trying to implement.
> >
> 
> > --
> 
> > Glen Turner         Tel: (08) 8303 3936 or +61 8 8303 3936
> > Australian Academic & Research Network   www.aarnet.edu.au
> >
> 
> >
> 
> >
> 
> 
> IMPORTANT: The information contained in this email and/or its 
> attachments is confidential. If you are not the intended 
> recipient, please notify the sender immediately by reply and 
> immediately delete this message and all its attachments.  Any 
> review, use, reproduction, disclosure or dissemination of 
> this message or any attachment by an unintended recipient is 
> strictly prohibited.  Neither this message nor any attachment 
> is intended as or should be construed as an offer, 
> solicitation or recommendation to buy or sell any security or 
> other financial instrument.  Neither the sender, his or her 
> employer nor any of their respective affiliates makes any 
> warranties as to the completeness or accuracy of any of the 
> information contained herein or that this message or any of 
> its attachments is free of viruses.
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 
> Our name has changed.  Please update your address book to the 
> following format: "recipient at capgemini.com".
> 
> This message contains information that may be privileged or 
> confidential and is the property of the Capgemini Group. It 
> is intended only for the person to whom it is addressed. If 
> you are not the intended recipient,  you are not authorized 
> to read, print, retain, copy, disseminate,  distribute, or 
> use this message or any part thereof. If you receive this  
> message in error, please notify the sender immediately and 
> delete all  copies of this message.
> 
> 
>