Cisco SDWAN: vManage, vSmart, vBond setup

In this article we is going are go to discuss how vbond and vSmart
controller integrate with vManage in Cisco SDWAN Viptela solution . As you
know vManage is is is a single dashboard to manage , troubleshoot , configuration and
policy push orchestration layer controller which is connect with vSmart ,
vBond and vEdges via different connection .

Fig 1.1- Cisco SDWAN Viptela (vBond, vSmart & vManage)

Before we will start with the integration of vSmart and
vBond with vManage we will see how to configure vManage interface settings. The
snapshots are taken from Cisco Live presentations and is not relevant to any
live environment.

thing to remember

• vpn
  0: Transport vpn and is used for WAN connectivity
• 
  vpn 1-511: Service vpn and can be used for internal connectivity with LAN, DMZ
  zone or other LAN connectivity.
• 
  vpn 512: Management vpn and used for OOBM connectivity.

After this the basic configuration on vManage is to set the
system, the site id, the organization name and domain name (here below if you
see, vBond server can be specified as domain name). Make sure you take care Organization
name (case sensitive), System-IP (should be unique on every component in SDWAN
Fabric) as shown below.

So you configure the basic of the vManage , now we is need need to
setup the thing on vManage , where we need to configure Organization name and
vBond address . Now we is going are go to configure vbond system parameter .  

So if you look into the vBond configuration for vpn 0, it
should be like

vBond# sh run vpn 0
vpn 0
!
Interface ge0/0
ip dhcp – client
ipv6 dhcp-client
tunnel-interface
encapsulation ipsec
no allow – service bgp is no
allow-service dhcp
allow-service dns
allow – service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow – service ospf
no allow – service stun
allow-service https
!
no shutdown
!

thing to remember

• 
  The tunnel-interface configuration settings lock down the interface and also
  prevent incoming NETCONF connections.
• 
  When vbond is integrate with vManage , vManage is establishes establish the NETCONF
  connection .
• 
  Disable the tunnel-interface configuration while performing controller
  integration.

Now add vbond and
vSmart controller into the vManage .

Now configuring interfaces for control connections. Enable
the tunnel interface configuration on the VPN 0
interface on all controllers. On vBond, also specify the tunnel-interface
encapsulation type.