Scribd
Upload
46 views

Principles of SDWAN

The document discusses SD-WAN controllers, topologies, forwarding options, programmability, components, and deployment models. It describes controllers like vManage, vSmart, and vEdge and topologies like full mesh, partial mesh, point-to-point, and hub-and-spoke. It also covers forwarding options like active-active, active-standby, and application-aware SLA.

Uploaded by

shan1512
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
46 views

Principles of SDWAN

The document discusses SD-WAN controllers, topologies, forwarding options, programmability, components, and deployment models. It describes controllers like vManage, vSmart, and vEdge and topologies like full mesh, partial mesh, point-to-point, and hub-and-spoke. It also covers forwarding options like active-active, active-standby, and application-aware SLA.

Uploaded by

shan1512
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Underlay - What we have

Overlay - What we want (acheived with VXLAN tunnels).

Controllers:
===========

- vManage - Configuration - Management Plane


- vSmart - Control Plane
- vEdge - Data Plane
- vBond - Orchestration Plane

SD-WAN Toplogies
================
- Full Mesh
- Partial Mesh
- Point to Point
- Hub and Spoke ( Only option with Base license feature)

Forwarding Options
=================
Incase of two WAN service providers we can use ACTIVE - ACTIVE (it can load
balance)
However what if one of the circuit is larger than other, now we can use ACTIVE -
ACTIVE (weighted version)
Suppose we want to send an applcation from reliable link we can use ACTIVE-STANDBY
PINNING on per application basis (Prefer WAN B, Switch to WAN A when WAN B goes
down).
APPLICATION AWARE SLA

But what if the WAN B has service degradation (jitter/drops) this is where we get
into Application Aware SLA

Once we reach certain threshold our WAN edge will intelligently switch to WAN
Service Provider A.

With License we can use Deep Packet Inspection

Without license we can use 6-Tuple:

1- Source IP address
2- Destination IP address
3- Source Port
4- Destination Port
5- QoS-DSCP
6- IP Protocol

SD WAN Programmability
----------------------

NETCONF (Uses SSH and XML as markup language)


REST API (Uses HTTP/HTTPS and XML or JSON as markup language)

|GUI|<--------|ADMIN PC|
|
|<REST API>
|
|vMANAGE|
|
|<NETCONF>
|
|vSMART|
|
|<OMP>
|
|vEdge|

SDWAN Components
================

vEdge

cEdge

vSmart - Only virtual

|vManage|<---------GUI
|
|NETCONF
|
|vSmart|
|
|OMP
|
|vEdge|

vBond is a virtual appliance and it must have a Public IP address. We can use NAT
but the NAT should be 1:1, we cant do PAT.

vEdge that come online we have to approve them, (we can also preapprove)

Controller Deployment Models


============================

- Public Model
- Hybrid Model
- Hybrid Model with Private IPs

You might also like