[j-nsp] Next-Hop Verification for static route WITHOUT BFD

[Stefan Stoyanov]

Hi Alex,

Try to check if "ip-monitoring" will fits your needs. (
https://kb.juniper.net/InfoCenter/index?page=content&id=KB25052  )

On Tue, Oct 25, 2016 at 8:20 PM, Alexander Marhold <alexander.marhold at gmx.at
> wrote:

> Hi !
>
>
>
> In the old Junoe E router we could use RTR to verify a next-hop for a
> static
> route when the neighbor is not able or willing to do BFD
>
>
>
> host1(config)#ip route 10.1.1.5 255.255.255.0 10.1.1.5 fastEthernet 1/0
> verify rtr 5 last-resort
>
>
>
> I do not find any good example of doing this on a MX.
>
>
>
> I need such a solution to change the BGP next-hop on an interface when the
> interface is always up, but the necessary next-hop on this multipoint
> interface is not reachable
>
>
>
> The successor of RTR namely ip-monitoring is not able to this in a simple
> way.
>
> Maybe any special policy or event-policy or an event-script can help here?
>
> Or a unknown way to redistribute the static route to OSPF only when the
> next-hop is reachable vis ip monitoring ?
>
>
>
> So if you have a practical way to do this please tell.
>
> To clarify it is not a matter of milliseconds, it is a matter of seconds
>
>
>
> What I want to achieve is that when the next-hop of this static route is
> not
> reachable, the static route is not readvertised into OSPF anymore and a
> second MX then looses the primary BGP next-hop and can then divert the BGP
> traffic to secondary Peer and next-hop.
>
>
>
> Many thanks in advance for your ideas and solutions
>
>
>
> Alexander Marhold
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>