[rbak-nsp] Basic QoS subscriber setup

[jim at scusting.com]

So if I wanted to use pq rather than policing I would need to apply 2 
QoS profiles - a metering one to mark priorities based on the class, and 
then the pq to do the queuing?

I dont believe you can apply 2 QoS profiles to a subscriber so I guess 
the way to do it is apply the metering profile that does the priority 
marking on the ingress port, and apply tge pq profile on the Subscriber?

Thanks,

Jim.

Tanan Satayapiwat wrote:
> Hi Jim,
> Perhaps there are many other different ways but what I can think of is you can mark priority on all incoming ports.
> policy access-list qostest
>   seq 10 permit tcp host 0.0.0.0 eq www any class class-1
>   seq 20 permit tcp 213.199.144.0 0.0.15.255 any class class-2
>   seq 30 permit ip any any class default
>
> Qos policy abc policing
>  access-group qostest local
>    class class-1
>      mark priority 1
>
> Port eth 1/1 (incoming port)
>  qos policy policing abc
>
> At least I see it work with one of my customers.
>
> Cheers,
> Tanan
>
>
> -----Original Message-----
> From: redback-nsp-bounces at puck.nether.net [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of jim at scusting.com
> Sent: Tuesday, April 27, 2010 1:14 PM
> To: redback-nsp at puck.nether.net
> Subject: [rbak-nsp] Basic QoS subscriber setup
>
> Hi,
>
> I'm trying to test some basic QoS on a subscriber circuit and I'm a little stuck.  I want to prioritise certain traffic types eg VOIP > IPTV  > HTTP > Other.  I have the following so far:
>
> -----
> qos policy testpq pq
>  num-queues 4
>  queue 0 rate 3250 burst 40000
>  queue 1 rate 250 burst 40000
>  queue 2 rate 250 burst 40000
>  queue 3 rate 250 burst 40000
>
> context testcontext
>  policy access-list qostest
>   seq 10 permit tcp host 0.0.0.0 eq www any class class-1
>   seq 20 permit tcp 213.199.144.0 0.0.15.255 any class class-2
>   seq 30 permit ip any any class default
>
>  subscriber name test at blah.com
>    qos policy queuing testpq
>    rate circuit out 4000 burst 10
> -----
>
> How do I classify traffic into different priority queues?  I will eventually set the DSCP value before it hits the SE800 and require the SE800 to map DSCP to priority somehow, but right now I want to have the Redback use different priorities based on traffic properties such as the source or the port.  I can see how this is done with a metering profile as you can apply an access-group to that to map traffic to classes.
>
> How do I achieve this with pq QoS as I dont want to set specific bandwidths for different traffic types as with metering/policing but use queues and priorities?  I'm sure I'm missing something obvious or got the wrong end of the stick.
>
> Thanks.
>
> Jim.
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>