Enable Cloud QoS

1. From the Cisco SD-WAN Manager menu, choose Configuration > Policies.

2. Click Localized Policy.

3. For the desired policy, click … and choose Edit.

   (Optionally) If the desired policy is not available in the list, you may create a customized localized policy following the steps below:

   1. Click Add Policy.

   2. In the Add Policy page, continue to click Next till you navigate to Policy Overview page.

   3. In the Policy Overview page, enter Policy Name and Description for your localized policy.

4. In the Policy Overview page, select the Cloud QoS checkbox to enable QoS on the transport side, and select the Cloud QoS Service side checkbox to enable QoS on the service side.

Configure QoS Scheduler

1. Click Forwarding Class/QoS. When you navigate to the Forwarding Classes/QoS page, QoS Map is selected by default.

2. Click Add QoS Map, and then click Create New.

3. Enter the name and description for the QoS mapping.

4. Queue 0 has already been defined by default and cannot be modified. Click the Add Queue.

5. Select a required queue from the Queue drop-down.

6. Slide the Bandwidth% and Buffer% bar and set the value as required.

7. From the Drops drop-down, select the required drop type.

8. Click Save Queue.

9. Repeat the last three steps to add more queue as required. The following are the examples for queue and sample Bandwidth/Buffer configurations:

   Table 2. Bandwidth and buffer values and drop algorithm

   Queue	Bandwidth/Buffer	Drops
   1	30/30	Random Early (RED)
   2	10/10	Random Early (RED)
   3	20/20	Random Early (RED)
   4	20/20	Random Early (RED)
   5	10/10	Tail Drop

10. QoS queue 0 should now be left at 10% Bandwidth and Buffer.

11. Click Save Policy.

Create Re-write Policy

1. (Optional) Click Policy Rewrite to add a rewrite policy.

2. From the Add Rewrite Policy drop-down, select Create New.

3. Enter a name and description for the rewrite rule.

4. Click Add Rewrite Rule.

5. In the Add Rule pop-up page:

   1. Select a class from the Class drop-down.

   2. Select the priority (Low or High) from the Priority drop-down.

      Low priority is supported only for Cisco IOS XE Catalyst SD-WAN device devices.

   3. Enter the DSCP value (0 through 63) in the DSCP field.

   4. Enter the class of service (CoS) value (0 through 7) in the Layer 2 Class of Service field.

6. Click Save Rule.

7. Repeat the previous 5 and 6 steps to add more QoS Rewrite rules as required. The following are example rewrite rule information:

   Table 3. QoS Rewrite Information

   Class	Priority	DSCP	Layer 2 Class of Service
   BULK	Low	10	1
   BULK	High	10	1
   DEFAULT	Low	0	0
   DEFAULT	High	0	0
   CONTROL_SIGNALING	Low	18	2
   CONTROL_SIGNALING	High	18	2
   CRITICAL_DATA	Low	18	2
   CRITICAL_DATA	High	18	2
   INTERACTIVE_VIDEO	Low	34	4
   INTERACTIVE_VIDEO	High	34	4

8. Click Save Policy.

9. Click Save Policy Changes to save the changes to the localized master policy.

1. From the Cisco SD-WAN Manager menu, choose Configuration > Templates.

2. Click Feature Templates.

   Note	In Cisco vManage 20.7.x and earlier releases, Feature Templates is called Feature.

3. Choose a feature template from the list. Click ..., and click Edit.

4. Click ACL/QoS.

5. From the QoS Map drop-down, select Global and enter a name in the field.

6. From the Rewrite Rule drop-down, select Global and enter a name in the field.

7. To save the feature template changes, click Update.

   Note	The configuration does not take effect till the feature template is attached to the device template.

8. In the left pane, choose the device to view the configuration in the right pane.

9. Click Configure Devices to push the policy map. In the pop up page, select the check box and confirm changes on multiple devices. Click OK.

This example shows a data policy that classifies incoming traffic by mapping each forwarding class to an output queue.

policy
class-map
  class Queue0 queue 0
  class ef queue 0
  class Queue1 queue 1
  class Queue2 queue 2
  class be queue 2
  class Queue3 queue 3
  class af1 queue 3
  class Queue4 queue 4
  class af2 queue 4
  class Queue5 queue 5
  class af3 queue 5
!

This example illustrates how to configure the QoS scheduler for each queue to define the importance of data packets.

class-map match-any Queue0
match qos-group 0
!
class-map match-any Queue1
match qos-group 1
!
class-map match-any Queue2
match qos-group 2
!
class-map match-any Queue3
match qos-group 3
!
class-map match-any Queue4
match qos-group 4
!
class-map match-any Queue5
match qos-group 5
!
 
