Alert Type

SRN - Software Release Notification

Product Affected

ACX, MX, EX, PTX, QFX, vMX, vRR, NFX, SRX, vSRX

Alert Description

Junos Software Service Release version 19.2R1-S3 is now available for download from the Junos software download site
Download Junos Software Service Release:
  1. Go to  Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select  Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

Solution

19.2R1-S3 - List of Fixed issues

PR Number Synopsis Category: QFX ISSUE PFE related
1472183 ISSU will not be supported for QFX5K in 19.4R1
  		During unified ISSU from previous releases to Junos OS Release 19.4R1 for QFX5000 platforms, dc-pfe will crash continuously and hence ISSU will not work. This issue will be fixed in S1.
PR Number Synopsis Category: QFX PFE L2
1469596 Ingress traffic might be blackholed if underlying interfaces flap in EVPN/VXLAN scenario
  		On QFX5000 platforms with Ethernet Virtual Private Network (EVPN) and Virtual Extensible LAN (VXLAN) scenario, if there is the underlying interface flaps for the core network side, all the ingress traffic might be backholed by the VXLAN Tunnel Endpoint (VTEP) due to this issue.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1475819 QFX5110 EVPN vxlan : Cannot forward traffic over ECMP link after ECMP link was flapped
  		On QFX series switch, traffic failure would be seen after reprogramming an ECMP object when resilient hashing enabled.
PR Number Synopsis Category: "agentd" software daemon
1426871 The decoding of telemetry data at collector may not be proper if configuring the sensors
  		On EX and MX platforms, if configuring the sensors to stream data over UDP in static DB, decoding of telemetry data at collector may not be proper.
PR Number Synopsis Category: MPC Fusion SW
1454595 The 100G Interfaces may not come up again after going down on MPC3E-NG
  		On MPC3E-NG cards with 100G interface in use, if the interface detects Loss of Lock (LOL) on the link without Loss of Signal (LOS), the interface will go down and may not come up again after the link is recovered.
PR Number Synopsis Category: Bi Directional Forwarding Detection (BFD)
1432440 In BFD and GR enabled scenario, BFD DOWN packets are not being sent immediately after BFD failure
  		In both GR helper and GR restarter scenarios, BFD down packets are not immediately sent. It might cause an issue where BGP session down is notified before BFD DOWN.
PR Number Synopsis Category: Border Gateway Protocol
1442291 The rpd process might crash in inter-AS option B Layer 3 VPN scenario if CNHs is used
  		In inter-AS option B L3VPN scenario with chained composite next hops (CNHs) used, on autonomous system boundary router (ASBR), if the configuration family mpls on the ASBR to ASBR interface is missing, the rpd might crash when there is AS loop of the received inter-AS option B L3VPN routes. It is a timing issue.
1454951 The rpd process might crash when multipath is in use
  		If multipath is enabled, in some certain conditions, The rpd process might crash while secondary route resolution is running.
1463673 The rpd might crash if both BGP add-path and BGP multipath is enabled
  		With both BGP add-path and BGP multipath enabled, the rpd might crash when BGP is resolving a prefix which has secondary path that need independent resolution. The issue is introduced in 19.2R1.
PR Number Synopsis Category: Cassis pfe microcode software
1464820 MPC5E/6E might crash due to internal thread hogging the CPU
  		PR 1382182 (which is fixed in 16.2R3 17.1R3 17.3R3-S3 17.3R4 17.4R2-S3 17.4R3 18.1R3-S2 18.1R4 18.2R2 18.2X75-D40 18.3R2 18.4R1 19.1R1) introduced an improper code which could cause an internal thread to hog the CPU and eventually result in the MPC crash. It is a timing issue and affects MPC5E/6E.
PR Number Synopsis Category: MX Platform SW - FRU Management
1463169 MX2000 CB 19.44MHz clock failure is fatal, should trigger a CB switchover
  		Problem: CB clock failure does not switchover mastership. Primary CB with faulty clock can't operate normally. Solution: Interrupt based CB clock failure detection and RE mastership switchover from faulty CB. Whenever CB 19.44MHz clock failure is detected by HW, it generates interrupt and handled by Chassis-control process. Chassis-control process interrupt handler does a RE switch if GRES is active and backup RE is ready to take over.
