Configuring EVPN VXLAN Fabric with Multitenant Networking Services

Junos OS supports different ways to configure an EVPN VXLAN fabric with multitenant networking services:

• Fabric-wide significance of a VLAN ID or enterprise style configuration

  In this mode, Contrail Networking ensures that every Layer 2 Service or VLAN ID in a fabric is unique, and that there is a 1:1 mapping between the VLAN ID (4K VLANs per fabric) and the Virtual Extensible LAN Network Identifier (VNI). In most cases, 4K bridge domains are more than sufficient for any enterprise deployment. Hence, fabric-wide significance of a VLAN ID implies that any VLAN being provisioned in an EVPN VXLAN fabric maps to a VNI in a 1:1 ratio.

• Local significance of a VLAN ID or service provider style configuration

  In some Junos OS devices like MX Series, the VLAN ID used to connect an endpoint on a physical port is independent of the VNI associated to the VLAN. This means that the same virtual network or a Layer 2 bridge domain identifier can have more than one VLAN ID (as access interface) attached to the same VNI. This is especially relevant when a Juniper EVPN VXLAN fabric is used in a VMWare vCenter environment, where different ESXI hosts might use distinct distributed virtual switches and but locally significant VLAN IDs.

Contrail Networking Release 1908 enables you to select enterprise style of configuration for the CRB-Access role on QFX Series switch-interfaces. Once configured you can modify the enterprise style setting to service provider style of configuration. However, you cannot modify the service provider style to enterprise style of configuration without having to recreate the fabric.