Hello,
@kr3ator wrote:
@ aarseniev
On 16.1 vMX I cannot configure a virtual link crossing a NSSA area, commit fails.
This is correct behavior as per RFC 2328.
@kr3ator wrote:
on vSRX it is totally possible and it works fine, all the FECs get installed in all routers.
This is incorrect behaviour and shall be eventually fixed so do not rely on that in Your designs.
@kr3ator wrote:
Other question I have that is related to this case is on what grounds LDP selects an RSVP tunnel as a next hop in "show ldp route" ?
When I lookup LDP database on one of the routers I can see that it has learnt a LDP label over ldp-tunnelling enabled RSVP, but it does not install it into inet.3 (and hence do not advertise it to its LDP native neighbor) because in "show ldp route" I can see that LDP chose the same interface as OSPF and selected a RSVP tunnel to the nearest next-hop over that interface (a node that doesn't do LDP or tunneling).
Again, this is correct behaviour. LDP does not have own loop preventing mechanism and relies on OSPF loop prevention. In simple words: LDP choses the same outgoing logical interface as OSPF. If that interface does not belong to LDP, then LDP does not install this route.
As for Your other experiment with forcing the RSVP path over specific interface and expecting the LDP will get tunneled - I wonder what You are trying to achieve here? LDP does not tunnel own lo0 on the RSVP ingress LSR itself. Any LDP bindings that exist beyond ingress LSR are tunneled.
Please review the topology and LDP/RSVP relationship in the below link
https://www.juniper.net/documentation/en_US/junos16.1/topics/example/vpn-ldp-over-rsvp-topology-configuring.html
HTH
Thx
Alex