Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring PBB with Multihomed EVPN

 

This example shows how to integrate provider backbone bridging (PBB) with Ethernet VPN (EVPN). With this integration, the control plane operations in the core are simplified, providing faster convergence and scalability enhancements than regular EVPN. The PBB-EVPN applications include Data Center Interconnect (DCI) and carrier Ethernet E-LAN services.

Requirements

This example uses the following hardware and software components:

  • Four provider edge (PE) devices connected to two common multihomed customer sites, and each PE device is connected to a host.

  • Two multihomed customer edge (CE) devices.

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

Before you begin:

  • Configure the device interfaces.

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

  • Establish an internal BGP session between the PE devices.

  • Enable RSVP on the PE devices.

  • Configure MPLS and label-switched paths (LSPs) between the PE devices.

Overview and Topology

Starting in Junos OS Release 17.2R1, PBB is integrated with Ethernet VPN (EVPN) to enable significant reduction in the control plane learning across the core, allowing a huge number of Layer 2 services, such as data center connectivity, to transit the network in a simplified manner.

In a PBB-EVPN network, the backbone core bridge (BCB) device in the PBB core is replaced with MPLS, while retaining the service scaling properties of the PBB backbone edge bridge (BEB). The B-component (provider routing instance) is signaled using EVPN BGP signaling and encapsulated inside MPLS using provider edge (PE) and provider (P) devices. Thus, PBB-EVPN combines the vast scaling property of PBB with the simplicity of a traditional basic MPLS core network, resulting in significant reduction in the amount of network-wide state information, as opposed to regular PBB.

Figure 1: PBB with Active/Standby EVPN Multihoming
PBB
with Active/Standby EVPN Multihoming

In Figure 1, PBB is integrated with EVPN, where the CE devices are multihomed in the active/standby mode. Device CE1 is multihomed to Devices PE1, PE2, and PE3, and Device CE2 is multihomed to Device PE3 and PE4.

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

CE2

PE1

PE2

PE3

PE4

Configuring Device CE1

Step-by-Step Procedure

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

To configure Device CE1:

  1. Set the number of aggregated Ethernet interfaces on Device CE1.
  2. Set Device CE1’s network services to enhanced Internet Protocol and use enhanced mode capabilities.
  3. Configure Device CE1’s interfaces.
  4. Configure the aggregated Ethernet bundle on Device CE1.
  5. Configure the bridge domains on Device CE1.

Results

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

If you are done configuring the device, enter commit from configuration mode.

Configuring Device PE1

Step-by-Step Procedure

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

To configure Device PE1:

  1. Set the number of aggregated Ethernet interfaces on Device PE1.
  2. Set Device PE1’s network services to enhanced Internet Protocol and use enhanced mode capabilities.
  3. Configure the CE-facing interfaces of Device PE1.
  4. Configure the aggregate Ethernet bundle on Device PE1 that connects to Device CE1.
  5. Configure the EVPN multihoming parameters for the CE-facing interfaces and aggregate Ethernet bundle that connect to the multihomed customer site.
    Note

    In this example, the EVPN multihoming is operating in the active/standby mode. To configure active/active EVPN multihoming, include the active-active statement at the [edit interfaces interface-name esi] hierarchy level instead of the single-active statement.

  6. Configure the interface of Device PE1 that connects to Devices PE2, PE3, and PE4.
  7. Configure the aggregate Ethernet bundle on Device PE1 that connect to Devices PE2, PE3, and PE4.
  8. Configure the interface of Device PE1 that connects to the host.
  9. Configure the loopback interface of Device PE1.
  10. Configure the customer backbone port (CBP) interfaces on Device PE1.
  11. Configure the Provider Instance Port (PIP) on Device PE1.
  12. Configure the router ID and autonomous system number for Device PE1.
  13. Configure RSVP on all the interfaces of Device PE1, excluding the management interface.
  14. Configure MPLS on all the interfaces of Device PE1, excluding the management interface.
  15. Configure LSPs from Device PE1 to all other PE devices.
  16. Configure MPLS paths from Device PE1 to all other PE devices.
  17. Configure an internal BGP session under family EVPN from Device PE1 to all other PE devices.
  18. Configure OSPF on all the interfaces of Device of PE1, excluding the management interface.
  19. Configure a customer routing instance (I-component) on Device PE1 with type virtual switch. Assign the CBP interface, route-distinguisher, and virtual routing and forwarding (VRF) target values to the PBBN routing instance.
  20. Configure PBB-EVPN integration from the customer routing instance. Assign the extended I-SID list and bridge domains to the routing instance.
  21. Configure a provider routing instance on Device PE1 with type virtual switch. Assign the PBP interface and bridge domains to the routing instance.
  22. Configure the peer PBBN routing instance in the customer routing instance.
  23. Configure the service groups to be supported in the customer routing instance.

Results

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

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly.

Verifying BGP Peering Status

Purpose

Verify that the BGP session is established between the PE devices.

Action

From operational mode, run the show bgp summary command.

user@PE1> show bgp summary

Meaning

A BGP session is established between the PE devices.

Verify MAC Table Entries

Purpose

Verify the number of rbeb interfaces learned in the MAC table on all PEs.

Action

From operational mode, run the show bgp summary command.

user@PE1> show bridge mac-table count instance pbn1 bridge-domain bda

Meaning

For VLAN ID 10, 10 MAC addresses have been learned in the MAC table of Device PE1.

Verifying the EVPN Database

Purpose

Verify the EVPN database information on Device PE4.

Action

From operational mode, run the show evpn database command.

user@PE1> show evpn database

Verifing EVPN Routing Instances

Purpose

Verify the EVPN routing instance information on all the PE devices.

Action

From operational mode, run the show evpn routing-instance command.

user@PE1> show evpn routing-instance
user@PE2> show evpn routing-instance
user@PE3> show evpn routing-instance
user@PE4> show evpn routing-instance

Meaning

The command output displays PBB-EVPN integration, where EVPN is in the active/standby multihoming mode. If EVPN multihoming was configured in the active/active mode, the status of all the ESIs would be Up/Forwarding. In the active/standby multihoming mode, one ESI is in the Up/Forwarding state and all other ESIs remain in the Up/Blocking state.