Same physical setup as the previous lab, the important point to note here, is that if a you are using VPNv4 for route exchange between ASes, hence Inter-AS, then you have to disable BGP's default behavior of filter route-targets that it doesn't need. "Doesn't need" meaning no interfaces that are configured for that VRF.
R2 and R4 are "PEs" and they sit in 2 different BGP ASes, the eBGP peer in the VPNv4 AFI (MP-eBGP) but they won't have the VPNv4 routes from their respective PEs since they don't have interfaces in the particular VRFs. This means those VPNv4 routes are filter until you disable the feature.
Configs:
R2
R2#sh run | b router bgp
router bgp 1
no bgp default ipv4-unicast
no bgp default route-target filter
bgp log-neighbor-changes
neighbor 150.1.3.3 remote-as 1
neighbor 150.1.3.3 update-source Loopback0
neighbor 150.1.24.4 remote-as 2
!
address-family vpnv4
neighbor 150.1.3.3 activate
neighbor 150.1.3.3 send-community extended
neighbor 150.1.3.3 next-hop-self
neighbor 150.1.24.4 activate <- notice there's no "next-hop-self" because ebgp next hop is the
neighbor 150.1.24.4 send-community extended neighbor
exit-address-family
!
R4
router bgp 2
no bgp default ipv4-unicast
no bgp default route-target filter
bgp log-neighbor-changes
neighbor 150.1.6.6 remote-as 2
neighbor 150.1.6.6 update-source Loopback0
neighbor 150.1.24.2 remote-as 1
!
address-family vpnv4
neighbor 150.1.6.6 activate
neighbor 150.1.6.6 send-community extended
neighbor 150.1.6.6 next-hop-self
neighbor 150.1.24.2 activate
neighbor 150.1.24.2 send-community extended
exit-address-family
!
