Webinar topic: Network LACP/Bonding/Teaming with Mikrotik Presenter: Achmad Mardiansyah In this webinar series, How Network LACP/Bonding/Teaming with Mikrotik Please share your feedback or webinar ideas here: http://bit.ly/glcfeedback Check our schedule for future events: https://www.glcnetworks.com/en/schedule/ Follow our social media for updates: Facebook, Instagram, YouTube Channel, and telegram also discord Recording available on Youtube https://youtu.be/smRcyLE42hU

1. www.glcnetworks.com
Network
LACP/Bonding/Teaming
with mikrotik
GLC webinar, 23 Dec 2021
Achmad Mardiansyah
achmad@glcnetworks.com
GLC Networks, Indonesia
1

2. www.glcnetworks.com
Agenda
● Introduction
● Review prerequisite knowledge
● Interface bonding
● Live practice
● Q & A
2

3. www.glcnetworks.com
introduction
3

4. www.glcnetworks.com
What is GLC?
● Garda Lintas Cakrawala (www.glcnetworks.com)
● Based in Bandung, Indonesia
● Areas: Training, IT Consulting
● Certified partner for: Mikrotik, Ubiquity, Linux foundation
● Product: GLC radius manager
● Regular event
4

5. www.glcnetworks.com
Trainer Introduction
● Name: Achmad Mardiansyah
● Base: bandung, Indonesia
● Linux user since 1999, mikrotik user since 2007, UBNT
2011
● Mikrotik Certified Trainer
(MTCNA/RE/WE/UME/INE/TCE/IPv6)
● Mikrotik/Linux Certified Consultant
● Website contributor: achmadjournal.com, mikrotik.tips,
asysadmin.tips
● More info:
http://au.linkedin.com/in/achmadmardiansyah
5

6. www.glcnetworks.com
Past experiences
6
● 2021 (Congo DRC, Malaysia): network support,
radius/billing integration
● 2020 (Congo DRC, Malaysia): IOT integration,
network automation
● 2019, Congo (DRC): build a wireless ISP from
ground-up
● 2018, Malaysia: network revamp, develop billing
solution and integration, setup dynamic routing
● 2017, Libya (north africa): remote wireless migration
for a new Wireless ISP
● 2016, United Kingdom: workshop for wireless ISP,
migrating a bridged to routed network

7. www.glcnetworks.com
About GLC webinar?
● First webinar: january 1, 2010 (title:
tahun baru bersama solaris - new year
with solaris OS)
● As a sharing event with various topics:
linux, networking, wireless, database,
programming, etc
● Regular schedule
● Irregular schedule: as needed
● Checking schedule:
http://www.glcnetworks.com/schedule
● You are invited to be a presenter
○ No need to be an expert
○ This is a forum for sharing: knowledge,
experiences, information
7

8. www.glcnetworks.com
Please introduce yourself
● Your name
● Your company/university?
● Your networking experience?
● Your mikrotik experience?
● Your expectation from this course?
8

9. www.glcnetworks.com
Prerequisite
● This presentation some prerequisite knowledge
● We assume you already know:
○ Computer networking
○ Mikrotik RouterOS
○
9

10. www.glcnetworks.com
Review prerequisite knowledge
10

11. www.glcnetworks.com
7 OSI layer & protocol
11
● OSI layer Is a conceptual model from ISO
(International Standard Organization) for project
OSI (Open System Interconnection)
● When you send a message with a courier, you
need to add more info to get your message arrived
at the destination (This process is called
encapsulation)
● What is protocol
○ Is a set of rules for communication
○ Available on each layer
● Communication consist of series encapsulation
○ SDU: service data unit (before PDU)
○ PDU: protocol data unit (after header is added)

12. www.glcnetworks.com
Layered model (TCP/IP vs ISO) and encapsulation
12
/ datagram

13. www.glcnetworks.com
Did you notice?
● There is a big overhead on encapsulation process
● More encapsulation means less payload?
13

