Configuring PWHT on a Transport Logical Interface for BNG

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:

[edit routing-instances]
user@host# show auto-vlan-pwht
vlan-demux {
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                no-traps;
                vlan-tags outer "$junos-stacked-vlan-id" inner "$junos-vlan-id";
                advisory-options {                        
                    upstream-rate 1g;
                    downstream-rate 1g;
                }
                demux-options {
                    underlying-interface "$junos-interface-ifd-name";
                }
                family pppoe {
                    duplicate-protection;
                    dynamic-profile pppv6p;
                    max-sessions 1;
                    short-cycle-protection {
                        lockout-time-min 5;
                        lockout-time-max 60;
                    }
                }
           }
     }
}

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.

set interfaces lt-1/0/0 hierarchical-scheduler maximum-hierarchy-levels 2
set interfaces ps0 description BNG-ps0____PE-xe-0/2/0
set interfaces ps0 anchor-point lt-1/0/0
set interfaces ps0 flexible-vlan-tagging
set interfaces ps0 auto-configure stacked-vlan-ranges dynamic-profile auto-vlan-pwht accept pppoe ranges any,any
set interfaces ps0 unit 0 encapsulation ethernet-ccc
set routing-instances VLL_VPWS_PWHT instance-type evpn-vpws interface ps0.0
set routing-instances VLL_VPWS_PWHT route-distinguisher 10.255.0.1:100
set routing-instances VLL_VPWS_PWHT vrf-target target:100:1004
set routing-instances VLL_VPWS_PWHT protocols evpn interface ps0.0 vpws-service-id local 33 remote 34

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.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set  lt-1/0/0 hierarchical-scheduler maximum-hierarchy-levels 2 

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.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set ps0 description BNG-ps0____PE-xe-0/2/0
   user@host# set ps0 anchor-point lt-1/0/0

3. Configure the VLAN tagging method for mixed (flexible) VLAN tagging on the PS interface.
   content_copy zoom_out_map

   [edit]
   user@host# set ps0 flexible-vlan-tagging

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.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set ps0 auto-configure stacked-vlan-ranges dynamic-profile auto-vlan-pwht accept pppoe ranges any,any

5. Configure the logical interface for the PS interface (this is the transport logical interface), and configure ethernet-ccc encapsulation.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set ps0 unit 0 encapsulation ethernet-ccc

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.
   content_copy zoom_out_map

   [edit routing-instances]
   user@host# set VLL_VPWS_PWHT instance-type evpn-vpws interface ps0.0
   user@host# set VLL_VPWS_PWHT route-distinguisher 10.255.0.1:1004
   user@host# set VLL_VPWS_PWHT vrf-target target:100:1004

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.
   content_copy zoom_out_map

   [edit routing-instances]
   user@host# set VLL_VPWS_PWHT protocols evpn interface ps0.0 vpws-service-id local 33 remote 34

Results

Check the results of the configuration:

[edit interfaces]
user@host# show
lt-2/0/0 {
    hierarchical-scheduler maximum-hierarchy-levels 2;
}
ps0 {
    description BNG-ps0____PE-xe-0/2/0;
    anchor-point {
        lt-2/0/0;
    }
    flexible-vlan-tagging;
    auto-configure {
        stacked-vlan-ranges {
            dynamic-profile auto-vlan-pwht {
                accept pppoe;
                ranges {
                    any,any;
                }
            }
        }
    }
   
    unit 0 {
        encapsulation ethernet-ccc;
    }
}
[edit routing-instances]
user@host# show
VLL_VPWS_PWHT {
    protocols {
        evpn {
            interface ps0.0 {
                vpws-service-id {
                    local 33;
                    remote 34;
                }
            }
        }
    }
    instance-type evpn-vpws;
    interface ps0.0;
    route-distinguisher 10.255.0.1:100;
    vrf-target target:100:1004;
}

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.

