Bringup Sequence for Overlay Network
Bring up Sequence for Overlay Network
There are two major bring up Sequence for Overlay network which uses Cisco SD-WAN Viptela devices
First Sequence (User Portion of Bring UP)
- In first Sequence , it requires user intervention , In this sequence Architect design network , create VM machine for Viptela devices , install and boot hardware Viptela routers, once its is done , then on vManage ( NMS ) Viptela devices are added to network and create configuration for each devices.
Second Sequence (Automatic Portion of Bring UP)
- In second Sequence, it occurs automatically which is orchestrated by Viptela software. Once they are added to network, they validate and authenticate themselves automatically and then they establish secure connection with each other.
Once two process are completed, a fully functional Overlay network is setup.
Summary of Events:
Below are the summery of events that occurs to bring up Cisco Viptela device. To bring up the Cisco Viptela hardware and software components in a Viptela Overlay network, all Viptela components must be connected and reachable to each other via any transport Network which includes Internet, MPLS, etc.
- The vManage NMS software get started on an ESXi or KVM server in the data center.
- The vBond orchestrator get started on an ESXi or KVM server in the DMZ.
- The vSmart controller get started on an ESXi or KVM server in the data center.
- At first the vManage NMS and the vBond orchestrator authenticate each other, their after vManage NMS and the vSmart controller authenticate each other, and then the vSmart controller and the vBond orchestrator authenticate each other.
- The vManage NMS sends configurations to the vSmart Controller and vBond devices.
- The vEdge routers deployed and get started in the network.
- The vEdge routers authenticate with the vBond orchestrator.
- The vEdge routers authenticate with the vManage NMS.
- The vEdge routers authenticate with the vSmart controller.
Once vEdge is authenticated to all SD-WAN component, the vManage NMS sends configurations to the vEdge routers