Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

per-evi

date_range 11-Sep-24

Syntax

content_copy zoom_out_map
            per-evi;

Hierarchy Level

content_copy zoom_out_map
[edit interfaces interface-name esi df-election-granularity],
[edit interfaces interface-name unit logical-unit-number esi df-election-granularity]
        

Description

Enable the designated forwarder (DF) election granularity to support Ethernet segment ID (ESI) at the EVPN instance (EVI) level.

You can configure multiple access interfaces to support ESI at the EVI level between a multihomed customer edge (CE) device and its multihoming provider edge (PE) peer. When you configure the access interfaces in the same EVI with the same ESI and the per-evi statement, these interfaces will share the same designated forwarder (DF) election role. They will transition to the backup designated forwarder (BDF) role only if all the access interfaces within the EVI fail. This configuration avoids traffic disruptions caused by role changes due to a single interface failure in the EVI.

To enable the ESI at the EVI level support:

  • Configure a unique ESI at the EVI level.

    • [edit routing-instances routing-instance-name protocols evpn esi]

  • Configure the access logical interfaces (IFLs) with the same ESI value as the EVI.

    • [edit interfaces interface-name unit logical-unit-number esi]

    Note:

    Different IFLs under different physical interfaces (IFDs) can have the same ESI configured, but they must be part of the same bridge domain.

  • Configure the IFLs with the df-election-granularity option per-evi.

  • Configure the IFLs with the esi single-active option.

  • Configure the IFLs with the df-election-type option mod.

    Note:

    If you configure the the df-election-granularity per-evi option, you must also configure the df-election-type mod option without configuring a df-election-type preference option to prevent an error when committing the configuration.

The following shows snippets from a sample configuration:

content_copy zoom_out_map
user@MX960> show configuration interfaces 
ge-0/0/1 {
    vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 0 {
        encapsulation vlan-bridge;
        vlan-id 100;
        esi {
            00:11:11:11:11:11:11:11:11:11;
            single-active;
            df-election-granularity {
                per-evi;
            }
            df-election-type {
                mod;
            }
        }
    }
}
ge-0/0/2 {
    vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 0 {
        encapsulation vlan-bridge;
        vlan-id 100;
        esi {
            00:11:11:11:11:11:11:11:11:11;
            single-active;
            df-election-granularity {
                per-evi;
            }
            df-election-type {
                mod;
            }
        }
    }
}

user@MX960> show configuration routing-instances 
EVPN {
    instance-type evpn;
    protocols {
        evpn {
            esi {
                00:11:11:11:11:11:11:11:11:11;
            }
        }
    }
    vlan-id 100;
    interface ge-0/0/1.0;
    interface ge-0/0/2.0;
    route-distinguisher 10.255.0.1:100;
    vrf-target target:100:100;
}

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 24.2R1

footer-navigation