To configure the vSmart Controller we need to setup virtual machines (VMs) first in our overlay. Once we setup and started VMs automatically they come up with factory default configuration. After that we need to configure some basic features and functions so that all the devices can be authenticated and can join the overlay network. The IP address, vBond orchestrator of our networks, IP address of our system, and a tunnel interfaces are included in these features.
For participation of vSmart controllers in the overlay network and for the overlay network to be functional we must do following:
Once we create this initial configuration we need to create full configuration now by templates configuration on vManage NMS. After that we will attach them to the vSmart Controllers. Once we do this the templates parameters overwrite the initial configuration.
Then we must assign a system IP address to the vSmart Controller in initial configuration. This IP address identifies the controllers of any interface addresses. The IP address is similar to the router ID on non-Cisco SD-WAN routers.
Let us learn how we can setup initial configuration for the vSmart controller
In CLI session, login to the Cisco vEdge (Viptela) device via SSH. Login as the user admin and the default password admin. You will login into CLI session.
Then enter configuration mode.
This is the optional step but recommended.
Cisco(config)# system host-name hostname
IP address configuration
The IP address can be IPV4 and IPV6 address.
vSmart(config-system)# system-ip ip-address
Here Cisco vManage uses the system IP address to identify the device. Then NMS can download the full configuration to the device.
vSmart(config-system)# site-id site-id
vSmart(config-system)# domain-id domain-id
IP address configuration of vBond orchestrator or vBond DNS name
The Cisco vBond orchestrator’s IP address must be a public IP address, so that all Cisco vEdge devices in the overlay network can reach it.
vSmart(config-system)# vbond (dns-name | ip-address)
vSmart(config-system)# upgrade-confirm minutes
This time may be from 1 minute through 60 minutes. When we upgrade the software on the device after this time limit configuration we must confirm that software upgrade is successful within configured limited time. If it does not happens it reverts to the previous software image.
vSmart(config-system)# user admin password password
Configure an interface in VPN 0 that will be used as tunnel interface
Configure an interface in VPN 0 that will be used as tunnel interface. VPN 0 is the WAN transport VPN. The interface name has eth number format. Here you must configure IP address and enable interface. This IP address can be configured as static or via DHCP.
vSmart(config)# vpn 0
vSmart(config-vpn-0)# interface interface-name
vSmart(config-interface)# (ip dhcp-client | ip address prefix /length)
vSmart(config-interface)# no shutdown
vSmart(config-tunnel-interface)# allow-service netconf
Tunnel interface must be configured on one interface in VPN 0. So that overlay network will come up and then Cisco vSmart Controller will participate in the overlay network. This interface should be connected with WAN transport network accessible by all Cisco vEdge devices.
Identify the type of WAN
To identify the type of WAN transport need to configure tunnel color. You can configure your color or default color.
vSmart(config-tunnel-interface)# color color
vSmart(config-vpn-0)# ip route 0.0.0.0/0 next-hop
vSmart(config)# commit and-quit
vSmart# show running-config
Now this is done. Hope this post will help you.
About the author