If you make your LSP with a strict path where it will not use the other IGP
path then you can use a forwarding table export policy to force the LSP as a
strict next next hop:
policy-statement name-of-policy {
term term-1 {
from <your match condition here>;
then {
install-nexthop strict lsp YOUR-LSP-NAME;
accept;
}
}
}
If the LSP fails the BGP route will disappear. I have tested this in the lab
but not at full table scale.
Kevin
> On Sep 13, 2016, at 6:26 PM, Rob Foehl <[email protected]> wrote:
>
> On Tue, 13 Sep 2016, Chuck Anderson wrote:
>
>> I guess I don't understand what you are trying to accomplish then.
>> Ttaffic engineering specific routes is exactly what RSVP is used for.
>> The MPLS path should be torn down if there is no available
>> RSVP-capable route. Did you try just not configuring RSVP on the
>> interfaces that can't support MPLS?
>
> The LSP is torn down; the BGP session carrying a bunch of routes for which
> that LSP is the only viable forwarding path survives. (RSVP is only
> configured where it ought to be, no "interfaces all" or anything like that.)
>
> The goal is for the BGP-learned routes to disappear along with the LSP --
> preferably by just tearing the session down with it, but otherwise
> invalidating the next-hops would suffice.
>
> I have another idea in my back pocket if this isn't workable, but that
> involves turning a bunch of P routers into full BGP RRs...
>
> -Rob
> _______________________________________________
> juniper-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
