I wonder if this convergence time issue wouldn't be a typical mission for «BGP PIC Edge for MPLS Layer 3 VPNs». But it would be necessary to migrate the DFZ to a VPN MPLS (and configure composite nexthop and BGP PIC / «Provider Edge Link Protection»).
> Le 24 mai 2018 à 09:20, Vincent Bernat <ber...@luffy.cx> a écrit : > > This feature is already enabled on MX with MPC cards. > > ――――――― Original Message ――――――― > From: Adam Kajtar <akaj...@wadsworthcity.org> > Sent: 23 mai 2018 23:21 -0400 > Subject: Re: Juniper BGP Convergence Time > To: Mark Tinka > Cc: nanog@nanog.org > >> Hello again: >> >> I've tried using the default route, adjusting bgp timers, and mutlipath. >> Unfortunately, these changes haven't helped much. Juniper support hasn't >> been very helpful also. Although, I think I might have found the solution. >> >> https://www.juniper.net/documentation/en_US/junos/topics/topic-map/forwarding-indirect-next-hop.html >> >> Let me know what you think. >> >> On Tue, May 22, 2018, 4:03 AM Mark Tinka <mark.ti...@seacom.mu> wrote: >> >>> >>> >>> On 16/May/18 18:59, Phil Lavin wrote: >>> >>> Ask if they will configure BFD for you. I’ve not found many transit >>> providers that will, but it’s worth a shot and it will lower failure >>> detection to circa 1 second. >>> >>> We've tended to shy away from it, but we have 2 customers we've done it >>> for.
