Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Supported Routing Instance Types and Services for EVPN-ELAN

Supported EVPN E-LAN Instance Types

EVPN E-LAN instance types supported across all Juniper platforms are:

  • mac-vrf—Provides all 3 services (vlan-based, vlan-bundle, vlan-aware bundle) associated with a single EVPN instance (EVI).

  • evpn—Provides vlan-based and vlan-bundle services for an EVI.

  • virtual-switch—Provides vlan-aware bundle service for an EVI.

Note:

ACX Series devices running Junos OS Evolved support only the mac-vrf instance type.

Supported EVPN E-LAN Services

Table 1: Supported EVPN E-LAN Services

Services

MAC-VRF

EVPN

VIRTUAL-SWITCH

Control word enabled by default (see control-word)

Yes

No

No

VLAN normalization or no normalization (see no-normalization)

Yes

Yes

No

Default normalization (Protocols EVPN)

no-normalization

normalization

N/A

Full RFC7432 compliance

Yes

Yes

Yes

Core isolation (see Understanding When to Disable EVPN-VXLAN Core Isolation)

Yes

Yes

Yes

Junos OS and Junos OS Evolved Configuration Differences

See this section for configuration differences between normalization and no-normalization on Junos OS and Junos OS Evolved.

Consider the following examples where two provider edge (PE) devices represent different ESIs, and their connected customer edge (CE) devices are part of the same VLAN.

Table 2 depicts use cases with no normalization to prevent VLAN translation for traffic transiting between PEs. The device that uses the evpn instance type must specify no-normalization. The device that uses the mac-vrf instance type doesn't specify normalization since that is the configuration default.

Table 2: Configuration Differences with No Normalization

Junos OS

Junos OS Evolved

 
user@PE3# show routing-instances
evpn-vlan-based {
     instance-type evpn;
     protocols {
          evpn;
     }
     vlan-id none;
     no-normalization;
. . .
}
 
user@PE1# show routing-instances
evpn-vlan-based {
     instance-type mac-vrf;
     protocols {
          evpn {
           no-control-word;
           encapsulation mpls;
          }
     }
     service-type vlan-based;
. . .
}

Table 3 illustrates a scenario where normalization is desired. The device that uses the evpn instance type has normalization as the device's default behavior. On the device that uses the mac-vrf instance type, you must specify normalization.

Table 3: Configuration Differences with Normalization

Junos OS

Junos OS Evolved

 
user@PE3# show routing-instances
evpn-vlan-based {
     instance-type evpn;
     protocols {
          evpn;
     }
     vlan-id 20;
. . .
}
 
user@PE1# show routing-instances
evpn-vlan-based {
     instance-type mac-vrf;
     protocols {
          evpn {
           normalization;
           no-control-word;
           encapsulation mpls;
          }
     }
     service-type vlan-based;
. . .
}