Step 1

From the Cisco SD-WAN Manager menu, selectConfiguration > Templates > Feature Templates > .

Step 2

Click Add Template and select a device from the device list in the left pane.

Step 3

In the right pane, select the BFD template listed under Basic Information.

Step 4

In the Basic Configuration pane, enter Multiplier and Poll Interval (milliseconds).

Step 5

In the Default DSCP value for BFD Packets field, enter the required device specific value or choose the default value for DSCP.

Step 6

(Optional) In the Color pane, choose the required color from the drop-down list.

Step 7

Enter the required Hello Interval (milliseconds) and Multiplier.

Step 8

Choose the Path MTU Discovery value.

Step 9

Enter the BFD Default DSCP value for tloc color.

Step 10

Click Add.

Step 1

From the Cisco SD-WAN Manager menu, choose Configuration > Policies. Centralized Policy is selected and displayed by default.

Step 2

Click Add Policy. The Create Applications or Groups of Interest page is displayed.

Step 3

Click Next. The Network Topology window opens, and in the Topology bar, Topology is selected by default.

Step 4

Click Next. The Configure Traffic Rules window opens, and in the Application-Aware Routing bar, Application-Aware Routing is selected by default.

Step 5

Click Next. The Apply Policies to Sites and VPNs window opens.

Step 6

In the Policy Name field, enter a name for the policy. This field is mandatory and can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens (–), and underscores (_). It cannot contain spaces or any other characters.

Step 7

In the Policy Description field, enter a description of the policy. It can contain up to 2048 characters. This field is mandatory, and it can contain any characters and spaces.

Step 8

From the Topology bar, select the type of policy block. The table then lists policies that you have created for that type of policy block.

Step 9

Click Add New Site List and VPN list. Select one or more site lists and select one or more VPN lists. Click Add.

Step 10

Click Preview to view the configured policy. The policy is displayed in CLI format.

Step 11

Click Save Policy. The Configuration > Policies page appears, and the policies table includes the newly created policy.

Step 1

Create lists of overlay network sites to which the policy will be applied.

vSmart(config)# policy
vSmart(config-policy)# lists site-list list-name
vSmart(config-site-list)# site-id site-id

Step 2

Define SLA classes with traffic characteristics to apply to matching application data traffic.

vSmart(config)# policy sla-class sla-class-name
vSmart(config-sla-class)# jitter milliseconds
vSmart(config-sla-class)# latency milliseconds
vSmart(config-sla-class)# loss percentage
vSmart(config-sla-class)# app-probe-class app-probe-class
vSmart(config-sla-class)# fallback-best-tunnelcriterialatencylossjitter

Step 3

Create Lists of Applications, IP Prefixes, and VPNs.

vSmart(config)# policy lists
vSmart(config-lists)# app-list list-name
vSmart(config-app-list)# (app application-name | app-family family-name)

vSmart(config-lists)# prefix-list list-name 
vSmart(config-prefix-list)# ip-prefix prefix/length

vSmart(config-lists)# vpn-list  list-name
vSmart(config-vpn-list)# vpn vpn-id

Step 4

Create an application-aware routing policy instance and associate it with a list of VPNs.

vSmart(config)# policy app-route-policy policy-name
vSmart(config-app-route-policy)# vpn-list list-name

Step 5

Create match-action sequences: Define one or more numbered sequences that match data traffic and apply SLA classes.

1. Create a sequence.

   Example:

   vSmart(config-app-route-policy)# sequence number

2. Define match parameters for data packets.

   Example:

   ​​vSmart(config-sequence)# match  parameters

3. Define the action to take if a match occurs.

   Example:

   vSmart(config-sequence)# action sla-class sla-class-name [strict]
   vSmart(config-sequence)# action sla-class sla-class-name [strict] preferred-color colors
   vSmart(config-sequence)# <userinput>action backup-sla-preferred-color</userinput> <varname>colors</varname>

Step 6

Configure action options for SLA classes:

1. Configure basic SLA Class

   sla-class sla-class-name

   Forwards matching traffic as long as one tunnel meets the SLA.

   • If one tunnel matches, traffic goes through it.

   • If multiple tunnels match, traffic is distributed among them.

   • If no tunnel matches, traffic uses any available tunnel.

