[j-nsp] labeled-unicast to ldp redistribution ?

[Andrey Kostin]

Hi Alexandre,

Not sure that I completely understood the issue. When connectivity 
between islands recovers, what is the primary route for regular BGP 
routes' protocol next-hop? Looks like it should be OSPF with route 
preference lower than BGP and in this case it should be labeled by LDP 
and propagated. Only if OSPF route for a protocol next-hop is not the 
best, the next-hop from BGP-LU will be used.

Kind regards,
Andrey Kostin

Alexandre Snarskii via juniper-nsp писал(а) 2021-12-17 12:29:
> Hi!
> 
> Scenario: router is a part of ospf/ldp island and also have ibgp
> labeled-unicast rib inet.3 link to other ospf/ldp island. In normal
> situations, some routes are known through ospf/ldp, however, during
> failures they may appear from ibgp-lu and redistributed to ldp just
> fine. However, when failure ends and route is known via ospf/ldp again,
> it's NOT actually in use. Instead, 'show ldp route extensive' shows
> this route as:
> 
>    Ingress route status: Inactive
>    Route type: Egress route, BGP labeled route
>    Route flags: Route deaggregate
> 
> and there are only ibgp route[s] in inet.3 table.
> 
> Are there any way to make ldp ignore 'BGP labeled' flag and install
> route to inet.3 ? (other than making all routes be known not only
> via ospf/ldp but also via ibgp-lu too).
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp