Configuring VPLS Without a Tunnel Services PIC

 

VPLS normally uses a dynamic virtual tunnel logical interface on a Tunnel Services PIC to model traffic from a remote site (a site on a remote PE router that is in a VPLS domain). All traffic coming from a remote site is treated as coming in over the virtual port representing this remote site, for the purposes of Ethernet flooding, forwarding, and learning. An MPLS lookup based on the inner VPN label is done on a PE router. The label is stripped and the Layer 2 Ethernet frame contained within is forwarded to a Tunnel Services PIC. The PIC loops back the packet and then a lookup based on Ethernet MAC addresses is completed. This approach requires that the router have a Tunnel Services PIC and that the PE router complete two protocol lookups.

Note

In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions.

You can configure VPLS without a Tunnel Services PIC by configuring the no-tunnel-services statement. This statement creates a label-switched interface (LSI) to provide VPLS functionality. An LSI MPLS label is used as the inner label for VPLS. This label maps to a VPLS routing instance. On the PE router, the LSI label is stripped and then mapped to a logical LSI interface. The Layer 2 Ethernet frame is then forwarded using the LSI interface to the correct VPLS routing instance.

By default, VPLS requires a Tunnel Services PIC. To configure VPLS on a router without a Tunnel Services PIC and create an LSI, include the no-tunnel-services statement:

For a list of the hierarchy levels at which you can include this statement, see the summary section for this statement.

To configure a VPLS routing instance on a router without a tunnel services PIC, include the no-tunnel-services statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level. To configure static VPLS on a router without a tunnel services PIC, include the no-tunnel-services statement at the [edit protocols vpls static-vpls] hierarchy level.

When you configure VPLS without a Tunnel Services PIC by including the no-tunnel-services statement, the following limitations apply:

  • An Enhanced FPC is required.

  • ATM1 interfaces are not supported.

  • Aggregated SONET/SDH interfaces are not supported as core-facing interfaces.

  • Channelized interfaces are not supported as core-facing interfaces.

  • GRE-encapsulated interfaces are not supported as core-facing interfaces.