Hello hakenkreuz,
there is another VPNv4 path that is considered best
>> 200.89.30.21 (metric 2) (via default) from 200.89.30.21 (200.89.30.21)
Origin IGP, metric 0, localpref 100, valid, confed-internal, >>>>best
Extended Community: >>>>>RT:14187:1081
mpls labels in/out 1325/7695
But note it is using a different RT value RT:14187:1081 that your local VRF does not import.
You can fix this by adding
vrf FA
route-target import 14187:1081
on your local PE node if that route is a valid and expected advertisement
it tells also the best path has no local table to import it
>> PE#show bgp vpnv4 unicast RD 1418:1081 10.253.13.80/29
BGP routing table entry for 1418:1081:10.253.13.80/29, version 214911496
Paths: (2 available, best #2, no table)
This path is preferred because of higher local preference 100 compared to local pref 50 for path 1.
Another way to fix it is to increase the local preference on VPNv4 routes received by neighbor 200.85.229.11.
To be noted path1 is an eBGP MP in AF VPNv4 (external)
path 2 comes from a BGP confederation (confed internal)
Hope to help
Giuseppe
