- play_arrow EVPN-VXLAN
- play_arrow Overview
- Understanding EVPN with VXLAN Data Plane Encapsulation
- EVPN-over-VXLAN Supported Functionality
- Understanding VXLANs
- VXLAN Constraints on EX Series, QFX Series, PTX Series, and ACX Series Devices
- EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches
- Implementing EVPN-VXLAN for Data Centers
- PIM NSR and Unified ISSU Support for VXLAN Overview
- Routing IPv6 Data Traffic through an EVPN-VXLAN Network with an IPv4 Underlay
- Understanding How to Configure VXLANs and Layer 3 Logical Interfaces to Interoperate
- Understanding GBP Profiles
- play_arrow Configuring EVPN-VXLAN Interfaces
- Understanding Flexible Ethernet Services Support With EVPN-VXLAN
- EVPN-VXLAN Lightweight Leaf to Server Loop Detection
- Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks
- Overlapping VLAN Support Using Multiple Forwarding Instances or VLAN Normalization
- Layer 2 Protocol Tunneling over VXLAN Tunnels in EVPN-VXLAN Bridged Overlay Networks
- MAC Filtering, Storm Control, and Port Mirroring Support in an EVPN-VXLAN Environment
- Example: Micro and Macro Segmentation using Group Based Policy in a VXLAN
- DHCP Smart Relay in EVPN-VXLAN
- play_arrow Configuring VLAN-Aware Bundle Services, VLAN-Based Services, and Virtual Switch Support
- play_arrow Load Balancing with EVPN-VXLAN Multihoming
- play_arrow Setting Up a Layer 3 VXLAN Gateway
- play_arrow Configuring an EVPN-VXLAN Centrally-Routed Bridged Overlay
- play_arrow Configuring an EVPN-VXLAN Edge-Routed Bridging Overlay
- play_arrow IPv6 Underlay for VXLAN Overlays
- play_arrow Multicast Features with EVPN-VXLAN
- Multicast Support in EVPN-VXLAN Overlay Networks
- Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment
- Example: Preserving Bandwidth with IGMP Snooping in an EVPN-VXLAN Environment
- Overview of Selective Multicast Forwarding
- Configuring the number of SMET Nexthops
- Assisted Replication Multicast Optimization in EVPN Networks
- Optimized Intersubnet Multicast in EVPN Networks
- play_arrow Configuring the Tunneling of Q-in-Q Traffic
- play_arrow Tunnel Traffic Inspection on SRX Series Devices
- play_arrow Fault Detection and Isolation in EVPN-VXLAN Fabrics
-
- play_arrow EVPN-MPLS
- play_arrow Overview
- play_arrow Convergence in an EVPN MPLS Network
- play_arrow Pseudowire Termination at an EVPN
- play_arrow Configuring the Distribution of Routes
- Configuring an IGP on the PE and P Routers on EX9200 Switches
- Configuring IBGP Sessions Between PE Routers in VPNs on EX9200 Switches
- Configuring a Signaling Protocol and LSPs for VPNs on EX9200 Switches
- Configuring Entropy Labels
- Configuring Control Word for EVPN-MPLS
- Understanding P2MPs LSP for the EVPN Inclusive Provider Tunnel
- Configuring Bud Node Support
- play_arrow Configuring VLAN Services and Virtual Switch Support
- play_arrow Configuring Integrated Bridging and Routing
- EVPN with IRB Solution Overview
- An EVPN with IRB Solution on EX9200 Switches Overview
- Anycast Gateways
- Configuring EVPN with IRB Solution
- Configuring an EVPN with IRB Solution on EX9200 Switches
- Example: Configuring EVPN with IRB Solution
- Example: Configuring an EVPN with IRB Solution on EX9200 Switches
- play_arrow Configuring IGMP or MLD Snooping with EVPN-MPLS
-
- play_arrow EVPN E-LAN Services
- play_arrow EVPN-VPWS
- play_arrow Configuring VPWS Service with EVPN Mechanisms
- Overview of VPWS with EVPN Signaling Mechanisms
- Control word for EVPN-VPWS
- Overview of Flexible Cross-Connect Support on VPWS with EVPN
- Overview of Headend Termination for EVPN VPWS for Business Services
- Configuring VPWS with EVPN Signaling Mechanisms
- Example: Configuring VPWS with EVPN Signaling Mechanisms
- FAT Flow Labels in EVPN-VPWS Routing Instances
- Configuring EVPN-VPWS over SRv6
- Configuring Micro-SIDs in EVPN-VPWS
-
- play_arrow EVPN-ETREE
- play_arrow Overview
- play_arrow Configuring EVPN-ETREE
-
- play_arrow Using EVPN for Interconnection
- play_arrow Interconnecting VXLAN Data Centers With EVPN
- play_arrow Interconnecting EVPN-VXLAN Data Centers Through an EVPN-MPLS WAN
- play_arrow Extending a Junos Fusion Enterprise Using EVPN-MPLS
-
- play_arrow PBB-EVPN
- play_arrow Configuring PBB-EVPN Integration
- play_arrow Configuring MAC Pinning for PBB-EVPNs
-
- play_arrow EVPN Standards
- play_arrow Supported EVPN Standards
-
- play_arrow VXLAN-Only Features
- play_arrow Flexible VXLAN Tunnels
- play_arrow Static VXLAN
-
- play_arrow Configuration Statements and Operational Commands
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 levelIn 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-distiguisher
statements. Then configure thevrf-import
statement with a policy that will be configured in a later step. Next, configure thevrf-target
statement with atarget
and theauto
option. The route target configured undervrf-target
will 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-options
in the next step.content_copy zoom_out_map[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-options
statement 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 theencapsulation
andextended-vni-list
statements. For the purposes of this example, theextended-vni-list
statement will be configured with only two VNIs.content_copy zoom_out_map[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.content_copy zoom_out_map[edit policy-options community comglobal] user@switch# set members target:1111:11
content_copy zoom_out_map[edit policy-options community com1234] user@switch# set members target:1234:11
content_copy zoom_out_map[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; }