folks, we see an increasing number of TAC cases relating to forwarding issues in MPLS/VPN scenarios (including 6vPE).
Starting in XR release 4.2.0 we have a functionality that is called Selective VRF download which will only install routes for vrf's on those linecards
that are interested in it. It seggregates between customer/edge and core facing LC's. The benefit is that if you have lower FIB scale cards on your edge with one LC supporting vrf X and another LC supporting vrf Y, then the LC supporting X would not get the FIB/LFIB tables for vrf Y.
Core facing LC's will have both.
Now it doesn't only pertain to FIB entries but also LPTS entries and if you are getting say a packet in mpls encapped for a vrf a particular receiving LC may not have the proper LPTS directives for it. One workaround is to create a dummy subinterface and put it in the vrf that you are expecting this for to pierce that hole.
In general however we recommend to DISABLE svd for asr9000, which unfortunately requires a reload on teh LC's to activate that change.
You can track the SVD state via show svd [state|role]
We're working to make this off by default starting a release (not defined yet) but in the interim the story above applies.
