cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2890
Views
0
Helpful
4
Replies

QoS on NCS

BB7
Level 1
Level 1

Hello Experts,

 

I am trying to configure QoS on NCS router using the reference guide. It's a simple configuration with one class-map having one match condition and one policy-map.

 

RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# class-map ipprec5
RP/0/RP0/CPU0:router(config-cmap)# match precedence ipv4 5	
RP/0/RP0/CPU0:router(config-cmap)# exit

RP/0/RP0/CPU0:router(config)# policy-map policy1
RP/0/RP0/CPU0:router(config-pmap)# class ipprec5
RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 1000 mbps
RP/0/RP0/CPU0:router(config-pmap)# exit

RP/0/RP0/CPU0:router(config)# interface HundredGigabitEthernet  0/1/0/9
RP/0/RP0/CPU0:router(config-if)# service-policy input policy1

According to the link: https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/qos/b-ncs5500-qos-cli-reference/b-ncs5500-qos-cli-reference_chapter_01.html#wp1772137353, the ip precedence match condition is supported in ingress direction. But after commiting the above config I am getting the following errors

 

service-policy input policy5

!!% 'DNX_QOSEA' detected the 'warning' condition 'Unsupported action type for ingress.

 

Any help would be appreciated?

 

Thanks.

 

4 Replies 4

Hello

I have same problem, getting the same message while for me, I want to shape traffic over EVC.

is there some one who can help ?

thank you

Joseph W. Doherty
Hall of Fame
Hall of Fame
I'm unfamiliar with the NCS, but in general, you cannot have a class bandwidth statement within an ingress policy.

Hi all

 

I have the same problem and till now, I dont find the solution, let me explain the situation.

We have N540-24Z8Q2C-Mand ASR 920 into our Carrier Ethernet Network, we provide, E-line over EVC to customers for instance to interconnect their branch offices, and we need to shape traffic in egress to commited rate, this is working on ASR 920, but on NCS 540 I get below message 

!!% 'DNX_QOSEA' detected the 'warning' condition 'Unsupported match type for egress.'

 

Find below my configuration, thank you for your suggestions

Best regards

!
class-map match-any ANY-TRAFFIC
match cos 0 1 2 3 4 5 6 7
end-class-map
!
policy-map 1G
class ANY-TRAFFIC
shape average 10 mbps
!
class class-default
!
end-policy-map
!
!
interface GigabitEthernet0/0/0/10
mtu 9230
!
interface GigabitEthernet0/0/0/10.200 l2transport
encapsulation dot1q 200
mtu 9230
!
l2vpn
xconnect group FSLNK00002
p2p FSLNK00002
interface GigabitEthernet0/0/0/15.200
neighbor ipv4 172.31.4.5 pw-id 200
!
!
!

RP/0/RP0/CPU0:host-1-ncs540(config-subif)#commit show-error
Fri Nov 29 23:04:32.299 CET

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.
!! 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 GigabitEthernet0/0/0/10.200 l2transport
service-policy output 10M
!!% 'DNX_QOSEA' detected the 'warning' condition 'Unsupported match type for egress.'
!
end

RP/0/RP0/CPU0:host-1-ncs540(config-subif)#

 

 

As it appears you're matching all CoS, have your tried any other matching, like all IP Prec or just use the class-default with the shaper there?
Review Cisco Networking products for a $25 gift card