Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


l3vpn (ingress)


Hierarchy Level


(M120 routers, M320 routers with Enhanced III FPCs, and MX Series routers only) Accept larger numbers of Layer 3 VPN BGP updates with unique inner VPN labels (up to one million). The neighboring provider edge (PE) routers are typically from other vendors and are configured to assign a unique inner label to each Layer 3 VPN BGP route.

  • On MX Series routers, this statement is not supported when the router has both DPCs and MPCs installed. You must remove one or the other type of card to successfully use this statement.

  • On MX Series routers containing both DPC and MPC FPCs, the chassis must be configured with enhanced-ip option for enabling chained composite next hops. Only the l3vpn option under the ingress statement is supported on DPC and DPCE-based MX Series routers. All other statements and functionality under the ingress statement are not supported on MX routers with DPC linecards.

  • In Junos OS Release 11.4 and earlier, the l3vpn statement was titled as l3vpn-composite-nexthop, and the statement was available at the [edit logical-systems logical-system-name routing-options] and [edit routing-options] hierarchy levels.

  • On ACX Series routers, the extended-space statement is not supported.


The [edit logical-systems] hierarchy level is not applicable in ACX Series routers.

The remaining statement is explained separately.


This statement is disabled by default.

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 12.1.