On 30/Jul/17 11:06, [email protected] wrote:
> The LACP QOS is a moot point, there's no right and wrong way of doing the > split. Doubling the bandwidth because the policer programs as such each member link is definitely the wrong way. The biggest trick with policing a LAG is that the load balancing has to be (near) perfect. Without that, it becomes tricky, or at worst, means that you only support LAG policing for traffic that is easy to hash across multiple member links. Either way, hitherto, Juniper do it better than Cisco. That said, it's still a complicated process, so we've found other ways to solve the issue. Mark. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
