Configuring VTEP Objects with Automatic Fabric Connections

Based on the command sequence above, configuring a series of unidirectional end-point interconnections (even in a simple triangular topology) requires the network administrator to manually issue a long list of explicit (and hence tedious) tunnel-create commands.

Therefore, starting from release 2.6.0, Pluribus has introduced an additional user-friendly operational simplification element called a logical VTEP configuration object that leverages the intelligence of the fabric’s distributed control plane to automate the aforementioned tedious connection setup process.

With this  configuration paradigm, instead of having to create individual unidirectional connections between the end points (i.e., the tunnel-create model), a user can simply create a single VTEP object per endpoint with the vtep-create command and then map the required VXLAN identifiers to it.

This in turn triggers the automatic creation of all the required VXLAN connections in both directions between endpoints, yielding a significant amount of configuration and time savings.

An example of VTEP object configuration syntax  is displayed below:

CLI (network-admin@switch) > vtep-create name <vtep-object-name>  vrouter-name <vrouter name> ip <primary IP> virtual-ip <vip> [location <switch name>]

CLI (network-admin@switch) > vtep-vxlan-add name <vtep-object-name> vxlan <vnid1>

CLI (network-admin@switch) > vtep-vxlan-add name <vtep-object-name> vxlan <vnid2>

CLI (network-admin@switch) > vtep-vxlan-add name <vtep-object-name> vxlan <vnid3>

And so on…

VTEP objects can also be displayed or deleted with the commands vtep-show and vtep-delete, respectively.