Hi Shabbir,
Assuming 192.168.1.1 and 192.168.1.2 correspond to lo0.100 addresses on both PE routers, you should be able to ping one from another with your configuration below.
However, if those correspond to IP's of fe-0/0/1.0 and your problem is indeed being unable to export the whole directly connected subnet within a VRF (hence the need for vrf-table-label to force an IP lookup on top of the MPLS label lookup), then you might be hitting one of the limitations described here
Also, you'll need something like the following to completely export direct prefixes, as the whole subnet:
set routing-instances test routing-options interface-routes family inet export lan
Another option to advertise the connected if you can't/don't want to use vrf-table-label, is to use vt-interfaces (created with the presence of a tunnel/services PIC in the router) with something like this (again, along with the code above) :
set interfaces vt-1/2/0 unit 0 family inet
set routing-instances test interface vt-1/2/0.0
The last suggestion I'd have is to check whether you need vrf-import and vrf-export statements in your configuration at all. What you've configured in your example is the default behavior (with the exception of locally connected prefixes, which I've explained the requirements to advertise them) anyways.
Hope this helps,
Erdem
____________________________________________
If you think your question's answered, please
mark the respective post as "Accepted Solution".
Kudos are an excellent way of showing appreciation, too.
- you're best option is to try to get a hold of PB-4E3 PICs that do support vrf-table-label.
