EVPN VXLAN network provisioner

This provisioner uses EVPN as a mechanism for L2 segmentation.

As of version 6.2 MetalSoft supports the following drivers:

• Dell Enterprise Sonic 4.x

• JunOS 18, 20,2 4

• Dell OS10

Network profiles

To allocate and attach a VXLAN to an VLAN use the Enable VXLAN checkbox in the network profiles.

Gateway management

To enable gateway provisioning check the “Provision Gateways” checkbox in the network profile. Depending on the underlying driver the implementation will be either as a Symmetric IRB (Multicast) set of gateways on all the switches involved in an L2 overlay network. EVPN Multi-homing is used for Juniper.

VRFs

VLANs and VNIs get mapped to a VRF per Fabric. VLAN 100 can belong to VRF-Internet on the WAN fabric, and to VRF-Private-Network on the SAN fabric, although we currently don’t support VRFs for the SAN fabric.

VLANs can also be mapped to VNIs. This is not user controllable atm, as each VLAN ID gets mapped to a particlar VNI (e.g. WAN vlan 100 gets mapped to VNI 10100).

VRF dedicated VLANs/VNIs

A special kind of VLANs and VNIs which we call “VRF dedicated VLANs/VNIs”. This is an extra VLAN/VNI that’s needed by the VRF, in addition to the ones we connect to servers / use through network profiles.

SONICs and JunOS need a dedicated VNI per VRF, but SONICs also need a dedicated VLAN per VRF.