Accepting More Than One Million Layer 3 Vpn Route Updates - Juniper ACX1000 Configuration Manual

Accepting More Than One Million Layer 3 VPN Route Updates

Copyright © 2017, Juniper Networks, Inc.
M320 routers with one or more Enhanced III FPCs
T Series routers (for Junos OS Release 10.4 and later)
To accept up to one million Layer 3 VPN route updates with unique inner VPN labels,
configure the statement. This statement is supported on indirectly connected PE
l3vpn
routers only. Configuring this statement on a router that is directly connected to a PE
router provides no benefit. You can configure the
of links to both directly connected and indirectly connected PE routers.
NOTE: You cannot configure the
same time that you have configured the vpn-unequal-cost statement.
To configure the router to accept up to one million Layer 3 VPN route updates with unique
inner VPN labels:
Include the l3vpn statement.
1.
[edit routing-options forwarding-table chained-composite-next-hop ingress]
user@host>set l3vpn
To enhance memory allocation to support a larger number of Layer 3 VPN labels,
2.
include the vpn-label statement.
[edit chassis memory-enhanced]
user@host>set vpn-label
NOTE: The vpn-label
when used on the MX Series routers. You can omit the configuration of
this statement on MX Series routers.
For more information about configuring more memory for Layer 3 VPN labels, see the
Junos OS Administration Library.
After you have configured the
3 VPN route is a part of a composite next hop by examining the display output of the
following commands:
show route route-value extensive
show route forwarding-table destination destination-value extensive
For Juniper Networks routers participating in a mixed vendor network with more than one
million Layer 3 VPN labels, include the
routing-options forwarding-table chained-composite-next-hop ingress l3vpn]
level. The extended-space
Chapter 25: Configuring Layer 2 and Layer 3 Services
l3vpn
statement and sub-statements at
l3vpn
statement does not provide any functional changes
l3vpn statement, you can determine whether or not a Layer
extended-space
statement is disabled by default.
statement on a router with a mix
statement at the
[edit
hierarchy
787