Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring EVPN-ETREE SERVICE

 

This example shows how to configure EVPN-ETREE service.

Requirements

This example uses the following hardware and software components:

  • Three MX Series 5G Universal Routing Platforms configured as provider edge (PE) routers.

  • Three customer edge (CE) routers, each connected to the PE routers.

  • Junos OS Release 17.2 or later running on all the PE routers.

Before you begin:

  • Configure the device interfaces.

  • Configure an IGP, such as OSPF, on all the devices.

  • Establish a BGP session between the PE devices.

  • Configure MPLS and LDP on the PE devices.

Overview

The EVPN-ETree service is a VPN service where each attachment circuit is designated as either root or leaf. The E-Tree service is a rooted-multipoint service that is supported only with EVPN over MPLS in the core. In an EVPN E-Tree service, each Customer Edge devices attached the service is either a root or a leaf. The EVPN E-Tree service adheres to the following forwarding rules:

  • A leaf can send or receive traffic only from a root.

  • A root can send traffic to another root or any of the leaves.

  • A leaf or root can be connected to provider edge (PE) devices in singlehoming mode or multihoming mode.

Figure 1: EVPN E-TREE Service
 EVPN E-TREE Service

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

CE1

PE1

PE2

PE3

CE2

CE3

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.

To configure Router PE1:

Note

Repeat this procedure for Routers PE2 and PE3, after modifying the appropriate interface names, addresses, and other parameters.

  1. Configure Router PE1 interfaces.
  2. Assign the interface as leaf or root.
  3. Set the router ID and autonomous system number for Router PE1.
  4. Enable LDP on all the interfaces of Router PE1, excluding the management interface.
  5. Assign local and neighbor addresses to the BGP group for Router PE1 to peer with Routers PE2 and PE3.
  6. Set up the local and peer autonomous systems.
  7. Include the EVPN signaling Network Layer Reachability Information (NLRI) to the bgp BGP group.
  8. Configure OSPF on all the interfaces of Router PE1, excluding the management interface.
  9. Configure MPLS on all the interfaces of Router PE1, excluding the management interface.
  10. Configure the EVPN routing instance.
  11. Set the VLAN identifier for the bridging domain in the evpna routing instance.
  12. Configure the interface name for the evpna routing instance.
  13. Configure the route distinguisher for the evpna routing instance.
  14. Assign the interface name that connects the PE1 site to the VPN.
  15. configure Ethernet VPN E-TREE service on PE1.
  16. Configure the VPN routing and forwarding (VRF) target community for the evpna routing instance.

Results

From configuration mode, confirm your configuration by entering the show interfaces, show routing-options, and show routing-instances commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

Confirm that the configuration is working properly.

Verifying the EVPN Instance Status

Purpose

Verify the EVPN routing instances and their status.

Action

From operational mode, run the show evpn instance extensive command.

user@PE1>show evpn instance extensive

Meaning

The output provides the following information:

  • List of EVPN and virtual switch routing instances

  • Mode of operation of each interface

  • Neighbors of each routing instance

  • Number of different routes received from each neighbor

  • Number of Ethernet segments on each routing instance

  • VLAN ID and MAC labels for each routing instance

Verifying local and remote MAC property

Purpose

Verify EVPN MAC table information.

Action

From operational mode, run the show evpn mac-table command.

user@PE1>show evpn mac-table

Meaning

The output provides the following information:

  • List of MAC addresses learned locally and via control-plane.

  • Property of MAC whether it is learned on a leaf or root interface.

Verifying EVPN ETREE Instances property

Purpose

Verify EVPN ETREE Instances property.

Action

From operational mode, run the show evpn instance evpna extensive command.

user@PE1>show evpn instance evpna extensive

Meaning

The output provides the following information:

  • List the details of specific instance “evpna”.

  • Lists the interfaces associated to this routing instance and its property (leaf or root).

  • Lists the bridge-domains associated to this routing instance.

  • Lists the neighbors and routes received.

Verifying traffic between leaf and root

Purpose

Verifying traffic flow between leaf and root

Action

From operational mode of CE2 (leaf), ping CE1 (root) to check traffic flow.

user@CE2> ping 10.100.0.1

Meaning

The output shows Ping is successful between CE2 (leaf) and CE1 (root).

Verifying traffic flow between leaf and leaf is not allowed

Purpose

Verifying traffic flow between leaf and leaf is not allowed.

Action

From operational mode of CE2 (leaf), ping CE3 (leaf) to check traffic flow.

user@CE2> ping 10.100.0.1

Meaning

The output shows Ping failed between CE2 and CE3 because traffic is not allowed between leaf and leaf interfaces.

Related Documentation