Scribd
Upload
223 views25 pages

Load Balance Traffic MikroTik

This document discusses using BGP and MPLS to aggregate load balance traffic across multiple backbone links. It provides examples of using MikroTik routers with MPLS and BGP configurations to load balance traffic between a core site in Jakarta and a remote subnet. The key steps outlined are preparing the links, creating a VPLS, setting up BGP peering with routing filters, adding firewall rules for sticky connections, and verifying the load balancing works as intended.

Uploaded by

Adhie Lesmana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
223 views25 pages

Load Balance Traffic MikroTik

This document discusses using BGP and MPLS to aggregate load balance traffic across multiple backbone links. It provides examples of using MikroTik routers with MPLS and BGP configurations to load balance traffic between a core site in Jakarta and a remote subnet. The key steps outlined are preparing the links, creating a VPLS, setting up BGP peering with routing filters, adding firewall rules for sticky connections, and verifying the load balancing works as intended.

Uploaded by

Adhie Lesmana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

Aggregate Load Balance with BGP and MPLS

MUM ID 2018 | 19 – 20 Oktober 2018


Yogyakarta, Indonesia
 Firdhyan Adhie Lesmana
 Adhielesmana.com
 LapakWifi.com
 DNS Premium
 ( www.facebook.com/dnspremium )
 Forum MikroTik Indonesia

 ISP Operations Manager


 PowerNet Liberia, West Africa.

 MikroTik Certified Trainer & Consultant


 PowerNet Training Center, Liberia

 Facebook:
 www.facebook.com/adhielesmana

 Whatsapp :
 +6289660206541 ( ID ) / +231777306097 ( LR )

2
 Aggregating traffic for two or more backbone link.

 Increase Total Backbone capacity.

 Traffic Aggregate Solution

 Not “Internet” Load Balance

3
FIREWALL STICKY CONN

5 KM LINK 1 VIA PTP WIRELESS 1


BGP + FILTER

EDGE CORE OFFICE NOC DISTRIBUTION


5 KM LINK 2 VIA PTP WIRELESS 2

BGP + FILTER
FIREWALL STICKY CONN

4
TUN-VPN + MPLS-VPLS
FIREWALL STICKY CONN

LINK 1 VIA ISP RED


BGP + FILTER

CORE REMOTE
JAKARTA SUBNET DISTRIBUTION
LINK 2 VIA ISP BLUE

BGP + FILTER
TUN-VPN + MPLS-VPLS FIREWALL STICKY CONN
BRIDGE
VPLS + ETHER
BGP + FILTER

FIREWALL STICKY CONN

BRIDGE
VPLS + ETHER

6
 Cost Efficient

 Support Redundancy / Failover

 Load Sharing / Aggregate Traffic

 Easy Maintenance & Troubleshoot

 MPLS is faster than EoIP, Less CPU and Less protocol overhead
7
 MikroTik Router ( Both Locations )

 Support MPLS, VPN, BGP, OSPF etc.

 Backbone Link

 Wireless Backbone

 Fiber Broadband ( Tunnel )

8
 1. Prepare Link  3. Setup BGP
 Make sure link established  Setup IP for VPLS interface
and traffic can passed.
 Create BGP peering in VPLS
 We can use Wireless
Backbone or Tunnel via  Additional Route Filter Rules.
Fiber Broadband
 4. Firewall & Mark Routing
 2. Create VPLS  Rule for Sticky Connections.
 MPLS - VPLS on each router
 Bridge with Ethernet *

9
 Mode AP
 AP Bridge or Bridge
 ap + wds if station using wds
 Bridged with Ethernet

 Mode Station
 Station Bridge or Station WDS
 Bridged with Ethernet

10
 Server PPTP / L2TP
 Setup PPP Profile and Secret for Client PPP User Password
 Use PTP Addressing /32 instead of IP Pool.

 Client PPTP / L2TP


 Dial VPN Tunnel
 Check IP
 Test Connection, Ping to neighbor PTP IP address

11
 Create VPLS links between point to point router.
 Follow this information about VPLS
 https://wiki.mikrotik.com/wiki/Manual:MPLSVPLS
 Require OSPF
 Require Loopback IP and Interfaces
 Join to MTCINE Training to learn BGP and MPLS Topic

12
 Create Interface Bridge ( For Topology 3 )
 add VPLS and Ethernet on Bridge.
 For topology 1 and 2 we don’t need bridge

13
 Once the link is established and both router is reacheable.

 Create BGP peering between both locations and each link.

 Create new Routing Filter with custom action parameter.

 Assign the routing filter on BGP Instance

14
 Make Incoming BGP
Route Filter.
 Make ICMP to Each
Opposite routers IP
 Apply Route filter on
Core and Remote Router

15
 Assign the Route filter to BGP Peers configuration
 Establishing the BGP Peers

16
 Routing Result from BGP + Routing Filter
 Result on Remote Router

17
 Result on Core Router

18
 Add new firewall mangle and mark route all incoming traffic from
each WAN interfaces.
 Create new routing mark for each Gateway following the routing mark
from ip firewall mangle.
 Do this on both end.

19
20
21
22
 Result on Remote Router
 Load Balance Aggregated Traffic.
 No NAT
 Packet go and comes with origin IP addresses
 No src-address changes even when the routing path changes
 Normally in load-balance our src-address always changes

23
 Result on MAIN CORE Router

24
 Q&A
 Thanks To MikroTik
 ClickMediaNet - Blora

25

You might also like