Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

device-attribute (Easy EVPN LAG Configuration)

Syntax

Hierarchy Level

Description

Specify device-specific parameters as part of a generated Ethernet VPN (EVPN) fabric configuration.

You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric with Ethernet segment identifier (ESI) link aggregation groups (LAGs) in the topology. The feature you enable with statements in this hierarchy is an easy EVPN LAG configuration feature, also called EZ-LAG.

You only need to configure a few statements to provide the parameters required for an EVPN core fabric with multihomed or single-homed customer edge (CE) devices (or end server devices). When you commit the [edit services evpn] configuration statements, the device uses a commit script to generate the corresponding standard EVPN fabric configuration statements.

The statements at the device-attribute hierarchy level provide parameters for configuration elements that are specific to:

  • The peer provider edge (PE) devices in the EVPN fabric.

  • Setting up LACP on the ESI LAG interfaces to multihomed customer edge (CE) devices (or end servers).

Options

loopback (peer1-subnet peer1-subnet peer2-subnet peer2-subnet)

Specify the device loopback IPv4 subnet address for each of the peer PE devices. The [edit services evpn] commit script uses the peer-id of the device on which it runs to derive the statements in the generated configuration for:

  • The router ID

  • The device overlay local address and peer neighbor address

Note:

The commit process doesn't do a commit check to enforce setting the same loopback subnet addresses across both devices. As a result, you should make sure to set the easy EVPN LAG configuration loopback peer1-subnet address to the same value on both peer PE devices, and likewise for the peer2-subnet address.

peer-id peer-id

Assign a unique identifier to the PE device among its peer PE devices in the EVPN fabric. The [edit services evpn] commit script uses this value to derive the statements to set values in the generated configuration that must be unique across the peer PE devices.

  • Values for peer-id: 1 or 2

system-id system-id

Specify the PE device's system ID, which is in the format of a MAC address. The [edit services evpn] commit script uses this value to derive statements to set up Link Aggregation Control Protocol (LACP) on the ESI LAG interfaces.

To configure LACP on an aggregated Ethernet interface in an ESI LAG, the commit script adds this system-id to the interface ESI parameter. The commit script uses that combined value as the LACP system-id in the generated LACP configuration statement. For example, if system-id is 10:11:12:13:14:10 and the interface ESI parameter is 1, the commit script generates the following statement in the configuration:

Note:

You set an aggregated Ethernet interface's ESI parameter using the esi-lag-id esi-lag-id statement at the [edit services evpn evpn-vxlan server server-name] hierarchy level.

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.