[j-nsp] discard route resolveability in BGP path selection?

[Damon Pegg]

So, for clarity, the default is that all routes are considered viable for
next-hop-availability, including another bgp route, or is bgp excluded?

In either event, since most of us carry the aggregates and some a default,
what is the default scan-time and can I change it?  I know I can change the
BGP timers but its naturally a much better solution to have a low scan
interval for next-hop validation check...

damon.

> -----Original Message-----
> From: Daniel Roesen [mailto:dr at cluenet.de]
> Sent: 27 February 2004 02:07
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] discard route resolveability in BGP path 
> selection?
> 
> 
> On Thu, Feb 26, 2004 at 05:27:18PM -0800, Pedro Roque Marques wrote:
> > dr at cluenet.de (Daniel Roesen) writes:
> > > set protocols bgp group foo protocol ospf
> > > 
> > > This makes next-hop resolution consider only OSPF-learned routes.
> > > 
> > That option doesn't do anything in releases > 5.0. It has 
> been removed
> > (hidden) in latest releases.
> 
> Uhm, not really:
> 
> # set protocols bgp group foo ?
> Possible completions:
> [...]
>   protocol             IGP to use to resolve the next hop
> [...]
> 
> This is 6.2R1.5
> 
> And the 6.2 docs still contain it too:
> http://www.juniper.net/techpubs/software/junos/junos62/swconfi
g62-routing/html/bgp-summary38.html#1015141

With no mentioning that it's without effect.


Regards,
Daniel
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp