[AusNOG] Mikrotik routers and "VLAN trunking over WAN"

[Andrew Cox]

My 2c

On MikroTik gear the optimal ways to do this sort of load balancing (with
reference to Ross's situation) are:
a) src based static routing (send VoIP vlan/ip-range via Link1, send Office
PC vlan/ip-range via Link2)
b) PCC based load-balancing (for 1 new connection-pair [based on src & dst
ip] send this out connection 1, next out 2, next out 1, next out 2)

There's older methods and more complex ways of going about it but these are
the 2 *best ways about it.

The PCC is best for balancing out over equal speed links and sharing
available bandwidth.

The src based is good for controlling the bandwidth and performance of a
given service type/group by explicitly defining what is allowed to go out
where (IE: voip should go out this 512k/512k L2 service by default and fail
over to a VPN path out the ADSL service)

Based on what you've asked Ross, I don't see any reason this would be a
problem provided properly resourced devices are spec'd.

Lastly: it's worth noting that this is all "Load-balancing" vs
"Aggregation".
Aggregating services would normally require an additional central point to
spit out the service at the other end, back out to your Layer3 link.

*IMO

Cheers,
Andrew


On 18 June 2014 13:30, Matt Ayre <matt.ayre at bigair.net.au> wrote:

> Re "out of order segments", that is why pretty much all modern platforms
> include L3/L4 data points for flow hashing, whether routing/forwarding or
> bundle load balancing.
>
> Even eeek MikroTik ;)
>
> Cheers,
> Matt
>
>
> On 18 June 2014 11:50, John Gavrilita <jgavrilita at thesummitgroup.com.au>
> wrote:
>
>> Hi Ross,
>> The first thing that crossed my mind is the inevitable situation when
>> packets will arrive out of order because the designed solution uses
>> bandwidth aggregation / load balancing. For TCP it's ok, but for UDP it'll
>> be a nightmare and the users will literally hear it.
>> Mikrotik is a nifty platform, and as with any other device, one has to
>> know how to cook it.
>> Cheers :)
>>
>>
>>
>>
>>
>> John Gavrilita
>> Network Engineer
>>
>> Summit IT Management | Summit Internet | Summit Creative - ‘reach your
>> peak’
>> Divisions of The Summit Group (Australia) Pty Ltd
>>
>> Phone (Australia):    1300 049 749
>> Phone (US & Canada): (321) 216 3844
>> E-mail:     jgavrilita at thesummitgroup.com.au
>> Internet:   http://www.thesummitgroup.com.au/
>> Address:   Level 1, 39 Railway Road, Blackburn  VIC  3130
>> Postal:      P.O. Box 3225, Doncaster East  VIC  3109
>>
>> -----Original Message-----
>> From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Ross
>> Wheeler
>> Sent: Wednesday, 18 June 2014 11:04 AM
>> To: ausnog at lists.ausnog.net
>> Subject: [AusNOG] Mikrotik routers and "VLAN trunking over WAN"
>>
>>
>> Looking for someone with Mikrotik experience to confirm which devices
>> (any? all?) might achieve the desired outcome here.
>>
>> Basically there are a number of sites of varying sizes, but for the
>> purposes of argument, lets say 20 sites.
>>
>> Most sites are proposed to have at least two diverse paths. These could
>> be ADSL, Microwave, 3G/4G/LTE etc. The point is, different providers,
>> different paths.
>>
>> Each site has it's (n) paths connected to interfaces on a Mikrotik router
>> which can aggregate bandwidth across (n) links (and reduce latency
>> somewhat) while providing an ability to withstand (n-1) link failures.
>>
>> The user further intends making extensive use of VLANs to "isolate"
>> services (eg, phones, computers, security devices, "public" devices etc).
>> Thus it would be entirely likely that there could be 40 switches at 20
>> sites, each with 10.10.8.0/22 for "phones" all on VLAN8.
>>
>> Not withstanding how YOU might do it, is there an intrinsic problem with
>> the design (or Mikrotik as the each sites 'edge device') as it stands?
>>
>> Thanks in advance,
>> RossW
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>>
>>
>>
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140618/e8bd1e43/attachment-0001.html>