In this configuration, the switches are isolated from one another. Maximum throughput Multiple switches may be utilized to optimize for maximum in a multiple network switch, when the switches are configured in parallel as part of an isolated network between two or more systems. Using TCP/UDP port numbers), which may increase the traffic variation across the links – depending on whether the ports vary – and bring the balance closer to an even distribution. More advanced switches can employ an L4 hash (i.e. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the NIC slaves in the single logical bonded interface such that different network-peers use different MAC addresses for their network packet traffic.įor this reason, an even load balancing and full utilization of all trunked links is almost never reached in real-life implementations. The receive load balancing is achieved by negotiation. Adaptive load balancing (balance-alb) includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special network switch support. If this receiving slave fails, another slave takes over the MAC address of the failed receiving slave. Incoming traffic is received by one currently designated slave network interface. The outgoing network packet traffic is distributed according to the current load (computed relative to the speed) on each network interface slave. LACP Features and practical examples.Īdaptive transmit load balancing (balance-tlb) Linux bonding driver mode that does not require any special network-switch support. LACP allows a network device to negotiate an automatic bundling of links by sending LACP packets to the peer (directly connected device that also implements LACP). Link Aggregation Control Protocol Within the IEEE specification, the Link Aggregation Control Protocol (LACP) provides a method to control the bundling of several physical together to form a single logical channel. To resolve this discrepancy, the 802.3ax (802.1AX) task force was formed, resulting in the formal transfer of the protocol to the 802.1 group with the publication of IEEE 802.1AX-2008 on 3 November 2008. Move to 802.1 layer in 2008 The 802.3 maintenance task force report for the 9th revision project in November 2006 noted that certain 802.1 layers (such as security) were positioned in the below Link Aggregation which was defined as an sublayer. Nearly every network equipment manufacturer quickly adopted this joint standard over their proprietary standards. Initial release 802.3ad in 2000 As of 2000, most gigabit channel-bonding schemes use the IEEE standard of Link Aggregation which was formerly clause 43 of the standard added in March 2000 by the IEEE 802.3ad task force.
0 kommentar(er)
