Versa SD-WAN · Independent administration practice

SD-WAN from zero: underlay and overlay

SD-WAN from zero: underlay and overlay, transports and IPsec, Versa architecture, the VOS CLI, and your first branch from circuit to Established overlay.

70 min read11 chapters3 labs15 quiz8 scenarios15 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

What SD-WAN is, and the problem it solves

What you will learn in this module. You will start from zero and finish able to bring up a Versa SD-WAN branch yourself. You will learn what SD-WAN is and why companies buy it, the difference between the underlay and the overlay, how carriers deliver Internet, MPLS and LTE circuits, how IPsec tunnels protect the overlay, what an organization (tenant), a site and a site-id are, how the Versa architecture fits together (Director, Controller, Analytics, VOS branch, optional Concerto), and how to drive the VOS command line. Then you will practise three labs: vs-underlay-inet (bring up the Delhi Internet circuit), vs-tenant-site (give Delhi its overlay identity) and vs-controller-typo (a ticket where the overlay is Idle after a change).

Prerequisites. Basic IPv4 addressing and subnetting (a /30 has two usable hosts), what a default route is, what ping does, and what a VRF or virtual router means in one sentence. If you have finished the CCNA-level modules in this academy you are ready. No Versa experience is needed.

Start with an analogy: a company with a courier network

Imagine a company with 200 shops across India and one head office in Mumbai. For years it hired one expensive courier company with a guaranteed delivery promise to carry every parcel between shops and head office. It worked, but each new shop took weeks to connect, and the bill grew every month. One day a manager asks: "Why not use the cheap public postal service for ordinary parcels and keep the expensive courier only for urgent ones? And can someone watch every parcel and choose the best route automatically?"

That manager is describing SD-WAN. A WAN (wide area network) connects sites that are far apart. SD-WAN means software-defined WAN: a central software brain decides how traffic crosses several different links, so the company can mix cheap and premium transports and still keep applications healthy.

Old: MPLS only New: hybrid SD-WAN Branch Branch Head office DC MPLS cloud Branch Branch Head office DC MPLS Internet Several transports, one policy brain

Left: every branch depends on one private carrier. Right: each branch has two or three transports and software chooses per application.

The problem SD-WAN solves

For two decades the enterprise WAN was MPLS: a private, carrier-managed network with a service level agreement (SLA). It is reliable but expensive per megabit, slow to order (weeks to months for a new circuit), and it carries branch Internet traffic backhaul-style to the head office. That last point hurts today. When an employee in Delhi opens a cloud application, the traffic travels over MPLS to Mumbai, through the central firewall, out to the Internet, and all the way back. The path is long, the head-office link is crowded, and the cloud application feels slow.

Meanwhile, ordinary broadband and 4G/5G became cheap and fast. The catch: the Internet gives no guarantee. Latency and loss change minute by minute. SD-WAN is the answer to "how do we safely use cheap links?" It does four things:

  • Builds an encrypted overlay across any transport, so private traffic is safe even on the public Internet.
  • Measures every path continuously (latency, jitter, loss) and picks the best one per application.
  • Breaks out locally: cloud and Internet traffic can leave directly at the branch (direct Internet access, DIA) with security applied there.
  • Centralises management: one place to define templates and policy for hundreds of branches, with zero-touch onboarding.
QuestionTraditional MPLS WANSD-WAN
TransportOne private carrierInternet, MPLS, LTE/5G together
New branchWeeks, per-branch router configDays, template plus serial number
Cloud trafficBackhauled to head officeLocal breakout at the branch
Path choiceStatic routingPer application, based on live SLA
Cost per MbpsHighLower (cheap links carry bulk traffic)

Worked example. The Delhi branch needs 100 Mbps. A carrier quotes an MPLS circuit at 5 units per Mbps and a business broadband line at 1 unit per Mbps. Buying 100 Mbps MPLS costs 500 units. With SD-WAN the company buys 20 Mbps MPLS (100 units) for voice and ERP, plus 100 Mbps broadband (100 units) for everything else: 200 units, more total capacity (120 Mbps), and a second path if one fails. Numbers are illustrative, but this is the exact business case that sold SD-WAN.

Where Versa fits, and how this course teaches it

Versa Networks builds an SD-WAN and security platform. Its branch software is VOS (Versa Operating System, which runs on the branch device, often called a CPE, customer premises equipment). A central Director manages devices, a Controller runs the control plane, and Analytics collects logs. You will meet all of them in this module.

About the lab CLI. The real VOS command line and the Director web interface are much larger than anything in a first course. The labs in this academy use a deliberately simplified CLI model that keeps the real concepts and the real style of commands (set, commit, show orgs org Acme sd-wan brief) but supports only the subset you need. Where the model is simpler than the product, the text says so.

Common beginner mistake. Thinking SD-WAN replaces routing and IP. It does not. SD-WAN sits on top of ordinary IP connectivity. If the underlay is broken, no policy can fix it. This single idea drives the order of this module: underlay first, overlay second.

The slow cloud application

A retailer with 120 stores backhauled all Internet traffic through two head-office firewalls over MPLS. Every Monday morning the head-office link hit 95 percent and the cloud billing app timed out. After moving to SD-WAN, each store kept MPLS for point-of-sale traffic to the data center and used a local broadband link for cloud applications, with a branch firewall inspecting it. The head-office link dropped to 40 percent and cloud response time halved.

Lesson: SD-WAN is not mainly about "cheaper circuits". It is about sending each application over the right path.

"What is SD-WAN and why would a company adopt it?"

Strong answer: a software-defined WAN that builds an encrypted overlay over multiple underlay transports and steers traffic per application using live path measurements, managed centrally. Reasons: lower cost by mixing broadband with MPLS, local Internet breakout for cloud, faster branch rollout with zero-touch provisioning, and visibility. Add one caveat: it depends on a healthy underlay.

Key takeaways

  • SD-WAN is a central software brain that uses several transports (Internet, MPLS, LTE/5G) together.
  • It solves cost, slow rollout, backhauled cloud traffic and lack of path visibility.
  • It builds an encrypted overlay and steers traffic per application using measured latency, jitter and loss.
  • Versa's pieces: VOS on branches, Director, Controller, Analytics.
  • The course lab CLI is a simplified model of the real VOS and Director.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. Underlay and overlay: two networks, one packet
  2. WAN transports and carriers: Internet, MPLS, LTE/5G
  3. IPsec and IKE: how overlay tunnels stay private
  4. Organizations (tenants), sites and the site-id
  5. Versa architecture: Director, Controller, Analytics, VOS
  6. The VOS CLI: modes, set, commit, rollback, compare
  7. Building the underlay: Delhi Internet circuit (lab vs-underlay-inet)
  8. Overlay identity and verification (lab vs-tenant-site)
  9. Troubleshooting workflow: the Idle overlay ticket (lab vs-controller-typo)
  10. Summary and exam checklist

Join the community