[j-nsp] JUNOS Equivalent to CISCO IOS next-hop-self

[Daniel Roesen]

On Mon, Oct 20, 2003 at 07:04:35PM -0600, Danny McPherson wrote:
> > Uhm, route reflectors MUST NOT change NEXT_HOP of reflected routes.
> > Otherwise it might lead to routing loops. Can you outline an example
> > of where setting NEXT_HOP to self on a route reflector for reflected
> > routes makes sense, so that a "SHOULD NOT" is justified instead of a
> > "MUST NOT"?
> 
> Yes, I can think of several!

Care to explain one?

> >> As such, you could enable setting of NEXT_HOP to self on a peering
> >> session and only locally generated and EBGP learned routes will be
> >> effected, NOT reflected routes.
> >
> > No, this is only the case for IOS, not for JunOS. Junos "then next-hop
> > self" _unconditionally_ overwrites the NEXT_HOP, no matter where the
> > route came from (local, EBGP, or IBGP [route reflection]). This is
> > the problem at hand.
> 
> Ahh, hence my language above.  If this is indeed the case, I'd say
> Juniper SHOULD fix this..

Well, if you stick to "SHOULD NOT" for overwriting next-hops for
reflected routes, and you're saying (see above) that you know scenarios
where setting next-hop self for reflected routes makes sense, then
Juniper MUST NOT "fix" this in order not to remove the option to do so.


Best regards,
Daniel