Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


evpn (Easy EVPN LAG Configuration)


Hierarchy Level


Specify parameters to generate an Ethernet VPN (EVPN) fabric configuration with one or more customer edge (CE) devices or end servers that are:

  • Single-homed to a provider edge (PE) device in the EVPN fabric.

  • Multihomed on an Ethernet segment identified by an Ethernet segment identifier (ESI), and connected in a link aggregation group (LAG) to two or more PE devices in the EVPN Fabric.


    We refer to this type of multihomed Ethernet segment connection as an ESI LAG. The feature you enable with statements in this hierarchy is an easy EVPN LAG configuration feature, also called EZ-LAG.

You use the statements at this hierarchy level to simplify setting up EVPN fabrics with ESI LAG configurations. You only need to configure a few statements to provide the parameters required for an EVPN core fabric with interfaces that connect to multihomed or single-homed end devices.

When you commit the configuration, the device accesses a commit script. The commit script uses the parameters from the [edit services evpn] statements to generate an EVPN fabric configuration that includes:

  • Underlay and overlay peering configuration

  • EVPN instance configuration (using MAC-VRF instances)

  • Interfaces configuration for the ESI LAGs and IRB interfaces

  • Host VLAN configuration

  • Virtual routing and forwarding (VRF) routing instance, routing options, and policy options configurations

  • Additional feature configuration such as:

    • Lightweight leaf to server loop detection

    • DHCP Relay

    • Storm control

The commit script generates a prescribed default EVPN fabric configuration. For mandatory EVPN fabric elements, the commit script uses default values or requires you to specify values for which it doesn't have prescribed defaults. For other elements, the commit script uses default algorithms to derive the values from the configured statements.

For some elements, you can choose to override generating configuration statements for those elements, and omit them or manually configure them instead. You can also add other standard EVPN fabric statements to the configuration manually as needed.



Select options to skip statements that the commit script would otherwise include by default when it generates the configuration:

  • no-aggregate-device-count-config—Don't derive and include the aggregated Ethernet interface count in the generated configuration. You must manually configure the set chassis aggregated-devices ethernet device-count num statement on each peer PE device.

  • no-loop-detect-config—Don't derive and add statements for the lightweight loop detection feature in the generated configuration. You can optionally configure loop detection manually.

  • no-platform-defaults-config—Don't add the default statements for platform-specific options in the generated configuration. You must configure any required platform-specific statements manually.

  • no-policy-and-routing-options-config—Don't derive and include the default routing options and policy options in the generated configuration.

    If you set this option, you must configure either of the following:

    • A routing policy with the name EXPORT-LO0 using set policy-options policy-statement commands. By default, when generating the EBGP peering configuration on a peer PE device, the commit script applies a policy with that name to advertise the device loopback interface to the device's neighbors.

    • The no-underlay-config option at the [edit services evpn defaults-override] hierarchy level to override the default behavior to generate the underlay peering configuration. In that case, you must manually configure the statements you need to set up the underlay peering.

  • no-storm-control-config—Don't derive and include the storm control configuration elements. You can optionally configure storm control manually.

  • no-underlay-config—Don't derive and add the underlay peering statements in the generated configuration. if you specify this override option, you must manually include the underlay peering configuration you need.

The remaining statements are explained in detail on separate pages.

You can also consult CLI Explorer.

Required Privilege Level

system—To view this statement in the configuration.

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

Release Information

Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1.

The loopback-subnet option was deprecated and replaced by the loopback peer1-subnet and loopback peer2-subnet options starting in Junos OS and Junos OS Evolved Release 23.4R1.