This article explains how to configure SDWAN policy to steer traffic based on Latency as SLA.

Please refer to this topology diagram for explanation in this article.

Scenario

In this example, we have two WAN links named as MPLS and INTERNET on the Versa FlexVNF CPE to forward the traffic.

We need to configure the SDWAN policy to forward the IPERF application traffic over low latency link. We have set the threshold to 50ms

Traffic will also be switched over to another link if any point of time the SLA gets violated i.e. latency on the link crosses 50ms.

Configuration

SLA Profiles

1. Login to Versa Director GUI and navigate to Appliance > Configuration>Services>SDWAN>SLA Profiles
2. Click on + in the right pane to add new SLA profile
3. We need to create SLA profile with 50ms of latency, so enter value of 50 under Maximum Latency (ms) variable in the SLA profile

Forwarding Profiles

4. Click on Forwarding Profiles tab in the left pane and click + to create the forwarding profile.
5. While creating forwarding profile, we need to select the SLA profile(Low_Latency) configured in step 1.
6. Recompute Timer sets the time in seconds which essentially used to re-evaluate the SLA compliance state. This will further influence traffic switching time between circuits when current circuit does not meet the SLA threshold values. You can change the value of Recompute timer as per the production need.
7. SLA Violation Action is set to Forward, as we intent to switch the traffic to another link when configured SLA gets Violated. You can also set it to Drop in case you want to drop the traffic when SLA gets Violated.
8. You can enable Evaluate Continuously by marking the given check box. This will enable continuous evaluation of the available circuits against configured SLA parameters.

Policies

9. Click on Policies tab at the left-hand pane. There will be a Default-Policy created. If not, create a Policy with some name.
10. Navigate to Rules and click + to create new rule

11. Configure the Rule name in General tab and then navigate to Applications/URL tab to define the list of applications needed to be matched. You can also use Source/Destination tab to provide layer 3 IP addresses to match certain traffic flows.
    In this example, we are using IPERF application hence we have selected IPERF under application list.
12. Click + under Applications section and select the application.
    Please Note: Versa Detects more than 3000 applications

13. Navigate to Enforce tab and select “Allow Flow” from drop-down for Action under Forwarding section.
14. Select the Forwarding Profile name configured in Forwarding Profiles section in steps 4 through 8 under section Forwarding Profiles
15. In case, you need the data to be captured in Versa Analytics, select the LEF Profile under Logging section.

Cli Configuration

set orgs org-services Tenant-1 sd-wan sla-profiles Low_Latency latency 50

set orgs org-services Tenant-1 sd-wan sla-profiles Low_Latency low-delay-variation

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic sla-profile Low_Latency

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic connection-selection-method weighted-round-robin

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic sla-violation-action forward

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic evaluate-continuously enable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic recompute-timer 300

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic encryption always

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic symmetric-forwarding enable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic turn-redirect disable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic replication mode disable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic fec sender mode disable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic fec receiver recovery enable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic fec receiver preserve-order enable

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic sla-smoothing enable false

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic sla-dampening enable false

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic load-balance per-flow

set orgs org-services Tenant-1 sd-wan forwarding-profiles low_latency_traffic gradual-migration disable

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency match source user user-type any

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency match application predefined-application-list [ ICMP IPERF WEBEX ]

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency set action allow

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency set forwarding-profile low_latency_traffic

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency set lef profile Default-Logging-Profile

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency set lef event never

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency set lef rate-limit 10

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency monitor interval 3

set orgs org-services Tenant-1 sd-wan policies Default-Policy rules Low_latency monitor threshold 5

Validation

Traffic switchover can be monitored and validated in the Branch monitor tab. Navigate to Appliance and click on the branch > Monitor > click on the Tenant > Summary