[j-nsp] JUNOS resolves indirect next-hops using other BGP routes
david.roy at orange-ftgroup.com
david.roy at orange-ftgroup.com
Wed Feb 4 09:08:19 EST 2009
Yes I understand, you want is to disable recursive lookup, but I believe that you can't do that.
Just for information could you give me the output of the command :
show route resolution 195.18.241.97 extensive
Thanks
Regards
David
-----Message d'origine-----
De : Tore Anderson [mailto:tore at linpro.no]
Envoyé : mercredi 4 février 2009 14:53
À : ROY David DTF/DERX
Cc : juniper-nsp at puck.nether.net
Objet : Re: [j-nsp] JUNOS resolves indirect next-hops using other BGP routes
* david.roy at orange-ftgroup.com
> The protocol next-hop seems to be resolvable : but it is not directly
> known in our IGP. So you have a recursive lookup til you find a
> forwarding next-hop.
Yes, exactly. What surprises me, however, is that EGP routes is considered at all when resolving indirect next-hops of iBGP routes. I have problems coming up with a scenario where that behaviour would be desireable, and the JUNOS documentation I quoted is also quite clear on the fact that it is intra-AS OSPF, IS-IS, RIP, or static routes that are supposed be used for next-hop resolving.
The behaviour I expect (and want) is for routes that come with a next-hop that is not resolvable through my IGP should be ignored outright and _not_ be placed in the PFE, even though the next-hop is resolvable using a BGP route.
Regards,
--
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
More information about the juniper-nsp
mailing list