Allocating More Memory for Routing Tables, Firewall Filters, and Layer 3 VPN Labels
The jtree memory on all MX Series, all M120, and some M320, M10i, M7i, T640, T1600, TX Matrix, TX Matrix Plus router Packet Forwarding Engines has two segments: One segment primarily stores routing tables and related information, and the other mainly stores firewall-filter-related information.
The Junos OS provides the memory-enhanced statement to reallocate the jtree memory for routes, firewall filters, and Layer 3 VPNs. The statement has the following options:
filter—Include this statement when you want to support larger firewall filters over routing tables. However, we recommend enabling this option only if you do not have a very large routing table configuration.
To allocate more memory for firewall filters, include the filter statement at the [edit chassis memory-enhanced] hierarchy level:
route—Include this statement when you want to support larger routing tables (with more routes) over firewall filters. For example, you can enable this option, when you want to support a large number of routes for Layer 3 VPNs implemented using MPLS. However, we recommend enabling this option only if you do not have a very large firewall configuration.
To allocate more memory for routing tables, include the route statement at the [edit chassis memory-enhanced] hierarchy level:
vpn-label—Include this statement when you want to enhance memory to support a larger number of Layer 3 VPN labels.
Layer 3 VPN composite next hops can be enabled by including the l3vpn-composite-nexthop statement at the [edit routing-options] and [edit logical-systems logical-system-name routing-options] hierarchy levels. This statement enables BGP to accept larger numbers of Layer 3 VPN BGP updates with unique inner VPN labels. Including the l3vpn-composite-nexthop in the configuration enhances scaling and convergence performance of PE routers participating in a Layer 3 VPN in a multivendor environment. For more information on configuring the l3vpn-composite-nexthop statement, see the Junos OS VPNs Library for Routing Devices.
To allocate more memory to support a larger number of Layer 3 VPN labels accepted by the l3vpn-composite-nexthop statement, include the vpn-label statement at the [edit chassis memory-enhanced] hierarchy level:
The memory-enhanced vpn-label statement increases the size of the fabric next-hop table, which is held on the egress FPC in the jtree, from the default value of 128,000 entries to 1,000,000 entries. This improves token fabric scaling, at the expense of additional segment 1 usage. This functionality is not applicable to MX Series or M320 platforms, as these platforms provide for flexibly sized fabric token tables by default. This means that the memory-enhanced route statement is applicable to T Series platforms and that you can configure both memory-enhanced vpn-label and memory-enhanced route on T Series platforms when their combined functionality is desired.
You can configure the memory-enhanced statement on the following routers:
M10i and M7i routers with Enhanced CFEB
M320 routers with Enhanced III FPC1, Enhanced III FPC2, and Enhanced III FPC3
MX Series routers with DPC (I-chip based) line cards
T Series (T640, T1600, TX Matrix, and TX Matrix Plus) routers with Enhanced Scaling FPC1, Enhanced Scaling FPC2, Enhanced Scaling FPC3, and Enhanced Scaling FPC4.
The following hardware is not supported for the TXP-T1600 configuration for Junos OS Release 10.0 and earlier releases, If you plan to run a release prior to Junos OS Release 10.0, you must remove the following FPCs and any PICs that require these FPCs prior to integrating the LCC into the routing matrix:
All type 1 FPCs
All type 2 FPCs
T640 Enhanced Scaling FPC4-1P FPCs
The following hardware is not supported for the TXP-T1600-3D or TXP-Mixed-LCC-3D configuration:
T640-FPC1-E and T640-FPC1-E2
T640-FPC2, T640-FPC2-E, and T640-FPC2-E2
T640-FPC3, T640-FPC3-E, and T640-FPC3-E2
As the allocation of more memory for routing tables or firewall filters might disrupt the forwarding operations of a Packet Forwarding Engine, the Junos OS CLI displays a warning to restart all affected FPCs when you commit a configuration that includes the memory-enhanced route statement. The configuration does not become effective until you restart the FPC or DPC (on MX Series routers).
To restart a single FPC or DPC without rebooting the entire router, issue the request chassis fpc slot slot-number restart command. On an M120 router, issue the request chassis feb slot slot-number restart command.
To view if the configuration is active on an FPC or DPC, issue the show pfe fpc slot-number command. The show pfe fpc command output shows the information about reallocation of the jtree memory on Packet Forwarding Engines.
For T Series routers only. With Junos OS Release 10.2, enhanced jtree memory allocation is disabled by default. For Junos OS Releases 9.3 through 10.1, the default routing tables (inet.0 and inet6.0) use both memory segments by default.
In Junos OS Release 11.2 and later, the memory-enhanced route statement at the [edit chassis] hierarchy level replaces the route-memory-enhanced statement at the [edit chassis] hierarchy level.
The filter and vpn-label statements are supported only on T Series routers.