QoS POLICE CIR/CBWFQ

[Just Kennie]

Hi All,

Please help with the solution. Below are the objectives.

- I want to do two rate policing on my PE for client. (CIR = 512000, PIR = 102400)

- On this traffic, I want to be able to do LLQ,CBWFQ,WRED e.t.c

- I want this to be in output direction to my client.

I came up with the following config..

policy-map PARENT

class class-default

  shape average 1024000

   police cir 512000 pir 1024000

  service-policy GBA_CORE_OUT

policy-map GBA_CORE_OUT

class GBA_CORE_CONTROL

  bandwidth percent 4

  random-detect dscp-based

class GBA_CORE_VOICE

  priority percent 10

class GBA_CORE_VIDEO

  priority percent 20

class GBA_CORE_INTERACTIVE

  bandwidth percent 35

  random-detect dscp-based

class GBA_CORE_STANDARD

  bandwidth percent 9

  random-detect dscp-based

class GBA_CORE_SCAVENGERS

  bandwidth percent 1

  random-detect dscp-based

class GBA_CORE_BUSINESS

  bandwidth percent 20

  random-detect dscp-based

interface FastEthernet0/0.1

service-policy output PARENT

I decided to include shape statement in the parent policy map because it wont allow me to do nesting without it.

Techically, will this configuration achieve the objective ??

Whats the implication of using shaping and policing on the same nested policy map ???

Please help look into this!

[acampbell]

Hi,

The one issue I see here I think you answerd yourself.

You invoked shaping and in my view correctly on your bearer cct.

This allows you to nest your QOS service policy.

I think you should remove the policing statement from the bearer as you only want to use 1 method of controlling

the bandwidth.

Policing is agressive where as shaping is more polite

Here is a nice wee link for you to look at

http://www.cisco.com/en/US/partner/tech/tk543/tk545/technologies_tech_note09186a00800a3a25.shtml

HTH

Alex

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

"Techically, will this configuration achieve the objective ??"

Don't believe it will.  The policer will engage before the shaper, since it set for 512k vs shaper's 1024k.  Policers also don't queue they just drop (everything).

Remove the policer as Alex suggests.