Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, and VMX

Alert Description

Junos Software Service Release version 19.3R2-S4 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

Junos Software service Release version 19.3R2-S4 is now available.

19.3R2-S4 - List of Fixed issues
PR Number Synopsis Category: NFX Layer 3 Features Software
1511306 NFX150: ZTP over LTE config commit failed for "operation=create" in xml operations configuration
Product-Group=junos 		NFX150: ZTP over LTE config commit failed for "operation=create" in xml operations configuration
PR Number Synopsis Category: "agentd" software daemon
1487416 The aftd might be crashed
Product-Group=junos 		On Junos platforms, with Telemetry implemented, sensors enabled under analytics hierarchy and Google Protocol Buffer (GPB) used to export profile, aftd might be crashed when Advanced Forwarding Toolkit (AFT) line card (MPC10/MPC11) is installed. This is a day-1 issue. Packetloss will be recovered after aftd self-restart.
PR Number Synopsis Category: Application Quality of Experience related PRs
1513461 CSO 5.1.2 : FLOWD : With CSO SDWAN configuration loaded, FLOWD cores seen while deleting GRE_IPSEC configuration
Product-Group=junos 		The flowd_octeon process restarts unexpectedly when deleting a GRE IPSec tunnel.
PR Number Synopsis Category: MPC5/6E pfe microcode software
1478392 MPCs might stop when there is bulk route update failure in a corner case.
Product-Group=junos 		On all MX Series with MPCs/MICs based line-card, if there are some events like interface flaps, the routes learnt over that interface might get retracted and deleted by the routing protocols. Because of this issue, when bulk route update failure happens, either some next hops are unable to reach or certain next hops are still reachable incorrectly, the line card might crash in a corner case. It is a rare timing issue.
PR Number Synopsis Category: AF interface in Node Virtualization
1473555 After Doing RE switchover on Bsys , the AF interface on Peer router shows status as down(instead of being up) with reason PFE is down on the GNF with MPC11E
Product-Group=junos 		After Doing RE switchover on Bsys , the AF interface on Peer router shows status as down(instead of being up) with reason PFE is down on the GNF with MPC11E
PR Number Synopsis Category: Control Plane for Node Virtualization
1472313 The chassis alarm might appear on BSYS: "RE0 to one or many FPCs is via em1: Backup RE"
Product-Group=junos 		In Junos Node Slicing environment, if a GNF RE mastership is not aligned with BSYS RE mastership (for example, BSYS primary RE is on RE0 but GNF primary RE is on RE1), a major chassis alarm would be reported on BSYS: "RE0 to one or many FPCs is via em1: Backup RE."
PR Number Synopsis Category: MX Inline Jflow
1457282 Ferrari_MPC10_Inline_Jflow: PFE status always remains in "Reconfiguring" state after configuring flex flow size knob second time.
Product-Group=junos 		During multiple config additions and deletion for flex-flow-sizing knob , pfe status may go in "Reconfiguring" state.
PR Number Synopsis Category: Layer 2 Circuit issues
1512834 The rpd might crash when deleting l2circuit configuration in a specific sequence
Product-Group=junos 		If l2circuit local-switching is enabled with connection-protection, the rpd could crash in the following configuration change sequence. 1. First, delete the logical interface (IFL) used by a l2circuit and commit the change. 2. Then, delete the corresponding l2circuit configuration. The rpd could crash after committing the change.
PR Number Synopsis Category: MPC11 ULC fabric software related issues.
1483124 Link errors may be seen after restarting the FPC or fabric plane
Product-Group=junos 		On MPC10/MPC11, if the main PFE is disabled due to the major errors, link errors are observed after the FPC or fabric plane is restarted.
PR Number Synopsis Category: MPC11 ULC interface software related issues.
1464652 The failover time for LACP link protection might be more than 2 seconds on MPC11E
Product-Group=junos 		On MX2000 platforms with MPC11E, if Link Aggregation Control Protocol (LACP) link protection is configured, when the Physical Interface Card (PIC) gets offline on which the active link is located, the failover time might be more than 2 seconds. Due to this issue, more traffic loss might happen than expected.
PR Number Synopsis Category: MPC11 ULC platform software related issues.
1478243 The ukern-platformd process might crash on MX2000 platforms with MPC11
Product-Group=junos 		On MX2000 platforms with MPC11, the ukern-platformd process might crash during interrupt handling. Due to this issue, the impacted MPC11 might reboot and traffic loss might happen.
PR Number Synopsis Category: QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1317750 Port LEDs do not work on QFX5100 in QFX5110-QFX5100 mixed mode virtual chassis
Product-Group=junosvae 		Port LEDs on the QFX5100 do not work. If a device connects to a port on the QFX5100, the port LED stays unlit.
PR Number Synopsis Category: RPD Interfaces related issues
1503075 Fabric interface might be Monitored down after chassis cluster reboot
Product-Group=junos 		On all SRX series devices with chassis cluster enabled, Fabric link might be Monitored down after rebooting both nodes simultaneously. This will cause CS(Cold Sync monitoring) and FL(Fabric Connection monitoring) failure.
PR Number Synopsis Category: SW PRs for SCBE3 fabric
1491968 FPCs might stay down or restart when swapping MPC7/8/9 with MPC10/11 or vice versa in the same slot
Product-Group=junos 		In MX240/MX480/MX960 routers with SCB3E or MX2010/2020 with SFB3 scenario, if MPC7E/8E/9E is swapped with MPC10E/11E each other or vice versa in the same slot, the different encoding mode between two MPCs might cause SCB3E/SFB3 to not change the mode gracefully according to the new MPC type inserted. This causes fabric destination errors which can trigger fabric healing mechanisms and cause system-wide impact due to fabric planes and FPCs getting reset. [TSB17748 [juniper.net]]
PR Number Synopsis Category: platform related PRs on SRX branch platforms
1518709 The PPPoE session does not go up after zeroize on SRX device
Product-Group=junos 		On SRX300/SRX320/SRX340/SRX345/SRX380 Series devices, the PPPoE session does not go up after doning zeroize and then reconfiguring the PPPoE client.
PR Number Synopsis Category: MPC7/8/9 Interface Issues
1441816 Egress stream flush failure and traffic blackhole might occur
Product-Group=junos 		Egress stream flush failure and silent dropping of traffic could occur in a rare occasion for a repeatedly flapping link on MPC7E, MPC8E, MPC9E cards, MX204 and MX10003.
PR Number Synopsis Category: Trio pfe qos software
1465870 The CoS might not work on MPC10E/MPC11E line cards
Product-Group=junos 		On MX platforms with MPC10E/MPC11E line cards used, classifier installation might fail during MPC restart or if interface and CoS classifiers are committed in single commit or deactivate/activate of interface and CoS configs. As a result, traffic might not be forwarded in the scheduled queue. This is a timing issue.
PR Number Synopsis Category: Trio pfe l3 forwarding issues
1484751 The logical tunnel interface might not work on MPC10 linecard
Product-Group=junos 		On MX960/MX480/MX240 platforms with MPC10 linecard, the logical tunnel (LT) interface might not work due to the software defect in Address Resolution Protocol (ARP) over it. Ping operation or the routing protocol sessions over LT interface might not be able to work due to this issue.
PR Number Synopsis Category: Trio pfe mpls- lsps,rsvp,vpns- ccc, tcc software
1452866 The traffic blackhole might happen after the LACP timeout
Product-Group=junos 		In Link Aggregation Control Protocol (LACP) with Unilist next-hop scenario, when Resource Reservation Protocol (RSVP) protection or BGP Prefix-Independent Convergence (PIC)is used, if the LACP interface flapping happens fast enough, which might cause traffic blackhole. Due to a delay which causes the first "link down message" arriving at Packet Forwarding Engine (PFE) after the "link up message" already being received. So that PFE marks both of the primary and backup next-hop as unusable. (This is a timing issue)
PR Number Synopsis Category: DDos Support on MX
1459605 ddos-protection doesn't stop logging when remote tracing enabled
Product-Group=junos 		With ddos-protection enabled, ddos violation set/clear message will be logged into /var/log/messages by default. However, sometimes the local logging will still be observed even with remote tracing enabled. That caused by the ddos-protection daemon only reads its logging setting at daemon start. With the fix, the daemon reads the logging setting in every commit.
PR Number Synopsis Category: ZT pfe CDA issues
1502877 MPC11 "show syslog" command in PFE shell might time out
Product-Group=junos 		If log size on MPC11 line card is large enough, "show syslog" command in PFE shell may time out. root@router-fpc11:pfe> show syslog error: timeout communicating with Aft System Info daemon daemon
PR Number Synopsis Category: ZT pfe infra issues
1478540 Interface traffic statistics in CLI command "show interface" may display incorrect values for a LAG with MPC10/MPC11 child links
Product-Group=junos 		On a MX series router with MPC10/11 and other MPC cards in a LAG bundle "show interface" CLI command might display incorrect traffic statistics. This might be triggered when an MPC10/11 child link is removed from a LAG with child links hosted on other MPC models. For example: <--- removing MPC11 based link from ae10 user@router-re0# show | compare [edit interfaces et-1/0/0] ! inactive: gigether-options { ... } <--- only 50kpps is going through ae10 user@router-re0> show interfaces ae10 | match rate Input rate : 4528 bps (3 pps) Output rate : 149134770 bps (67057 pps) <<<< output displays higher packet rate
PR Number Synopsis Category: ZT pfe firewall software
1478358 Traffic drop might be seen if interface-specific filter is configured
Product-Group=junos 		On MX platforms with MPC10/MPC11 equipped, traffic drop might be seen if interface-specific filter is applied in scaled configuration. This issue might occur when loading interface-specific filter or rebooting the router with interface-specific filter configured.
1493084 MPC10/11 linecard might crash if the interface is configured with firewall filter referencing shared-bandwidth policer
Product-Group=junos 		On MX platforms with MPC10/11, if the shared-bandwidth policer is referenced by an interface specific firewall filter, and the filter is bound to the interface of the affected linecard, during the linecard reboot, there is a chance that firewall filter information updates come out of order when being sent from Routing Engine (RE) to Packet Forwarding Engine (PFE). Due to handling the out of order update messages, the linecard might crash and get into continuous reboot state.
PR Number Synopsis Category: ZT pfe multicast software
1475187 On an affected FPC type, error message ?user.err aftd-trio: [Error] IF:Primary Dest Address, NO ENTRY found! ? can appear after upgrading to affected release OR after performing RE switchover.
Product-Group=junos 		On an affected FPC type, error message ?user.err aftd-trio: [Error] IF:Primary Dest Address, NO ENTRY found! ? can appear after upgrading to affected release OR after performing RE switchover. Error messages are not functionality impacting and can be ignored. The problem is applicable to MPC10 and MPC11E.
1499631 The heap memory leak might be seen on MPC10/MPC11 linecards
Product-Group=junos 		On MPC10/MPC11 linecards, under heavy route churn, the aftd-trio process might slowly leak memory.
PR Number Synopsis Category: ZT pfe, vpls, mesh group software
1463040 ZT VPLS: vt remote macs are not learnt with correct age if vt is from non-ZT card
Product-Group=junos 		RCA : IF-design changed for non-local interfaces: earlier IflTriowill be created for both local and remote interfaces. Now IflRemoteTriowill be used for remote interfaces. Because of this IffBridgeTrio::setup fails for remote interfaces as the earlier code expcets IflTrio class.Hence, IFBD creation fails later, as IFF-Bridge is not initialized. Will be fixed in 19.4 release.
 