PR Number Synopsis Category: PTX Chassis Manager
1462987 PIC may restart if the temperature of QSFP optics is overheated on PTX3K/5K
  		On PTX3K/5K platform with P3-24-U-QSFP28/P3-15-U-QSFP28/P3-10-U-QSFP28 PIC used, if the temperature of QSFP optics is overheated, the PIC might restart.
PR Number Synopsis Category: Device Configuration Daemon
1475634 Commit error is not thrown when member link is added to multiple aggregation group with different interface specific options
  		Commit error is not thrown when member link was added to multiple aggregation group with different interface specific options. When member interface added to bundle with both ether and gig-ether interface specific options, gig-ether option takes precedence over ether options.
PR Number Synopsis Category: Covers Application classification workflows apart from custo
1455465 The traffic loss might occur when application service is configured
  		On vSRX3.0 platform, the traffic loss might occur when application service is configured.
PR Number Synopsis Category: Kernel software for AE/AS/Container
1429917 The AE interface does not come up after rebooting the FPC/device though the physical member link is up
  		When a single FPC carries minimum 10 member links which belong to the same or different AE (Aggregate Ethernet) bundle, if one of the static AE bundle (LACP is not enabled) has disabled member link, this static AE interface does not come up after rebooting the FPC/device though it has physical member link with UP state.
PR Number Synopsis Category: jdhcpd daemon
1449353 Junos OS and Junos OS Evolved: Multiple vulnerabilities in JDHCPD allow for OS command injection and code execution of JDHCPD
  		A device using Juniper Network's Dynamic Host Configuration Protocol Daemon (JDHCPD) process configured relay mode is vulnerable to multiple vulnerabilities which allow an attacker to send crafted packets who may arbitrarily execute commands as root on the target device, or who may take over the code execution of the JDHDCP process. Refer to https://kb.juniper.net/JSA10981 [juniper.net] for more information.
PR Number Synopsis Category: Layer 2 Control Module
1461236 Explicit Deletion Notification (del_path) Not Received when LLDP Neighbor is Lost as result of disabling local interface on the DuT via CLI (gNMI)
  		Explicit Deletion Notification (del_path) Not Received when LLDP Neighbor is Lost as result of disabling local interface on the DuT via CLI (gNMI)
PR Number Synopsis Category: Label Distribution Protocol
1428843 The LDP might withdraw a label for an FEC once the IGP route is inactive in inet.0
  		If LDP is used without using egress-policy, when the route from other routing protocol is preferred over the IGP route in inet.0, e.g. BGP-LU route exported in inet.0, LDP might withdraw the FEC label hence causing LDP traffic to get lost.
1447170 The transit packets might be dropped if an LSP is added or changed on MX/PTX device
  		On MX/PTX series platforms acting as a transit router, if the "set protocol mpls sensor-based-stats" and "ldp-tunneling" are used and when an LSP is added or changed, part of its data structure might not be freed which might cause the resources to be exhausted. Once the resource is exhausted, the kernel routing table (KRT) queue will be built-up and new routes cannot be programmed in the forwarding engine, in the end, the transit packets might be lost.
1459301 All LDP adjacencies flap after changing ldp preference
  		When changing the protocol LDP preference, all LDP adjacencies would be bounced, it results in all LDP targeted sessions flapping.
1460292 High CPU usage and rpd coredump might be observed if "ldp track-igp-metric" is configured and IGP metric is changed
  		If "protocols ldp track-igp-metric" is configured, metric change of IGP route might cause high CPU usage and rpd coredump on the device.
PR Number Synopsis Category: lldp sw on MX platform
1460621 Support of del_path for the LLDP neighbor change at various levels
  		LLDP neighbor delete notificaton is supported event for paths /lldp/interfaces/interface/neighbors/neighbor/custom-tlvs/tlvs and /lldp/interfaces/interface/neighbors/neighbor/capabilities/capability
