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

[Temkin, David]

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.