Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: EVPN-MPLS Interworking With Junos Fusion Enterprise

 

This example shows how to use Ethernet VPN (EVPN) to extend a Junos Fusion Enterprise over an MPLS network to a geographically distributed campus or enterprise network.

EVPN-MPLS interworking is supported with a Junos Fusion Enterprise, which is based on a multichassis link aggregation group (MC-LAG) infrastructure to provide redundancy for the EX9200 switches that function as aggregation devices.

The aggregation devices in the Junos Fusion Enterprise are connected to a provider edge (PE) device in an MPLS network. The PE device can be either an MX Series router or an EX9200 switch.

This example shows how to configure the aggregation devices in the Junos Fusion Enterprise and the PE device in the MPLS network to interwork with each other.

Requirements

This example uses the following hardware and software components:

  • Three EX9200 switches:

    • PE1 and PE2, which both function as aggregation devices in the Junos Fusion Enterprise and EVPN BGP peers in the EVPN-MPLS overlay network.

    • PE3, which functions as an EVPN BGP peer in the EVPN-MPLS overlay network.

  • The EX9200 switches are running Junos OS Release 17.4R1 or later software.

Note

Although the Junos Fusion Enterprise includes three satellite devices, this example focuses on the configuration of the PE1, PE2, and PE3. For more information about configuring satellite devices, see Configuring or Expanding a Junos Fusion Enterprise.

Overview and Topology

Figure 1 shows a Junos Fusion Enterprise with dual aggregation devices PE1 and PE2. The aggregation devices are connected using an interchassis link (ICL) and communicate with each other using the Inter-Chassis Control Protocol (ICCP).

Figure 1: EVPN-MPLS Interworking with Junos Fusion Enterprise
EVPN-MPLS Interworking with
Junos Fusion Enterprise

The Junos Fusion Enterprise also includes three satellite devices. Satellite device SD120 is a standalone satellite device that has a single-homed connection to PE1. Satellite devices SD100 and SD108 are included in a cluster named Cluster_100_108. SD100 is the only cluster member with a connection to an aggregation device, in this case, multhomed connections to PE1 and PE2.

The topology in Figure 1 also includes PE3, which is positioned at the edge of an MPLS network. PE3 functions as the gateway between the Junos Fusion Enterprise network and a geographically distributed campus or enterprise network. PE1, PE2, and PE3 run EVPN, which enables hosts in the Junos Fusion Enterprise network to communicate with hosts in the campus or enterprise network by way of the intervening MPLS network.

From the perspective of the EVPN-MPLS interworking feature, PE3 functions solely as an EVPN BGP peer, and PE1 and PE2 in the Junos Fusion Enterprise have dual roles:

  • Aggregation devices in the Junos Fusion Enterprise.

  • EVPN BGP peers in the EVPN-MPLS network.

Because of the dual roles, PE1 and PE2 are configured with Junos Fusion Enterprise, EVPN, BGP, and MPLS attributes.

Table 1 outlines key Junos Fusion Enterprise and EVPN (BGP and MPLS) attributes configured on PE1, PE2, and PE3.

Table 1: Key Junos Fusion Enterprise and EVPN (BGP and MPLS) Attributes Configured on PE1, PE2, and PE3

Key Attributes

PE1

PE2

PE3

Junos Fusion Enterprise Attributes

Interfaces

ICL: ge-1/0/3

ICCP: ge-1/0/2

ICL: ge-3/1/9

ICCP: ge-3/1/7

Not applicable

EVPN-MPLS

Interfaces

Connection to PE3: ge-1/1/3

Connection to PE2: ge-1/1/7

Connection to PE3: ge-3/1/5

Connection to PE1: ge-3/1/8

Connection to PE1: ge-0/3/5

Connection to PE2: ge-0/3/7

IP addresses

BGP peer address: 10.25.0.1

BGP peer address: 10.25.0.2

BGP peer address: 10.25.0.3

Autonomous system

100

100

100

Virtual switch routing instances

evpn1

evpn1

evpn1

Note the following about the EVPN-MPLS interworking feature and its configuration:

  • You must configure Ethernet segment identifiers (ESIs) on the dual-homed extended ports in the Junos Fusion Enterprise. The ESIs enable EVPN to identify the dual-homed extended ports.

  • The only type of routing instance that is supported is the virtual switch instance (set routing-instances name instance-type virtual-switch).

  • Only one virtual switch instance is supported with Junos Fusion Enterprise.

  • On the aggregation devices in the Junos Fusion Enterprise, you must include the bgp-peer configuration statement in the [edit routing-instances name protocols evpn mclag] hierarchy level. This configuration statement enables the interworking of EVPN-MPLS with Junos Fusion Enterprise on the aggregation devices.

  • Address Resolution Protocol (ARP) suppression is not supported.

Aggregation Device (PE1 and PE2) Configuration

To configure aggregation devices PE1 and PE2, perform these tasks.

Note

This section focuses on enabling EVPN-MPLS on PE1 and PE2. As a result, the Junos Fusion Enterprise configuration on PE1 and PE2 is performed without the use of the configuration synchronization feature. For information about configuration synchronization, see Understanding Configuration Synchronization.

CLI Quick Configuration

PE1: Junos Fusion Enterprise Configuration

PE1: EVPN-MPLS Configuration