2. Configure preferred tunnel color.

   sla-class sla-class-name
             preferred-color color

   Traffic prefers a tunnel of the specified color.

   • If no tunnel matches the SLA, data traffic is sent through any available tunnel. In this sense, color preference is considered to be a loose matching, not a strict matching, because data traffic is always forwarded, whether a tunnel of the preferred color is available or not.

   • When no tunnel matches the SLA, you can choose how to handle the data traffic:

     • strict—Drop the data traffic.

     • backup-sla-preferred-color color —Direct the data traffic to a specific tunnel. Data traffic is sent out the configured tunnel if that tunnel interface is available; if that tunnel is unavailable, traffic is sent out another available tunnel. You can specify one or more colors. As with the preferred-color option, the backup SLA preferred color is loose matching. In a single action configuration, you cannot include both the strict and backup-sla-preferred-color options.

3. Count matching packets/bytes:

   vSmart(config-sequence)# action count counter-name

4. Place a sampled set of packets into syslog:

   vSmart(config-sequence)# action log

   Match–action pairs are evaluated in numerical order. If no match occurs, the default action applies. For application-aware routing, the default is to accept nonmatching traffic. To apply SLA parameters to nonmatching packets:

Step 7

If a packet does not match any of the conditions in one of the sequences, configure the default action.

vSmart(config-policy-name)# default-action sla-class sla-class-name

Step 8

Apply the policy to a site list.

vSmart(config)# apply-policy site-list list-name app-route-policy policy-name

Step 1

Create applications or groups of interest.

Step 2

Configure traffic rules.

Step 3

Apply policies to sites and VPN.

Step 4

Activate the policy, to make an application-aware routing policy effective.

Step 1

Define the SLA parameters to apply to matching ICMP traffic.

​vSmart# config
vSmart(config)# policy sla-class test_sla_class latency 50
vSmart(config-sla-class-test_sla_class)#

Step 2

Define the site and VPN lists to which you want to apply the application-aware routing policy.

vSmart(config-sla-class-test_sla_class)# exit
vSmart(config-sla-class-test_sla_class)# lists vpn-list vpn_1_list vpn 1
vSmart(config-vpn-list-vpn_1_list)# exit
vSmart(config-lists)# site-list site_500 site-id 500
vSmart(config-site-list-site_500)#

Step 3

Configure the application-aware routing policy and specify the protocol numbers for ICMP, TCP, and UDP.

vSmart(config-site-list-site_500)# exit
vSmart(config-lists)# exit
vSmart(config-policy)# app-route-policy test_app_route_policy
vSmart(config-app-route-policy-test_app_route_policy)# vpn-list vpn_1_list
vSmart(config-vpn-list-vpn_1_list)# sequence 1 match protocol 6
vSmart(config-match)# exit
vSmart(config-sequence-1)# action sla-class test_sla_class strict
vSmart(config-sequence-1)# exit
vSmart(config-vpn-list-vpn_1_list)# sequence 2 match protocol 17
vSmart(config-match)# exit
vSmart(config-sequence-2)# action sla-class test_sla_class
vSmart(config-sequence-2)# exit
vSmart(config-vpn-list-vpn_1_list)# sequence 3 match protocol 1
vSmart(config-match)# exit
vSmart(config-sequence-3)# action sla-class test_sla_class strict
vSmart(config-sequence-3)# exit
vSmart(config-sequence-4)#

Step 4

Apply the policy to the desired sites in the Cisco IOS XE Catalyst SD-WAN overlay network.

vSmart(config-sequence-4)# top
vSmart(config)# apply-policy site-list site_500 app-route-policy test_app_route_policy

Step 5

Display the configuration changes.

vSmart(config-site-list-site_500)# top
vSmart(config)# show config

Step 6

Validate that the configuration contains no errors.

vSmart(config)# validate
Validation complete

Step 7

Activate the configuration.

vSmart(config)# commit
Commit complete.

Step 8

Exit from configuration mode.

vSmart(config)# exit
vSmart#