I vote for #1 and #3. Both should give you fast fault detection.
> On Jun 30, 2015, at 4:09 AM, Peter Ehiwe <petereh...@gmail.com> wrote: > > Possible options : > 1) link bundling technologies And run single ebgp session over the > bundle > 2) two ebgp sessions with shorter keep Alive > 3) two ebgp sessions with bfd > > Sent from a mobile . > > On Tuesday, June 30, 2015, Mohammad Khalil <eng.m...@gmail.com> wrote: > >> Hi all >> I have a case where my router is connected to the upstream provider via two >> physical links , we decided to configured eBGP over a loopback interface >> The issue is that when the remote peer goes down (over which I have learned >> the loopback from through static routing) , the route will still be >> installed in my routing table (because from my side it's up) , so I will >> lose connectivity and my eBGP neighbor will go down >> So , what is the best redundancy solution I can implement so that I will >> not lose my peering and switch over to the other static route without >> disrupting my service? >> >> Thanks >> >> BR, >> Mohammad >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net <javascript:;> >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > -- > Sent from Mobile > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp