ON THIS PAGE
Example: Configuring VNI Route Targets Automatically with Manual Override
This example shows how to automatically set route targets for multiple VNIs, and manually override the route target for a single VNI in an EVPN-VXLAN topology.
Requirements
This example uses the following hardware and software components:
A QFX Series switch.
Junos OS version 15.1X53-D30
Overview
You can configure the vrf-target statement to automatically derive
route targets for each VNI or you can configure route targets manually. You can also
manually override the auto-derived route target specifically for one or more VNIs.
This example explains how to enable auto-derivation of route targets and manually override the automatically assigned route targets for a specific VNI.
To manually assign a route target for a specific VNI, you configure the
vrf-target statement with a route target
value at either of the following hierarchy levels:
-
In the default switch instance—
[edit protocols evpn vni-options vni vni] -
In a configured routing instance—
[edit routing-instances name protocols evpn vni-options vni vni]
When you manually set a route target for a specific VNI, the setting applies only to EVPN Type 2 and Type 3 routes.
To set a route target for other EVPN route types, such as Type 1 routes, you must
also manually configure the vrf-target statement with a route
target value at the global level, as follows:
-
In the default switch instance—
[edit switch-options]hierarchy level -
In a configured routing instance—
[edit routing-instances name]hierarchy level
For EVPN Type 2 and Type 3 routes only, the auto route target
setting or a VNI level route target setting overrides a route target you set
manually at the global level.
Configuration
To manually override an automatically configured VNI route target, perform these tasks:
Configuring Automatic VNI Route Targets with Manual Override
Step-by-Step Procedure
To configure automatic VNI route targets with manual override:
-
At the
[switch-options]hierarchy level, configure thevtep-source-interface, androute-distiguisherstatements. Then configure thevrf-importstatement with a policy that will be configured in a later step. Next, configure thevrf-targetstatement with atargetand theautooption. The route target configured undervrf-targetwill be used by Type 1 EVPN routes and all Type 2 and Type 3 EVPN routes for all VLANs except the ones that do not match the VNI undervni-optionsin the next step.[edit switch-options] user@switch# set vtep-source-interface lo0.0 user@switch# set route-distinguisher 192.0.2.11:1 user@switch# set vrf-import import-policy user@switch# set vrf-target target:1111:11 user@switch# set vrf-target auto
-
The
[evpn]hierarchy level is where you can override the automatic assignment of VNI route targets. Configure thevni-optionsstatement for VNI 100 with an export target of 1234:11. This route target will be used by Type 2 and Type 3 EVPN routes for all VLANs that match VNI 100. Next, configure theencapsulationandextended-vni-liststatements. For the purposes of this example, theextended-vni-liststatement will be configured with only two VNIs.[edit protocols evpn] user@switch# set vni-options vni 100 vrf-target export target:1234:11 user@switch# set encapsulation vxlan user@switch# set extended-vni-list 100 101
-
Configure two communities at the
[edit policy-options community]hierarchy level. The first community is namedcomglobal, and the next community is namedcom1234. Configure an import policy at the[edit policy-options policy-statement]hierarchy level. The policy is namedimport-policy, which you apply in the first step in this procedure. The communities and policy function as an import filter that accepts routes using the auto-derived route target and the manual override route target.[edit policy-options community comglobal] user@switch# set members target:1111:11
[edit policy-options community com1234] user@switch# set members target:1234:11
[edit policy-options policy-statement import-policy] user@switch# set term 1 from community comglobal com1234 user@switch# set term 1 then accept user@switch# set term 100 then reject
Results
After following the steps above, use the show command to verify the results of your configuration.
user@switch> show configuration switch-options
vtep-source-interface lo0.0;
route-distinguisher 192.0.2.11:1;
vrf-import imp;
vrf-target {
target:1111:11;
auto;
}
user@switch> show configuration protocols evpn
vni-options {
vni 100 {
vrf-target export target:1234:11;
}
}
encapsulation vxlan;
extended-vni-list [ 100 101 ];
user@switch> show configuration policy-options community comglobal members target:1111:11;
user@switch> show configuration policy-options community com1234 members target:1234:11;
user@switch> show configuration policy-options policy-statement import-policy
term 1{
from community [ com1234 comglobal ];
then accept;
}
term 100 {
then reject;
}