From WAN to SD-WAN

The traditional WAN architecture is complex, rigid, and expensive. As organizations undergo digital transformations, they are eagerly seeking flexible, cost-effective, and easy-to-manage alternatives for WAN network connectivity and optimization. The software-defined WAN (SD-WAN) has emerged as not only the foremost choice among many organizations but as a business imperative.

Providing WAN connectivity across an enterprise means having to:

  • Manage multiple disparate transport networks
  • Embed policy and control at every hop in the network
  • Address security vulnerabilities that inadequate network-wide segmentation create
  • Deal with long provisioning times to roll out new applications that require network-specific behavior
  • Handle simple change requests that take months to complete
  • Reconcile performance issues pertaining to the public cloud, VDI, and bandwidth-hungry applications

Viptela Secure Extensible Network (SEN) SD-WAN technology addresses these challenges with five major architectural elements:

  1. Transport independence. Regardless of the connectivity types an organization uses, an overlay is built on top of the connectivity. This approach enables complete transport independence.
  2. Secure endpoints. Encryption and device authentication is provided from an any-to-any perspective, whether the network has 10 nodes or 100,000 nodes.
  3. End-to-end network segmentation. To separate lines of business or create a business partner extranet, networks can be isolated from each other. There can be different encryption schemes for each network segment.
  4. Centrally enforced policy and business logic. Policy and control of all devices across the network is centralized. Each location enforces its own policies, but a centralized controller influences all locations.
  5. Layer 4–7 service advertisement. Requests for third-party network or cloud services are connected to the Viptela SD WAN overlay. Users of a service set a centralized policy to direct traffic to a particular location.

diagram3