Multiple vManage to vBond Control Connections

[Steytler]

Here is a teaser.  Why would vManage have 8 vBond control connections in a network with 1 vManage, 2vSmart, 1vBond and 6 vEdge-Cloud devices with 'show control connections'?

Isn't control connection OMP?

[Octavian Szolga · Accepted solution]

Hi,

vManage does not run OMP. You'll have OMP sessions between WAN Edge devices and vSmart controllers.

Control sessions between controllers refer to pure DTLS with no OMP (even though the OMP between vSmart and WAN Edges run on top of DTLS).

A vManage with 8 CPU will have 8 control sessions (DTLS) to each vBond. Another vManage with 2 CPU will have only 2 DTLS to each vBond.

Ports Used by Cisco SD-WAN Devices Running Multiple vCPUs

The Cisco vSmart Controllers can run on a virtual machine (VM) with up to eight virtual CPUs (vCPUs). Cisco vManage can be configured to a minimum of 16 vCPUs, and eight vCPUs are used for control connection ports. The vCPUs are designated as Core0 through Core7.

Each core is allocated separate base ports for control connections. The base ports differ, depending on whether the connection is over a DTLS tunnel (which uses UDP) or a TLS tunnel (which uses TCP).

https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/cisco-sd-wan-overlay-network-bringup.html#c_Firewall_Ports_for_Viptela_Deployments_8690.xml

BR,

Octavian

[Steytler]

Thanks! 

I was pretty certain it was not suppose to be OMP, but when you issue the "control connection" on an edge device it's specific to OMP.  I was a little confused.  

I read the vManage to vBond control connections were not perm too.  But it looks like they are.

[svemulap@cisco.com]

Control connections between controllers are persistent.
https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/cisco-sdwan-design-guide.html?dtid=osscdc000283#ControlConnections