On 15/Mar/18 12:18, [email protected] wrote:
> Maybe you might start looking at some scaling techniques when you'll have a > need to transport multiple paths for a prefix for load-sharing or > primary-backup use cases, say to reduce internet convergence times form 2 > mins down to less than 1ms (MX with 2M prefixes). As I mentioned to Saku, we already do load balancing at the IGP/LDP layer. We don't need multiple paths in BGP to achieve that. It works well. The NEXT_HOP is abstracted for BGP destinations at the edge, so installing an alternate path does not take 2 minutes. It's instant. We've got a highly distributed (peering) edge, so a customer-serving router will not lose the entire Internet in one go, unless that device suffers a catastrophe itself. Mark. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
