NX-OS vrf bgp local-as interaction with L3vpn

Question

I use standard MPLS BGP-L3vpn to forward traffic between VRFs on Nexus 7k routers.  All of my VRFs are within the same BGP process, so have the same local-as.
I'd like to bring-up an eBGP session from one VRF to a carrier, but the carriers requires that they peer with a specific BGP ASN (call it "65432").  It doesn't look like NX-OS supports the "router bgp 1234, vrf VRF1 neighbor w.x.y.z local-as 65432" command.  However, it does appear to support "router bgp 1234, vrf VRF1, local-as 65432".  
My limited understanding is that this would prepend "65432" onto all routes advertised to all VRF1 neighbors?  And that all neighbors defined under VRF1 on this router would learn routes from me with as-path "^65432 1234 ..."?
If so, would this have any affect on routes exchanged with other VRFs using import/export rd? 

Answer 1

It's tricky given that BGP's AD is always going to beat out EIGRP's all other things being equal. Most of the things you can do with BGP route-maps involve making one BGP route preferred over another.
You could inject the preferred path as a static route (AD = 1) to the firewall using an ip sla operation and having the static route track that. Once the ip sla operation fails, the static route is withdrawn and then the BGP-learned route (AD = 20) will take precedence.