Accepting BGP Updates with Unique Inner VPN Labels in Layer 3 VPNs
In some multi-vendor network environments, you can enhance the scaling and convergence performance of the PE routers participating in a Layer 3 VPN by including the l3vpn-composite-nexthop statement in the configuration of the PE routers. The l3vpn-composite-nexthop statement feature enables BGP to accept larger numbers of Layer 3 VPN BGP updates with unique inner VPN labels. This feature is applicable when the neighboring PE routers providing the BGP updates are routers from other vendors that assign a unique inner label to each Layer 3 VPN BGP route. Juniper Networks recommends that in such multi-vendor environments, the best practice is to include the l3vpn-composite-nexthop statement in the PE router configurations.
The l3vpn-composite-nexthop statement is disabled by default.
You can configure the l3vpn-composite-nexthop statement on the following platforms:
- MX Series
- M120
- M320 with an Enhanced III FPC
To accept larger numbers of Layer 3 VPN BGP updates with unique inner VPN labels, configure the l3vpn-composite-nexthop statement:
You can include this statement at the following hierarchy levels:
- [edit routing-options]
- [edit logical-systems logical-system-name routing-options]
 | Note: You cannot include the vpn-unequal-cost equal-external-internal statement and the l3vpn-composite-nexthop statement simultaneously. The commit operation fails. |