PR Number Synopsis Category: Multicast for L3VPNs
1441099 The resumed multicast traffic for certain groups might be stopped in overlapping MVPN scenario
  		In NG-MVPN scenario, if the receiver and the source exist in the different VRF instance of the same ingress PE, Type-5 (Source active AD route) and Type-7 (Source tree join route) routes might not be removed correctly after the multicast flow stop, and during this time the RP might prune the multicast tree to an incorrect SPT (shortest-path trees) using these Type-5 and Type7 routes. Then the resumed multicast flow will be dropped due to the wrong SPT.
PR Number Synopsis Category: Interface related ISSU PRs on Mx-series
1379398 Interface with Tri Rate Copper SFP(P/N:740-013111) in "MIC 3D 20x 1GE(LAN)-E,SFP" will stop forwarding traffic after ISSU upgrade
  		Interface with Tri Rate Copper SFP (P/N: 740-013111) in "MIC 3D 20x 1GE(LAN)-E,SFP" will stop forwarding traffic after ISSU upgrade.
PR Number Synopsis Category: MX10K platform
1451011 JNP10K-LC2101 FPC generates "Voltage Tolerance Exceeded" major alarm for EACHIP 2V5 sensors
  		On a JNP10K-LC2101 line card, the MAJOR Alarm with "FPC Voltage Tolerance Exceeded" message may be logged and cleared. This is a software issue. There is no need to replace the FPC.
PR Number Synopsis Category: Track Mt Rainier SPMB platform software issues
1460992 Hardware failure in CB2-PTX causes traffic interruption
  		In PTX 3000/5000 platforms with CB2-PTX (Control Board), there is an existence of an errata on a clock signal component manufactured by a third-party supplier, which might cause the Switch Processor Mezzanine Board (SPMB) and Switch Interface Boards (SIBs) failure, eventually, traffic will be interrupted.
PR Number Synopsis Category: OS IPv4/ARP/ICMPv4
1442815 ARP resolution might fail after ARP HOLD NHs are added and deleted continuously.
  		ARP (Address Resolution Protocol) address resolution might fail after ARP HOLD NHs (next-hop) are getting added and deleted from ARP entries continuously.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1454950 mgd error found during Junos 18.4R2.7 boot up and Junos did not work as expect
  		Packet Forwarding Engine sometimes does not come up after system reboot.Timeout is required to handle the fifo tx/rx error. Debug sysctls are been removed. Mutex been added to handle to race condition.
1469400 Member of virtual chassis might reboot because of lack of watchdog patting
  		In virtual-chassis scenario on EX3400, if watchdog pat did not happen within stipulated time, member (primary or backup or linecard) of virtual chassis might reboot automatically with "0x2:watchdog" as reboots reason.
PR Number Synopsis Category: PFE Peer Infra
1448858 Interface attributes might cause high CPU usage of dcd
  		When the interface attributes are configured, this configuration might cause an error in the IRSD (IRSD syncing errors) and lead the CPU usage of dcd spike up. The convergence time of this interface will be impacted.
PR Number Synopsis Category: Kernel Stats Infrastructure
1462986 Slow response from SNMP might be observed after an upgrade to 19.2R1 and above
  		Slow response introduced with PR/1411303 fix, is getting resolved with this PR.
PR Number Synopsis Category: TCP/UDP transport layer
1449664 FPC might reboot with vmcore due to memory leak
  		On all Junos platforms, if the device is up for a long period (e.g. several weeks or months), there might be a slow memory leak happening in some error scenarios where an application tries to send some data on a stale TCP socket (e.g. short-lived TCP connections used by the mgd process), and this issue might lead to FPC reboot with vmcore files.
PR Number Synopsis Category: Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1448102 Rebooting QFX5120-48Y using "request system reboot" doesn't take physical links offline immediately
  		After rebooting QFX5120-48Y using "request system reboot", the physical link doesn't become offline immediately, which might result in traffic loss.
1456742 The laser from the 10G SFP+ interface is still on when the interface is disabled or the device is rebooted
  		On the QFX5210 platform, the laser is still emitting from 10G SFP+ port even though the interface is disabled or the device is rebooted. It will cause the peer's interface is still up and might impact traffic.
