Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

peer-subnet (Easy EVPN LAG Configuration)

Syntax

Hierarchy Level

Description

Specify interface parameters for the peer-to-peer connections between Ethernet VPN (EVPN) fabric provider edge (PE) devices as part of a generated 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 [edit services evpn device-attribute peer-to-peer peer-subnet] hierarchy level provide the interface names and subnet addresses for the interfaces that connect the peer PE devices in the fabric. The commit script uses these parameters to generate the required statements to configure the aggregated Ethernet interfaces and underlay peering in the EVPN fabric.

You must provide an inet or an inet6 subnet address (or both) for the aggregated Ethernet interface links between the peer PE devices.

For configuration simplicity, you configure the same subnet address on both peer PE devices. By default, the commit script derives a different interface address on each peer PE device based on that device's peer ID, as follows:

  • If the peer ID is 1, the commit script uses the subnet address provided.

  • Otherwise, the commit script uses the subnet address + 1 (adds 1 to the low order segment of the subnet range).

For example, if you specify inet-address as 10.0.1.0/31:

  • Peer ID 1 peer-to-peer link address = 10.0.1.0

  • Peer ID 2 peer-to-peer link address = 10.0.1.1

Note:

The commit process doesn't do a commit check to enforce setting the same subnet address across both devices. As a result, we strongly recommend that you make sure when you configure this subnet-address statement, you use the same base value on both peer PE devices. That way the default address derivation works as expected for the peer-to-peer interface addresses on each peer PE device.

Options

inet inet-address

The IPv4 subnet address for the interfaces or aggregated Ethernet interfaces that connect the PE device to a peer PE device. You should configure the same subnet address for this option on both peer PE devices.

inet6 inet6-address

The IPv6 subnet address for the interfaces or aggregated Ethernet interfaces that connect the PE device to a peer PE device. You should configure the same subnet address for this option on both peer PE devices.
(Required) interface-name [interface-name ... ]

The interface or interfaces that connect the PE device to a peer PE device.

See CLI Explorer for more on other related statements.

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.

Related Documentation