C892, 15.3(3)M5, QoS Allowed CIR range

[MATTHIAS SCHAERER]

Hi I'm trying to apply the following QoS config:

policy-map PM-L2-OUT
description LEVEL2 Out Policy
class CM-NET-CONTROL
bandwidth percent 20
set mpls experimental topmost 6
!
class CM-QG3
bandwidth percent 20
set mpls experimental topmost 3
!
class CM-QG1
bandwidth percent 50
set mpls experimental topmost 1
!
class class-default
random-detect
queue-limit 300 ms
set mpls experimental topmost 0
!
policy-map PM-CORE-L1-OUT
description LEVEL1 Out Policy
class CM-QG5
priority level 2
police rate percent 10
!
set mpls experimental topmost 5
!
class class-default
service-policy PM-L2-OUT
shape average percent 100
!
interface GigabitEthernet0
bandwidth 200000

When I try to apply the service policy to Gig0 the router complains:

router1(config-if)#service-policy output PM-CORE-L1-OUT
Configured Percent results in CIR out of range. Allowed CIR range is 1000-154400000.
The present CIR value is 200000000

It looks a bit like the max-reserved-bandwith thing, however that does not exist anymore in IOS 15.3. I tried it with real bandwith values in the policy-map, no success either. Is there a numeric upper limit for a shaper, is this box dependent, or is there another possibility to get this running? I have not found any clear explanation or even better a solution to my problem.

[Georg Pauwen]

Hello,

post the full config.

class CM-QG5

does not exist in the partial config you posted...

[MATTHIAS SCHAERER]

Hi Georg

I basically match to QoS-groups (QG...) that were set on the input interfaces with matching of PHBs. But that does not really add valuable information to the question I have. I asked for the shaper, not for the marker. And to keep the output short I omitted the class-maps.

Kind regards

Mat

[Georg Pauwen]

Hello,

the reason I am asking for the full configuration is so I can lab this with different IOS versions and on different platforms. I want to see if it is IOS and/or platform related.

You can post the full config and take out any sensitive information such as public IP addresses and username/passwords, etc.

[Georg Pauwen]

Hello,

either way, I entered your config in 15.6(2)T, and got no errors. The 'show policy-map output is below, can you post the equivalent of your output ?

Router#sh policy-map
Policy Map PM-L2-OUT
Class CM-NET-CONTROL
bandwidth 20 (%)
set mpls experimental topmost 6
Class CM-QG1
bandwidth 50 (%)
set mpls experimental topmost 1
Class CM-QG3
bandwidth 20 (%)
set mpls experimental topmost 3
Class class-default
msec wred, exponential weight 9

class min-threshold max-threshold mark-probablity
----------------------------------------------------------
0 - - 1/10
1 - - 1/10
2 - - 1/10
3 - - 1/10
4 - - 1/10
5 - - 1/10
6 - - 1/10
7 - - 1/10
queue-limit 300 ms
set mpls experimental topmost 0

Policy Map PM-CORE-L1-OUT
Class CM-QG5
priority level 2
police rate percent 10
conform-action transmit
exceed-action drop
set mpls experimental topmost 6
Class class-default
Average Rate Traffic Shaping
cir 100%
service-policy PM-L2-OUT

Router#

[MATTHIAS SCHAERER]

Hi

the error only pops up when I try to apply the policy-map to a Gig Interface with a configured BW of 200000 kbps. The policy map as such works perfectly for scenarios with lower bandwidths. 

Here's the config including the class-maps:

class-map match-any CM-NET-CONTROL
description matches Routing Protocols, BFD and LDP
match dscp cs6
match mpls experimental topmost 6
match qos-group 6
class-map match-any CM-QG5
match qos-group 5
class-map match-any CM-QG3
match qos-group 3
class-map match-any CM-QG1
match qos-group 1
!
policy-map PM-L2-OUT
description LEVEL2 Out Policy
class CM-NET-CONTROL
bandwidth percent 20
set mpls experimental topmost 6
!
class CM-QG3
bandwidth percent 20
set mpls experimental topmost 3
!
class CM-QG1
bandwidth percent 50
set mpls experimental topmost 1
!
class class-default
random-detect
queue-limit 300 ms
set mpls experimental topmost 0
!
policy-map PM-CORE-L1-OUT
description LEVEL1 Out Policy
class CM-QG5
priority level 2
police rate percent 10
!
set mpls experimental topmost 5
!
class class-default
service-policy PM-L2-OUT
shape average percent 100
!
!
interface GigabitEthernet0
bandwidth 200000
service-policy output PM-CORE-L1-OUT

[paul driver]

Hello

Instead of BW percent try accommodating whats is available on the Bw

class CM-NET-CONTROL
bandwidth remaining percent 20

class CM-QG3
bandwidth remaining percent 20

class CM-QG1
bandwidth remaining percent 50

[MATTHIAS SCHAERER]

Hi

As I said in an answer before the policy-map works fine with lower bandwidths. It's the shaper that seems to cause the issue. I have set up a policy-map with only a shaper and get the same error:

policy-map PM-TEST
 class class-default
   shape average percent 100

interface GigabitEthernet0
 bandwidth 200000
 service-policy output PM-TEST

-> Configured Percent results in CIR out of range. Allowed CIR range is 1000-154400000.
The present CIR value is 200000000

The actual CIR value and the allowed CIR range look like 100%/75%. So that's why I think it might have something in common with the 75% rule (max-reserved-bandwidth). But I have not found any documentation that gives me details on my situation.

[paul driver]

Hello

It does seem to suggest this is the case - 0.25 x200000 =150000
One way to check would to look at the queueing on the interface and possibly change the default

show queueing interface x/x | Av

int x/x
max-reserved-bandwidth 90
end

Also suggest aply some fair queueing to the class class default
policy-map PM-L2-OUT
class class-default
fair-queue

[MATTHIAS SCHAERER]

Paul

As I said before the max-reserved-bandwidth command has been deprecated since IOS 15.0 or 15.1. So no possibility to use that one. The fair-queue is a good hint, I'm sure that I had it in a previous version, I have to check why I removed it.

Kind regards

Mat

[Georg Pauwen]

I wonder if it is platform related, the 892 throughput is relatively low. What if you set the bandwidth to 275000 ? If it is related to the max reserved bandwidth, the error shouldn't appear...

[MATTHIAS SCHAERER]

Cool idea, however it seems to be hardware related:

router(config)#int g0
router(config-if)#band 266666
router(config-if)#service-policy output PM-TEST
Configured Percent results in CIR out of range. Allowed CIR range is 1000-154400000.
The present CIR value is 266666000

[Georg Pauwen]

Hello,

I think it is a hardware limitation. On the 800 series, you can shape the average to a maximum value of 154400000

800(config-pmap-c)#shape average ?
<8000-154400000>

On a higher end router, the limit is1000000000:

Router(config-pmap-c)#shape average ?
<1000-1000000000>