[162919] in North American Network Operators' Group
Re: Per Site QOS policy with Cisco IOS-XE
daemon@ATHENA.MIT.EDU (Tyler Haske)
Wed May 8 10:03:04 2013
In-Reply-To: <CAEVhvj+00b8i2EGmzF81NPcxQt9Ffx=sqWVase_KSFzYC83g2Q@mail.gmail.com>
From: Tyler Haske <tyler.haske@gmail.com>
Date: Wed, 8 May 2013 10:02:07 -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
If you want to prevent a PE router from deciding which ingress packets to
drop, the only plan is to send packets to spoke sites at or below the spoke
line-rate. The only good way to do that is shaping on the hub router.
policy-map parent_shaper
class class-default
shape average 100000000 < --- 100Mbps parent shaper.
service-policy site_shaper
policy-map site_shaper
class t1_site
shape average 1536000
service-policy qos_global
class multilink_site
shape average 3072000
service-policy qos_global
class class-default
service-policy qos_global
policy-map qos_global
... whatever you typically use here....
Tyler Haske
On Wed, May 1, 2013 at 5:03 PM, Wes Tribble <westribble@gmail.com> wrote:
> I have a question for the QOS gurus out there.
>
> We are having some problems with packet loss for our
> smaller MPLS locations. This packet loss is due to the large speed
> differential on our Hub site(150mb/s) in comparison the the branch office
> locations(single T-1 to 4.5mb/s multilinks). This packet loss only seems
> to impact really bursty applications like our Web Proxy. I have been
> around and around with WindStream to give me some extra buffer or enable
> random early detection on the smaller interfaces in my MPLS network. So
> far they are unwilling to do a custom policy and none of their standard
> policies have enough buffer to handle the bursts. They do FIFO tail drop
> in every queue, so I can=92t even choose a policy that has WRED implement=
ed.
>
