VLAN ID Ranges and Lists in an EVPN Environment
You can specify VLAN ID lists and ranges in a service provider style of interface configuration that is referenced in an Ethernet VPN (EVPN) routing instance (a routing instance of type evpn). For more information, see the following topics:
Understanding VLAN ID Ranges and Lists in an EVPN Environment
The service provider style of interface configuration enables you to customize Ethernet-based services at the logical interface level. Service providers typically have multiple customers connected to the same physical interface or aggregated Ethernet interface. Using the service provider style, you can configure multiple logical interfaces on the physical interface or aggregated Ethernet interface and associate each unit with a different VLAN.
Starting in Junos OS Release 19.2R1, you can specify VLAN ID lists and ranges in a service provider style interface configuration that is referenced in an Ethernet VPN (EVPN) routing instance (a routing instance of type evpn). This configuration is supported with the following EVPN environments, services, and features:
Environments:
EVPN with Virtual Extensible LAN (VXLAN) encapsulation
EVPN with MPLS encapsulation
VLAN bundle service:
E-LAN
E-Tree
E-Line
Features:
EVPN multihoming
All-active
Single-active
Single homing
- Benefits of VLAN ID Range and List Support
- VLAN Bundle Service
- Sample VLAN ID Range and List Configuration
- Caveats and Limitations
Benefits of VLAN ID Range and List Support
Without the support of VLAN ID ranges and lists, you must configure a dedicated logical interface for each VLAN. VLAN ID range and list support enables you to associate multiple VLANs with a single logical interface. which reduces the overall number of logical interfaces needed. Using fewer logical interfaces provides these benefits:
Reduces the amount of configuration time
Reduces the amount of memory consumed
Reduces the impact to system performance
VLAN Bundle Service
The VLAN bundle service supports the mapping of multiple broadcast domains (VLANs) to a single bridge domain (MAC learning domain). You can associate multiple VLANs with a single EVPN routing instance. As a result, these broadcast domains (VLANs) share the same MAC table in the EVPN routing instance, thereby reducing the utilization of resources—for example, the number of MAC tables, MAC routes, and labels.
Sample VLAN ID Range and List Configuration
The following sample configuration shows a service provider style interface (interface xe-1/0/0 and logical interfaces xe-1/0/0.0 and xe-1/0/0.1) that is configured on a Juniper Networks device in an EVPN-VXLAN topology. The sample configuration also shows the EVPN routing instance (EVPN-VXLAN-3) in which logical interfaces xe-1/0/0.0 and xe-1/0/0.1 are referenced.
interfaces {
xe-1/0/0 {
unit 0 {
encapsulation vlan-bridge;
vlan-id-range 100-102;
family bridge;
}
unit 1 {
encapsulation vlan-bridge;
vlan-id-list [ 200-203 213 248 ];
family bridge;
}
}
}
routing-instances {
EVPN-VXLAN-3 {
description "EVPN-VXLAN Vlan Bundle service";
instance-type evpn;
vtep-source-interface lo0.0;
interface xe-1/0/0.0;
interface xe-1/0/0.1;
route-distinguisher 10.255.235.35:200;
vrf-target target:123:123;
protocols {
evpn {
encapsulation vxlan;
}
}
vxlan {
vni 551;
encapsulate-inner-vlan;
decapsulate-accept-inner-vlan;
}
}
}
In this configuration, logical interface xe-1/0/0.0 includes a VLAN ID range and logical interface xe-1/0/0.1 includes a VLAN ID list, which is comprised of a VLAN ID range and individual VLAN IDs. EVPN routing instance EVPN-VXLAN-3 references both logical interfaces.
Caveats and Limitations
When specifying VLAN ID ranges and lists in a service provider style interface configuration in an EVPN environment, keep these caveats and limitations in mind:
When specifying a range in either a VLAN ID range or list, you must use an ascending range—for example, 100-102. If you specify a descending range—for example, 102-100—the system considers the range to be invalid, and a commit error occurs.
Configuring VLAN ID Lists and Ranges in an EVPN Environment
Starting in Junos OS Release 19.2R1, you can specify VLAN ID lists and ranges in a service provider style of interface configuration that is referenced in an Ethernet VPN (EVPN) routing instance (a routing instance of type evpn).
This feature enables you to associate multiple VLANs with a single logical interface, thereby freeing you from having to configure a dedicated logical interface for each VLAN.
This feature works with the VLAN bundle service.
This procedure shows you how to specify multiple VLANs using VLAN ID ranges and lists in a service provider style interface configuration and to associate the interface with an EVPN routing instance.
The sample configurations that follow the procedure provide more comprehensive configurations of service provider style interfaces in an EVPN environment.
Sample Configuration: Multiple Logical Interfaces
This sample configuration shows aggregated Ethernet interface ae0, which is divided into logical interfaces ae0.100 and ae0.150. Logical interface ae0.100 is associated with VLANs ranging from 100 through 102. Logical interface ae0.150 is associated with a list of VLANs, which includes 150 through 152, 200, 213, and 248. EVPN routing instance EVPN-1 references both logical interfaces.
interfaces {
ae0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 100 {
encapsulation vlan-bridge;
vlan-id-range 100-102;
family bridge;
}
unit 150 {
encapsulation vlan-bridge;
vlan-id-list [ 150-152 200 213 248 ];
family bridge;
}
}
}
routing-instances {
EVPN-1 {
instance-type evpn;
interface ae0.100;
interface ae0.150;
route-distinguisher 192.160.0.1:111;
vrf-target target:65000:111;
protocols {
evpn;
}
}
}
Sample Configuration: Single Logical Interface
This sample configuration is similar to the multiple logical interface sample configuration except that aggregated Ethernet interface ae0 includes only one logical interface (ae0.150) with which all VLANs (100 through 102, 150 through 152, 200, 213, and 248) are associated. EVPN routing instance EVPN-1 references logical interface ae0.150.
interfaces {
ae0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 150 {
encapsulation vlan-bridge;
vlan-id-list [ 100-102 150-152 200 213 248 ];
family bridge;
}
}
}
routing-instances {
EVPN-1 {
instance-type evpn;
interface ae0.150;
route-distinguisher 192.160.0.1:111;
vrf-target target:65000:111;
protocols {
evpn;
}
}
}
Sample Configuration: E-Tree
This sample E-Tree configuration is similar to the other sample configurations except for some information specific to E-Tree use (for example, specifying each logical interface as either root or leaf, and enabling the EVPN-ETREE service).
interfaces {
ae0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 100 {
encapsulation vlan-bridge;
vlan-id-range 100-102;
family bridge;
etree-ac-role leaf;
}
unit 200 {
encapsulation vlan-bridge;
vlan-id-list [ 200 213 248 ];
family bridge;
etree-ac-role root;
}
}
}
routing-instances {
ETREE-1 {
instance-type evpn;
interface ae0.100;
interface ae0.200;
route-distinguisher 192.160.0.1:111;
vrf-target target:65000:111;
protocols {
evpn {
evpn-etree;
}
}
}
}
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.