PE2: Junos Fusion Enterprise Configuration

PE2: EVPN-MPLS Configuration

PE1: Configuring Junos Fusion Enterprise

Step-by-Step Procedure

  1. Configure the cascade ports.

  2. Configure the FPC slot ID for standalone satellite device SD120 and map it to a cascade port.

  3. Create a satellite device cluster, and assign a name and a cluster ID to it.

  4. Define the cascade ports associated with the satellite device cluster.

  5. Configure the FPC slot ID number, and map it to the MAC address of satellite devices SD100 and SD108, respectively.

  6. Assign a member ID to each satellite device in the satellite device cluster.

  7. Create two satellite software upgrade groups—one that includes satellite device SD120 and another that includes satellite device SD100.

  8. Create and configure a redundancy group, which includes the aggregation devices and satellite devices in Cluster_100_108.

  9. Configure the ICL and ICCP links.

    Note

    While this step shows the configuration of interface ge-1/0/2, which is designated as the ICCP interface, it does not show how to configure the ICCP attributes on interface ge-1/0/2. By default, ICCP is automatically provisioned in a Junos Fusion Enterprise using dual aggregation devices. For more information about the automatic provisioning of ICCP, see Configuring or Expanding a Junos Fusion Enterprise.

PE1: Configuring EVPN-MPLS

Step-by-Step Procedure

  1. Configure the loopback interface and the interfaces connected to the other PE devices.

  2. Configure the extended ports with EVPN multihoming in active-active mode, an ESI, and map the ports to VLAN v100..

  3. Assign a router ID and the autonomous system in which PE1, PE2, and PE3 reside.

  4. Enable MPLS on the loopback interface and interfaces ge-1/1/3.0 and ge-1/1/7.0.

  5. Configure an IBGP overlay that includes PE1, PE2, and PE3.

  6. Configure OSPF as the internal routing protocol for EVPN by specifying an area ID and interfaces on which EVPN-MPLS is enabled.

  7. Configure the Label Distribution Protocol (LDP) on the loopback interface and the interfaces on which EVPN-MPLS is enabled.

  8. Configure a virtual switch routing instance for VLAN v100, and include the interfaces and other entities associated with the VLAN.

PE2: Configuring Junos Fusion Enterprise

Step-by-Step Procedure

  1. Configure the cascade port.

  2. Create a satellite device cluster, and assign a name and a cluster ID to it.

  3. Define the cascade port associated with the satellite device cluster.

  4. Configure the FPC slot ID number, and map it to the MAC address of satellite devices SD100 and SD108, respectively.

  5. Assign a member ID to each satellite device in the satellite device cluster.

  6. Create a satellite software upgrade group that includes satellite device SD100.

  7. Create and configure a redundancy group, which includes the aggregation devices and satellite devices in Cluster_100_108.

  8. Configure the ICL and ICCP links.

    Note

    While this step shows the configuration of interface ge-3/1/7, which is designated as the ICCP interface, it does not show how to configure the ICCP attributes on interface ge-3/1/7. By default, ICCP is automatically provisioned in a Junos Fusion Enterprise using dual aggregation devices. For more information about the automatic provisioning of ICCP, see Configuring or Expanding a Junos Fusion Enterprise.

PE2: Configuring EVPN-MPLS

Step-by-Step Procedure

  1. Configure the loopback interface, the interfaces connected to the other PE devices, and an IRB interface that is also configured as a default Layer 3 gateway.

  2. Configure the extended ports with EVPN multihoming in active-active mode, an ESI, and map the ports to VLAN v100..

  3. Assign a router ID and the autonomous system in which PE1, PE2, and PE3 reside.

  4. Enable MPLS on the loopback interface and interfaces ge-3/1/5.0 and ge-3/1/8.0.

  5. Configure an IBGP overlay that includes PE1, PE2, and PE3.

  6. Configure OSPF as the internal routing protocol for EVPN by specifying an area ID and interfaces on which EVPN-MPLS is enabled.

  7. Configure the LDP on the loopback interface and the interfaces on which EVPN-MPLS is enabled.

  8. Configure a virtual switch routing instance for VLAN v100, and include the interfaces and other entities associated with the VLAN.

PE3 Configuration

CLI Quick Configuration

PE3: EVPN-MPLS Configuration

PE3: Configuring EVPN-MPLS

Step-by-Step Procedure

  1. Configure the interfaces on EVPN-MPLS interworking occurs.

  2. Configure interface ge-0/0/46 with EVPN multihoming in active-active mode, an ESI, and map the ports to VLAN v100..

  3. Assign a router ID and the autonomous system in which the PE1, PE2, and PE3 reside.

  4. Enable per-packet load-balancing for EVPN routes when EVPN multihoming active-active mode is used.

  5. Enable MPLS on the loopback interface and interfaces ge-0/3/5.0 and ge-0/3/7.0.

  6. Configure an IBGP overlay that includes PE1, PE2, and PE3.

  7. Configure OSPF as the internal routing protocol for EVPN by specifying an area ID and interfaces on which EVPN-MPLS is enabled.

  8. Configure the LDP on the loopback interface and the interfaces on which EVPN-MPLS is enabled.

  9. Configure a virtual switch routing instance for VLAN v100, and include the interfaces and other entities associated with the VLAN.