Chassis

Support for Forwarding Information Base (FIB) installation and prefix prioritization (PTX10001-36MR, PTX10004, PTX10008, and PTX10016) that includes:

• FIB Prefix Prioritization: Applied at routing policy level. FIB prefix prioritization is currently supported only for IPv4 & IPv6.

• FIB prioritization: A system-wide configuration, where the user can specify percentage of memory to be reserved for high-priority and medium-priority IP routes at device level. High and medium priority routes are installed using the pre-allocated resource pools with default or user-defined limits. The number of high-priority or medium-priority routes supported depends on memory available on the FPCs. This feature provides an extra level of assurance that important routes are installed and retained into the FIB.

The list of important routes may include the following:

• Interface and local routes
• Host routes
• IGP routes
• Certain important BGP routes for various infrastructure services or business-critical services
• Static, aggregate, and generated routes

The related CLI commands are as follows:

At the device level:

• fib-prioritization (high-priority-memory-percent <memory_percent> | medium-priority-memory-percent <memory_percent>)
• Use the show pfe route summary command to view the total number of errors per route table per FPC slot.

At the routing policy level:

• Configure route installation prioritization based on user-configurable priorities through the forwarding table export policy, using the command set policy-options policy-statement <policy-name> term <term-name> then fib-install-priority (high | medium).
• Use the show route extensive command to confirm if the FIB priority flag is set or cleared correctly according to the configuration.

• Route prioritization is based on user-configurable priorities using forwarding tables. Interface routes bypass the policy evaluation and receive the highest priority unconditionally.
• If a next-hop installation fails, then the addition of any high-priority route can fail.
• If a user adds a static route for the same host that is at a higher priority over a destination host route, the user-defined route is selected as the best route by default.
• You must reboot the device every time the FIB prioritization configuration is changed.

Support for JNP10K-RE2-E128 Routing Engines on PTX10008 Packet Transport Routers. The new routing engines come with a Trusted Platform Module (TPM) 2.0 chip that supports secure device IDs (DevID).

DevID is a device ID with an X.509 cryptographic certificate. DevID uniquely identifies the device and helps Juniper Networks validate device authenticity. It is programmed in to the TPM 2.0 chip during manufacturing and contains the serial number of the device. The key benefits of the TPM 2.0 chip are that:

• It supports Secure Zero Touch Provisioning (sZTP).
• It helps Juniper Networks validate the authenticity of the device.
• It protects device data.

JNP10K-RE2-E128 routing engines replace the JNP10K-RE1-E128 routing engines. The new TPM2.0-based SKU Model names are:

• JNP10K-RE2-E128 (Spare)
• JNP10K-RE2-E128-BB (Bundle)
• JNP10K-RE2-E128-R (Dual RE)

[See Zero Touch Provisioning, PTX10008 Hardware Guide, Master Password for Configuration Encryption .]