Hello Vikrant,
from what we see we don't know if you have advertised each router loopback address in OSPF.
You need to perform this in order for the LDP session to be established, because it is a TCP session between the loopbacks.
Note: if not using /32 subnets in the loopbacks in OSPF you need to add
int loop0
ip ospf network point-to-point
in order to advertise the effective subnet mask of the loopback (this is important for correct MPLS forwarding plane), otherwise instead of implicit null POP action you would see untagged in show mpls forwarding <remote-PE-loop-addr>
In global config mode you need to enable MPLS and you can also enforce the use of the loopback as LDP router-id with the following:
mpls ip
mpls ldp router-id loop0 force
As suggested by Harold output of show mpls ldp discovery can be used to validate LDP configuration it shows you the LDP router-id on the local node and the status of MPLS LDP discovery on each MPLS enabled interface.
A good state is xmit/receive.
Hope to help
Giuseppe
