|Nortel Split Multi-Link Trunking|
|SMLT mesh with nine 1Gig paths (all connections active and load balancing traffic) 9Gb/s full duplex mesh providing 18Gb/s of bandwidth between core switches.|
Link aggregation or Multi-Link Trunking (MLT) allows multiple physical network links between two network switches and another device (which could be another switch or a network device such as a server) to be treated as a single logical link and load balance the traffic across all available links. For each packet that needs to be transmitted, one of the physical links is selected based on a load-balancing algorithm (usually involving a hash function operating on the source and destination Media Access Control (MAC) address information). For real-world network traffic this generally results in an effective bandwidth for the logical link equal to the sum of the bandwidth of the individual physical links. Redundant links that were once unused due to Spanning Tree’s loop protection can now be used to their full potential.
A general limitation of standard Link aggregation or Multi-Link Trunking (MLT) or EtherChannel is that all the physical ports in the link aggregation group must reside on the same switch. The SMLT, DSMLT and RSMLT protocols remove this limitation by allowing the physical ports to be split between two switches, allowing for the creation of Active load sharing High availability network designs that meet "Five Nines" availability requirements. The SMLT protocol has been submitted to the IETF for consideration to be made into an IETF standard.
The split may be at one or at both ends of the MLT. If both ends of the link are split, the resulting topology is referred to as an SMLT square or mesh. If only one end is split, the topology is referred to as an SMLT triangle.
In an SMLT triangle, the end of the link which is not split does not need to support SMLT. This allows non-Nortel devices including third-party switches and servers to benefit from SMLT. The only requirement is that IEEE 802.3ad static mode must be supported.
For each SMLT connection, the aggregation switches have a standard MLT or individual port with which an SMLT identifier is associated. For a given SMLT connection, the same SMLT ID must be configured on each of the peer aggregation switches.
For example, when one switch receives a response to an ARP request from an end-station on a port that is part of an SMLT, it will inform its peer switch across the IST and request the peer to update its own ARP table with a record pointing to its own connection with the corresponding SMLT ID.
In general, normal network traffic does not traverse the IST unless this is the only path to reach a host which is connected only to the peer switch. By ensuring all devices have SMLT connections to the aggregation switches, traffic never needs to traverse the IST and the total forwarding capacity of the switches in the cluster is also aggregated.
The communication between peer switches across the IST allows both unicast and multicast routing information to be exchanged allowing protocols such as Open Shortest Path First (OSPF) and Protocol Independent Multicast-Sparse Mode (PIM-SM) to operate correctly.
In a network utilising SMLT, it is often no longer necessary to run a spanning tree protocol of any kind since there are no logical bridging loops introduced by the presence of the IST. This eliminates the need for spanning tree reconvergence or root-bridge failovers in failure scenarios which causes interruptions in network traffic longer than time-sensitive applications are able to cater for.
SMLT is fully interoperable with devices supporting standard MLT (IEEE 802.3ad static mode).