no-tunnel-services
Syntax
no-tunnel-services;
Hierarchy Level
[edit logical-systems logical-system-name protocols vpls static-vpls], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit protocols vpls static-vpls], [edit routing-instances routing-instance-name protocols vpls]
Description
Configure VPLS on a router without a Tunnel Services
PIC. Configuring the no-tunnel-services 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.
In VPLS documentation, the word Router in terms such as PR Router is used to refer to any device that provides routing functions.
On MX Series routers, label-switched interfaces configured with
the no-tunnel-services statement are not supported with
GRE tunnels when the GRE interface resides on a DPC.
Although visible in the CLI, the no-tunnel-services statement is not supported on DPC cards at the [edit logical-systems logical-system-name protocols vpls static-vpls] and
the [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls] hierarchy levels.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 7.6.
Support for static VPLS added in Junos OS Release 10.2.