Gotcha. I am familiar with using SLA to track a route, but there is still the issue of convergence within the ISPs. We implemented a similar configuration in my environment using AS prepend on the least favored link, but it takes several minutes to converge "globally."
Thanks for the link. On Mon, Dec 14, 2009 at 8:52 PM, <[email protected]> wrote: > have a look at the following URL.. > > http://www.ciscoblog.com/archives/2008/08/dynamic_failove.html > > Kind Regards, > Masood > Blogs: http://weblogs.com.pk/jahil/ > > > > Out of curiosity, what is ping based routing? > > > > 02 PM, jack daniels <[email protected]> wrote: > > > >> Hi , > >> > >> I can run any protocol , cant run tunnel as other side is client who > >> cant > >> make changes > >> > >> > >> > >> > >> On Sun, Dec 13, 2009 at 10:23 PM, Vincent C Jones < > >> [email protected]> wrote: > >> > >> > On Sun, 2009-12-13 at 21:06 +0530, jack daniels wrote: > >> > > I have a scenario - > >> > > > >> > > CE -------ISP1 > >> > > | > >> > > | > >> > > | > >> > > ISP2 > >> > > > >> > > users behind CE connect to remote application , > >> > > Now issue is if ISP1 LINK or ISP1 goes down I have times less than 4 > >> sec > >> > > for application to go via other link so that users are not imacted. > >> > > So can there be any solution for traffic to converge before 2 > >> request > >> > > timeouts , so that my application users are not impacted. > >> > > >> > There are a wide variety of solutions, but whether or not they will > >> work > >> > for you depends very much on both the specifics of the application and > >> > how you connect to your ISPs. Classic dual-homed BGP is not one of the > >> > solutions given your timeout requirements. "Ping based routing" may do > >> > the job if your user application can tolerate changing public IP > >> > addresses. If you have a presence at both ends of the public internet > >> > connection, you could also look at tunnel based solutions. > >> > > >> > -- > >> > Vincent C. Jones > >> > Networking Unlimited, Inc. > >> > Phone: +1 201 568-7810 > >> > [email protected] > >> > > >> > > >> > > >> _______________________________________________ > >> cisco-nsp mailing list [email protected] > >> https://puck.nether.net/mailman/listinfo/cisco-nsp > >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > >> > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
