How to Initialize all vEdges via CLI

This SD-WAN lab practical will show you how to Initialize vBond and Add in vManage. You can practice along with this practical using our SD-WAN virtual lab.

Topology

Tasks 

● Upload the vEdge serial file to vManage provided to you via email 

● Configure the following system parameters on vEdge via CLI

● Configure Clock timezone Asia/Kolkata in all vEdges

● Configure VPN0 on vEdge with the following parameters 

● Configure VPN512 on all vEdges with the following parameters 

Interface: Eth0 

IP address: DHCP Client

Online Cisco SD-WAN TrainingLearn from expert trainers and master SD-WAN.Explore course

Configuration and Verification 

Open the link (shorturl.at/mrEKL) on CA-Server (Windows Server) and download the serial file from the location, click on top right icon to download this file (this file contains 3 items).  

Note: This serial license file was being created from the Cisco portal (Authorize Access to Cisco portal) using parameters such as Organization-name etc. So, make sure you already the Organization-name matching which is given in the

On the vManage, navigate to Configuration->Devices. Click on “Upload WAN Edge List” which will open a window then click on choose  

Select the serial license file (which you downloaded in previous step) and then upload it. Also check box “Validate the uploaded vEdge List and send to controllers” and click on upload 

Confirm it by clicking on OK 

The WAN Edge list has now been uploaded successfully

Now start configuring system components, VPN0 and VPN512 on the vEdge devices, Get the console access of vEdges using default username “admin” and password “admin” 

vEdge-1

Now you can configure the basic configuration on vEdge1 such as hostname, organization name, system-IP, etc. as per required in this lab tasks 

Verify this system configuration on vEdge1 on its running configuration  

Now configure the parameters of VPN0 and VPN512 on vEdge1. It has Ge0/0 and Eth0 interfaces, configure Ge0/0 in VPN0 and Eth0 in VPN512. There are other interfaces as well, but we are not using them in our lab. 

Note: In our topology Ge0/0 and Eth0 interfaces are depicted as Eth1 and Eth2 respectively 

Verify this configuration in the vEdge1 running configuration of each VPN0 and VPN512 

Check the connectivity to its gateway which is HQ router. vEdge1 will also have the connectivity to other controllers on their management interfaces in VPN0 because for return traffic we already a default route configured on SDWAN controller towards HQ router IP address 200.1.1.1 

Note: Here we are checking connectivity to vEdge1 gateway and vBond. You can also check others  

vEdge-2 

Now you can configure the basic configuration on vEdge2 such as hostname, organization name, system-IP, etc. as per required in this lab tasks

Verify this system configuration on vEdge2 on its running configuration

Now configure the parameters of VPN0 and VPN512 on vEdge2. It has Ge0/0, Eth0 and Ge0/1 interfaces, configure Ge0/0 in VPN0 and Eth0 in VPN512. Ge0/1 is not yet configured which is going towards MPLS-Cloud router. There are other interfaces as well, but we are not using them in our lab. 

Note: In our topology Ge0/0, Ge0/1 and Eth0 interfaces are depicted as Eth1, Eth2 and Eth3 respectively

Verify this configuration in the vEdge2 running configuration of each VPN0 and VPN512 

Check the connectivity to its gateway which is Internet-Cloud router. vEdge2 will also have the connectivity to controllers on their management interfaces in VPN0 because for return traffic we already a default route configured on SDWAN controller towards HQ router IP address 200.1.1.1 and HQ has a default route towards Internet-cloud. 

Note: Here we are checking connectivity to vEdge2 gateway (Internet-Cloud) and vBond. You can also check for others  

vEdge-3 

Now you can configure the basic configuration on vEdge3 such as hostname, organization name, system-IP, etc. as per required in this lab tasks 

Verify this system configuration on vEdge3 on its running configuration

Now configure the parameters of VPN0 and VPN512 on vEdge3. It has Ge0/0, Eth0 and Ge0/1 interfaces, configure Ge0/0 in VPN0 and Eth0 in VPN512. Ge0/1 is not yet configured which is going towards MPLS-Cloud router. There are other interfaces as well, but we are not using them in our lab. 

Note: In our topology Ge0/0, Ge0/1 and Eth0 interfaces are depicted as Eth1, Eth2 and Eth3 respectively  

Verify this configuration in the vEdge3 running configuration of each VPN0 and VPN512 

Check the connectivity to its gateway which is Internet-Cloud router. vEdge3 will also have the connectivity to controllers on their management interfaces in VPN0 because for return traffic we already a default route configured on SDWAN controller towards HQ router IP address 200.1.1.1 and HQ has a default route towards Internet-cloud. 

Note: Here we are checking connectivity to vEdge3 gateway (Internet-Cloud) and vBond. You can also check for others

vEdge-4 

Now you can configure the basic configuration on vEdge4 such as hostname, organization name, system-IP, etc. as per required in this lab tasks 

Verify this system configuration on vEdge4 on its running configuration  

Now configure the parameters of VPN0 and VPN512 on vEdge4. It has Ge0/0, Eth0 and Ge0/1 interfaces, configure Ge0/0 in VPN0 and Eth0 in VPN512. Ge0/1 is not yet configured which is going towards MPLS-Cloud router. There are other interfaces as well, but we are not using them in our lab. 

Note: In our topology Ge0/0, Ge0/1 and Eth0 interfaces are depicted as Eth1, Eth2 and Eth3 respectively

Verify this configuration in the vEdge4 running configuration of each VPN0 and VPN512 

Check the connectivity to its gateway which is Internet-Cloud router. vEdge4 will also have the connectivity to controllers on their management interfaces in VPN0 because for return traffic we already a default route configured on SDWAN controller towards HQ router IP address 200.1.1.1 and HQ has a default route towards Internet-cloud. 

Note: Here we are checking connectivity to vEdge3 gateway (Internet-Cloud) and vBond. You can also check for others