I have a router and have configured multiple VRFs. I was also able to leak routes between the global routing table and one of the VRFs (VRF data) successfully.
Now, I have not been able to leak the loopback address of the VRF data (220.127.116.11) into the global routing table, so I can ping the VRF loopback address from the global routing table.
I have also read this article:
Has any one experienced this before?
Attached is the config
If VRF select is not supported, you can create a fake route-map and apply it to the loopback interface:
set vrf data
int loopback 0
ip policy route-map FAKE
ip vrf receive data