Then we enable the LDP on that tunnel:
mpls ldp
router-id 20.20.20.1
nsr
graceful-restart
session protection
label
advertise
disable
for LOOPBACK_0
!
!
interface tunnel-te15

Yes, with AToM just configuring the xconnect command initiates the targeted LDP session, but with TE it is a little different (remember that the most common scenario that you require LDP with TE is when the tunnel is terminated on a P router, we can have a latter post discussing this in details), with TE it depends on the scenario, if you have just one tunnel from the head-end to the tail-end thus you’ll need to instruct the tail-end router to accept the LDP targeted session using the “mpls ldp discovery targeted-hello accept” command, while if you had bidirectional TE tunnels setup, in this case having “mpls ip” under both tunnel interfaces initiates the session for you.

I hope that I’ve been informative.

BR,
Mohammed Mahmoud.

‘In the AToM and TE cases you don’t need to use the previous command because the session will be established automatically after adding the service required configuration’

When is the targetted LDP initated in the above case?

Can you give some examples of such commands? xconnect?