Juniper ACX1000 Configuration Manual page 916

ACX Series Universal Access Router Configuration Guide
858
BEST PRACTICE:
statement in mixed vendor networks containing more than one million routes
to support Layer 3 VPNs. However, b
Because using this statements 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 statement in these networks
as well.
Using the
extended-space
VPN labels that can be processed by a Juniper Networks router. However, when configuring
such very large-scale Layer 3 VPN scenarios, keep the following guidelines in mind:
The extended-space statement is supported only on MX Series routers containing only
MPCs.
The chassis must be configured to use the
mode.
For more information about configuring chassis network services, see the Junos OS
Administration Library.
Ensure that you configure per-packet load balancing for associated policies.
For more information about configuring policies, see the Routing Policies, Firewall Filters,
and Traffic Policers Feature Guide.
BEST PRACTICE:
running 64-bit Junos OS to support Layer 3 VPN prefixes with unique inner
VPN labels at higher scale.
To configure the router to accept more than one million Layer 3 VPN route updates with
unique inner VPN labels:
Include the statement.
1. l3vpn
[edit routing-options forwarding-table chained-composite-next-hop ingress]
user@host>set l3vpn
Include the
extended-space
2.
[edit routing-options forwarding-table chained-composite-next-hop ingress l3vpn]
user@host> set extended-space
Configure chassis network services for enhanced mode.
3.
[edit chassis]
user@host>set network-services enhanced-ip
We recommend that you configure the
statement can double the number of routes with unique inner
enhanced-ip
We strongly recommend using 64-bit routing engines
statement.
extended-space
option in network services
Copyright © 2017, Juniper Networks, Inc.