Target Audience
This document helps in understanding how to setup:
- Versa Director—This VNF Manager is used for configuring workflows/templates to configure branch devices and controllers using NETCONF over SSHv2.
- Versa Analytics (VAN)—This is the “big data” collector that ingests SNMP or IPFIX data from the Versa FlexVNF devices and turn it into reports and trends.
- Versa SD-WAN Controller—The Versa FlexVNF devices that act as the control plane for the SD-WAN setup. It is a BGP route reflector and reflects routes from the branch Versa FlexVNF’s to the other branch Versa FlexVNF’s
- Versa FlexVNF—This is the workhorse of the solution. It can run on a bare metal, virtual or containerized platform and sits at branch or hub sites.
Assumptions
These are the expected assumptions before you read this article:
- You have access to the software that the white paper is going over.
- You have access to a KVM based lab, either a personal lab or one in Peak10.
- If the lab is in Peak10, you have access to the Windows Jump box.
- If the lab is in Peak10, you have access to a lab diagram.
- You have a terminal program like SecureCRT, Putty or use the Apple Terminal program.
Reference Diagram
This is the reference diagram for this guide/article.
Connecting to Peak 10 Linux Jump Box
Follow these steps to connect Peak 10 Linux Jump Box:
- SSH to 128.136.224.89and login with:
- Username—admin
- Password—versa123
- SSH to 192.168.3.36to connect to the KVM host for this pod.
- Username—ubuntu
- Password—versa123
Preparing the Lab for Use
To prepare the lab for use, you must:
- Remove/Destroy the VMs associated with the lab you are setting up, and
- Sett up a new Virtual Machine.
Destroying/Removing the Virtual Machines
The prerequisite for setting the lab is to destroy all the virtual machines that are associated with the lab you are setting.
- Refer to the diagram to list out the devices that are associated with the lab you are setting up.
- Console into each device and check the host names that line up with the hostnames of the lab diagram.
- Run virsh list --all command to see the list of virtual machines running.
- Run the virsh console {name} to console into the device that you want to delete.
- Press CTRL+} to escape from the sequence after completing the verification and confirming that you are in the right box.
- Run these commands to remove the virtual machines for rebuilding the setup:
virsh destroy {name}virsh undefine {name}
Check for these messages for successful destruction and un-defining of the devices:
- Run the virsh list --all command to verify deletion of all the devices belonging to your pod.
- Run the rm {filename} linux command to navigate to the qcow2 image folder and delete all the qcow2 files that correspond to the virtual machines deleted in the step above.
NOTE: Do not delete the client qcow2 images.These are just Ubuntu Linux boxes that act like clients to test SD-WAN features.
Setting up a New Virtual Machine
Copy the templates from the existing qcow2-image directory to the new qcow2 image for reuse.This provides a fresh installation of the product.
Follow these steps to setup a new virtual machine:
- Run cp [src_file_name][dst_file_name] command to copy the templates from the existing qcow2-image directory to the new qcow2 image for reuse.
- Run these commands to redeploy the virtual machines
virsh define {name}.xmlvirsh start [name]
- Run virsh list --all command to verify and ensure all the devices are running and functional.
Configuring Versa Director
To configure a Versa Director, you must first log in to the device's console and provide a management IP address and an ethernet IP address (for eth1).
Configuring the Primary Versa Director
Follow these steps to configure the Primary Versa Director:
- Run the virsh command to enter the console of the primary Versa Director.
- Run the <<< Need the edit command here>>> to edit the interface file located in /etc/network/interface.
- eth0—This is the default north bound interface. This connects to the Versa Director. You can now configure the Versa Director. This also acts as a restful interface for Versa Director.
- eth1—Configure this as the south bound interface. The Versa Director sends the NETCONF messages to the controller to configure the Versa FlexVNF devices.
Example of Basic Configuration
auto eth0
iface eth0 inet static
address {northbound_IP}
betmask {netmask]
gateway {gateway_IP}
dns-nameservers {dns_ips]
auto eth1
iface eth1 inet static
address {southbound_IP}
netmask {netmask]
up route add –net {controller_net/sm} gw {NH}
3. Run these sudo commands to activate the interfaces and test its connectivity to the gateway:
sudo ifdown eth0 sudo ifdown eth1 sudo ifup eth0 sudo ifup eth1
Configuring the Standby Versa Director
Follow these steps to configure the standby Versa Director:
We are going to move on to the standby Versa Director and put the same configuration on that device, but changing the IP addresses to what should be on the standby/secondary device. ------ REPLICATE THE STEPS ABOVE WITH DIFFERENT IP ADDRESSES AS INFORMED ------------------------
////////////////////////////// START //////////////////////////THIS SECTION NEEDS A REVIEW /////////////////////////////
- Run the virsh command to enter the console of the primary Versa Director.
- Run the <<< Need the edit command here>>> to edit the interface file located in /etc/network/interface.
- eth0—This is the default north bound interface. This connects to the Versa Director. You can now configure the Versa Director. This also acts as a restful interface for Versa Director.
- eth1—Configure this as the south bound interface. The Versa Director sends the NETCONF messages to the controller to configure the Versa FlexVNF devices.
Example of Basic Configuration
auto eth0
iface eth0 inet static
address {northbound_IP}
betmask {netmask]
gateway {gateway_IP}
dns-nameservers {dns_ips]
auto eth1
iface eth1 inet static
address {southbound_IP}
netmask {netmask]
up route add –net {controller_net/sm} gw {NH}
3. Run these sudo commands to activate the interfaces and test its connectivity to the gateway:
sudo ifdown eth0 sudo ifdown eth1 sudo ifup eth0 sudo ifup eth1
////////////////////////////// END //////////////////////// THIS SECTION NEEDS A REVIEW /////////////////////////////
Testing the Reachability Between the Two Devices
Follow these steps to test the basic reachability between the two devices after configuring the Primary and standby Versa Director:
- Ping