Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring PWHT on a Transport Logical Interface for BNG

You can configure PWHT over EVPN-VPWS on a transport logical interface, with subscriber management (BNG) service logical interfaces.

Overview

You can deploy a broadband network gateway (BNG) that is connected to an aggregation network running EVPN-VPWS, and you can configure pseudowire headend termination (PWHT) on the transport logical interface that is on the pseudowire subscriber (PS) interface. The BNG pops the EVPN and VPWS headers and terminates subscribers at Layer 2.

This feature includes support for:

  • All broadband features available on PWHT on MX Series routers
  • Single-homed EVPN-VPWS with the PS interface anchored to a logical tunnel (LT) interface
  • Choice of whether or not to use a control word

Topology

This example shows configuration of a single-homed EVPN-VPWS with the PS interface anchored to a logical tunnel (LT) interface.

Topology

Requirements

  • An MX Series router to serve as the BNG router
  • A router (PE1 in the topology) to serve as the EVPN-VPWS remote peer to the BNG router
  • Juno OS Release 21.1R1 or later

Before You Begin

This example shows the connection between the BNG router and the EVPN-VPWS remote peer router, PE1. For details on configuring your subscriber management setup—such as CoS dynamic profiles and router advertisement, DHCP or PPPoE clients, RADIUS servers—or your EVPN-VPWS network, see guides such as:

Note:

Ensure that you have done these two things before you try to commit the configurations for the two routers:

  • Defined the dynamic profile in the [edit dynamic-profiles] hierarchy
  • Enabled MPLS to run EVPN instances, so that you can commit the commands that are in the [edit routing-instances VLL_VPWS_PWHT protocols] hierarchy

If you don't have those items defined and enabled when you try to commit the two router configurations, commit errors occur.

Configuration

Configure the connection between the transport logical interface on the PS interface on the BNG router and the logical interface at the pseudowire tunnel end on the PE1 remote peer router.

BNG Router

Prerequisites

As one of the prerequisites, the auto-vlan-pwht must be configured. For example, you can configure PPPoE over auto-configured stacked VLAN. The sample configuration is as follows:

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, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

  1. Navigate to the interfaces hierarchy. Specify the logical tunnel interface that is the anchor point for the pseudowire logical interface device. The anchor point must be an lt device in the format lt-fpc/pic/port.
  2. Still in the interfaces hierarchy, configure the pseudowire subscriber (PS) interface with the description that you supply and then associate it with its anchor point logical tunnel interface.
  3. Configure the VLAN tagging method for mixed (flexible) VLAN tagging on the PS interface.
  4. Configure the PS interface to use a dynamic profile when the dynamic VLANs are created. The dynamic profile uses the VLAN ranges configured for the interface.
  5. Configure the logical interface for the PS interface (this is the transport logical interface), and configure ethernet-ccc encapsulation.
  6. Navigate to the routing-instances hierarchy, and then configure the routing-instance name, instance type evpn-vpws, the route distinguisher, and the VPN routing and forwarding (VRF) target community for the EVPN-VPWS routing instance.
  7. Still in the routing-instances hierarchy, configure the interface of the routing instance with local and remote service identifiers. These identifiers identify the PE routers that forward and receive the traffic in the EVPN-VPWS network. The local service identifier is used to identify the PE router that is forwarding the traffic, and the remote service identifier is used to identify the PE router that is receiving the traffic in the network.

Results

Check the results of the configuration:

PE1 EVPN-VPWS Remote Peer

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, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

  1. Navigate to the interfaces hierarchy. Specify the interface that is the connecting interface on the PE1 EVPN-VPWS remote peer.
  2. Still in the interfaces hierarchy, configure the peer connection interface with the description that you supply, hierarchical-scheduler implicit-hierarchy, and no-traps.
  3. Configure the VLAN tagging method for mixed (flexible) VLAN tagging on the connecting interface.
  4. Configure flexible-ethernet-services encapsulation on the interface.
  5. Configure the logical interface for the xe-0/2/0 interface , and configure a description, encapsulation, the VLAN ID, and the output-vlan-map settings.
  6. Navigate to the routing-instances hierarchy, and then configure the routing-instance name, instance type evpn-vpws, the route distinguisher, and the VPN routing and forwarding (VRF) target community for the EVPN-VPWS routing instance.
  7. Still in the routing-instances hierarchy, configure the interface of the routing instance with local and remote service identifiers. These identifiers identify the PE routers that forward and receive the traffic in the EVPN-VPWS network. The local service identifier is used to identify the PE router that is forwarding the traffic, and the remote service identifier is used to identify the PE router that is receiving the traffic in the network.

Results

Check the results of the configuration: