When you configure the vrf-table-label statement, be aware of the following other limitations:
The time-to-live (TTL) value in the MPLS header is not
copied back to the IP header of packets sent from the PE router to
the CE router.
You cannot configure a virtual loopback tunnel interface
and the vrf-table-label statement on the same routing
instance. Doing so causes the commit to fail.
Do not use the vrf-table-label statement
for source class usage/destination class usage (SCU/DCU) configurations.
For information on SCU/DCU configuration, see the JUNOS Network Interfaces Configuration Guide.
You can configure the vrf-table-label statement on Multilink Frame Relay (MLFR FRF.16) encapsulated PE-router-to-P-router
interfaces, but only on J-series routing platforms.
When you configure the vrf-table-label statement, MPLS packets with label-switched interface (LSI) labels
that arrive on core-facing ATM or Frame Relay interfaces, or on aggregated
Ethernet interfaces configured with VLANs or Ethernet interfaces configured
with VLANs, are not counted at the logical interface level.
You cannot configure the vrf-table-label statement within a VRF routing instance if the PE-router-to-P-router
interface is any of the following:
Aggregated SONET/SDH interfaces
All channelized interfaces
All tunnel interfaces (for example, generic routing encapsulation
[GRE] and IP Security [IPSec])
Circuit cross-connect (CCC) and translational cross-connect
(TCC) encapsulated interfaces
Logical tunnel interfaces
Virtual private LAN service (VPLS) encapsulated interfaces
Note:
All CE-router-to-PE-router and PE-router-to-CE-router
interfaces are supported.
You cannot configure the vrf-table-label statement within a VRF routing instance if the PE-router-to-P-router
PIC is one of the following: