nanog mailing list archives
Re: Multiple ISP Load Balancing
From: Jonathan Lassoff <jof () thejof com>
Date: Wed, 14 Dec 2011 11:38:35 -0800
The best applications for analyzing paths, that I've seen, have been in-house development projects. So, admittedly, I don't have much experience with commercial products for route optimization. Projects I've seen that analyze "best" paths to Internet destinations via multiple ISPs add instrumentation to content-serving applications to log stream performance details to a database or log collection system along with a timestamp. Another database keeps a periodic log of RIB data that lists the specific next-hops out of the AS. Another log keeps a running log of UPDATEs.
From joining up all of this information, you can figure out the ISP you're
taking to a destination (at a given time) and how the stream performed. Then, add some logic to inject routes to try out different next-hop ISPs for some destinations. Then, compare the newer ISP-path to the older one and see which performs "best". Where "best" means something specific to your application (optimizing for latency, cost, etc.) Cheers, jof
Current thread:
- Multiple ISP Load Balancing Holmes,David A (Dec 14)
- RE: Multiple ISP Load Balancing Drew Weaver (Dec 14)
- Re: Multiple ISP Load Balancing Christopher Morrow (Dec 14)
- RE: Multiple ISP Load Balancing Drew Weaver (Dec 14)
- Re: Multiple ISP Load Balancing Christopher Morrow (Dec 14)
- Re: Multiple ISP Load Balancing Jonathan Lassoff (Dec 14)
- RE: Multiple ISP Load Balancing Jeff Tantsura (Dec 14)
- Re: Multiple ISP Load Balancing Justin M. Streiner (Dec 14)
- RE: Multiple ISP Load Balancing Rampley Jr, Jim F (Dec 14)
- RE: Multiple ISP Load Balancing Drew Weaver (Dec 15)
- RE: Multiple ISP Load Balancing Rampley Jr, Jim F (Dec 14)
- RE: Multiple ISP Load Balancing Drew Weaver (Dec 14)