Junos OS Release 191R3 For The ACX Series EX Series MX Series NFX Series PTX Series QFX Series SRX Series And Junos Fusion Tech

Februari 11, 2023Januari 19, 2023 falma.u99 191r3, fusion, junos, release, series

These release notes accompany Junos OS Release 19.1R3 for the PTX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at /documentation/product/en_US/junos-os.

What’s New
Learn about new features introduced in the Junos OS main and maintenance releases for PTX Series.

What’s New in 19.1R3
There are no new features or enhancements to existing features for PTX Series Packet Transport Routers in Junos OS Release 19.1R3.

What’s New in 19.1R2
There are no new features or enhancements to existing features for PTX Series Packet Transport Routers in Junos OS Release 19.1R2.

What’s New in 19.1R1
Hardware
* QFX S-6Q line card (PTX10008 and PTX10016 routers)—Starting with Junos OS Release 19.1R1, the QFX S-6Q line card provides 60 SFP+ ports that can be configured at either 10-Gbps or 1-Gbps, and six flexible configuration ports for 100-Gbps and 40-Gbps. By default, all the ports will be in the 10-Gbps mode. Of the six flexible configuration ports, two ports have QSFP28 sockets that support either 100-Gbps, 40-Gbps, or 10-Gbps speeds. The remaining four ports have QSFP+ sockets that can be configured as either a native 40-Gbps port or four 10-Gbps ports using a breakout cable. With breakout cables, the line card supports a maximum of 84 logical 10-Gigabit Ethernet ports.

* Support for 40-Gbps ports to operate at 10-Gbps or 1-Gbps speed (PTX1000, PTX10008, and PTX10016)—Starting in Junos OS Release 19.1R1, you can use the Mellanox 10-Gbps pluggable adapter (QSFP+ to SFP+ adapter or QSA; model number: MAM1Q00A-QSA) to convert quad-lane based ports to a single-lane based SFP+ port. The QSA adapter has the QSFP+ form factor with a receptacle for the SFP+ module. Use the QSA adapter to convert a 40-Gigabit Ethernet port to a 10-Gbps port or a 1-Gbps port . You can then plugin a 10-Gbps SFP+ transceiver or a 1–Gbps SFP transceiver into the QSA adapter, which is inserted into the QSFP or QSFP+ ports of the PTX1000 router or the PTX10K-LC1101 and PTX10K-LC1102 line cards of the PTX10008 and PTX10016 routers. [See PTX1000 Transceivers, PTX10008 Transceivers, and PTX10016 Transceivers.]

Authentication, Authorization, and Accounting (AAA)
* Support for SFTP global disablement (PTX Series)—Starting in Junos OS Release 19.1R1, we have globally disabled incoming SSH File Transfer Protocol (SFTP) connections by default. You can enable incoming SFTP connections globally by configuring the statement sftp-server at the [edit system services ssh] hierarchy level. Prior to Junos OS Release 19.1R1, the incoming SFTP connections were globally enabled by default. [See Configuring sftp-server.]

Class of Service
* Support for class of service (CoS) (PTX C)—Starting in Junos OS Release 19.1R1, PTX C routers support class of service (CoS) functionality for IPv6 traffic. Only default and custom INET, DSPC, and DSPC IPv6 classifiers are supported. Rewrite rules are not supported. CoS is the assignment of traffic flows to different service levels. Service providers can use router-based CoS features to define service levels that provide different delay, jitter (delay variation), and packet loss characteristics to particular applications served by specific traffic flows. [See CoS Features and Limitations on PTX Series Routers.]

Forwarding and Sampling
* Support for tracking static RPM routes across multiple next hops (PTX Series)—Starting in Junos OS Release 19.1R1, you can use rpm-tracking to track up to 16 next hops for RPM-controlled static routes. This features supports both IPv4 and IPv6 static rpm-tracked routes, and extends the single-hop rpm-tracking introduced in Junos OS Release 18.4. [See show route rpm-tracking.]

* Support for using IP addresses in a SR-TE LSP segment list (PTX series)—Starting in Junos OS Release 19.1R1, you can use IP addresses (IPv4 or IPv6) for next hops in a segment routing traffic engineering (SR-TE) list of label-switched paths (LSPs). This work extends the support for traffic steering based on a segment routing policy that was introduced in Junos OS Release 17.4R1, wherein the controller can specify a segment routing policy consisting of multiple paths to steer labeled or IP traffic. [See auto-translate in segment-list and retry-timer in source-packet-routing.]

Junos Telemetry Interface
* Support for the Junos telemetry interface (JTI) (PTX10002)—Starting with Junos OS Release 19.1R1, you can provision sensors through the Junos telemetry interface to export telemetry data for several network elements without involving polling. You can stream data through UDP or gRPC. Only the following sensors are supported on PTX10002 routers: * Physical interfaces statistics * Label-switched-path (LSP) statistics * Network processing unit (NPU) memory * NPU memory utilization * CPU memory

To provision sensors to stream data through UDP, all parameters are configured at the [edit services analytics] hierarchy level. To provision a sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models. [See Guidelines for gRPC Sensors (Junos Telemetry Interface) and show chassis hardware.]

* Transit SPRING sensor support on Junos telemetry interface (JTI) (PTX3000 and PTX5000 with FPC2)—Starting in Junos OS Release 19.1R1, JTI sensor support is available for Source Packet Routing in Networking (SPRING), also known as segment routing. Segment routing is a control-plane architecture that enables an ingress router to steer a packet through a specific set of nodes and links in the network. Segment routing statistics must first be enabled before the sensor can be configured and statistics streamed to an outside collector by means of JTI. To enable collection of statistics, configure set protocols isis source-packet-routing sensor-based-stats per-sid ingress through the Junos CLI. To configure the sensor for statistics to be issued to an outside collector, include the following path for either UDP (native) or gRPC streaming: * /junos/services/segment-routing/sid/usage/

For exporting statistics using UDP native sensors, configure parameters at the [edit services analytics] hierarchy level. To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos telemetry interface (JTI). [See sensor (Junos Telemetry Interface), Configuring a Junos Telemetry Interface Sensor (CLI Procedure), and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

* RSVP interface OpenConfig model support and self-ping logs on Junos telemetry interface (JTI) (PTX10003 )—Starting in Junos OS Release 19.1R1, JTI sensor support is enhanced for RSVP interfaces to include delivery of more statistics. The level of support is equivalent to the output delivered when using the show rsvp interface detail operational mode command. To configure the sensor for statistics to be issued to an outside collector, include the following path for gRPC streaming: * /network-instances/network-instance/mpls/signaling-protocols/rsvp-te/interface-attributes/interfaces/interface/*

To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos telemetry interface (JTI). [See gRPC Services for Junos Telemetry Interface and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

* Support for LSP statistics on Junos telemetry interface (JTI) (PTX C)—Starting with Junos OS Release 19.1R1, you can provision the LSP statistics sensor /junos/services/label-switched-path/usage/ to monitor per-MPLS LSP statistics on the PTX C router and export telemetry data through JTI to external collectors. You can stream data at configurable intervals through gRPC without involving polling. JTI support is only for RSVP LSPs. Statistics that are streamed are similar to the output displayed by the operational mode command show mpls lsp bypass statistics. To provision a sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI). To enable statistics for export from the Junos OS, include the sensor-based-stats statement at the [edit protocols mpls] hierarchy level. [See Guidelines for gRPC Sensors (Junos Telemetry Interface) and Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

* Export of data associated with the Junos kernel through Junos Telemetry Interface (JTI) (PTX Series)—Starting in Junos OS Release 19.1R1, you can export data associated with the Junos kernel through remote procedure calls (gRPC) and JTI. Kernel telemetry data includes information on Veriexec state, graceful Routing Engine switchover (GRES), in-service software upgrade (ISSU), and Routing Engine ifstate. Junos kernel sensors can be used by device monitoring and network analytics applications to provide insight into the health status of the Junos kernel. Junos kernel sensors introduced in Junos OS Release 19.1R1 support both periodical and ON_CHANGE streaming. The following Junos kernal resource paths support periodical streaming only: * /junos/kernel-ifstate/dead-ifstates-cnt * /junos/kernel-ifstate/alive-ifstates-cnt * /junos/kernel-ifstate/delayed-unrefs-cnt * /junos/kernel-ifstate/delayed-unrefs-max

[See Understanding OpenConfig and gRPC on Junos Telemetry Interface and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

Layer 3 Features
* Support for Layer 3 unicast features (PTX10001)—Starting in Junos OS Release 19.1R1, PTX10001 routers support the following Layer 3 forwarding features for unicast IPv4 and IPv6 traffic: * Basic IPv6 Forwarding * Virtual router (VRF-lite) for both IPv4 and IPv * Layer 3 subinterfaces support for both IPv4 and IPv * VRF-lite, subinterfaces and IPv6 forwarding support on link aggregation group (LAG) * Statistics support for Layer 3 subinterfaces * 32-way equal-cost multipath (ECMP) * Centralized Bidirectional Forwarding Detection (BFD) * IPv4 Layer 3 protocols such as * IPv6 Layer 3 protocols such as

MPLS
* Flexible MPLS label stack depth (PTX Series routers with third-generation FPCs)—Currently, Junos OS supports push of up to a maximum of five labels per component of the next hop chain, even though the underlying device capability can be higher. Starting in Junos OS Release 19.1R1, the device capability of pushing more than 5 labels can be leveraged for features, such as, segment routing traffic engineering (TE) LSPs and RSVP-TE pop-and-forward LSPs. The number of labels that can be pushed for an MPLS next hop is the number of labels the device is capable of pushing, or the maximum-labels configured under family mpls of the outgoing interface, whichever is smaller. [See Configuring the Maximum Number of MPLS Labels, maximum-labels.]

* Support for MPLS ping and traceroute for segment routing (PTX Series)—Starting in Junos OS Release 19.1R1, MPLS ping and traceroute are supported for segment routing for protocols IS-IS and OSPF over IPv4. This feature also supports ECMP traceroute for protocols IS-IS and OSPF. In Junos OS Release 19.1R1, MPLS ping and traceroute for segment routing supports IPv4 IGP-Prefix segment FEC validation. FEC validation for IGP-Adjacency Segment ID is not supported. [See ping mpls segment routing isis, ping mpls segment routing ospf, traceroute mpls segment-routing ospf, traceroute mpls segment-routing isis.]

* Enhancements to MPLS for LSP path selection (PTX Series)—Starting in Junos OS Release 19.1R1, the following enhancements to MPLS have been added for LSP path selection and optimization: * Earlier when LSP active paths were modified, the LSP path gets cleared and gets resignaled immediately. From Junos OS Release 19.1R1 onward, if a secondary path is available, then Junos OS selects the secondary path as active, clears and resignals the primary path after the expiry of the optimize-hold-dead-delay timer. When the primary LSP path is established, the revert-timer gets started. After the revert-timer expires, the primary LSP path becomes active. If the primary LSP path is not active with revert-timer on and when there is a change to the primary LSP path, then the LSP path gets cleared and resignaled immediately. When the primary LSP path is established, the revert-timer gets restarted. * Earlier, if there was any Constrained Shortest Path First (CSPF) failure then the current LSP path becomes invalid because it did not match with the configured constraints. In this case, the current LSP path gets cleared immediately. From Junos OS Release 19.1R1 onward, if a secondary LSP path is available, then Junos OS selects the secondary LSP path as active and clears the primary path after the expiry of the optimize-hold-dead-delay timer. * The CLI command no-bypass-statistics-polling added under the [edit protocols mpls statistics] hierarchy now provides information on bypass LSP statistics. * A new CLI command delay has been introduced under the [edit protocols mpls optimize-adaptive-teardown] hierarchy and the value for delay is in the range of (3..65535 seconds). When the adaptive-teardown configuration is triggered, the delay CLI command further delays the tearing down of old optimized LSP paths based on the configured value. [See statistics (Protocols MPLS), optimize-adaptive-teardown.]

* Control transport address used for targeted LDP session (PTX Series)—Currently, only the router ID or interface address is used as the LDP transport address. Starting in Junos OS Release 19.1R1, you can configure any other IP address as the transport address of targeted LDP sessions, session groups, and interfaces. This new configuration is applicable only for configured LDP neighbors that have Layer 2 circuit, MPLS, and VPLS adjacencies. This feature is beneficial when you have multiple loopback interface addresses, and different IGPs associated with LDP interfaces, and you can control the session established between targeted LDP neighbors with the configured transport address. [See Control Transport Address Used for Targeted-LDP Session.]

* MPLS egress traffic statistics for label IS-IS routes at ingress device (PTX Series)—Currently, sensors are available for collecting segment routing statistics for MPLS transit traffic, which is MPLS-to-MPLS in nature. Starting in Junos OS Release 19.1R1, additional sensors are introduced to collect segment routing statistics for MPLS egress traffic at the ingress provider edge (PE) device, which is IP-to-MPLS in nature. With this feature, you can enable sensors for label IS-IS segment routing egress traffic only, and stream the statistics to a gRPC client. [See Understanding Source Packet Routing in Networking (SPRING).]

* Policy-based multipath routes (PTX Series)—In segment routing networks with multiple protocols in the core, you can combine segment routing traffic-engineered (SR-TE) LDP routes and SR-TE IP routes to create a multipath route that is installed in the routing information base (also known as routing table). You can resolve BGP service routes over the mutlipath route through policy configuration and steer traffic differently for different prefixes. [See Policy-Based Multipath Routes Overview.]

* Use of SID labels as first hop for resolving non-colored static segment routing LSPs (PTX Series)—Currently, for a static non-colored segment routing traffic-engineered LSP to be usable, the first hop of the segment list must be an IP address. Only the second to nth hop could be segment identifier (SID) labels. Starting in Junos OS Release 19.1R1, this requirement does not apply. You can now configure SID labels as the first hop in the segment list. With this configuration, static non-colored segment routing LSPs are resolved using MPLS fast reroute (FRR) and weighted equal-cost multipath. Without this configuration, by default, the LSPs are resolved using IP address. [See Static Segment Routing Label Switched Path.]

* Support of install statement for segment routing LSPs (PTX Series)—The install destination-prefix statement which is currently supported at the [edit protocols mpls label-switched-path lsp-name] and [edit protocols mpls static-label-switched-path lsp-name ingress] hierarchy levels is now also supported at the [edit protocols source-packet-routing source-routing-path lsp-name] hierarchy level for both colored and non-colored static segment routing label-switched paths (LSPs). You can associate one or more prefixes with a segment routing LSP using the install statement. When the LSP is up, all the prefixes are installed as entries into the inet.3 or inet6.3 routing table. [See install (Protocols MPLS).]

Network Management and Monitoring
Routing Policy and Firewall Filters
* Support for IPv6 firewall filters (PTX100020C)— Starting with Junos OS Release 19.1R1, you can configure a firewall filter with match conditions for IPv6 traffic (ingress direction only). You configure firewall filters under the [edit firewall] hierarchy level. This feature was previously supported in an “X” release of Junos OS. [See IPv6 Firewall Filter Match Conditions and Actions (PTX C).]

Routing Protocols
* Support for BGP graceful shutdown (PTX Series)— Starting in Junos OS Release 19.1R1, graceful traffic migration from one BGP next hop to another is supported, without traffic interruption. Also, BGP administrative shutdown communication can be sent to the BGP peer. You can configure both graceful-shutdown and shutdown statements at the [edit protocols bgp], [edit protocols bgp group group-name], and [edit protocols bgp groupgroup-name neighboraddress] hierarchy levels. NoteGraceful shutdown is disabled by default. [See: graceful-shutdown (Protocols BGP), shutdown (Protocols BGP).]

* Support for export of BGP Adjacency-RIB-Out through BGP Monitoring Protocol (BMP) (PTX Series)— Starting in Junos OS Release 19.1R1, BMP is enhanced to support route monitoring of pre and post rib-out policy. You can configure post-policy and pre-policy under rib-out statement at [edit protocols bgp bmp], [edit protocols bgp group group-name bmp], and [edit protocols bgp group group-name neighbor address bmp] hierarchies. NoteThe default monitoring mode of rib-out is pre-policy. [See: Understanding the BGP Monitoring Protocol.]

* Support for configurable SRGB used by SPRING in OSPF protocols (PTX Series)— Starting in Junos OS Release 19.1R1, you can configure the segment routing global block (SRGB) range label used by segment routing. Labels from this range are used for segment routing functionality in OSPF domain. The SRGB is a range of the label values used in the segment routing. Prior to Junos OS Release 19.1R1, you could not configure the range for the SRGB block. Locally you can configure srgb start-label index-range command under [edit protocols ospf source-packet-routing] hierarchy or globally under [edit protocols mpls label-range] hierarchy. Following are the SRGB precedences for OSPF protocol: * Local SRGB * Global SRGB * Node-segment implementation of 256 label block

[See source-packet-routing (Protocols IS-IS and OSPF).]

* Support for BGP advertising aggregate bandwidth across external BGP links for load balancing (PTX Series)—Starting in Junos OS Release 19.1R1, BGP uses a new link bandwidth extended community, aggregate-bandwidth, to advertise an aggregated bandwidth of multipath routes across external links. BGP calculates the aggregate of multipaths that have unequal bandwidth allocation and advertises the aggregated bandwidth to external BGP peers. A threshold to the aggregate bandwidth can be configured to restrict the bandwidth usage of a BGP group. In earlier Junos OS releases, a BGP speaker receiving multipaths from its internal peers advertised the link bandwidth associated with the active route. To advertise the aggregated bandwidth of multipath routes and to set a maximum threshold, configure a policy with the aggregate-bandwidth and limit bandwidth actions at the [edit policy-options policy-statement name then] hierarchy level. [See Advertising Aggregate Bandwidth Across External BGP Links for Load Balancing Overview.]

* Support for policy-based allocation for IPv4 BGP-labeled unicast (PTX Series)—Starting in Junos OS Release 19.1R1, this feature supports: * Allocating policy-based labels for IPv4 BGP-LU prefixes in per-prefix label allocation mode * 1:1 mapping between prefixes and labels * Map policy for labels * Fallback actions of dynamic and reject for handling error conditions

[See policy-options, route-filter-list.]

* Support for BGP link-state distribution with SPRING extensions (PTX Series)—Starting in Junos OS Release 19.1R1, BGP link-state extensions export segment routing topology information to software-defined networking controllers. Controllers can get the topology information by either being a part of an interior gateway protocol (IGP) domain or through BGP link-state distribution. BGP link-state distribution is supported on inter-domain networks and provides a scalable mechanism to export the topology information. This feature benefits networks that are moving to source packet routing in networking (SPRING) but also have RSVP deployed, and continue to use both SPRING and RSVP in their networks. In this release, OSPF link-state protocol is supported, which pushes SPRING information to the BGP link-state address family. [See Link-State Distribution Using BGP Overview.]

* Scalability for LDP-over-RSVP and BGP labeled unicast services (PTX Series)—Starting in Junos OS Release 19.1R1, this feature enhances RPD to produce the chain next hop for various services. The RPD is enhanced to build a translation layer between RIB and FIB to segment multi protocol transport tunnels. Segmentation happens as follows: * Only LDP, RSVP, LDP-over-RSVP, and LDP-over-RSVP-over-BYPASS ingress tunnels are considered for segmentation. * Segmentation does not happen if there is only one label in the stack. * Segmentation happens at the application boundary. A next hop with two LDP labels in its stack or two RSVP labels will not be split into two next hops with one label each.

Any route resolution over LDP or LDP-over-RSVP is changed from INH->FNH to CNH->INH->CNH->FNH in kernel and Packet Forwarding Engine, and for LDP routes in INET.3, where the indirect next hop (INH) is an application installed in direction toward the final next hop (FNH). Any segmented stack introduces the composite chain next hop (CNH), where the segmented portion of the label stack precedes an INH or an FNH. The chain is collapsed and the resulting label stack is encoded in the packet header by the hardware before forwarding the packet. By chaining labels instead of stacking them, PTX Series memory is made available for FNH label operations, as well as CNH by grouping CNHs within the same unilist next hop (for ECMP) based on the label space identifier. The following applications are supported: * Transit * LBGP stitching with LDP over RSVP * Ingress * 6PE BGP-V6-Route->LBGP(Explicit V6 NULL label) over LDP over RSVP * 4PE BGP-V4-Route->LBGP(Explicit V4 NULL label) over LDP over RSVP * BGP-L3VPN over LDP over RSVP * BGP-V6-VPN over LDP over RSVP * BGP route with indirection resolving over LDP over RSVP * IBGP-V4-ROUTE over LDP over RSVP * IBGP-V6-ROUTE over LDP over RSVP

[See Tunneling LDP LSPs in RSVP LSPs Overview, BGP Route Resolution Overview.]

Services Applications
* Support for IPv4 and IPv6 inline active flow monitoring on IRB interfaces (PTX1000)—Starting in Junos OS Release 19.1R1, you can perform inline active flow monitoring for IPv4 and IPv6 traffic on integrated routing and bridging (IRB) interfaces. Both IPFIX and version 9 templates are supported. IRB interfaces enable a switch to identify packets that are being sent to local addresses to be bridged whenever possible and to be routed only when required. Switching or bridging uses fewer layers of processing than routing, thus reducing the number of address lookups. [See Inline Active Flow Monitoring on IRB interfaces.]

* Support for automatic restart of Two-Way Active Measurement Protocol (TWAMP) Client (PTX Series)—Starting in Junos OS Release 19.1R1, the TWAMP client restarts automatically after a network failure, a configuration change, or an IP connectivity issue. However, for the client to reconnect to the TWAMP server automatically, you must use 0 as the test-count value in the set rpm twamp client control-connection test-count command. Also, at the TWAMP server side, the default value of max-connection-duration in the set rpm twamp server max-connection-duration must also be 0. You can display the test results after the network recovers, or after the server is reachable, by using the set services rpm twamp client control-connection c1 persistent-results command. [See Understanding TWAMP Auto-Restart.]

* Port mirroring support for the IPv6 address family (PTX10001)—Starting in Release 19.1R1, Junos OS supports port mirroring on the PTX10001 router for the IPv6 address family. Port mirroring copies packets entering or exiting a port and sends the copies to a local interface for local monitoring. You can use port mirroring to send traffic to applications that analyze traffic for purposes such as monitoring compliance, enforcing policies, detecting intrusions, monitoring and predicting traffic patterns as correlating events. The PTX Series routers support the IPv6 (inet6) address family only. [See Configuring Port Mirroring.]

What’s Changed
Learn about what changed in the Junos OS main and maintenance releases for PTX Series.

What’s Changed in Release 19.1R3-S4
Infrastructure
* Support for unicast ARP request on table entry expiration—You can configure the device to send a unicast ARP request instead of the default broadcast request when an ARP table entry is about to expire. The retry requests are unicast at intervals of 5 seconds. Without this option, the retry requests are broadcast at intervals of 800 milliseconds. This behavior reduces ARP overall broadcast traffic. It also supports the use case where access nodes are configured not to forward broadcast ARP requests toward customer CPEs for security reasons and instead translate ARP broadcasts to unicast requests. To confirm whether this is configured, you can issue the following command: show configuration system arp | grep unicast-mode-on-expire. [See arp.]

What’s Changed in 19.1R3
General Routing
* Advertising 32 secondary loopback addresses to traffic engineering database as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We’ve made changes to export multiple loopback addresses to the lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router IDs instead of prefixes. In earlier releases, multiple secondary loopback addresses in the traffic engineering database were added to the lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router ID.

Interfaces and Chassis
* Updates to the show interfaces and show policer commands (PTX Series)—Starting in Junos OS Release 19.1R3, on PTX Series routers, when you issue the show interfaces command or the show policer command, the output does not display the default ARP policer (_default_arp_policer_). In earlier releases, when you issue the show interfaces command or the show policer command, the output displays the default ARP policer (_default_arp_policer_) although PTX Series routers do not support the default ARP policer.

Routing Protocols
* Advertising 32 secondary loopback addresses to Traffic Engineering Database (TED) as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—In Junos OS Release, multiple loopback addresses export into lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router-ids instead of prefixes. In earlier Junos OS releases, multiple secondary loopback addresses in TED were added into lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router-id.

What’s Changed in 19.1R2
General Routing
* User confirmation prompt for configuring the sub options of request vmhost commands (MX Series and PTX series)—While configuring the following request vmhost commands, the CLI now prompts you to confirm a [yes,no] for the sub options also. * request vmhost reboot * request vmhost poweroff * request vmhost halt

In previous releases, the confirmation prompt was available for only the main options.

Network Management and Monitoring
* The show system schema command and RPC require specifying an output directory (PTX Series)—Starting in Junos OS Release 19.1R2, when you issue the show system schema operational mode command in the CLI or execute the RPC in a remote session to retrieve schema files, you must specify the directory in which to generate the output files by including the output-directory command option in the CLI or the element in the RPC. In earlier releases, you can omit the output-directory argument when requesting a single module to display the module in standard output.

Routing Protocols
* Change in the default behavior of advertise-from-main-vpn-tables configuration statement—BGP now advertises EVPN routes from the main bgp.evpn .0 table. You can no longer configure BGP to advertise the EVPN routes from the routing instance table. In earlier Junos OS Releases, BGP advertised EVPN routes from the routing instance table by default. [See advertise-from-main-vpn-tables.]

Software-Defined Networking
* Increase in the maximum value of delegation-cleanup-timeout (PTX Series)—You can now configure a maximum of 2,147,483,647 seconds as the delegation cleanup time for a Path Computation Client (PCC). This extends the time taken by the PCC to retain the last provided path over a PCEP session from the last session down time. With the increase in maximum value of delegation-cleanup-timeout from 600 to 2,147,483,647 seconds, you can benefit during a Path Computation Element (PCE) failover, or other network issues that might disrupt the PCEP session with the main active stateful PCE. [See delegation-cleanup-timeout.]

What’s Changed in 19.1R1
EVPNs
* Starting with Junos OS Release 19.1R1, the no-arp-suppression configuration statement is no longer supported on any device.

Interfaces and Chassis
* Support to get optics loopback status for QSFP-100GE-DWDM2 transceivers (PTX Series)—Starting in Junos OS Release 19.1R1, you can get the optics loopback status of QSFP-100GE-DWDM2 transceivers along with the regular Ethernet loopback status by issuing the show interfaces interface-name or show interfaces interface-name brief command. The new utput field Optics Loopback is added under Link-level type when the show interfaces interface-name CLI command is executed.

* New XML tag element added in show lacp interfaces XML display (PTX Series)—Starting in Junos OS Release 19.1R1, the show lacp interfaces | display xml command displays a new XML tag element . The displays the time interval an interface holds before it changes from state, down to up. In earlier Junos OS releases, the LACP hold-up information for all interfaces was in a single XML tag. Now, for each interface it is displayed in a separate XML tag.

* Support for creating Layer 2 logical interface independently (ACX Series, EX Series, MX Series, PTX Series, and QFX Series)—Starting in Junos OS Releases 18.4R1, 18.4R2, 19.1R1, and later, PTX Series routers support creating Layer 2 logical interfaces independent of the Layer 2 routing-instance type. That is, you can configure and commit the Layer 2 logical interfaces separately and add the interfaces to the bridge domain or Ethernet VPN (EVPN) routing instance separately. Note that the Layer 2 logical interfaces work fine only when they are added to the bridge domain or EVPN routing instance. In earlier Junos OS releases, when you use a Layer 2 logical interface configuration (units with encapsulation vlan-bridge configuration), then you must add the logical interface as part of a bridge domain or EVPN routing instance for the commit to succeed.

MPLS
* New debug statistics counter (PTX Series)—The show system statistics mpls command has a new output field, called Packets dropped, over p2mp composite nexthop, to record the packet drops over composite point-to-multipoint next hops.

Network Management and Monitoring
* NETCONF operation returns different values in when the session identifier is equal to the current session ID (PTX Series)—Starting in Junos OS Release 19.1R1, when you execute the NETCONF operation and the session identifier is equal to the current session ID, the values of the and elements in the resulting are application and invalid-value, respectively. In earlier releases, the and values are protocol and operation-failed. [See .]

* sysName.0 MIB object displays the fully qualified domain name (PTX Series)—Starting in Junos OS Release 19.1R1, the sysName.0 MIB object displays the fully qualified domain name. That is, if the hostname and domain name are configured on the system, both show up for the sysName.0 MIB object: host-name.domain-name. Previously, only the hostname showed up. [see show snmp mib.]

* Change in error severity (PTX10016)—Starting in Junos OS Release 19.1R1, on PTX10016 routers, the severity of the FPC error, shown in the syslog as PE Chip::FATAL ERROR!! from PE2[2]: RT: Clear Fatal if it is detected LLMEM Error MEM:llmem, MEMTYPE: 1, is changed from fatal to non fatal (or minor). In case of this error, only a message is displayed for information purposes. To view the error details, you can use the commands show chassis fpc errors and show chassis errors active. [See show chassis fpc errors.]

Services Applications
* Support for enabling hardware timestamping of RPM probe messages (PTX Series)—Starting in Junos OS Release 19.1R1, PTX Series routers support timestamping of RPM probe messages on the Packet Forwarding Engine. The following configuration statements at the [edit services rpm probe owner test test-name] hierarchy level are supported: * hardware-timestamp—To enable timestamping of RPM probe messages in the Packet Forwarding Engine host processor. * one-way-hardware-timestamp—To enable timestamping of RPM probe messages for one-way delay and jitter measurements.

These features are supported only with icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp probe types.

User Interface and Configuration
* Options for monitor traffic interfaces statement added (PTX Series)—Starting in Junos OS Release 19.1R1, the options write-fileand read-file under the monitor traffic command are included in the visible CLI. [See monitor traffic.]

Known Limitations
Learn about known limitations in this release for PTX Series routers.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing
* On PTX switches with FPC3, if the filter action of policer and count are configured in one same filter term, then it might cause the policer counter to be higher than the actual count. PR * When an FPC goes offline or restarts, FPC x sends traffic to FPC y. PR * The Routing Engine boots from the secondary disk when you: * Press the reset button, on the RCB front panel, while the Routing Engine is booting up but before Junos OS is up. * Upgrade software, by booting from the network using the request vmhost reboot network command, and the system fails to boot from the network. * Upgrade BIOS and the upgrade fails. * Reboot and the system hangs before Junos OS is up. PR * PTX1000 sFlow sampling output has different VLAN priority in extended switch data fields with the same dual-tag configuration when egress sampling is configured. This issue is dependent on the sequence in which sampling and MAC rewrite happen. In MX Series MAC rewrite occurs after sampling and in the case of PTX Series sampling happens after MAC rewrite. PR * The request vmhost power-off command does not actually power off the system in the latest releases. It only does a reboot and the system comes back up. PR * Frames that cannot be fragmented and are larger than the outgoing interface MTU size are dropped; however, the show interface statistics extensive output might not show these dropped frames against output errors and MTU errors. PR * In case of stacked VLAN Series tagging, VLAN tagged frames counter is not supported for LC1101, LC1102, and LC1103 series card in PTX Series. PR Open Issues
Learn about open issues in this release for PTX Series routers.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing
* On a PTX Series PIC with the CFP2-DCO-T-WDM transceiver installed, after repeated configuration rollbacks, the link sometimes takes a long time to come up. PR * When CFP2-DCO-T-WDM-1 is plugged in a PTX Series PIC, after FPC restarts, the carrier frequency offset TCA is raised even when TCA is not enabled. PR * In a specific case, when semigraceful RCB reboot is initiated by the internal shell command vhclient init 0, GRES takes longer to complete. That is, 3 minutes as opposed to 21 seconds. We don’t see this delay when we use the regular CLI command request vmhost reboot (graceful reboot) or disconnect the Routing Engine by plugging out the cable and reconnect it by plugging the cable back in (ungraceful reboot). PR * On a PTX Series router with a third-generation FPC, an error message is displayed when the FPC goes online or offline. PR * Alarm action does not work for minor errors after the threshold is changed to 1. PR * The user might not be able to stop the zero-touch provisioning (ZTP) bootstrap when a PTX10016 or PTX10008 router with more number of line cards is powered on with factory-default configuration. PR * Control plane switch management (CPSM) daemon memory leak occurs in the VM host. The issue might also cause logrotate not to work, and result in a large CPSM log size. PR * The show ephemeral-configuration command syntax was changed between Junos OS Release 17.2X75 and Release 18.2X75. In Junos OS Release 18.2X75, the correct command is show ephemeral-configuration instance. PR * Because of the small counter size present in the ASIC, the normal discard counter reported in the CLI is less than the actual packet drop rate. PR * The rx_power value streamed to the telemetry server is the raw value (mW) returned directly from the transceiver driver. The Junos CLI value has been transformed in the transportd daemon into different units: Rx input total power (0.01dBm). PR * Sometimes the SFP+ read does not work on one or more ports of the LC1103-2C/6Q/60X. If this happens, the corresponding SFP+ module does not get detected and is not displayed at the Routing Engine CLI in the output of show chassis hardware. As a workaround, re-seat the SFP+ module. PR * The telemetry statistics might not account correctly for the traffic on SRTE policies (both byte count and packet count) on PTX Series platforms. This is a sensor-related issue. PR * VTY command show filter index number counter shows values as zero at HOSTBOUND_NDP_DISCARD_TERM on a PTX5000 platform. Basically, the counter does not increase for NDP packets. The issue is only with show filter index, which is a debug tool in VTY. This issue has no impact on NDP functionality for user traffic. There are no issues with NDP functionality, and DDoS for NDP is also working. PR * The firewall counter for the lo0 interface does not increment for FPC3-PTX-U2 and FPC3-PTX-U3. PR * An em2 interface configuration causes an FPC to crash during initialization and the FPC does not come online. After you delete the em2 configuration and restart the router, the FPC comes online. PR * More packet loss is seen after unified ISSU with inter-AS Layer 3 VPN Option B configuration. PR * Memory leaks are observed while running the longevity check. PR Interfaces and Chassis
* Upgrading Junos OS Release 14.2R5 and later maintenance releases and Junos OS Release 16.1 and later mainline releases with CFM configuration might cause the cfmd process to crash after the upgrade. This is because of the presence of the old version of /var/db/cfm.db. PR Routing Protocols
* With bidirectional forwarding detection (BFD) configured on an aggregated Ethernet interface, if you disable or enable the aggregated Ethernet interface, then that interface and the BFD session might not come up. PR Resolved Issues
Learn which issues were resolved in the Junos OS main and maintenance releases for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 19.1R3
General Routing
* Line-card interface stays down after maintenance. PR * On PTX3000 routers, the core-olympus-fpc3-sevfpc.elf.0.tgz core file is generated after switchover with GRES. PR * LACP packet does not pass through Layer 2 circuit. PR * The host-bound traffic might be dropped after you perform a change operation related to the prefix-list configuration. PR * On PTX Series platforms, reclassification policy applied on the route prefixes might not work. PR * The l2cpd process might crash and generate a core file when interfaces flap. PR * The FPC might crash when a firewall filter is modified. PR * Changing the hostname triggers LSP on-change notification, and currently IS-IS is sending the hostname instead of the system ID in OC paths. PR * JNP10K-LC2101 FPC generates Voltage Tolerance Exceeded major alarm for EA_chip_2v5 sensors. PR * On PTX5000 router, the 100-Gigabit Ethernet interface might not come up after flapping. PR * Traffic gets dropped silently upon interface flap after DRD autorecovery. PR * The forwarding option is missed in routing-instance type. PR * Hardware failure in CB2-PTX causes traffic interruption. PR * On PTX10008 routers, the sample/syslog/log action in output firewall filter with packet size less than 128 bytes might cause an ASIC wedge (all packet loss). PR * On PTX3000 and PTX5000 routers, PICs might restart if the QSFP optics is overheated. PR * On PTX10000 platforms, the FPC might restart during run time. PR * On PTX Series platforms, EBUF parity interrupt is not seen. PR * IPv6 traffic between two CE devices might get dropped in a Layer 3 VPN. PR * On PTX5000 platforms, Packet Forwarding Engine error logs prds_packet_classify_notification: Failed to find fwd nh for flabel 48 might be reported when IGMP packets are sampled. PR * Optics measurements might not be streamed for interfaces of a PIC over JTI. PR * Incorrect counter values are observed for the arrival rate and peak rate for DDoS commands. PR * Traffic loops for pure Layer 2 packets coming over an EVPN tunnel with destination MAC matching IRB MAC. PR * On PTX10000 and PTX1000 platforms, MACsec traffic over a Layer 2 circuit might not work after upgrading from Junos OS Release 15.1 to later versions. PR Forwarding and Sampling
* On PTX Series or TVP platforms, the pfed might crash and might not be able to come up. PR Infrastructure
* On all Junos OS VM-based platforms, FPCs might reboot if jlock hog occurs. PR Interfaces and Chassis
* After a member interface flaps, the aggregated Ethernet interface remains down on 5-port 100-Gigabit Ethernet DWDM CFP2-ACO PIC. PR Multiprotocol Label Switching (MPLS)
* Kernel might crash and device might restart. PR Routing Protocols
* Route churn might be seen after the maximum-prefixes configuration is changed from value A to value B. PR * The rpd might crash with SRTE configuration change. PR * SSH login might fail if a user account exists in both the local database and RADIUS or TACACS+. PR * The rpd process might crash with BGP multipath enabled and the active route withdrawn occasionally. PR Resolved Issues: 19.1R2
General Routing
* The agentd sensor transmits multiple interface telemetry statistics per FPC slot. PR * Confirmation message is missing when issuing request vmhost reboot re*. PR * The DHCPv6 relay-reply packet might be dropped by the DHCP relay. PR * Incorrect memory statistics message is seen in FPC logs of PTX Type 1 FPC. PR * ZTP upgrade might fail if there is more than one 10-Gigabit Ethernet interface connected to the DHCP server. PR * On PTX3000 and PTX5000, the backup Control Board’s chassis environment status keeps “Testing” after the backup Control Board is removed or reinserted. PR * Openconfig-network-instance:network-instances support for IS-IS must be hidden unless supported. PR * The port at FPC(For example, JNP10K-LC1101) might fail to come up. PR * The CPU might be hogged by jsd process in JET scenario. PR * Hostname does not update at FPC shell after system configuration change on CLI. PR * Junos PCC might reject PCUpdate/PCCreate message if there is metric type other than type 2. PR * The PTX1000/PTX10002 might stop forwarding packets after the chassis-control process restarts. PR * Traffic loss could be seen for duration of hold-time down timer when flapping an interface with hold-time down timer configured. PR * RX alarms are not set as according to the threshold value configured for the DCO Tunable Optics. PR * An interface might go to down state on QFX10000/PTX10000 platform. PR * Virtual Chassis might become unstable and FXPC generates core files when there are a lot of configured filter entries. PR * Packet Forwarding Engine wedge might be observed after performing the command show forwarding-options load-balance … PR * The 4x10G interfaces on PTX3000/PTX5000 FPC type 3 might not come up after frequent flap ping occurs for a long time. PR * While committing a huge configuration, customer is seeing the error error: mustd trace init failed. PR * Traffic is dropped after FPC reboot with AE member links deactivated by remote device. PR * JDI-l2circuit-REGRESSIONS:AE not coming up with LACP enabled over the ccc circuit between R0 and R3. PR * The per-interface-per-member-link command is hidden for PTX5000 FPC. PR * Specific interface on P3-15-U-QSFP28 PIC card remains down until another interface comes up. PR * An interface with port 7, 9, 17, 19, 27, or 29 might go to down state on 30-port 40-Gigabit Ethernet or 100-Gigabit Ethernet line cards. PR * When an interface is configured with jumbo frames support (For example, MTU = 9216), the effective MTU size for locally sourced traffic is 24 bytes less than the expected value. PR * Inline Jflow might cause PECHIP Major error. PR * IPFIX J-Flow timestamp is not matching with NTP synchronized system time. PR * SIB Link Error detected on a specific Packet Forwarding Engine might cause complete service impact. PR * Scaled filter leads to packet drop as flt.Dispatcher.flt_err on PTX Series router. PR * IPv6 neighbor solicitation packets are getting dropped on PTX Series router. PR * On PTX10016 platforms, mastership cannot switch over immediately while facing SSD failure. PR * On PTX10002, no chassis alarm is raised when PEM is removed or power is lost to PEM. PR * Interfaces on PTX Series router might not come up after FPC restart or port flap. PR * BCM FW needs to be upgraded to DE2E. PR * Receipt of a malformed packet for J-Flow sampling might create a FPC process core file. PR * The jdhcpd process might crash after issuing the command show access-security router-advertisement-guard. PR * Egress sampling for sFlow might stop working for more than eight interfaces on PTX Series platforms. PR * Interfaces might flap forever after deleting the interface disable configuration. PR * Firewall filter applied at interface level is not working when entropy level is present in certain scenarios. PR * The FPC might crash when the severity of error is modified. PR Infrastructure
* Command request system recover oam-volume might fail on PTX Series router. PR * Unsupported package warning is seen after system upgrade. PR Interfaces and Chassis
* Syslog message /kernel: %KERN-3: pointchange for flag not supported on IFD aex occurs upon LFM-related configuration commit on AE interfaces. PR * After interface flap, the LAG/AE remains down on 5X100GE DWDM CFP2-ACO MIC. PR * Some ports on PTX might remain down after rebooting the FPC/device at remote side. PR Layer 2 Ethernet Services
* DHCP request might get dropped in DHCP relay scenario. PR MPLS
* Services dependent on LDP might be impacted if committing any configuration changes. PR * RSVP Path error received on PSB:2 (new path calculated by CSPF) is not treated as optimization when CSPF is computed and optimization retry is not honoring 2^retry + rsvp-error-hold-time. PR * The dynamic bypass RSVP LSP tears down when being used to protect LDP LSP. PR * The transit packets might be dropped if an LSP is added or changed. PR Platform and Infrastructure
* REST API process will get non responsive when a number of requests come in at a high rate. PR Routing Protocols
* Routing Engine based micro BFD packets do not go out with configured source IP when the interface is in logical system. PR * Syslog message is seen whenever prefix SID coincides with the node SID. PR * Dynamic routing protocol flapping with vmhost Routing Engine switchover occurs on next-generation Routing Engine. PR * PTX Series device cannot intercept PIM BSR message. PR * RPD might crash with OSPF overload configuration. PR VPNs
* In a specific CE device environment in which asynchronous notification is used, after the link between the PE and CE devices goes up, the L2 circuit flaps repeatedly. PR * Memory leak might happen if PIM messages are received over an MDT (mt- interface) in Draft-Rosen MVPN scenario. PR Resolved Issues: 19.1R1
General Routing
* Repeated log messages %PFE-3 fpcX expr_nh_index_tree_ifl_get and expr_nh_index_tree_ipaddr_get are observed when sampling packet is discarded with log (or syslog) statement under firewall filter. PR * On PTX Series platform, multicast traffic packet drop seen is more than 50 percent when having FPC1/FPC2 mix with FPC3. PR * On PTX10001 platform, the FRR link-protection convergence during FRR and MBB with various MPLS optimize-timers is observed. PR * The netproxy service client component fails to start after issuing request vmhost reboot command. PR * The IPLC card might take a long time to come up after requesting it online from an offline state. PR * Some harmless log messages are suppressed on the backup SPMB. PR * On PTX10001 platform, 100G-LR4 optics and 100G-ER4 optics are not supported. PR * Inline BFD might keep flapping when inline sampling is configured. PR * Traffic might be dropped on third-generation FPCs on PTX Series routers. PR * BFD sessions flap when restarting one FPC on PTX10000. PR * Packet Forwarding Engine based local repair does not happen for IP routes pointing to unilist of composites with indirect next hops. PR * Disable reporting of correctable single-bit error on Hybrid Memory Cube (HMC) and prevent the major alarm. PR * Packet drop might be seen in AF3 queue on PTX Series platforms. PR * The system might hang after issuing request system reboot. PR * BFD flaps are seen on PTX Series platforms with inline BFD. PR * Forwarding issue on mixed link-speed aggregated Ethernet interface after FPC reloads. PR * PTX C FPC might not be detected after the ukern crashes. PR * High jsd or na-grpcd CPU usage might be seen even when JET or JTI is not used. PR * CPU hog might be observed on PTX Series platform. PR * Log message JAM HW data base open failed for ptx5kpic_3x400ge-cfp8 occurs during commit. PR * On PTX3000, FPCs are not able to come online for tens of minutes after a reboot of the chassis. PR * The 100G SR4 optics with part number should be displayed as QSFP-100G-SR4-T2. PR * Layer 2 VPN flaps repeatedly after linkup between PE and CE devices under asynchronous notification and some types of MIC conditions. PR * For PTX C devices, the DHCP relay functionality and binding of DHCP do not work. PR * On PTX3000 router, the rpd crash is observed at if_addr_link, krt_chnh_template_create_restart, krt_chnh_create_restart, krt_comp_add_comp_nh, krt_build_comp_nh, krt_build_nexthop, krt_rt_add_sock, krt_decode_rt, krt_sysctl_read_consume, krt_rt_read,krt_sys_rtread, krt_var_init, ctx_handle_node, ctx_walk_features, task_read_config, main. PR Interfaces and Chassis
* PE Chip:pe0[0]: IPW: oversize_drop error causes major error on FPC. PR MPLS
* MPLS LSP will remain in down state because of routing loop detection after flapping link between PE router and egress PE. PR * The rpd might crash when LDP route with indirect next hop is deleted. PR * A single-hop bypass LSP might not be used for traffic when both transit chaining mode and sensor-based-stats are used. PR Platform and Infrastructure
* On PTX Series routers, the RPM hardware-timestamp and one-way-hardware-timestamp statements are not enabled. PR * When non-root user tries to archive the var/log, some files are missing from the cscript.log file. PR Routing Protocols
* The rpd process generates a core file on the backup Routing Engine during neighborship flap when using authentication key with size larger than 20 characters. PR * The rpd RT_NEXTHOPS_TEMPLATE memory leaks while using segment routing for IS-IS protocols. PR There are no errata or changes in Junos OS Release 19.1R3 documentation for the PTX Series.

Migration, Upgrade, and Downgrade Instructions
This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for the PTX Series. Upgrading or downgrading Junos OS might take several hours, depending on the size and configuration of the network.

Basic Procedure for Upgrading to Release 19.1
When upgrading or downgrading Junos OS, use the jinstall package. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide. Use other packages, such as the jbundle package, only when so instructed by a Juniper Networks support representative.

NoteBack up the file system and the currently active Junos OS configuration before upgrading Junos OS. This allows you to recover to a known, stable environment if the upgrade is unsuccessful. Issue the following command:

user@host> request system snapshot

NoteThe installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the router, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the Installation and Upgrade Guide.

NoteWe recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

To download and install Junos OS Release 19.1R3:

1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage: /support/downloads/

2. Select the name of the Junos OS platform for the software that you want to download.
3. Select the release number (the number of the software version that you want to download) from the Release drop-down list to the right of the Download Software page.
4. Select the Software tab.
5. In the Install Package section of the Software tab, select the software package for the release.
6. Log in to the Juniper Networks authentication system by using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
7. Review and accept the End User License Agreement.
8. Download the software to a local host.
9. Copy the software to the routing platform or to your internal software distribution site.
10. Install the new jinstal package on the router.NoteWe recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process. All customers except the customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package: user@host> request system software add validate reboot source/junos-install-ptx-x .1R3.9.tgz Customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (limited encryption Junos OS package): user@host> request system software add validate reboot source/junos-install-ptx-x .1R3.9-limited.tgz Replace the source with one of the following values: * /pathname—For a software package that is installed from a local directory on the router. * For software packages that are downloaded and installed from a remote location: * ftp://hostname/pathname * /pathname * scp://hostname/pathname The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release. Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes. Rebooting occurs only if the upgrade is successful.

NoteYou need to install the Junos OS software package and host software package on the routers with the RE-PTX-X8 Routing Engine. For upgrading the host OS on this router with VM Host support, use the junos-vmhost-install-x.tgz image and specify the name of the regular package in the request vmhost software add command. For more information, see the VM Host Installation topic in the Installation and Upgrade Guide.

NoteAfter you install a Junos OS Release 19.1jinstall package, you cannot return to the previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

NoteMost of the existing request system commands are not supported on routers with RE-PTX-X8 Routing Engines. See the VM Host Software Administrative Commands in the Installation and Upgrade Guide.

Upgrade and Downgrade Support Policy for Junos OS Releases
Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.4, 18.1, and 18.2 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3. However, you cannot upgrade directly from a non-EEOL release that is more than three releases ahead or behind.

To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information about EEOL releases and to review a list of EEOL releases, see /support/eol/software/junos/.

Upgrading a Router with Redundant Routing Engines
If the router has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation as follows:

1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos telemetry interface (JTI).

Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI).