Tenant Services exposes the CLI and REST API for automating the Tenant network configuration on the Clos and small data center (non-Clos) overlay fabric.
Tenant network configuration includes VLAN, BD, VE, EVPN, VTEP, VRF, and Router BGP configuration on the necessary fabric devices to provide L2-Extension, L3-Extension across the fabric, L2-Handoff, and L3-Handoff at the edge of the fabric.
Tenant Services provisioning automates the Tenant configuration, which can be a subset of the combinations provided by the switching hardware.
You cannot perform fabric and tenant operations when manual DRC is in progress.
A Tenant is a logical construct that owns resources as follows:
NoteCtag (Customer VLAN tag) is used to identify the customer broadcast domain. In the IP fabric network, it represents the customer and is mapped into a VXLAN tunnel thru a VNI (virtual network identifier). The VNI is the ID used to identify the VXLAN tunnel. With auto VNI mapping the Ctag ID equals the VNI. You can also manually map Ctags to user-defined VNIs. These VNIs can be VLAN IDs (up to 4k) or to BD‘s (bridge domain) IDs.
For a VLAN based tenant, realization of network on the device is done using VLAN and switchport VLANs. Bridge domains are used for EVPN IRB.
For a BD based tenant, realization of network on the device is done using BD and BD-LIF. BD is used for EVPN IRB.
|Non-auto VNI mapping
|Auto VNI mapping
Event handling specifies the scope of the tenant configuration on the devices.
Devices are added to the Tenant service only when the fabric is provisioned on the devices.
An event is an occurrence of a device being removed from the fabric or from the Inventory.