Yes vrf-target export and vrf-target import overrides vrf-target target:x:x
Please use vrf-import and vrf-export instead of vrf-target import and vrf-target export, using this you can use multiple RT's
for import and export.
Only difference is you have to do via policy.
An example for vrf-import
routing-instances SITE-1 vrf-import import-vpn-A
policy-options{
policy-statement import-vpn-a {
term 1 {
from {
protocol bgp ; <<<< THIS IS always bgp as vrf routes are imported from bgp.l3vpn.0
community vpn-a;
}
then {
accept;
}
}
}
community vpn-a member target:7777:1111;
community vpn-a member target:4:4;
An example for vrf-export
routing-instances SITE-1 vrf-export export-vpn-A
If BGP is the PE-CE protocol
policy-options{
policy-statement export-vpn-a {
term 1 {
from {
protocol [bgp direct];
}
then
{
community add vpn-a;
}
}
}
If OSPF is the PE-CE protocol
policy-options{
policy-statement export-vpn-a {
term 1 {
from {
protocol [ospf direct];
}
then
{
community add vpn-a;
}
}
}
community vpn-a member target:7777:1111;
community vpn-a member target:4:4;
One of these targets can be your route-leak target(common between the leaked instances) and the other can be the target specific to the particular vrf....
Please rever back if you face any issues