[c-nsp] mpls and etherchannel

George Giannousopoulos ggiannou at gmail.com
Wed Apr 20 17:00:23 EDT 2016


Assuming that these devices are just P routers in your MPLS network, load
balancing between these two will be based on the bottom label(VC label).

So the only way to see traffic load balancing, is to have several different
EoMPLS pseudowires with different bottom labels.. The fewer you have, the
less the chances to see load balancing across your links.

Alternatively, if your PE routers support FAT pseudowires(eg ASR9K), you
could activate it and then load balancing will take place based on the flow
label. Of course that assumes your traffic is able to be split into
different flows..

Another alternative MPLS TE, where you statically specify which path to use
for each pseudowire. I don't recommend it though.. Not worth the
administrative burden.

If your devices are operating as PE routers, normally you'll be able to
load balance across your links on the egress direction without problems,
since the decision for the egress interface happens before adding the MPLS

Hope that helps..


On Wed, Apr 20, 2016 at 11:00 PM, Mike <mike-cisconsplist at tiedyenetworks.com
> wrote:

> On 04/20/2016 11:12 AM, Lukas Tribus wrote:
>> Clarify:
>> - what platforms are you using (the LSR's doing ECMP or port-channeling
>>    on those 2 wireless bridges)?
>> - what will your traffic look like once on mpls (unlabeled IP, vpnv4 or
>> l2vpn)?
>>         The platform would be ASR920 on one side and ME3600 on the other,
> and the bulk of the traffic will be l2vpn running thru it.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list