For Sponsored Posts & Articles, please email us on 📧 networks.baseline@gmail.com

Cisco SD-WAN: Multi-Tenancy

Cisco SD-WAN: Multi-Tenancy

SD-WAN from Cisco is available in dedicated and multi-tenancy deployment modes. Depending on the owner's needs, one of the models can be selected. A Cisco vManage NMS running in multi-tenant mode allows one to manage multiple tenants, or customers, from the same interface. There is a shared domain name for the vBond orchestrator and service provider for all tenants. A subdomain can be assigned to each tenant.

Cisco SD-WAN routers are managed by each tenant's set of vSmart controllers. The mode of the vManage NMS must be selected during the initial configuration (dedicated/multi-tenant). It is not convertible after the initial configuration. Multi-tenant mode offers network isolation between tenants by allowing multiple overlay networks to coexist under a single Cisco vManage (or cluster).

Fig 1.1- Cisco SD-WAN: Multi-Tenancy

Service Provider Setup for vManage
The service provider deploys and sets up Cisco 
vManage. In order to service tenants, the supplier enables multitenancy and establishes a Cisco vManage cluster. Through the SSH terminal, a Cisco vManage instance can only be accessed by the provider.

With Cisco vManage, service providers may manage the shared Cisco vBond Orchestrator and Cisco vSmart Controller devices as well as get a comprehensive overview of the SD-WAN multi-tenant implementation. Service providers may also keep an eye on and control how each tenant's installations are handled with Cisco vManage.

++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco SDWAN: vManage as Management Plane - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++

Tenants may manage and keep an eye on their deployment with Cisco vManage. Tenants can set up and deploy WAN edge devices using Cisco vManage. Additionally, tenants can set up unique policies on the allocated Cisco vSmart Controllers.

Service Provider Setup for vBond and vSmart
The service provider deploys and sets up Cisco 
vBond Orchestrators. A Cisco vBond Orchestrator can only be accessed by the provider via the SSH terminal.

As devices are added to the overlay network, Cisco vBond Orchestrators service WAN edge devices belonging to various tenants.

++++++++++++++++++++++++++++++++++++++++++++++++++++
vBond in Cisco Viptela SDWAN - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++

The service provider sets up Cisco vSmart Controllers. Only the provider has access to a Cisco vSmart Controller using an SSH interface and has the ability to build, connect, and use device and feature templates.

Cisco vManage assigns the tenant the pair of Cisco vSmart Controllers linked to the fewest number of forecast devices when more than one pair of Cisco vSmart Controllers are available to serve a tenant. The pair of Cisco vSmart Controllers servicing the fewest tenants is given to the tenant if two pairs of Cisco vSmart Controllers are connected to the same number of devices.

++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco Viptela SD-WAN : vSmart as a Control Plane - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++

On the Cisco vSmart Controllers that have been allocated to them, tenants can set up unique policies. The Cisco vSmart Controllers get a request for the policy templates from Cisco vManage. The templates are pulled and the policy configuration is deployed by Cisco vSmart Controllers for the particular tenant.

Check all the SDWAN resources, recorded Sessions, Articles & Documents
++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco SDWAN Resources - The Network DNA
++++++++++++++++++++++++++++++++++++++++++++++++++++

No comments

Note: Only a member of this blog may post a comment.