Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Option: Configuring VPLS to Use LSI Interfaces

    On M Series and T Series routers, VPLS uses tunnel-based PICs to create virtual ports on vt interfaces. If you do not have a tunnel-based PIC installed on your M Series or T Series router, you can still configure VPLS by using label-switched interfaces (LSIs) to support the virtual ports. Use of LSI interfaces requires the use of Ethernet-based PICs installed in an Enhanced FPC.

    Note: On MX Series routers, when using VPLS with an LSI interface, you cannot enable ingress-and-egress mode CoS queuing using the traffic-manager statement. On I-chip ASIC-based DPCs in MX Series routers you can enable EXP classification on traffic entering core facing VPLS LSI interfaces using the classifiers statement.

    To use LSI interfaces for VPLS instead of vt interfaces, include the no-tunnel-services statement at the [edit routing-instances instance-name protocols vpls] hierarchy level.

    [edit routing-instances]
    instance-name {protocols {vpls {no-tunnel-services;}}}

    Note: The following interface types do not support the use of LSI interfaces with VPLS:

    • Aggregated SONET/SDH interfaces (cannot be used as the core-facing interface)
    • Channelized interfaces (cannot be used as the core-facing interface)
    • ATM1 interfaces

    Note: When VPLS is configured with the no-tunnel-services option to use an LSI interface instead of a Tunnel-PIC, statistics pertaining to VPLS traffic arriving on a PE router from the core-facing interface cannot be obtained. This is because statistics per logical LSI interface is not supported.

    Modified: 2017-03-10