QOS implementing

[dijix1990]

I have a question about qos implementing.

In this guide https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/221615-configure-and-verify-qos-in-sd-wan-route.html we create Centralized Traffic Data QoS policy to classify traffic into proper queue, but what the difference if we classify traffic via local policy? Can we do it? maybe it has some problem not doing it via local policy?

I know after create acl for classifying traffic via local policy we need to attach it to inside interface as ingress ACL. For Central policy we need to add new sequence if we already had data policy for site and by my opinion it's not convenient

[Kanan Huseynli]

Hi,

whatever you described is correct.

In centralized policy you don't point incoming interface, it does policing/ qos mapping for all traffic (regardless of the incoming interface). However, when you do via localized policy, you point service-side interface and acl. Policing/ mapping happens only for traffic which is received through interface where acl exists.

[dijix1990]

Thanks for answering. I have another question, maybe you know.

I created new class map

• Q0-Control-LLQ
• Q1-Critical-Data
• Q2-Bulk
• Q3-Best-Effort

and after connected it to local policy I found that we have extra classes. Is it by default?

• Queue0
• Queue1
• Queue2

Looks like some classes connects to same queue (Q0-Control-LLQ queue 0 and Queue0 queue 0)

 class-map
  class Q0-Control-LLQ queue 0
  class Queue0 queue 0
  class Q1-Critical-Data queue 1
  class Queue1 queue 1
  class Q2-Bulk queue 2
  class Queue2 queue 2
  class Q3-Best-Effort queue 3