In this use case, you used CSO SaaS to configure SD-WAN in an enterprise scenario consisting of one headquarters (modelled as an enterprise hub site) and two branches (modelled as two branch sites), with the headquarters connected to a data center. You also added an SD-WAN policy to enable traffic to break out locally directly from the sites to the Internet.
Even though the enterprise scenario that we’ve used is generic, it gives you an understanding of the underlying principles of how to implement SD-WAN in your network. In addition, this use case demonstrates how the CSO GUI simplifies the implementation of SD-WAN and demonstrates CSO’s powerful secure SD-WAN capabilities.
While the tasks for configuring SD-WAN in your own network depend on the complexity of your network and the functionality that you want to implement, you can use the underlying principles explained in this use case to configure SD-WAN in your own, unique network.
In CSO SaaS, there are several tasks that are handled by the Juniper team, such as onboarding a provider hub for OAM connectivity, and SMTP server configuration. If you use the on-premise version of CSO, which means that you install CSO on your own infrastructure, the service provider (SP) administrator must handle these tasks.
More Breakout Options—Now that you know how to use an SD-WAN policy intent to implement local breakout, you can use intents to route traffic from specific applications to use local breakout.
You can also use intents to route traffic from specific applications over a Zscaler overlay (cloud breakout), if you have a Zscaler account. For more information, see Adding Cloud Breakout Settings in the Customer Portal User Guide (available at the CSO Documentation page).
Path-Based Traffic Steering—You can add a path-based traffic steering profile that enables you to specify the path that traffic should take and add an SD-WAN policy intent that references the profile, which enables CSO to reroute traffic from specific applications over the overlay (MPLS or Internet) specified in the profile. For more information, see Adding Path-Based Steering Profiles in the Customer Portal User Guide (available at the CSO Documentation page).
SLA-Based (Dynamic) Traffic Steering—You can add an SLA-based traffic steering profile that enables you to set SLA criteria (such as latency, packet loss, and jitter) and add an SD-WAN policy intent that references the profile, which enables CSO to dynamically select the path on which to route traffic from specific applications based on the SLA criteria specified in the profile. For more information, see Adding SLA-Based Steering Profiles in the Customer Portal User Guide (available at the CSO Documentation page).