14. www.glcnetworks.com
Connecting Network devices
14

15. www.glcnetworks.com
Typical network hardware
● End-devices
● Intermediary devices
● Media
15

16. www.glcnetworks.com
Typical connection (physical topology)
16
R2
R1
R3
● Router connects layer 2
segments
● Router works on layer 3
● Meaning, each layer 2
segment has network ID

17. www.glcnetworks.com
Typical connection (logical topology)
Routing table:
● A table at router that is used to forward packet
● Available on every devices (router and host)
● Entry is executed sequentially
17
192.168.0.0/26
R1
192.168.0.1/26
192.168.0.3/26
192.168.0.2/26
R3
R2
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24
192.168.3.3/24
192.168.3.9/24
192.168.2.9/24
192.168.2.2/24
192.168.1.1/24
192.168.1.9/24
destination gateway
192.168.0.0/26 direct
192.168.1.0/24 direct
192.168.2.0/24 192.168.0.2
192.168.3.0/24 192.168.0.3
192.168.16.3/32 192.168.0.2
0.0.0.0/0 (default gw) 192.168.0.3

18. www.glcnetworks.com
Layer 2 technology: Ethernet
18

19. www.glcnetworks.com
Ethernet specs
● Defined by IEEE 802.3
● Media:
○ Coaxial cable
○ Twisted pair
○ Fiber optic
● Devices required:
○ Bridge / switch
○ HUB
● Everyone likes it!!
○ Affordable
○ Easy to install
○ Easy maintenance
19

20. www.glcnetworks.com
How ethernet works (CSMA/CD)
● Carrier Sense Multiple Access / Collision
Detection (CSMA/CD)
○ Every host do not know when other send data
○ Before sending data, host check the shared medium
○ Every host only knows when collision happens
● You will have:
○ Collision domain
■ Area where collision happens
■ Can use any frame
○ Broadcast domain
■ Area when broadcast happens
■ Using broadcast frame
● CSMA/CD != CSMA/CA
20

21. www.glcnetworks.com
How ethernet works (ARP)
● ARP = Address resolution protocol
● A mapping between IPv4 and MAC
address
● Requires broadcast frame
● Will be eliminated in IPv6
21
Source: ipcisco.com

22. www.glcnetworks.com
Ethernet evolution (1)
22

23. www.glcnetworks.com
Ethernet evolution (2)
23

24. www.glcnetworks.com
Ethernet issue: Collision domain
● Area where collision happens. See CSMA/CD
● Some ideas:
○ Using bridged/switched network
○ Now is very hard to find a HUB
24
Source: devto.com

25. www.glcnetworks.com
Ethernet issue: Broadcast domain
● An area where broadcast happens
● Try use 5-4-3-2-1 rules
● Broadcast can go wild (especially on infected
hosts)
● Some ideas:
○ Using router to split segments
○ Port isolation on switch
○ Use storm control on switch
25

26. www.glcnetworks.com
Ethernet issue: Loop
● A condition when frame is forwarded in the
media
● Will stop until one of cable is removed
● Some ideas:
○ Do not use traditional switch
○ activate STP between switch
○ Port isolation
26

27. www.glcnetworks.com
Layer 2 technology: Bonding
27

28. www.glcnetworks.com
Issue…
● Topology: A server/router connected to a switch with multiple interface
● Questions:
○ Can we doubled the capacity?
○ Which capacity traffic? Inbound or outbound?
28

29. www.glcnetworks.com
analyses
● Guys… you really need to know how the layer 2 works!!
● Outbound traffic
○ It is possible to send data from multiple interface
○ Problem with TCP sequence? -> low performance?
● Inbound traffic
○ Can an IP address attached on both interfaces?
○ Can a MAC address attached on both interfaces?
○ Incoming traffic is still problem?
29

