[162935] in North American Network Operators' Group
Re: Per Site QOS policy with Cisco IOS-XE
daemon@ATHENA.MIT.EDU (Tyler Haske)
Thu May 9 09:34:50 2013
In-Reply-To: <CAEVhvjJWBzn-cKxf83A72d=_8o8mOMWDD-eNry5OPQppG_E=eQ@mail.gmail.com>
From: Tyler Haske <tyler.haske@gmail.com>
Date: Thu, 9 May 2013 09:33:45 -0400
To: Wes Tribble <westribble@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Wes,
The earlier policy doesn't use bandwidth commands, hence, it doesn't
*subscribe* anything. The only thing it does is ensures that individual
sites do not exceed their shaped rate. You could add bandwidth statements
if you wanted to ensure a certain site always is guaranteed a certain
amount of bandwidth from the parent shaper. You can't oversubscribe with
the bandwidth command.
policy-map parent_shaper
class class-default
shape average 100000000
service-policy site_shaper
policy-map site_shaper
class t1_site
shape average 1536000
bandwidth percent 1
service-policy qos_global
class multilink_site
shape average 3072000
bandwidth percent 2
service-policy qos_global
class class-default
bandwidth percent 97
service-policy qos_global
policy-map qos_global
! ... whatever you want here.
This would make sure that large sites don't stare out small spoke sites for
bandwidth.
On Thu, May 9, 2013 at 8:58 AM, Wes Tribble <westribble@gmail.com> wrote:
> Thanks for the information Tyler, I will have to play around with that
> kind of policy in my lab. What would you suggest if you are
> oversubscribing the interface? With the child policy inheriting the
> bandwith of the parent shaper, wouldn't I run out of bandwidth allocation
> before I built all the shapers for all of my 29 sites?
>
