Date: Fri, 29 Mar 2024 02:55:00 +0200 (EET) Message-ID: <2035918252.51.1711673700439@help.mikrotik.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_50_42253423.1711673700436" ------=_Part_50_42253423.1711673700436 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Bonding is a technology that allows the aggregation of multiple ethernet= -like interfaces into a single virtual link, thus getting higher data rates= and providing failover.
Let us assume that we have two Ethernet interfaces on each router (SW1 a= nd SW2) and want to get the maximum data rate between these two routers. To= make this possible, follow these steps:
Add bonding interface and IP address on the= SW1:
/interface bonding add m= ode=3D802.3ad slaves=3Dether1,ether2 name=3Dbond1 /ip address add address=3D172.16.0.1/24 interface=3Dbond1
Do the same thing on the SW2:
/interface bonding add m= ode=3D802.3ad slaves=3Dether1,ether2 name=3Dbond1 /ip address add address=3D172.16.0.2/24 interface=3Dbond1
Test the link from Router1:
[admin@Router1] > pin= g 172.16.0.2 SEQ HOST &= nbsp; &nbs= p; SIZE TTL TIM= E STATUS &= nbsp; 0 172.16.0.2 &nb= sp; = 56 64 0ms = ; 1 172.16.0.2 &nb= sp; = 56 64 0ms = ; 2 172.16.0.2 &nb= sp; = 56 64 0ms = ; sent=3D3 received=3D3 packet-loss=3D0% min-rtt=3D0m= s avg-rtt=3D0ms max-rtt=3D0ms
The bonding interface has to be co= nfigured on both hosts and needs a couple of seconds to get connectivity wi= th its peers.
802.3ad mode is an IEEE standard also called LACP (Link Aggregation Cont= rol Protocol). It includes automatic configuration of the aggregates, so mi= nimal configuration of the switch is needed. This standard also mandates th= at frames will be delivered in order and connections should not see misorde= ring of packets. The standard also mandates that all devices in the aggrega= te must operate at the same speed and duplex mode.
LACP balances outgoing traffic across the active ports based on hashed p= rotocol header information and accepts incoming traffic from any active por= t. The hash includes the Ethernet source and destination address and if ava= ilable, the VLAN tag, and the IPv4/IPv6 source and destination address. How= this is calculated depends on the transmit-hash-policy&= nbsp;parameter. The ARP link monitoring is not recommended, because = the ARP replies might arrive only on one slave port due to transmit hash po= licy on the LACP peer device. This can result in unbalanced transmitted tra= ffic, so MII link monitoring is the recommended option.
The layer-3-and-4 transmit hash mode is not fully comp= atible with LACP. More details can be found in https://= www.kernel.org/doc/Documentation/networking/bonding.txt
This mode balances outgoing traffic across the active ports based on the=
hashed protocol header information and accepts incoming traffic from any a=
ctive port. The mode is very similar to LACP&nb=
sp;except that it is not standardized and works with layer-3-and-4 hash policy. The mode c=
an work together with static Link Aggregation Group (LAG) interfaces.<=
/p>
Learn more about Bonding in Router=
OS!Additional Informatio=
n