30. www.glcnetworks.com
Proposed solution:
LACP (Link Aggregation Control Protocol)
● Defined by IEEE: 802.3ad -> IEEE 802.1AX.
● Requires layer 2 devices that support the standard -> the switch must
support this standard
● Increasing traffic for outbound and inbound
● Both server & switches needs to be configured to use LACP
30

31. www.glcnetworks.com
Additional to IEEE LACP
● Cisco: etherchannel, port aggregation protocol
● Juniper: aggregated ethernet
● Avaya: multi-link trunking
● BSD: lagg (Link AGGregation and fail-over)
● Solaris: link aggregation
● Linux: bonding, teaming
31

32. www.glcnetworks.com
What is bonding?
● A feature to combine multiple ethernet-like interfaces into a single virtual link
● Benefits:
○ Higher throughput
○ Failover
● Settings:
○ Setup bonding interface
○ Setup monitoring
32

33. www.glcnetworks.com
Link monitoring
● The bonding is broken when an individual link failed -> we need to enable a
link monitoring
● Option:
○ ARP monitoring -> recommended
○ MII monitoring -> depends on the driver
● CLI: /interface bonding set bonding1 link-monitoring=arp
arp-ip-targets=192.168.0.2
33

34. www.glcnetworks.com
Mode: 802.3ad
● Requires switch support
● Provide failover
● Outbound traffic: provide load balancing
● Inbound traffic: provide load balancing
● The best mode
34

35. www.glcnetworks.com
Mode: balance-rr
● Can use generic switch
● Provide failover
● Outbound traffic: load balancing using round-robin algorithm among slave
interfaces
● Inbound traffic: provide incoming load balancing if supported by switch.
otherwise only use single interface
● Packet may arrive out of order
35

36. www.glcnetworks.com
Mode: balance-XOR
● Can use generic switch
● Provide failover
● Outbound traffic: load balancing based on hash policy: src-mac XOR
dst-mac XOR packet-type-id
● Inbound traffic: provide incoming load balancing if supported by switch.
otherwise only use single interface
● To overcome out-of-order packet arrival
36

37. www.glcnetworks.com
Mode: broadcast
● Can use generic switch
● Provide failover
● Outbound traffic: no aggregation. Sending the same data over multiple
interface (each interface connected to partitioned broadcast domain)
● Inbound traffic: no aggregation
37

38. www.glcnetworks.com
Mode: active backup
● Can use generic switch
● Provide failover
● Outbound traffic: NO load balancing
● Inbound traffic: NO load balancing
38

39. www.glcnetworks.com
Mode: balance tlb
● Can use generic switch
● Provide failover
● Outbound traffic: provide transmit load balancing (tlb)
● Inbound traffic: only use single interface
39

40. www.glcnetworks.com
Mode: balance tlb (picture)
40

41. www.glcnetworks.com
Mode: balance alb
● Can use generic switch
● Provide failover
● Outbound traffic: provide transmit load balancing
● Inbound traffic: balance incoming traffic from local network peer
41

42. www.glcnetworks.com
Mode: balance alb (picture)
42

43. www.glcnetworks.com
LIVE practice
43

44. www.glcnetworks.com
preparation
● SSH client
● SSH parameters
○ SSH address
○ SSH port
○ SSH username
○ SSH password
44

45. www.glcnetworks.com
Q & A
45

46. www.glcnetworks.com
Interested? Just come to our training...
● Topics are arranged in systematic and logical way
● You will learn from experienced teacher
● Not only learn the materials, but also sharing experiences, best-practices, and
networking
46

47. www.glcnetworks.com
End of slides
● Thank you for your attention
● Please submit your feedback: http://bit.ly/glcfeedback
● Like our facebook page: https://www.facebook.com/glcnetworks
● Slide: http://www.slideshare.net/r41nbuw
● Recording (youtube): https://goo.gl/28ABHU
● Stay tune with our schedule
● Any questions?
47