set interfaces xe-0/2/0 description PE-xe-0/2/0____BNG-ps0
set interfaces xe-0/2/0 hierarchical-scheduler implicit-hierarchy
set interfaces xe-0/2/0 no-traps
set interfaces xe-0/2/0 flexible-vlan-tagging
set interfaces xe-0/2/0 encapsulation flexible-ethernet-services
set interfaces xe-0/2/0 unit 10 description VPWS-PE-BNG-PWHT
set interfaces xe-0/2/0 unit 10 encapsulation vlan-ccc
set interfaces xe-0/2/0 unit 10 vlan-id 10
set interfaces xe-0/2/0 unit 10 output-vlan-map swap tag-protocol-id 0x8100 inner-vlan-id 10
set routing-instances VLL_VPWS_PWHT instance-type evpn-vpws interface xe-0/2/0.10
set routing-instances VLL_VPWS_PWHT route-distinguisher 10.255.0.2:1004
set routing-instances VLL_VPWS_PWHT vrf-target target:100:1004
set routing-instances VLL_VPWS_PWHT protocols evpn interface xe-0/2/0.10 vpws-service-id local 34 remote 33

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.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set xe-0/2/0

2. Still in the interfaces hierarchy, configure the peer connection interface with the description that you supply, hierarchical-scheduler implicit-hierarchy, and no-traps.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set xe-0/2/0 description PE-xe-0/2/0____BNG-ps0
   user@host# set xe-0/2/0 hierarchical-scheduler implicit-hierarchy
   user@host# set xe-0/2/0 no-traps

3. Configure the VLAN tagging method for mixed (flexible) VLAN tagging on the connecting interface.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set xe-0/2/0 flexible-vlan-tagging

4. Configure flexible-ethernet-services encapsulation on the interface.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set xe-0/2/0 encapsulation flexible-ethernet-services

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.
   content_copy zoom_out_map

   [edit interfaces]
   user@host# set xe-0/2/0 unit 10 description VPWS-PE-BNG-PWHT
   user@host# set xe-0/2/0 unit 10 encapsulation vlan-ccc
   user@host# set xe-0/2/0 unit 10 vlan-id 10
   user@host# set xe-0/2/0 unit 10 output-vlan-map swap tag-protocol-id 0x8100 inner-vlan-id 10

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.
   content_copy zoom_out_map

   [edit routing-instances]
   user@host# set VLL_VPWS_PWHT instance-type evpn-vpws
   user@host# set VLL_VPWS_PWHT interface xe-0/2/0.10
   user@host# set VLL_VPWS_PWHT route-distinguisher 10.255.0.2:1004
   user@host# set VLL_VPWS_PWHT vrf-target target:100:1004

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.
   content_copy zoom_out_map

   [edit routing-instances]
   user@host# set VLL_VPWS_PWHT protocols evpn interface xe-0/2/0.10 vpws-service-id local 34 remote 33

Results

Check the results of the configuration:

[edit interfaces]
user@host# show
xe-0/2/0 {
    description PE-xe-0/2/0____BNG-ps0;
    no-traps;
    hierarchical-scheduler implicit-hierarchy;
    flexible-vlan-tagging;
    encapsulation flexible-ethernet-services;
    unit 10 {
        description VPWS-PE-BNG-PWHT;
        encapsulation vlan-ccc;
        vlan-id 10;
        output-vlan-map {
            swap;
            tag-protocol-id 0x8100;
            inner-vlan-id 10;
        }
    }
}
[edit routing-instances]
user@host# show
VLL_VPWS_PWHT {
    protocols {
        evpn {
            interface xe-0/2/0.10 {
                vpws-service-id {
                    local 34;
                    remote 33;
                }
            }
        }
    }
    instance-type evpn-vpws;
    interface xe-0/2/0.10;
    route-distinguisher 10.255.0.2:1004;
    vrf-target target:100:1004;
}