19.3R2-S4 - List of Known issues
PR Number Synopsis Category: MX Platform SW - Power Management
1488575 Add support for PSM firmware upgrade on MX2K
Product-Group=junos 		Supporting PSM firmware upgrades on MX2K platforms
PR Number Synopsis Category: JSR Infrastructure
1505864 The installation fails when upgrading from legacy Junos to specific BSDx based Junos
Product-Group=junos 		The installation fails when upgrading from legacy(non-BSDx) Junos to specific BSDx based Junos releases.
PR Number Synopsis Category: Layer 2 Control Module
1473610 ERPS might not come up properly when MSTP and ERPS are enabled on the same interface.
Product-Group=junos 		When both "Multiple Spanning Tree Protocol " (MSTP) and Ethernet Ring Protection Switching" ERPS are enabled on the same interface, then ERPS does not come up properly.
PR Number Synopsis Category: sflow on MX PRs for defect & enhancement requests
1487876 Incorrect 'frame length' of 132 bytes might be captured in packet header
Product-Group=junos 		On all MX/PTX5k/EX platforms with Trio based line cards, if a packet is send with more than 128 bytes it will always show incorrect "Frame length" of 132 bytes in raw packet header of sflow collector captured data.
PR Number Synopsis Category: Bugs related to ethernet interface on MX platform
1436327 Control logical interface is not created by default for LLDP.
Product-Group=junos 		Default config doesn't create any IFLs and LLDP cannot discover neighbor for those interfaces which ifl is not configured explicitly in Junos configuration.
1522132 during ISSU, observed ksyncd core @ Replication error EINVAL has been encountered while processing an incoming (RTM_IFLOGICAL) message, in the context of RTM_ADD operation. Name of the ifl is xe-2/0/1.
Product-Group=junos 		This issue is introduced by PR1436327, as part of default IFL creation for index 16386. when FROM build is having PR 1436327 fix and TO build is not having PR 1436327 fix, then ISSU will fail.
PR Number Synopsis Category: QFX L2 PFE
1500825 The ERPS might not work correctly on QFX5k
Product-Group=junos 		On QFX5k platforms, Ethernet ring protection switching (ERPS) might not work correctly due to ERPS instance programming failure in hardware which might cause loop in the network.
PR Number Synopsis Category: RPD Next-hop issues including indirect, CNH, and MCNH
1429949 dynamic tunnel summary is displaying wrong count of up and total tunnels
Product-Group=junos 		Dynamic tunnel summary displays an incorrect count of up and total tunnels after multiple iterations of activating and deactivating the dynamic tunnel configuration. It is just a display issue, and there is no problem with the functionality.
PR Number Synopsis Category: platform related PRs on SRX branch platforms
1488348 All interfaces remain in the down status after the SRX300 line of devices power up or reboot.
Product-Group=junos 		The SRX3xx device may encounter a condition where revenue ports remain in the down status after the device reboot/power-up.
1488348 All interfaces remain in the down status after the SRX300 line of devices power up or reboot.
Product-Group=junosvae 		The SRX3xx device may encounter a condition where revenue ports remain in the down status after the device reboot/power-up.
PR Number Synopsis Category: MPC7/8/9 Interface Issues
1473280 "Failed to complete DFE tuning" syslog messages may appear on MX
Product-Group=junos 		Even with the fix for PR 1463015, the "Failed to complete DFE tuning" syslog may appear. This message has no functional impact and can be ignored.
PR Number Synopsis Category: ZT pfe firewall software
1458499 Traffic blackhole or MPC crash might be seen on MPC10E during firewall filter terms changing on it
Product-Group=junos 		The firewall filter might be incorrectly updated in the MPC10E Packet Forwarding Engine when a change (for example, add, delete, deactivate, or activate) of firewall filter terms occurs in some scenarios, such as large-scale term changes or changes happening during MPC reboot. The incorrect firewall filter might cause the traffic to be silently dropped or discarded and even lead to an MPC crash. It is a timing issue.
PR Number Synopsis Category: ZT pfe l3 forwarding issues
1474146 JDI-RCT:-MPC10E:- ISIS and micro bfd sessions are not coming up during baseline.
Product-Group=junos 		For the MPC10E card line, the IS-IS and micro-BFD sessions do not come up during baseline.
1486315 The MPC10E/MPC11E might crash with aftd-trio core-dump when there are a lot of configuration churns with AE interfaces
Product-Group=junos 		From 19.3R2 19.4R1, when there are a lot of configuration churns with AE interfaces on MPC10E/MPC11E, the MPC might crash due to a null pointer issue. This is a rare issue.

Modification History

First publication 2020-08-06
2022-03-23: Non-technical changes; corrected formatting issue