Hi @vin.marco ,
On startup, LDP looks at the routing table and if it sees a route to reach the LDP neighbor, it will attempts to bring up a session to that neighbor. In the meantime OSPF waits for LDP to establish the session. The issue happens when the route present in the routing table is either an aggregate or a default route and that route doesn't lead to that specific neighbor. The LDP session will obviously not come up. OSPF will wait forever by default or for the value configured with the command "mpls ldp igp sync holddown".
We can see in the output you provided that you use the default setting and OSPF will therefore wait for ever:
RMC4DFDI12002#sh mpls ldp igp sync
TenGigabitEthernet0/1/7:
LDP configured; LDP-IGP Synchronization enabled.
…
IGP holddown time: infinite.
One more thing. I see you have NSF configured on the above device. Here's a note from documentation about using NSF and the LDP IGP synchronization feature:
"MPLS LDP IGP Synchronization Incompatibility with IGP Nonstop Forwarding
The MPLS LDP IGP Synchronization feature is not supported during the startup period if the Interior Gateway Protocol (IGP) nonstop forwarding (NSF) is configured. The MPLS LDP IGP Synchronization feature conflicts with IGP NSF when the IGP is performing NSF during startup. After the NSF startup is complete, the MPLS LDP IGP Synchronization feature is supported."
Regards,
Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México