This web traffic flow using CenturyLink® SD-WAN use case shows the steps necessary to complete a rule for web traffic flow based on network service level agreement (SLA) parameters such as latency, jitter, and packet loss on the WAN connectivity of your branch location. These three steps need to be done to make a complete configuration: SLA profiles, forwarding profiles, policies and rules:
In the example below, we are:
Note: the CenturyLink engineer may have already defined some standard SLA profiles and forwarding profiles. In this case, you will see them and can add a new rule that refers to those profiles.
Step 1—configuring SD-WAN SLA profiles
A service level agreement (SLA) defines the network performance parameters between your organization and CenturyLink and includes packet delay, packet loss, and jitter.
You can also select the checkbox to turn on default options.
Step 2—configuring SD-WAN forwarding profiles
A forwarding profile determines the traffic path based on realtime SLA performance of traffic. A forwarding profile defines the properties such as load balancing method, priority of circuits, circuit type, circuit media, and others to be selected for traffic.
Step 3—configuring SD-WAN policies and rules
Establishing SD-WAN policies and rules helps you configure web traffic based on matching criteria such as the traffic source address, destination address, source zone, and specific IP packet header information. The default policy is the only policy that can be created; CenturyLink will have done this. Follow these steps to configure rules:
Note: Items selected in the same section (like Applications) will be added in an OR condition, which means HTTPS or HTTP traffic will be captured by the rule. Items added into different sections in the same rule will be considered an AND condition, which means if you have HTTP in Applications and Games in a URL Category list, the traffic would have to match both of those conditions for the rule to apply.
Apply these changes to your branches.