Virtual Link Extension between ports on the same switch
To support a many-to-one virtual wire configuration, Pluribus proposes the Virtual Link Extension (vLE) technology. Previously, vLE implementation supported only one port per node to be part of a vLE. The other port should be on a remote node. However, with the implementation of this feature, both the ports of the vLE can be part of the same node and is referred as local vLE.
A vLE can have two ports in the same node only if the corresponding vLE VXLAN is not already attached to a tunnel. Similarly a tunnel can be attached to a vLE VXLAN
if there is atmost one local port in the vLE. In the case of auto-tunnels, vxlan can be added to a vtep only if there is atmost one local port on the node containing that vtep.
Netvisor allows you to also track the vLE port status on the local vLE. The node-1 and node-2 refers to the same switch in the local vLE, where node-2-port is displayed as remote port in the vle-show output, even though both the vLE ports are on the same switch. For example,
if port 30 (node-2-port) goes down, the vle status displays as remote-down (see example below) so that we know exactly why the vLE is down. But, if port 22 (node-1-port) is down, then the vle status displays as local-down.
CLI network-admin@switch > vle-show
name node-1 node-2 node-1-port node-2-port status tracking
---- --------- --------- ----------- ----------- ----------- --------
vle1 vanquish1 vanquish1 22 30 remote-down enabled
Use the port-show command to check if the node-2 status is down or vle-wait. The vle-wait state indicates that the port is brought down due to remote port being down.