NCS-5501-SE erros is 'DPA_QOSEA' detected the 'warning' condition

[Yang Li]

version is ncs5500-xr-7.1.2 version=7.1.2 

Mon Nov 3 05:46:46.878 UTC
Node Type State Config state
--------------------------------------------------------------------------------
0/RP0/CPU0 NCS-5501-SE(Active) IOS XR RUN NSHUT
0/RP0/NPU0 Slice UP
0/FT0 NCS-1RU-FAN-RV OPERATIONAL NSHUT
0/FT1 NCS-1RU-FAN-RV OPERATIONAL NSHUT
0/PM0 NCS-1100W-ACRV OPERATIONAL NSHUT

----------------------qos------------------

prefix-set RESERVED_PREFIX
103.203.133.0/30
end-set

ipv4 access-list RESERVED_ACL
10 permit 103.203.133.0/30

class-map match-any CLASS_RESERVED
match access-group ipv4 RESERVED_ACL

policy-map Member_POLICY
class CLASS_RESERVED
bandwidth percent 4
class class-default

policy-map VIP_POLICY
class class-default
service-policy Member_POLICY

interface Bundle-Ether5.699
service-policy output VIP_POLICY

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

[smilstea]

Do you have this command configured and the box reloaded after enabling?

hw-module profile qos hqos-enable

Thanks,

Sam

[Yang Li]

yes  It has been enabled and restarted.

It still cannot match the IP address in the class-map and then call it.

!
!
hw-module profile qos hqos-enable

ipv4 access-list RESERVED_ACL
10 permit 103.203.133.0/30

class-map match-any CLASS_RESERVED
match access-group ipv4 RESERVED_ACL

policy-map Member_POLICY
class CLASS_RESERVED
bandwidth percent 4
class class-default

policy-map VIP_POLICY
class class-default
service-policy Member_POLICY

interface Bundle-Ether5.699
service-policy output VIP_POLICY

[Yang Li]

yes  It has been enabled and restarted.

It still cannot match the IP address in the class-map and then call it.

!
!
hw-module profile qos hqos-enable

ipv4 access-list RESERVED_ACL
10 permit 103.203.133.0/30

class-map match-any CLASS_RESERVED
match access-group ipv4 RESERVED_ACL

policy-map Member_POLICY
class CLASS_RESERVED
bandwidth percent 4
class class-default

policy-map VIP_POLICY
class class-default
service-policy Member_POLICY

interface Bundle-Ether5.699
service-policy output VIP_POLICY

[smilstea]

ACL match on egress is not supported.

"The match access-group command is supported only in the ingress direction"

https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/qos/79x/b-qos-cg-ncs5500-79x/config-mod-qos-service-packet-classification.html

[Yang Li]

Hi Mr Smilstea,

Thanks for you update ~

There is an interesting question

interface Bundle-Ether200  I used two 10G ports for binding. The size is 20GB

RP/0/RP0/CPU0:A#show interfaces bundle-ether 200 brief
Thu Nov 6 07:13:16.762 UTC

Intf Intf LineP Encap MTU BW
Name State State Type (byte) (Kbps)
--------------------------------------------------------------------------------
BE200 up up ARPA 1514 20000000

When the policy rate was set to 11G or 12G, which is greater than the physical interface's 10G, the policy call interface could not be routed, and the same issue occurred with the shape method.

I don't know why you can explain it to me?

-----------------config----------------------------

The following configuration strategy can only be invoked if the size is less than 10GB.

ipv4 access-list CDN-ACL
10 permit ipv4 any 103.203.132.0 0.0.0.255
20 permit ipv4 103.203.132.0 0.0.0.255 any
!
ipv4 access-list OFFICE-ACL
10 permit ipv4 any 103.203.133.0 0.0.0.3
20 permit ipv4 103.203.133.0 0.0.0.3 any
!

class-map match-any CLASS-CDN
match access-group ipv4 CDN-ACL
end-class-map

class-map match-any CLASS-OFFICE
match access-group ipv4 OFFICE-ACL
end-class-map

policy-map PMARK_TRaffic
class CLASS-OFFICE
set traffic-class 2
!
class CLASS-CDN
set traffic-class 1
!
class class-default
!
end-policy-map

class-map match-any CTraffic_1
match traffic-class 1
end-class-map
!
class-map match-any CTraffic_2
match traffic-class 2
end-class-map

!
policy-map LIMIT-UPSTREAM
class CLASS-CDN
police rate 5 gbps
!
!
class CLASS-OFFICE
police rate 1 gbps
!
!
class class-default
police rate 4 gbps
!
!
policy-map SHAPE-UPSTREAM
class CLASS-CDN
shape average 3 gbps
!
class CLASS-OFFICE
shape average 1 gbps
!
class class-default
shape average 6 gbps
!
end-policy-map

!
policy-map SHAPE-UPSTREAM
class CTraffic_1
shape average 1650 mbps
!
class CTraffic_2
shape average 350 mbps
!
class class-default
shape average 8 gbps
!
end-policy-map
!

!

interface Bundle-Ether200
service-policy input LIMIT-UPSTREAM
service-policy output SHAPE-UPSTREAM

[smilstea · Accepted solution]

QoS is replicated, so if you have 1x10gbe you can set a 5gb policer to limit to that much traffic, if you have 2x10gbe then you have 20gb in aggragate so if you apply a 5gb policer then each port is policed at 5gb not 5gb total. So the biggest policer you can have is still 10gb for any number of ports that are 10gb in a bundle. You will have to influence inbound or outboard load-balancing so that the consumer isnt getting 2x, 3x, etc the traffic rate they should be.

Sam

[Yang Li]

thank you