EVPN-VXLAN RT communities
The general route target configured under vrf-target will be used by type 1 EVPN routes:
MX: set routing-instances VS_VLAN100 vrf-target target:1:100
QFX: set switch-options vrf-target target:65000:2
QFX: set switch-options vrf-target target:65000:2
If you configure vrf-target auto, then type 2 and type 3 EVPN routes will use the auto-derived per-VNI route target for export and import. Community numbers based on autonomous system number defined in routing-options stanza.
MX: set routing-instances VS_VLAN100 switch-options vrf-target auto
QFX: set switch-options vrf-target auto
QFX: set switch-options vrf-target auto
If you prefer to use manual per-VNI route-target assignments, then you should configure it in protocols evpn section:
MX: set routing-instances VS_VLAN100 protocols evpn vni-options vni 1 vrf-target export target:10003:1
QFX: set protocols evpn vni-options vni 1 vrf-target export target:10003:1
QFX: set protocols evpn vni-options vni 1 vrf-target export target:10003:1
So you have three options to configure VNI RT assignments:
- Configure only general vrf-target statement (under switch-options/routing-instances stanza) – this RT will be used for all EVPN route-types.
- Configure general vrf-target statement and vrf-target auto – general RT will be used for EVPN type 1 routes, per-VNI RTs will be auto-derived (using AS number from routing options) for each VNI and used for type 2 and type 3 EVPN routes.
- Configure general vrf-target statement and specific vrf-target – general RT will be used for EVPN type 1 routes, configured specific per-VNI RTs will be used for each VNI.
I think it’s possible to mix this three types of RT assignments – most specific one will be applied. Need to check it in the lab.