On Friday, March 14, 2014 11:08:39 AM Lukas Tribus wrote: > I would say one of the major drawbacks with LAG is that > the links need to be connected to a single box on the > other site, while with ECMP you can connect links to > different boxes and as long as the cost are equal, you > will load-balance.
Also, on some platforms, QoS needs to be applied on member links, and can't be applied on the LAG bundle itself. I try to stay away from such platforms if I can, or make sure this isn't an operational concern, e.g., placing it on core- rather then customer-facing ports. As of now, with Cisco and Juniper, all major features are supported on LAG bundles, e.g., QoS, MPLS, IPv6, BFD, MPLS- TE, data plane filters, e.t.c. Just make sure all the features you have on regular interfaces are supported on LAG bundles. This development is not always one-to-one. Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
