Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring PBB with Single-Homed 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:

  • Three provider edge (PE) devices each connected to single-homed customer sites.

  • Four customer edge (CE) devices that are single-homed to the PE 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 signalled 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 Single-Homed EVPN
PBB with Single-Homed
EVPN

In Figure 1, PBB is integrated with EVPN, where the CE devices are single-homed to Devices PE1, PE2, and PE3.

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.

PE1

PE2

PE3

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 interfaces connecting Device PE1 with the other PE devices.
  5. Configure the aggregated Ethernet bundle ae6.
  6. Configure the loopback interface of Device PE1.
  7. Configure the integrated routing and bridging (IRB) interfaces for Device PE1.
  8. Configure the customer backbone port (CBP) interfaces on Device PE1.
  9. Configure the Provider Instance Port (PIP) on Device PE1.
  10. Configure the router ID and autonomous system number for Device PE1.
  11. Configure RSVP on all the interfaces of Device PE1, excluding the management interface.
  12. Configure MPLS on all the interfaces of Device PE1, excluding the management interface.
  13. Configure LSPs from Device PE1 to all other PE devices.
  14. Configure an internal BGP session under family EVPN from Device PE1 to all other PE devices.
  15. Configure OSPF on all the interfaces of Device of PE1, excluding the management interface.
  16. 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.
  17. Configure PBB-EVPN integration from the customer routing instance. Assign the extended I-SID list and bridge domains to the routing instance.
  18. Configure a provider routing instance on Device PE1 with type virtual switch. Assign the PBP interface and bridge domains to the routing instance.
  19. Configure the peer PBBN routing instance in the customer routing instance.
  20. Configure the service groups to be supported in the customer routing instance.
  21. Configure the bridge domains on Device PE1.

Results

From configuration mode, confirm your configuration by entering the show chassis, show interfaces, show routing-options, show protocols, show routing-instances, 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.

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.

Verifying MPLS LSPs

Purpose

Verify the MPLS LSP status on Device PE1.

Action

From operational mode, run the show mpls lsp command.

user@PE1> show mpls lsp

Verifying the EVPN Routing Instance

Purpose

Verify the EVPN routing instance information.

Action

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

user@PE1> show evpn instance extensive

Meaning

The output displays the pbbn1 routing instance information, such as the integration of PBB with EVPN, the single-homed EVPN mode of operation, and the IP address of Devices PE2 and PE3 as the negihbors.

Verifying Routing Table Entries of the EVPN Routing Instance

Purpose

Verify the routing table entries of the EVPN routing instance.

Action

From operational mode, run the show route table pbbn1.evpn.0 command.

user@PE1> show route table pbbn1.evpn.0

Meaning

The output displays the use of IRB intefraces for routing the LSPs between the PE devices.

Verifying the EVPN Database

Purpose

Verify the EVPN database information on the PE devices.

Action

From operational mode, run the show evpn database command.

user@PE1> show evpn database
user@PE2> show evpn database
user@PE3> show evpn database

Verifying the MAC Table Entries

Purpose

Verify the bridge MAC table entries.

Action

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

user@PE1> show bridge mac-table

Meaning

The output displays the MAC addresses associated with the ae6 aggregated Ethernet bundle.

Verifying the inet.3 Routing Table Entries

Purpose

Verify the inet.3 routing table entries on Device PE1.

Action

From operational mode, run the show route table inet.3 command.

user@PE1> show route table inet.3

Meaning

The LSPs to Device PE2 and PE3 are routed using the IRB interface.