Policy rate problem in NCS5500

[j.restaino]

I am having problems when trying to limit the bandwidth of different services on sub interfaces in IOS Xr in NCS5500.

I recently buy 2 NCS5508 and 2 NCS5504 routers and i need limit my customers bandwith.
I have this configuration in a ASR9k and works properly.

In ASR9k

policy-map Policy_10000161
class class-default
police rate 1575 mbps
!
!
end-policy-map
!
interface Bundle-Ether1100.10000161
description Customer X
service-policy input Policy_10000161
service-policy output Policy_10000161
vrf Customer
ipv4 address 10.10.10.181 255.255.255.252
encapsulation dot1q 161

But in NCS5500 when i try to applied the same policy-map in the output direction in a subinterface, the configuration is rejected

RP/0/RP0/CPU0:router(config)#interface HundredGigE0/0/0/0.10000161
RP/0/RP0/CPU0:router(config-subif)# service-policy output Policy_10000161
RP/0/RP0/CPU0:router(config-subif)#commit
Sun Dec 12 11:52:03.265 UTC

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:router(config-subif)#sho conf fail
Sun Dec 12 11:52:09.429 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.

interface HundredGigE0/0/0/0.10000161
service-policy output Policy_10000161
!!% 'DPA_QOSEA' detected the 'warning' condition 'Unsupported action type for egress'
!

I will appreciate if someone could help me.

Regards

[tkarnani · Accepted solution]

This router NCS5500 has more restrictions vs asr9k

on this router policing is only supported on ingress

https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/qos/73x/b-qos-cg-ncs5500-73x/configure-qos-congestion-avoidance.html

[j.restaino]

Thanks for your fast response, i will implement traffic shape despite that this is not what i want to do. I hope that this feature will be include in a near future.

Regards

[smilstea]

This is a limitation of the ASIC not the software.

However, policing and shaping are not really *that* different, policing does allow for bursting, and shaping allows burst too. The methods they use to accomplish this is slightly different though and accuracy of the shaper will vary.

You could have a shaper with no burst on egress.

https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/qos/72x/b-qos-cg-ncs5500-72x/b-qos-cg-ncs5500-72x_chapter_0100.html

Sam

[j.restaino]

Thanks for your response Sam, but now i have a new problem with the policy shapping. When i try to apply in a subinterface i have the next error.

policy-map Shape_10000202
 class class-default
  shape average 31500 mbps
 !
end-policy-map
!
interface Bundle-Ether 1201.10000202
 service-policy output Shape_10000202

router(config-subif)#commit

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors

router(config-subif)#sho configuration failed
Wed Jan 4 13:30:26.810 GMT+3
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.

!!% 'DPA_QOSEA' detected the 'warning' condition 'QoS is supported on sub-interface(s) only in Hierarchical QoS Mode.'

The only thing that i want to do is limit all the traffic in a subinterface, so is very strange for me use HQoS.

i will try with this config

policy-map Shape_10000202_child
class class-default
shape average 31500 mbps
!
end-policy-map

policy-map Shape_10000202
class class-default
service-policy Shape_10000202_child
!
end-policy-map

But to enable HQoS i need to made a hw-module reload on production routers, so i prefer to avoid this option if it´s possible.

Thanks in advance for your help

[smilstea · Accepted solution]

This is a limitation of the ASIC, there is no workaround for this and indeed you will have to enable the hw-module profile and reload the router to get QoS to work on sub-interface.

Sam

[j.restaino]

Ok, thanks for your fast response.

Regards
José