We try to establish easy to use policy-map on NCS 540 for business customers. Form the policy we just need to shape traffic in the egress direction. We would like to shape it overall QoS queues. Inside XR world (ASR9k) we use class class-default which catch-all queues. On the NCS540 class, class-default catches only non-marked traffic. This behavior complicates the structure of policy-map if we will like to shape traffic overall queues.
On ASR egress policy looks like this:
!
policy-map BUSINESS-Q2-2M-OUT
class class-default
shape average 2 mbps
!
We would like to find an equivalent for the ASR9k policy map on NCS540.
Right now we are using this policy on NCS540:
class-map match-any TRAFFICCLASS-Q2-OUT
match traffic-class 2
end-class-map
!
policy-map BUSINESS-Q2-2M-OUT
class TRAFFICCLASS-Q2-OUT
shape average 2 mbps
!
class class-default
!
end-policy-map
This policy-map is fine if the traffic is marked right on the far end router and comes to the router in queue 2. If traffic comes to the NCS540 in the wrong queue NCS will not shape it at all.
We try to find a solution that will cover all traffic class at once but we can't attach it to the interface:
We try with this:
class-map match-any TRAFFICCLASS-ANY
match traffic-class 1 2 3 4 5 6 7
end-class-map
!
policy-map BUSINESS-TS-Q2-2M-OUT
class TRAFFICCLASS-ANY
shape average 2 mbps
!
class class-default
!
end-policy-map
In ingress direction policy like this works fine:
class-map match-all COS-ANY
match cos 0 1 2 3 4 5 6 7
end-class-map
!
policy-map BUSINESS-Q2-2M-IN
class COS-ANY
set mpls experimental topmost 2
set traffic-class 2
police rate 2 mbps burst 65536 bytes peak-burst 131072 bytes
!
!
end-policy-map
!
Please let us know hot make class class-default to work on the NCS in the way that we know it from the old IOS routers.
Thanks, Primoz
