Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring L2PT for VPLS

You can use Layer 2 Protocol Tunneling (L2PT) to transparently send packets across a VPLS network. The customer edge (CE) device sends and receives packets over VPLS pseudowires to and from the provider edge (PE) device. L2PT doesn't interfere with protocol instances in the network. L2PT supports 802.1x, 802.3ah, CDP, E-LMI, MVRP, LACP, STP/RSTP/MSTP, LLDP, MMRP, and VTP Layer 2 control protocols.

Use Feature Explorer to determine if a feature is supported on your platform and release.

Here is how to configure L2PT for VPLS on the PE device.

  1. The packets leave the CE from an untagged or single-tagged port called interface CE-interface-name. Configure VPLS VLAN encapsulation for packets that arrive from this port.
    1. Enable flexible VLAN tagging and flexible Ethernet services so you can configure more than one instance of VPLS encapsulation on the port.
    2. Since the L2CP frames from the CE device are untagged, configure the native VLAN ID to support untagged VLAN packets.
    3. Configure VPLS VLAN encapsulation.
  2. Configure the routing instance.
    1. Configure VPLS as the routing instance protocol.
    2. (Optional) If your router doesn't have a Tunnel Services PIC, you will need to configure the no-tunnel-services statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level.
    3. Configure the instance type and identify the CE port. Use the VLAN ID from Step 1.
  3. Configure the L2PT protocol. The protocol can be any of the following: (stp | vtp | cdp | ieee8021x | ieee8023ah | elmi | lacp | lldp | mmrp | mvrp).
You have configured L2PT for VPLS on your network.

Platform Specific L2PT Behavior

(ACX Series) These devices don't support L2PT on logical tunnel, access, or trunk interfaces.

(ACX Series) When L2PT is configured for a protocol, the drop-threshold, shutdown-threshold, and class-of-service parameters can't be configured for that protocol on the same interface.

(ACX Series) If any L2PT supported L2 control protocol is configured on an interface, then you can't configure the same L2PT protocol again on that interface. The CLI will show an error and the configuration won't commit. Due to this restriction, LACP for L2PT is not supported on aggregated ethernet (AE) interfaces, either static or dynamic type. This limitation only applies to user-to-network (UNI) AE interfaces. L2PT can co-exist with L2 control protocol configuration on network-to-network (NNI) AE interfaces, and non-AE UNI interfaces.

Related Documentation