Leaking MPLS routes to nondefault routing instances

You can use the import-labeled-routes statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level to specify one or more nondefault routing instances where you want MPLS pseudowire labeled routes to be leaked from the mpls.0 path routing table in the master routing instance. This capability prevents traffic loss in an L2VPN/VPLS configuration where the remote PE router is learned from the IGP in a nondefault routing instance. Because ingress-labeled routes are installed only in the master mpls.0 table by default, no route is found in the routing-instance-name.mpls.0 table when L2VPN/VPLS traffic received on the core-facing interface, and that traffic is dropped.