cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
985
Views
0
Helpful
1
Replies

ASR920 QoS Classification

sean_kndy
Level 1
Level 1

I am implementing a QoS policy on the ASR920 and I'm having trouble getting it to classify packets on egress.   I tried a very simple class matching EF and a policy to test it and when pinging out the interface with dscp ef set, all the pings fall into class-default instead of my dscp-ef class.  Here is the test config:

 

class-map match-all dscp-ef
  match dscp ef

policy-map test
  class dscp-ef
    priority percent 5

 

int te0/0/12

  service instance 888 ethernet

     service-policy output test

 

ping 172.18.7.105 dscp ef repeat 1000

 

#sh policy-map interface te0/0/12 service instance 888
TenGigabitEthernet0/0/12: EFP 888

Service-policy output: test

queue stats for all priority classes:
Queueing
queue limit 1966 us/ 122880 bytes
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0

Class-map: dscp-ef (match-all)
0 packets, 0 bytes
5 minute offered rate 0000 bps, drop rate 0000 bps
Match: dscp ef (46)
Priority: 5% (500000 kbps), burst bytes 12500000, b/w exceed drops: 0


Class-map: class-default (match-any)
1000 packets, 122000 bytes
5 minute offered rate 0000 bps, drop rate 0000 bps
Match: any

queue limit 98 us/ 122880 bytes
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 1000/122000

1 Reply 1

sean_kndy
Level 1
Level 1
My initial thoughts is that it's due to the fact the service instance is actually a "bridged" configuration and the IP sits on a BDI therefore the service instance may only "see" L2 CoS values. Is this indeed the case? This document seems to indicate that since version 3.5, dscp classification on an EFP is supported : https://www.cisco.com/c/en/us/td/docs/routers/asr920/configuration/guide/qos/qos-guidelines-xe-3-13-asr920-book.html