Configuring QoS in Cisco SD-WAN Edges by Localized Policies

There are 8 Queues in Cisco SD-WAN edges defined from 0 - 7.

Queue 0 is the LLQ (Low Latency Queue) which the network control traffic like OMP, BFD uses.

All other traffic is going through the Queue 2 by default and with Localized Policies you can configure the traffic you want to go through any Queue.

Let's take an example using following topology.

For this example I am taking the vEdge1 in Site-1. cEdges are also same in configuration as this is done through vManage.

Send VoIP traffic through LLQ and send Web Traffic as 2nd higher priority and give least priority / best effort to the rest of the traffic. Bandwidth reservation should be 10% to VoIP traffic , 20% to Web Traffic and remaining to the rest of the traffic. Note that the Internet Link is 80 MBps. Do this QoS on Internet Link assuming MPLS link is not congesting.

Since QoS is configured under Localized Policies, following are the steps to create it.

1. Create Groups of Interests

2. Configure Forwarding Classes/QoS

3. Configure Access Control Lists

4. Configure Route Policy

5. Policy Overview

So we can skip step 4 as we don't need to configure route policies to achieve this.

Configuration > Policies > Localized Policies

Add Policy

1. Create Groups of Interests

Configuration > Policies > Custom Options > Localized Policy > Lists > Class-Maps

2. Configure Forwarding Classes/QoS

(click on the image to view in full screen)

3. Configure Access Control Lists

Remember to set Default Action to Accept Enabled to rest of the traffic.

5. Policy Overview

Cloud QoS Service Side needs to be ticked because we are applying it in the Service / LAN side.

If this policy required Deep Packet Inspection to work means if the policy is configured for Applications in Layer 7, Application check box need to be checked.

Applying to Devices

Unlike Centralized Policies, Localized Polices are applied via the templates as they are going to the running configuration of the WAN edges.

First let's send the QoS MAP, Policy Map and ACLs to the devices via Device Templates.

It is under the Additional Templates section in the Device Template.

Then have to apply the ACL in ingress interface and the Policy Map in egress interfaces by Interface Templates.

Note that this should be done after the QoS MAP, Policy Map and ACLs are pushed because it will not work when the Interface configuration tries to refer the ACL name etc if it is not done upfront.

Let's apply the QoS Map to G0/0 interface 1st and this is under the ACL/QOS section of the Interface Template.

Next the ACL to G0/2 interface.