Accepting Up To One Million Layer 3 Vpn Route Updates - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide

Accepting Up to One Million Layer 3 VPN Route Updates

856
NOTE: ACX Series routers supports
statement at the
for Layer 3 VPNs. The
Layer 2 services is not supported.
You can configure the router based on the number of VPN labels you want to manage
and on whether or not you want to create chained composite next hops for IPv6 labeled
routes:
Accepting Up to One Million Layer 3 VPN Route Updates on page 856
Accepting More Than One Million Layer 3 VPN Route Updates on page 857
Enabling Chained Composite Next Hops for IPv6 Labeled Unicast Routes on page 859
For Juniper Networks routers participating in a mixed vendor network with up to one
million Layer 3 VPN labels, include the
forwarding-table chained-composite-next-hop ingress]
is disabled by default.
NOTE: ACX Series routers do not support
CLI statement at the
BEST PRACTICE:
whenever you have deployed Juniper Networks routers in mixed vendor
networks of up to one million routes to support Layer 3 VPNs.
Because using this statement can also enhance the Layer 3 VPN performance
of Juniper Networks routers in networks where only Juniper Networks routers
are deployed, we recommend configuring the statements in these networks
as well.
You can configure the
l3vpn
ACX Series routers
MX Series routers
M120 routers
M320 routers with one or more Enhanced III FPCs
T Series routers (for Junos OS Release 10.4 and later)
chained-composite-next-hop ingress
[edit routing-options forwarding-table]
chained-composite-next-hop ingress
statement at the
l3vpn
hierarchy level. The
chained-composite-next-hop ingress
[edit routing-options forwarding-table] hierarchy level.
We recommend that you configure the
statement on the following routers:
hierarchy level only
CLI statement for
[edit routing-options
statement
l3vpn
l3vpn statement
Copyright © 2017, Juniper Networks, Inc.
CLI