cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

7999
Views
0
Helpful
1
Replies
Highlighted
Beginner

Explanation of CIR, BE, and BC when defining policy maps?

> Committed Burst is a soft cap. Traffic past the committed threshold is only dropped if there isn't available bandwidth.

> Extended Burst is a hard cap. Traffic past the extended threshold is always dropped.

> CIR this sets total bandwidth allowed on interface.

Correct so far?

So, CIR sets the bandwidth total for that circuit, correct? This is in bits, btw.

Committed Burst is in bytes. That means that if we hit a bottle neck everything up to the roughly 60 megabits over the CIR threshold is guaranteed. The Extended Burst is set to roughly 120 megabits. This means that if they ever go 120 megabits over their CIR threshold, any and all data will be dropped.

Do I have the right idea here?

Or is BC and BE not in addition TO overall bandwidth, but only take affect in case OF bandwidth issues?

Example:

policy-map police-300mb
  class access-match
  police cir 300000000 bc 7812500 be 15625000 conform-action transmit exceed-action drop violate-act

1 REPLY 1
Beginner

Re: Explanation of CIR, BE, and BC when defining policy maps?

Bump

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards