Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Important Features in Junos OS Release 19.4

 

For details on these features, go to the other chapters in this guide or click the link in the feature description below.

  • Inline monitoring services (MX Series with MPCs excluding MPC10E and MPC11E linecards)—Starting in Junos OS Release 19.4R1, you can configure a new monitoring technology that provides the flexibility to monitor different streams of traffic at different sampling rates on the same interface. You can also export the packet up to the configured clip length to a collector in an IP Flow Information Export (IPFIX) format. The IPFIX format includes important metadata information about the monitored packets for further processing at the collector.

    The inline monitoring services overcome the limitations of traditional sampling technologies, such as JFlow, sFlow, and port mirroring, thereby providing you the benefit of effective sampling and troubleshooting processes.

    [See How to Configure Inline Monitoring Services.]

  • Integrating RIFT protocol into Junos OS (MX Series, QFX Series, and VMX virtual routers)—Starting in Junos OS Release 19.4R1, you can integrate a new IGP protocol, Routing in Fat Tree (RIFT), into Junos OS to route packets in variants of CLOS-based and fat tree network topologies (also called the spine and leaf model).

    The RIFT protocol is capable of automatic construction of fat-tree topologies, providing you the benefit of having a close to zero necessary configuration. RIFT makes networks resilient, extensively traceable, and simpler to manage, thereby overcoming the deployment limitations of evolving IP fabrics.

    [See How to Integrate RIFT protocol into Junos OS.]

  • Junos Multi-Access User Plane (MX240, MX480, MX960)—With Junos OS Release 19.4R1, we introduce Junos Multi-Access User Plane, a software solution that turns your MX router into a high-capacity user plane function called a System Architecture Evolution Gateway-User Plane (SAEGW-U). This MX SAEGW-U interoperates with a third-party SAEGW-C (control plane function), per 3GPP Release 14 Control User Plane Separation (CUPS) architecture, to provide high-throughput 4G and 5G fixed-wireless access service with support for 5G non-stand-alone (NSA) mode. CUPS enables independent scaling of the user and control planes, network architecture flexibility, operational flexibility, and an easier migration path from 4G to 5G services. The CUPS architecture is optional for 4G but inherent in 5G architecture.

    To transform your MX240, MX480, or MX960 router into an SAEGW-U, all you need is at least one MPC7 linecard, a routing engine with at least 32GB memory, and Junos OS Release 19.4R1.

    [See Junos Multi-Access User Plane.]

  • Microsoft Azure Key Vault (HSM) integration (vSRX 3.0)—Starting in Junos OS Release 19.4R1, vSRX 3.0 is integrated with Microsoft Azure Key Vault hardware security module (HSM). With the integration of Microsoft Azure Key vault HSM, vSRX can protect and manage sensitive data such as private cryptographic keys, passwords, and configurations.

    [See Deployment of Microsoft Hardware Security Module on vSRX 3.0.]

  • Support for BGP PIC Edge with BGP labeled unicast (MX Series and PTX Series)—Starting with Junos OS Release 19.4R1, MX Series and PTX Series routers support BGP PIC Edge with BGP labeled unicast as the transport protocol. BGP PIC Edge using the BGP labeled unicast transport protocol helps to protect and reroute traffic when border nodes (ABR and ASBR) failures happen in multi-domain networks. Multi-domain networks are typically used in Metro Ethernet aggregation and Mobile Backhaul networks designs.

    [See How to Protect and Reroute Traffic Using BGP Labeled Unicast.]

  • Support for flexible algorithm in IS-IS for segment routing–traffic engineering (MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, you can thin slice a network by defining flexible algorithms that compute paths using different parameters and link constraints based on your requirements. For example, you can define a flexible algorithm that computes a path to minimize IGP metric and define another flexible algorithm to compute a path based on traffic engineering metric to divide the network into separate planes. This feature allows networks without a controller to configure traffic engineering and utilize segment routing capability of a device.

    To define a flexible algorithm, include flex-algorithm statement at the [edit routing-options] hierarchy level.

    To configure participation in a flexible algorithm include the flex-algorithm statement at the [edit protocols isis segment routing] hierarchy level.

    [See How to Configure Flexible Algorithm in IS-IS for Segment Routing Traffic Engineering.]

  • Wi-Fi Mini-Physical Interface Module (SRX320, SRX340, SRX345, and SRX550M)—In Junos OS Release 19.4R1, we introduce the Wi-Fi Mini-Physical Interface Module (Mini-PIM). For retail and small offices, the Wi-Fi Mini-PIM provides secure wireless LAN connectivity to endpoint devices. The Wi-Fi Mini-PIM supports 802.11ac wave 2 wireless standards.

    [See Wi-Fi Mini-Physical Interface Module Overview.]