[cisco-bba] [cisco-nas] Support for "percent" directive in per-session QoS

[David Freedman]

Many thanks, I shall give this a try, as with many new features these days documentation is sparse on useful stuff such as this :)


------------------------------------------------
David Freedman
Group Network Engineering 
Claranet Limited
http://www.clara.net



-----Original Message-----
From: Ben Steele [mailto:ben at internode.com.au]
Sent: Thu 1/10/2008 00:10
To: David Freedman
Cc: cisco-nas at puck.nether.net; cisco-bba at puck.nether.net
Subject: Re: [cisco-nas] Support for "percent" directive in per-session QoS
 
They sure are, they will just reference the bandwidth you specify in 
your radius av-pair, so if you set priority percent 10 to a class you 
have put 435Kb in radius for it will give up to 43Kb of LLQ to that 
class, that radius bandwidth statement is like the equivalent of a 
bandwidth statement under a normal physical interface, it now becomes 
the global bandwidth for that virtual-interface that the router 
recognises, you just have to make sure you do shape it properly though 
otherwise your QoS won't be very affective.

Cheers

David Freedman wrote:
>
> Thats great, the percentage I was referring to though was in the LLQ 
> (as in priority percent and bandwidth percent) are these possible?
>
> Dave.
>
> ------------------------------------------------
> David Freedman
> Group Network Engineering
> Claranet Limited
> http://www.clara.net
>
>
>
> -----Original Message-----
> From: Ben Steele [mailto:ben at internode.com.au]
> Sent: Wed 1/9/2008 23:53
> To: David Freedman
> Cc: cisco-nas at puck.nether.net; cisco-bba at puck.nether.net
> Subject: Re: [cisco-nas] Support for "percent" directive in 
> per-session QoS
>
> You specify your bandwidth via a radius av-pair, say for example you
> have a 512kb downstream ADSL service landing on your LNS you would have
> a line like:
>
> cisco-avpair = "lcp:interface-config#1=bandwidth 435"     (435kb
> allowing for a 15% dsl overhead)
> cisco-avpair = "lcp:interface-config#2=service-policy output SHAPED-QOS"
>
> Then using the shape average percent command the LNS would shape the
> user to that speed, you can then apply your actual QoS policy under
> that, like so:
>
> policy-map SHAPED-QOS
>  class class-default
>   shape average percent 100 50 ms
>   service-policy QOS
>
> This would apply the policy "QOS" to the shaped interface, I hope that
> is what you were after, and yes it does work quite well with
> priority(LLQ), the most important thing is to shape it to the correct
> speed, when the link is being saturated and you do a "sh policy-map int
> xx" you want to see it reporting that it is being shaped.
>
> Cheers
>
> Ben
>
>
> David Freedman wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I believe this is possible reading the documentation at
> > 
> http://www.cisco.com/en/US/products/ps6566/products_feature_guide09186a0080610dad.html
> >
> > there is mention of it, but the question I want to ask is :
> >
> > how does it know what the available bandwidth is such to be able to
> > calculate the percentage?
> >
> > I mean, with a standard CBWFQ attached to an interface, it derrives this
> > from the interface bandwidth, but for vaccess QoS we are required to
> > nest the CBWFQ under a shaper, so does the percentage directive
> > use the shape average rate of this shaper?
> >
> > Does anybody use this directive (interested for those whom use it for a
> > priority queue) and does it work?
> >
> > Many thanks,
> >
> >
> > - --
> > David Freedman
> > Group Network Engineering
> > Claranet Limited
> > http://www.clara.net
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2.2 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFHhRGktFWeqpgEZrIRAh4TAKDM9Kl+ikOSt8j19/9GfCDaTG8EegCgpYBW
> > AwNWZohx+5dbeFZ3pQkDr7A=
> > =Rn2w
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > cisco-nas mailing list
> > cisco-nas at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nas
> >  
>
>

 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-bba/attachments/20080110/8bbeb92f/attachment-0001.html