Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

New and Updated Features

This section describes the new features in the Juniper Cloud-Native Router (JCNR) 25.2 release.

New Features in Juniper Cloud-Native Router Release 25.2

  • Support for Layer 2 Circuits—Juniper Cloud-Native Router supports Layer 2 circuits for a point-to-point Layer 2 connection over an IP/MPLS-based service provider's network. To establish the Layer 2 circuit, it uses Label Distribution Protocol (LDP) as the signaling protocol to advertise the ingress label to the remote PE routers. A targeted LDP session is established between the loopback addresses of the two PEs to exchange VPN labels. You can enable Layer 2 circuit features on Physical (PF/VF), VLAN sub-interface, bond interface (towards core), and pod interfaces.

  • Support for multiple IPSec tunnels with service chaining on a single pair of interfaces—Juniper Cloud-Native Router supports multiple IPSec tunnels for security services through service chaining with Juniper cSRX on a single pair of interfaces.

  • Telemetry data for Layer 2 Circuits—Juniper Cloud-Native Router provides telemetry data for Layer 2 circuits through Prometheus-based API and gRPC Network Management Interface (gNMI).

  • Support for Multihop BFD—Juniper Cloud-Native Router supports both single-hop and multihop Bidirectional Forwarding Detection (BFD) protocol to detect failures in a network.

  • Overlay management access—Juniper Cloud-Native Router can be managed across an overlay network. This allows you to situate your management host on the overlay network instead of only on the underlay network, giving you more options in your network implementation.

  • Wind River pre-bound L2 interfaces—In a Wind River deployment, Juniper Cloud-Native Router supports pre-bound L2 interfaces in addition to pre-bound L3 interfaces.

  • Support for Dropper and Shaper modules in Layer-3 Class of Service—Juniper Cloud-Native Router supports the DPDK dropper module that drops packets arriving at the scheduler block to avoid congestion. The drop is performed based on the weighted random early detection (WRED) drop profile maps. The Cloud-Native Router also supports configuring a transit rate to shape traffic per egress queue, preventing high priority queues from starving low priority queues.

  • Support for configuring IPSec tunnels post deployment using Configlets—Juniper Cloud-Native Router supports deploying IPSec tunnels post cSRX deployment using configlets. You must set the enableUserConfig flag to true in the installation helm chart. You can then create IPSec tunnels or modify the tunnel configuration after deployment using a configlet.

  • Support for four QoS scheduler cores—Juniper Cloud-Native Router supports up to four cores for the QoS scheduler (up from one).

  • Contrail Tools—Juniper Cloud-Native Router makes available the optional Contrail Tools package, with initial support for the collect_jcnr_support_info and dpdkvifstats commands (to collect troubleshooting information and DPDK performance statistics respectively).