server (Easy EVPN LAG Configuration)

Syntax

Hierarchy Level

Description

Specify parameters to generate the configuration statements for servers connected to a provider edge (PE) device in an Ethernet VPN (EVPN) fabric with Virtual Extensible LAN (VXLAN) encapsulation.

The server might be a customer edge (CE) device or end server connected to the EVPN PE device, and can be:

Single-homed to the PE device.
Multihomed on an Ethernet segment (identified by an Ethernet segment identifier [ESI]) in a link aggregation group (LAG) to the PE device and a peer PE device in the EVPN fabric.

Note:
We refer to this type of multihomed Ethernet segment connection as an ESI LAG.

You use statements at the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric with ESI 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 evpn-vxlan server] hierarchy level provide the parameters the commit script needs to generate a default configuration for the peer PE to server connections, including configuration for:

Multihomed server Etehrnet segments, ESI LAG interfaces and member VLANs
Single-homed server interfaces and member VLANs
Lightweight leaf to server loop detection on interfaces connecting PE leaf devices to servers

Note:
To disable generation of the loop detection configuration statements, you can configure the no-loop-detect-config option at the [edit service evpn defaults-override] hierarchy level.
Storm control on PE to server interfaces

Note:
To disable generation of the storm control configuration statements, you can configure the no-storm-control-config option at the [edit service evpn defaults-override] hierarchy level.

Options

(Required) `name`	Specify a name to identify a server connected to the peer PE device. For example, SERVER_1 or hostA.
apply-config-groups `config-groups`	Apply the specified configuration groups to the configuration for the server aggregated Ethernet interface bundles that the commit script generates from the statements for this server.
enable-pxe-boot	Enable this connected server to use a preboot execution environment (PXE) boot process. When you set this option set, the commit script configures LACP `force-up` status on the link to the server. That status ensures the link is UP when the server boots up, which the PXE boot process requires. See Aggregated Ethernet Interfaces for more on the LACP `force-up` option and forcing LAG links or interfaces with limited LACP capacity to be up.
(Required) esi-lag-id `esi-lag-id`	Assign an ESI LAG connection ID for this server. With this option, the commit script generates the configuration statements for an ESI LAG connection from the PE device to this multihomed server. The commit script assigns aggregated Ethernet interfaces (ae`X`) on the peer PE device for ESI LAG connected servers starting with the base number 0. The commit script adds the `esi-lag-id` value to that base. For example, if you configure `esi-lag-id` = 2 for this server, the generated configuration uses interface name ae2. Note: The commit script uses ae0 for the peer to peer PE devices connections, so ae0 is never assigned as a PE-device-to-server ESI LAG interface. You must configure this option or the `single-home-id` option for each connected server. Range for `esi-lag-id`: 1 through 1024 (which generates interface names ae1 through ae1024)
(Required) interface [ `interface-name` ... ];	Specify the interface name for the physical link or links from the peer PE device to this multihomed or single-homed server. Use this option with the `esi-lag-id` option or the `single-home-id` option that identifies this connected server.
mac-vrf-instance `instance-id`	Specify a MAC-VRF instance identifier that hosts this server. By default, if you don't configure this statement, the commit script generates the configuration for one MAC-VRF instance with 1 as the default MAC-VRF `instance-id`. If you include the `vlan-id-list vlan-id-list` option with this statement, the commit script generates configuration statements that associate this MAC-VRF instance with the listed server VLANs. Note: If you don't configure the `mac-vrf-instance` statement, you must configure the `vlan-id-list vlan-id-list` statement at the `[edit services evpn evpn-vxlan server name]` hierarchy level with at least one member VLAN. The commit script generates configuration statements that associate that list of VLANs with the default MAC-VRF instance (which has `instance-id` 1 and instance name __SERVICES_EVPN_EVPN_VXLAN_MAC_VRF_1). See the description for the `vlan-id-list` option below for details on how to specify the list of VLAN IDs. Range for `instance-id`: 1 through 255
(Required) single-home-id `single-home-id`	Assign a single-homed connection ID for this server. With this option, the commit script generates the configuration statements for a connection from the PE device to this single-homed server. The commit script assigns aggregated Ethernet interface names on the peer PE device for single-homed server connections. The highest `esi-lag-id` index for interfaces to multihomed servers is 1024, which corresponds to interface name ae1024. So to assign interface names for links to single-homed servers, the commit script adds the `single-home-id` value to the base number 1024. As a result, single-homed server interface names start with ae1025 for `single-home-id` = 1 . If you configure `single-home-id` = 2, the generated configuration uses interface name ae1026, and so on. You must configure this option or the `esi-lag-id` option for each connected server. Range for `single-home-id`: 1 through 1024 (which generates interface names ae1025 through ae2048)
vlan-id-list [ `vlan-id-number` ... ]	(Required) List the VLANs this server hosts. Specify one or more VLANs by VLAN ID number. Use spaces to separate multiple individual VLAN IDs (such as [100 200], or use a dash to indicate a contiguous range of VLAN IDs (such as [100-300]). The commit script generates the statements that configure the specified VLANs. You must configure at least one VLAN ID list for each server. You can configure the server's `vlan-id-list` statement at either of the following hierarchy levels: `[edit services evpn evpn-vxlan server name mac-vrf-instance instance-id]`—Associate the listed VLANs with the MAC-VRF instance for the specified instance ID in the generated configuration . `[edit services evpn evpn-vxlan server name]`—Associate the listed VLANs with: The default MAC-VRF instance ID, which is 1. The commit script uses MAC-VRF instance ID 1 when you don't specify any `mac-vrf-instance` statements for this server. All MAC-VRF instance IDs that you configure using the `mac-vrf-instance` statement for this server. Range for `vlan-id-number` values: 1 through 4094

See 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.

ON THIS PAGE