PR Number Synopsis Category: QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1465327 Request for JUNOS to exhibit consistent Fan and Power Supply numbering on Accton WBes (-O and -OZ) in 19.2R1
  		Starting 19.2R2 Junos, PSU Numbering on AS7816-64X platform has changed from 0->1 and 1->0. Fan Numbering has changed from 0,1,2,3->3,2,1,0
PR Number Synopsis Category: RPD policy options
1453439 Routes resolution might be inconsistent if any route resolving over the multipath route
  		On all Junos platforms, any route resolving over the multipath routes, one scenario is BGP over BGP. After the metric value of any PNH (refers to the second PNH and using it to performing the second time next-hop resolving) changes, meanwhile, if the hash-selection changes happened, it might result in routes resolution inconsistency. Traffic drops could be observed if the packages are still forwarding to the old PNH (Protocol Next Hop). Any recursive resolving multipath scenario might trigger this issue.
PR Number Synopsis Category: RPD route tables, resolver, routing instances, static routes
1447595 The rpd crashes and commit fails when trying to commit configuration changes
  		When loading configuration changes related to routing instance through RPC (e.g. OpenConfig), if the mgd reads an invalid routing-instance name (e.g. longer than 256 characters or mistaken name) from the configuration file and transfers it to the rpd, rpd crash happens.
PR Number Synopsis Category: IPSEC functionality on M/MX/T ser
1444462 High CPU utilization might be observed for 'eventd' along with error logs
  		This issue is specific to ipv6 traffic. Huge error logs and high CPU utilization for 'eventd' process might be observed when syslog level is set to 'debug'.
PR Number Synopsis Category: MPC7/8/9 Interface Issues
1463015 An interface might get stuck in down state on certain MX platforms
  		The DFE tuning enabled interfaces on certain MX platform might get stuck in down state, if the remote interface sends invalid code to the local interface. Link might not come up even after the remote peer has begun sending a good signal.
PR Number Synopsis Category: MX10003/MX204 Platform SW - Chassisd s/w defects
1436832 The device may not be reachable after a downgrade from some releases
  		On an MX10003, it is possible that there are multiple processes try to access CB FPGA concurrently. This can lead to the system hung state immediately after bootup. This fix makes "alarmd" process retries if it failed to gain access to the FPGA. This will prevent alarmd to hang the router during boot-up.
PR Number Synopsis Category: MX10003/MX204 MPC defects tracking
1445508 The 1G interface on MX204 might stay down after the device is rebooted
  		On MX204 platform, the interface with the parameter "speed 1g" configured might stay down after the device is rebooted. This is a timing issue.
PR Number Synopsis Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1449427 Cm errors on certain MPC line cards are classified as major, which should be minor or non-fatal.
  		Cm errors on certain MPC line cards are classified as major which should be minor or non-fatal. If these errors are generated, it might get projected as a bad hardware condition and therefore trigger Packet and Forwarding Engine disable action.
PR Number Synopsis Category: Trio pfe qos software
1436872 With CNH enabled, the MPLS COS rewrite does not work for 6PE traffic
  		On MX platforms with Chained Composite Next Hop (CNH) for labeled BGP configured, the MPLS COS rewrite does not work for 6PE traffic. This issue has service/traffic impact.
PR Number Synopsis Category: Trio pfe stateless firewall software
1433034 The FPC might crash when the firewalls filter manager deals with the firewall filters
  		In some corner scenarios (e.g. the IGP neighbor flaps on the IFL configured with the firewall filters), the crash of FPC might be observed if the firewalls filter manager (DFW) deals with the filters of the interface.
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1456578 CLI command with "invoke-on" and "display xml rpc" results in unexpected multiple RPC commands
  		In the previous Junos version, the CLI command combination of "invoke-on" and "display xml rpc" may give incorrect RPC command, because this combination is not supported in Junos. E.g., issuing the command "show version invoke-on all-routing-engines | display xml rpc".

Modification History

First publication date 2020-01-20