[c-nsp] ECMP v Link Aggregation ofr MPLS

[Ivan]

Thanks to all have responded so far.  Adam, what features were not
available for you when using LAG and what platform are you using?

Cheers

Ivan

> As mentioned just make sure LAG on your platforms will allow you to use
> all the features you require on your backbone.
> That's why we had to go the ECMP way -the drawback is more IGP routes.
>
> adam
>> -----Original Message-----
>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
>> Keegan Holley
>> Sent: Friday, March 14, 2014 12:29 AM
>> To: Ivan
>> Cc: cisco-nsp at puck.nether.net
>> Subject: Re: [c-nsp] ECMP v Link Aggregation ofr MPLS
>>
>> It depends on your platform, traffic and code versions.  Aggregated
>> links and
>> MLAG are the better option since they are simpler.  However they are
>> more
>> susceptible to bugs on certain platforms and traffic spread of course
>> depends
>> what kind of traffic flows will traversing the links.  It's also easier
>> to remove
>> links from service with ECMP.  If you're a transit AS you probably have
>> enough diversity to ensure an even spread.  All things considered I'd
>> choose
>> aggregated links as well.
>>
>> On Mar 13, 2014, at 4:28 PM, Ivan <cisco-nsp at itpro.co.nz> wrote:
>>
>> > So we are crossing the bridge to >10Gbps for some MPLS core links.  I
>> > am trying to work out if it is better to use aggregated links or ECMP.
>> > If anyone has any experience or recommendation it would be much
>> appreciated.
>> >
>> > Thanks
>> >
>> > Ivan
>> >
>> > _______________________________________________
>> > 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/
>>
>>
>> _______________________________________________
>> 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/
>