MPLS, SD-WAN, and the Indian Enterprise WAN

Manish Garg
Manish Garg Associate of (ISC)² · RingSafe
Apr 27, 2026
10 min read
Read as

Last updated: May 1, 2026

100% Free

No signup. No paywall. No catch. One of our 10 most-requested practitioner modules — published in full so anyone can learn for free. We earn through consulting, not by gating knowledge.

See all 10 free modules →

MPLS is the legacy carrier-grade WAN — expensive, predictable, low-jitter, with operator-managed L3 VPNs. SD-WAN overlays multiple cheaper transports (broadband, LTE, 5G, MPLS) with software-defined policy, dynamic path selection, and integrated security. The Indian enterprise WAN is migrating fast: every BFSI and large enterprise is at some stage of MPLS reduction + SD-WAN expansion. This module covers MPLS fundamentals, SD-WAN architecture, the major vendors (Cisco Viptela, VMware/Velocloud, Versa, Fortinet), and the realistic migration path.

For two decades, “the corporate WAN” meant MPLS — leased L3 VPNs from Tata, Airtel, Sify, Reliance, BSNL connecting branches to headquarters and data centres. MPLS works well; it is also expensive, slow to provision, and rigidly policy-controlled by the carrier. SD-WAN — software-defined WAN — promises the same predictability over cheaper, more flexible transports plus integrated security. This module covers both worlds and the migration path that most Indian enterprises are now actively executing.

MPLS — what it actually is and why carriers like it

Multiprotocol Label Switching (RFC 3031) attaches small “labels” to packets at the carrier edge. Inside the carrier network, switches forward by label rather than IP — fast, simple, with operator-controlled paths. MPLS L3VPN uses VRFs (Module 13) per customer; each customer’s prefixes live in their own routing table, isolated from other customers on the same physical infrastructure. The customer-facing edge router (CE) talks BGP or static routes to the provider edge (PE); inside the carrier, BGP-VPN distributes routes; LDP or RSVP-TE assigns labels.

Why customers liked itpredictable latency and jitter, SLA-backed, the carrier handles reachability — the enterprise just connects branches and lets the carrier worry about paths.

Why it is being replacedcost (10-20× per Mbps versus broadband), provisioning lead times (weeks for new branches), and inflexibility (carrier-controlled, slow to adapt to traffic patterns).

Want this for your team?

Custom team training + practitioner advisory

Beyond the free academy — we run private workshops, vCISO advisory, and red-team exercises tailored to your stack. For Indian SMBs scaling past their first hire.

Book team training call Replies in 4 working hrs · India-only · Senior consultants