Force10 Virtual Link Trunking or VLT is a proprietaryaggregation protocol developed by Force10 and available in their datacenter-class or enterprise-class network switches. VLT is implemented in the latest firmware releases for their high-end switches like the S-, Z- and E-series 10/25,40 and 100 Gbit/s datacenter switches. Although VLT is a proprietary protocol from Dell Networking other vendors offer similar features to allow users to set up an aggregated link towards two different switches, where a standard aggregated link can only terminate on a single logical switch like Cisco vpc or MLAG. VLT is a layer-2 link aggregation protocol between end-devices connected to access-switches, offering these servers a redundant, load-balancing connection to the core-network in a loop-free environment, eliminating the requirement for the use of a spanning-tree protocol. Where existing link aggregation protocols like LAG or LACP require the different links to be connected to the same switch, the VLT, for example, allows link connectivity between a server and the network via two different switches. Instead of using VLT between end-devices like servers it can also be used for uplinks between switches and the core switches. A major complication of existing link aggregation or bonding technologies is that all members interfaces of such a team/group need to terminate on one single logical switch. Beside increasing bandwidth another reason for link aggregation is redundancy. To make it possible to connect a LAG to different physical switches is to combine more than one physical switch into one logical switch using switch stacking techniques where the different physical boxes are seen as one logical switch for management and topology. The switches running in a stacked configuration always have to run the same firmware, which means that in case of a firmware upgrade the network manager has to implement the new firmware on all stack-members at the same time, resulting in an outage of the entire stack. The alternative is to have different logical switches, but then one of the used links will have to be blocked to ensure a loop-free topology (which can partially be overcome by using Multiple Spanning Tree or Cisco's proprietary per VLAN spanning tree. Spanning Tree Protocol is relatively slow in convergence, which can result in periods that traffic can't be forwarded over the network - and thus leads to outages of the applications. VLT should address all these issues, making it possible to create a loop free redundant network topology without using the Spanning Tree Protocol. An example configuration how it works can be found on the Blog Geslinux written by Grzegorz Witkowski
Prior to supporting standardized IEEE 802.1Q tagging, 3Com used proprietary Virtual LAN Trunking. 3Com VLT supported VLAN IDs 1–16 with 15 being reserved for Autoselect VLAN Mode and 16 reserved for Spanning Tree Protocol.
