Instance - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide
Configuring the MPLS Routing Table to Leak Routes a Nondefault Routing Instance
1250
If you do not specify an encapsulation type for the VPLS routing instance or the VPLS
neighbor, is used.
ethernet
To specify an encapsulation type for the VPLS routing instance, include the
encapsulation-type statement:
encapsulation-type (ethernet | ethernet-vlan);
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name protocols vpls]
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols vpls]
You can also specify an encapsulation type for a specific VPLS neighbor by including the
statement at the following hierarchy levels:
encapsulation-type
[edit routing-instances routing-instance-name protocols vpls neighbor address]
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols vpls neighbor address]
Starting in Junos OS Release 16.1, you can specify one or more nondefault routing instances
where you want MPLS routes to be leaked from the mpls.0 path routing table in the
master routing instance. This capability is useful in an L2VPN/VPLS configuration when
the remote PE router is learned from the IGP in a nondefault routing instance, because
L2VPN/VPLS installs ingress-labeled routes only in the master mpls.0 table.
By default, routes in the mpls.0 routing table in the master routing instance are not leaked
to the corresponding routing tables in nondefault routing instances. When L2VPN/VPLS
traffic is received on the core-facing interface in a nondefault routing instance, the router
performs a lookup in the table that corresponds to that interface,
routing-instance-name.mpls.0. Because the routes are not leaked by default, then no
routes are found in the routing-instance-name.mpls.0 routing table and all the incoming
traffic is dropped.
To leak MPLS routes to a nondefault routing instance, include the
statement and specify one or more routing instances where the routes need to be leaked:
import-labeled-routes [ routing-instance-name ];
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name protocols vpls]
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols vpls]
import-labeled-routes
Copyright © 2017, Juniper Networks, Inc.