- play_arrow Features Common to EVPN-VXLAN, EVPN-MPLS, and EVPN-VPWS
- play_arrow Configuring Interfaces
- play_arrow MAC Address Features with EVPN Networks
- play_arrow Configuring Routing Instances for EVPN
- Configuring EVPN Routing Instances
- Configuring EVPN Routing Instances on EX9200 Switches
- MAC-VRF Routing Instance Type Overview
- EVPN Type 5 Route with VXLAN Encapsulation for EVPN-VXLAN
- EVPN Type 5 Route with MPLS encapsulation for EVPN-MPLS
- Understanding EVPN Pure Type 5 Routes
- Seamless VXLAN Stitching with Symmetric EVPN Type 2 Routes using Data Center Interconnect
- Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics
- EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN
- Ingress Virtual Machine Traffic Optimization
- Tracing EVPN Traffic and Operations
- Migrating From BGP VPLS to EVPN Overview
- Configuring EVPN over Transport Class Tunnels
- Example: Configuring EVPN-VPWS over Transport Class Tunnels
- play_arrow Configuring Route Targets
- play_arrow Routing Policies for EVPN
- play_arrow Layer 3 Gateways with Integrated Routing and Bridging for EVPN Overlays
- play_arrow EVPN Multihoming
- EVPN Multihoming Overview
- EVPN Multihoming Designated Forwarder Election
- Understanding Automatically Generated ESIs in EVPN Networks
- Easy EVPN LAG (EZ-LAG) Configuration
- Configuring EVPN Active-Standby Multihoming to a Single PE Device
- Configuring EVPN-MPLS Active-Standby Multihoming
- Example: Configuring Basic EVPN-MPLS Active-Standby Multihoming
- Example: Configuring EVPN-MPLS Active-Standby Multihoming
- Example: Configuring Basic EVPN Active-Active Multihoming
- Example: Configuring EVPN Active-Active Multihoming
- Example: Configuring LACP for EVPN Active-Active Multihoming
- Example: Configuring LACP for EVPN VXLAN Active-Active Multihoming
- Example: Configuring an ESI on a Logical Interface With EVPN-MPLS Multihoming
- Configuring Dynamic List Next Hop
- play_arrow Link States and Network Isolation Conditions in EVPN Networks
- play_arrow EVPN Proxy ARP and ARP Suppression, and NDP and NDP Suppression
- play_arrow Configuring DHCP Relay Agents
- play_arrow High Availability in EVPN
- play_arrow Monitoring EVPN Networks
- play_arrow Layer 2 Control Protocol Transparency
-
- 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
Overlapping VLAN Support Using Multiple Forwarding Instances or VLAN Normalization
In platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) deployments, each customer uses a separate physical interface to connect to a leaf device. In this situation, you can't use the same VLAN ID for two different tenants in separate MAC-VRF instances that share the same default forwarding instance. However, you can have a VLAN name with the same VLAN-ID (for example, vlan200 with VLAN ID 200) in two different MAC-VRF instances if they each have their own forwarding instances. You can also configure explicit or implicit VLAN normalization using service provider style interface configuration.
You can configure forwarding instance identifiers on the QFX10000 line of switches and ACX7100-32C and ACX7100-48L devices.
We support overlapping VLANs on some platforms that don’t support multiple forwarding instances. See Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks for more information.
On the QFX10000 line of switches, you can configure up to 99 forwarding instance identifiers.
On ACX7100-32C and ACX7100-48L devices, you can configure up to 6 forwarding instances.
Overlapping VLANs Using the Enterprise Style Interface Configuration
Overlapping VLANs with Multiple Forwarding Instances
This configuration allows overlapping VLAN-ID 200 in different MAC-VRF instances by configuring separate forwarding instances.
set interfaces et-0/0/20:3 unit 0 family ethernet-switching interface-mode trunk set interfaces et-0/0/20:3 unit 0 family ethernet-switching vlan members vlan200 set interfaces et-0/0/0:0 unit 0 family ethernet-switching interface-mode trunk set interfaces et-0/0/0:0 unit 0 family ethernet-switching vlan members vlan200 set routing-instances MAC-VRF1 instance-type mac-vrf set routing-instances MAC-VRF1 forwarding-instance identifier 1 set routing-instances MAC-VRF1 interface et-0/0/20:3.0 set routing-instances MAC-VRF1 vlans vlan200 vlan-id 200 set routing-instances MAC-VRF1 vlans vlan200 vxlan vni 200 set routing-instances MAC-VRF2 instance-type mac-vrf set routing-instances MAC-VRF2 forwarding-instance identifier 2 set routing-instances MAC-VRF2 interface et-0/0/0:0.0 set routing-instances MAC-VRF2 vlans vlan200 vlan-id 200 set routing-instances MAC-VRF2 vlans vlan200 vxlan vni 2000
Overlapping VLANs Using the Service Provider Interface Style Configuration
- Implicit Normalization With VLAN ID Sample Configuration
- Implicit Normalization with VLAN ID None Sample Configuration
- Explicit Normalization with VLAN Maps
- Multiple Forwarding Instances Sample Configuration
Implicit Normalization With VLAN ID Sample Configuration
This configuration implicitly translates the customer VLAN ID to the VLAN ID specified in the bridge domain upon ingress. At egress, the VLAN ID used to normalize the bridge domain is removed, and the customer VLAN ID is pushed onto the frame. In this case, the overlapping VLAN IDs of 150 are mapped to VLAN ID 200 and 400, respectively. In this example, the subscriber traffic is transported over the EVPN core using VXLAN VNI assignments that match the normalized VLAN IDs.
set interfaces et-0/0/20:3 flexible-vlan-tagging set interfaces et-0/0/20:3 unit 150 encapsulation vlan-bridges set interfaces et-0/0/20:3 unit 150 vlan-id 150 set interfaces et-0/0/0 flexible-vlan-tagging set interfaces et-0/0/0 unit 150 encapsulation vlan-bridge set interfaces et-0/0/0 unit 150 vlan-id 150 set routing-instances VS1 vlans vlan200 vlan-id 200 set routing-instances VS1 vlans vlan200 interface et-0/0/20:3.150 set routing-instances VS1 vlans vlan200 vxlan vni 200 set routing-instances VS2 vlans vlan400 vlan-id 400 set routing-instances VS2 vlans vlan400 interface et-0/0/0:0.150 set routing-instances VS2 vlans vlan400 vxlan vni 400
Implicit Normalization with VLAN ID None Sample Configuration
This configuration implicitly normalizes the two overlapping customer VLANs to unique VLAN IDs within their respective bridge domains. At ingress, the customer VLAN ID is stripped and the (now) untagged traffic is transported over the EVPN VXLAN fabric. At egress on the customer interface, the VLAN tag is pushed back onto the frame. In the EVPN core, the two customer VLANs, which both use VLAN ID 150, map to VXLAN VNIs 200 and 400, respectively.
set interfaces et-0/0/20:3 flexible-vlan-tagging set interfaces et-0/0/20:3 unit 150 encapsulation vlan-bridge set interfaces et-0/0/20:3 unit 150 vlan-id 150 set interfaces et-0/0/0 flexible-vlan-tagging set interfaces et-0/0/0 unit 150 encapsulation vlan-bridge set interfaces et-0/0/0 unit 150 vlan-id 150 set routing-instances MAC-VRF1 vlans vlan200 vlan-id none set routing-instances MAC-VRF1 vlans vlan200 interface et-0/0/20:3.150 set routing-instances MAC-VRF1 vlans vlan200 vxlan vni 200 set routing-instances MAC-VRF2 vlans vlan400 vlan-id none set routing-instances MAC-VRF2 vlans vlan400 interface et-0/0/0:0.150 set routing-instances MAC-VRF2 vlans vlan400 vxlan vni 400
Explicit Normalization with VLAN Maps
Explicit normalization does not specify a VLAN ID in the bridge domain. Instead, VLAN map operations are used to manipulate the VLAN label stack to achieve the desired normalization. In this example, two customers use the same VLAN ID of 150. The input and output maps applied to the interface explicitly swap the customer tag with the normalized assignments used in the provider network. In the egress direction, the swap operation causes the interface's VLAN tag to be swapped onto the frame.
Explicit normalization is needed when using the vlan-bundle service type
for the instance.
set interfaces ge-2/0/4 flexible-vlan-tagging set interfaces ge-2/0/4 unit 150 encapsulation vlan-bridge set interfaces ge-2/0/4 unit 150 vlan-id 150 set interfaces ge-2/0/4 unit 150 input-vlan-map swap set interfaces ge-2/0/4 unit 150 input-vlan-map vlan-id 200 set interfaces ge-2/0/4 unit 150 output-vlan-map swap set interfaces ge-2/0/10 flexible-vlan-tagging set interfaces ge-2/0/10 unit 150 encapsulation vlan-bridge set interfaces ge-2/0/10 unit 150 vlan-id 150 set interfaces ge-2/0/10 unit 150 input-vlan-map swap set interfaces ge-2/0/10 unit 150 input-vlan-map vlan-id 400 set interfaces ge-2/0/10 unit 150 output-vlan-map swap set routing-instances VS4 instance-type mac-vrf set routing-instances VS4 protocols evpn encapsulation vxlan set routing-instances VS4 protocols evpn multicast-mode ingress-replication set routing-instances VS4 vtep-source-interface lo0.0 set routing-instances VS4 bridge-domains vlanBundle-1 interface ge-2/0/4.150 set routing-instances VS4 bridge-domains vlanBundle-1 vxlan vni 200 set routing-instances VS4 bridge-domains vlanBundle-1 vxlan ingress-node-replication set routing-instances VS4 service-type vlan-bundle set routing-instances VS4 route-distinguisher 10.1.0.1:4 set routing-instances VS4 vrf-target target:10:4 set routing-instances VS5 instance-type mac-vrf set routing-instances VS5 protocols evpn encapsulation vxlan set routing-instances VS5 protocols evpn multicast-mode ingress-replication set routing-instances VS5 vtep-source-interface lo0.0 set routing-instances VS5 bridge-domains vlanBundle-1 interface ge-2/0/10.150 set routing-instances VS5 bridge-domains vlanBundle-1 vxlan vni 400 set routing-instances VS5 bridge-domains vlanBundle-1 vxlan ingress-node-replication set routing-instances VS5 service-type vlan-bundle set routing-instances VS5 route-distinguisher 10.1.0.1:5 set routing-instances VS5 vrf-target target:10:5
Multiple Forwarding Instances Sample Configuration
This configuration is similar to the enterprise style interface configuration. You use separate forwarding instances to allow overlapping VLAN-ID 200 in different MAC-VRF instances.
set interfaces et-0/0/20:3 flexible-vlan-tagging set interfaces et-0/0/20:3 unit 200 encapsulation vlan-bridge set interfaces et-0/0/20:3 unit 200 vlan-id 200 set interfaces et-0/0/0 flexible-vlan-tagging set interfaces et-0/0/0 unit 200 encapsulation vlan-bridge set interfaces et-0/0/0 unit 200 vlan-id 200 set interfaces et-0/0/1 flexible-vlan-tagging set interfaces et-0/0/1 unit 200 encapsulation vlan-bridge set interfaces et-0/0/1 unit 200 vlan-id-list 1000-2000 set routing-instances MAC-VRF1 instance-type mac-vrf set routing-instances MAC-VRF1 forwarding-instance identifier 1 set routing-instances MAC-VRF1 vlans vlan200 vlan-id 200 set routing-instances MAC-VRF1 vlans vlan200 interface et-0/0/20:3.200 set routing-instances MAC-VRF1 vlans vlan200 vxlan vni 200 set routing-instances MAC-VRF2 instance-type mac-vrf set routing-instances MAC-VRF2 forwarding-instance identifier 2 set routing-instances MAC-VRF2 vlans vlan200 vlan-id 200 set routing-instances MAC-VRF2 vlans vlan200 interface et-0/0/0:0.200 set routing-instances MAC-VRF2 vlans vlan200 interface et-0/0/1.200 set routing-instances MAC-VRF2 vlans vlan200 vxlan vni 2000
