Virtual Link Extension with Cluster Configurations
Limitations for this release are as follows:
Only supported on the Accton and Pluribus Freedom platforms.
Only create vLE tunnels between a port or trunk and a VXLAN tunnel.
VTEPs configured for vLE used as endpoints for carrying multiple vLE VLANs.
This feature only allows creation of VTEPs on switches in cluster mode and does not support any active or backup failover between VTEPs.
VTEPs cannot use the VRRP virtual IP address as the local IP address.
Cluster ports always allow VXLAN termination.
LACP packets on vLE VLANs are not sent to CPU.
Netvisor ONE supports Virtual Link Extension (vLE) on switches part of a cluster configuration iby creating a dedicated VXLAN tunnel end points (VTEPs). Configure the VTEPs using one of the physical or primary IP addresses on the switch. The physical or primary IP address can be from a new Layer 3 interface dedicated for vLE configuration or from reusing the existing physical or primary IP addresses used to build the cluster VIP and used for VXLAN tunnel redundancy in a cluster environment. These dedicated tunnels and VTEPs are stateless with no dependency on each other.
Figure 3: Example Topology for Virtual Link Extension and Cluster Configuration
In the example topology, Host1 connects to both cluster nodes, PN-SW1 and PN-SW2. No vLAG on PN-SW1 and PN-SW2 connected to Host1. Host2 has 2 links connected to PN-SW3, a standalone switch. PN-SW3 does not configure trunking on the ports connected to Host2. Configure both Host1 and Host2 with LACP on links connecting to switches to High Availability (HA) functionality.
Create a new VLAN Layer 3 interface on the local vRouter used as a VTEP source IP. Create the VLAN as local only and dedicated for this usage.
In this example configuration, you must configure one virtual link extension for each point to point connectivity.
1. Configure vLE VLANs for each virtual link extension and add the ports:
On PN-SW1
CLI network-admin@switch > vlan-create id 400 vxlan 400 vxlan-mode transparent scope local
CLI network-admin@switch > vlan-port-add vlan-id 400 ports 11
On PN-SW2
CLI network-admin@switch > vlan-create id 401 vxlan 401 vxlan-mode transparent scope local
CLI network-admin@switch > vlan-port-add vlan-id 401 ports 11
On PN-SW3
CLI network-admin@switch > vlan-create id 400 vxlan 400 vxlan-mode transparent scope local
CLI network-admin@switch > vlan-create id 401 vxlan 401 vxlan-mode transparent scope local
CLI network-admin@switch > vlan-port-add vlan-id 400 ports 11
CLI network-admin@switch > vlan-port-add vlan-id 401 ports 12
Create VXLAN tunnels using the Primary IP address. Note that 10.10.10.1 and 10.10.10.2 are primary IP addresses on PN-SW1 and PN-SW2 and 20.20.20.3 is primary IP on PN-SW3.
On PN-SW1
CLI network-admin@switch > tunnel-create scope local name VTEP1 vrouter-name vr-s1 local-ip 10.10.10.1 remote-ip 20.20.20.3
On PN-SW2
CLI network-admin@switch > tunnel-create scope local name VTEP2 vrouter-name vr-s2 local-ip 10.10.10.2 remote-ip 20.20.20.3
On PN-SW3
CLI network-admin@switch > tunnel-create scope local name VTEP3 vrouter-name vr-s3 local-ip 20.20.20.3 remote-ip 10.10.10.1
CLI network-admin@switch > tunnel-create scope local name VTEP4 vrouter-name vr-s3 local-ip 20.20.20.3 remote-ip 10.10.10.2
2. Add vLE VLANs and VXLANs to VXLAN tunnels.
On PN-SW1
CLI network-admin@switch > tunnel-vxlan-add name VTEP1 vxlan 400
On PN-SW2
CLI network-admin@switch > tunnel-vxlan-add name VTEP2 vxlan 401
On PN-SW3
CLI network-admin@switch > tunnel-vxlan-add name VTEP3 vxlan 400
CLI network-admin@switch > tunnel-vxlan-add name VTEP4 vxlan 401
vLE1 is created on PN-SW1 with port 11 and VTEP1, 10.10.10.3 to 50.50.50.5, over VXLAN 400.
vLE1 is created on PN-SW1 with port 11 and VTEP3 tunnel, 50.50.50.5 to 10.10.10.3, over VXLAN 400.
Port 11 and VTEP2, 10.10.10.4 to 51.51.51.5, over VXLAN 401.
vLE2 is created on PN-SW2 with pvLE2 is created on PN-SW3 with port 12 and VTEP4, 51.51.51.5 to 10.10.10.4, over VXLAN 401.