policy-map test
class Queue0
  priority percent 20
!
class Queue1
  random-detect
  bandwidth percent 20
!
class class-default
  bandwidth percent 20
!
class Queue3
  bandwidth percent 15
!
class Queue4
  random-detect
  bandwidth percent 15
!
class Queue5
  bandwidth percent 10
!
!

Define Access Lists

Define an access list to specify match conditions for packet transmission.

policy
access-list acl1
  sequence 1
   match
    dscp 46 48
   !
   action accept
    class ef
   !
  !
  sequence 11
   match
    dscp 34
   !
   action accept
    class af3
   !
  !      
  sequence 21
   match
    dscp 24
   !
   action accept
    class af2
   !
  !
  sequence 31
   match
    dscp 18
   !
   action accept
    class af1
   !
  !
  sequence 41
   match
    dscp 0 10
   !
   action accept
    class be
    log  
   !
  !
  default-action accept
!

Apply Access List to a Specific Interface

This example illustrates how to apply the previously access list defined on the input of a service interface. Here "access-list acl1" is applied on the input of interface Gi0/0/1.

sdwan
interface GigabitEthernet0/0/1
  access-list acl1 in
!
 !
!

Configure Rewrite Rule

This example shows how to configure the rewrite rule to overwrite the DSCP field of the outer IP header. Here the rewrite rule "transport" overwrites the DSCP value for forwarding classes based on the drop profile. Since all classes are configured with RED drop, they can have one of two profiles: high drop or low drop. The rewrite rule is applied only on the egress interface, so on the way out, packets classified as "af1" and a Packet Loss Priority (PLP) level of low are marked with a DSCP value of 3 in the IP header field, while "af1" packets with a PLP level of high are marked with 4. Similarly, "af2" packets with a PLP level of low are marked with a DSCP value of 5, while "af2" packets with a PLP level of high are marked with 6, and so on.

Apply the Queue Map and Rewrite Rule to the Egress Interface

This example applies the queue map "test" and the rewrite rule "transport" to the egress interface. (Note that you can apply QOS maps to VLAN interfaces, also called subinterfaces, on Cisco IOS XE Catalyst SD-WAN devices (not on Cisco vEdge devices), using Cisco IOS XE SD-WAN Release 16.12.x or later, or Cisco SD-WAN Release 19.1.x or later.)

policy
rewrite-rule transport
  class af1 low layer-2-cos 1
  class af2 low dscp 16 layer-2-cos 2
  class af3 low dscp 24 layer-2-cos 3
  class be low dscp 0
  class ef low dscp 46 layer-2-cos 5
!
sdwan
interface GigabitEthernet0/0/2
  tunnel-interface
   encapsulation ipsec weight 1
   no border
   color public-internet restrict
  exit
  rewrite-rule transport
exit

Apply a Rewrite Rule for Outgoing Traffic in a Carrier Supporting Carrier Scenario

In carrier supporting carrier (CSC) scenarios, which use MPLS, the rewrite-rule command assigns the MPLS EXP value in the MPLS header for outgoing traffic. Use the rewrite-rule command using a CLI template or CLI add-on template, and the mpls-exp-topmost keyword. If, in a CSC scenario, you use the dscp keyword instead, such as with legacy configurations created before support of the mpls-exp-topmost keyword, the rewrite-rule command converts the DSCP value to an MPLS EXP value in accordance with the standard mapping of DSCP to MPLS EXP values. The benefit of using the mpls-exp-topmost keyword is that you can set the MPLS EXP value directly, without depending on the mapping of DSCP to MPLS EXP values.

The following example applies to a CSC scenario. It defines a rewrite rule called rw-exp, which sets the MPLS EXP value for outgoing traffic to 1 and applies the rule to the outbound interface.

Define the rewrite rule using the mpls-exp-topmost keyword, as follows:

sdwan
  policy
    rewrite-rule rw-exp
      class BULK low mpls-exp-topmost 1
      class BULK high mpls-exp-topmost 1

Alternatively, if you define the rewrite rule using the dscp keyword, the rewrite-rule command converts the value of 10 to an MPLS EXP value of 1, in accordance with the standard mapping of DSCP to MPLS EXP values.

sdwan
  policy
    rewrite-rule rw-exp
      class BULK low dscp 10
      class BULK high dscp 10

Apply the rule as follows:

sdwan
interface GigabitEthernet0/0/2
  tunnel-interface
   encapsulation ipsec weight 1
   no border
   color public-internet restrict
  exit
  rewrite-rule rw-exp
exit