Alert Type

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

Product Affected

ACX, EX, MX, PTX, QFX, NFX, SRX, VMX, VRR, JET, JNS and VSRX platforms

Alert Description

Junos Software Service Release version 19.3R2-S2 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-S2 is now available.


19.3R2-S2 - List of Fixed issues

PR NumberSynopsisCategory: NFX Dual CPE software category
1490077Coredumps on NFX250 while adding the second lan subnet
Product-Group=junos		Coredumps on NFX250 while adding the second lan subnet. fixed
PR NumberSynopsisCategory: DHCP related Issues
1467182[dhcp] [DHCP_RELAY]- JDI-_DHCP_-REGRESSION-SWITCHING:: DHCPvX ACK Messages did not receive response to Broadcast INFORM packets with 19.1R2.3
Product-Group=junos		Few of DHCPvX INFORM Messages, specific to particular VLAN are not receiving any ACK from server.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1475819Traffic might not be forwarded over ECMP link in EVPN VXLAN scenario
Product-Group=junosvae		On QFX5110/QFX5120 platforms, when Traffic Load Balance is used in EVPN VXLAN scenario, traffic might not be forwarded over ECMP link after the ECMP link flapped.
PR NumberSynopsisCategory: ChassisD changes specific for ACX series
1448884Fans on an ACX5448-M may not be running at the correct speed
Product-Group=junos		Correct the fan speeds under different conditions on an ACX5448-M platform.
PR NumberSynopsisCategory: common or misc area for SRX product
1467376Physically disconnecting the cable from fxp0 interface causes Hardware(HW) monitor failure and redundancy group failover on SRX1500 and SRX4K primary node in a chassis cluster.
Product-Group=junos		On SRX1500 and the SRX4000 line of devices, physically disconnecting the cable from fxp0 interface causes hardware monitor failure and redundancy group failover, when the device is the primary node in a chassis cluster.
PR NumberSynopsisCategory: Junos Fusion Infrastructure
1454335SDPD core found @ vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry
Product-Group=junos		SDPD core found @ vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry
PR NumberSynopsisCategory: Border Gateway Protocol
1487691High CPU utilization might be observed when the outgoing BGP updates are sending slowly
Product-Group=junos		On all Junos platforms with the BGP routing protocols, the rpd process might go into a high CPU utilization causing slow network convergence. If a BGP peer is receiving and processing BGP updates slowly, this may cause the BGP output queue of the sending BGP peer to be full. When the queue is full it causes high CPU utilization of the BGP IO thread (bgpio, it is part of the rpd daemon) on the sending BGP peer. This defect could cause network-wide slow BGP network convergence. (See also https://kb.juniper.net/TSB17725 [juniper.net])
PR NumberSynopsisCategory: OpenSSH and related subsystems
1454177SSH login might fail if a user account exists in both local database and RADIUS or TACACS+.
Product-Group=junos		SSH login from an automation tool to the Junos device might not be successful if the username is configured both as a local user and on remote RADIUS/TACACS server, and using authentication method 'password'.
PR NumberSynopsisCategory: Device Configuration Daemon
1438172Decoupling of L2IFL from bridge / EVPN configuration
Product-Group=junos		L2IFL configuration is now decoupled from bridge / EVPN configuration. A L2IFL can now be configured without being assigned to a bridge / EVPN.
PR NumberSynopsisCategory: DNX platform MPLS FRR features
1485444ACX5448 L2VPN with interface ethernet-ccc input-vlan-map/output-vlan-map can cause traffic blackhole
Product-Group=junos		On the ACX5448 platform, l2vpn application with ethernet-ccc input-vlan-map/output-vlan-map can experience traffic blackhole while the control plane is still up. This issue is a software defect introduced by changes made via PR1456624 in the ethernet-ccc ingress interface. This software defect adds an internal vlan tag to all packets. As a result, customers' desired vlan-tag was not added in ccc->mpls direction. Causing the remote PE -- expecting vlan-tagged traffic -- to drop these packets due to vlan mismatch.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1479684Recent changes to JDPI's classification mechanism caused a considerable performance regression (more than 30 percent).
Product-Group=junos		Recent changes to JDPI's classification mechanism caused a considerable performance regression (30%+).
PR NumberSynopsisCategory: EVPN control plane issues
1467309The rpd might crash after changing EVPN related configuration
Product-Group=junos		In EVPN scenario without encapsulation type specified (the default EVPN encapsulation type is set to MPLS), if "vlan-id none" and "vni " is configured in EVPN instance, the rpd might crash after changing EVPN related configuration (such as set the encapsulation as vxlan or delete label-allocation scheme).
1482774Deleting a L2IFL generates an error if not deleted first from EVPN
Product-Group=junos		The fix for this PR allows a L2IFL to be deleted without having first to delete it from the EVPN.
PR NumberSynopsisCategory: Express PFE FW Features
1432116The FPC might crash when a firewall filter is modified
Product-Group=junos		In QFX10K/PTX series platforms, if a firewall filter with multiple match conditions is configured on interfaces which are Up and the firewall filter is modified (either a new action is added or the condition is added/removed etc.), the FPC might crash and restart. It might affect the service/traffic.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1471465The traffic loss might occur when VTEP source interface is configured in multiple routing instances
Product-Group=junos		In VXLAN scenario on QFX10000 series platforms, when VTEP source interface is configured in multiple routing instances, the traffic loss might occur if one of such routing instances is deleted.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1473313The detached interface in LAG might process the xSTP BPDUs
Product-Group=junos		If the xSTP protocol is running between a detached lag member and the physically connected peer interface (which is not part of a LAG), the xSTP BPDUs might get exchanged instead of getting dropped. Because of this behavior, the xSTP protocol might make the lag interface flap.
1474876The input-vlan-map/output-vlan-map might not work properly in L2circuit local-switching scenario
Product-Group=junos		On PTX1K/PTX10K platforms, in L2circuit local-switching scenario, when vlan-ccc encapsulation is configured with input-vlan-map/output-vlan-map, all traffic passing through might have unexpected vlan manipulation (vlan tag push/pop/swap).
PR NumberSynopsisCategory: track re issu control procedure bugs
1480561ISSU might fail on MX204/MX10003 Virtual-chassis(VC) with an error message
Product-Group=junos		An ISSU performed on MX204/MX10003 VC with MPC7/8/9 cards might fail while upgrading to the below specific releases due to a regression issue: -18.4R3 -19.1R3 -19.3R2, 19.3R2-S1 -19.4R1
PR NumberSynopsisCategory: Layer 2 Control Module
1473610ERP might not come up properly when MSTP and ERP are enabled on the same interface
Product-Group=junos		When both MSTP and ERP are enabled on the same interface, then ERP will not come up properly.
1478157"show evpn statistics instance" command gets stuck on multihomed scenario.
Product-Group=junos		"show evpn statistics instance" command gets stuck on multihomed scenario. The command shall give proper output but will not terminate and only time out. Ctrl+C can be used to exit the command immediately.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1484468Packet loss might be observed after device rebooted or l2ald restarted in EVPN-MPLS scenario
Product-Group=junos		In EVPN-MPLS scenario, if the core-facing interface (mpls interface) and the CE-facing interface are on different PEs, and the traffic from core is not continuous and DMAC (Dynamic MAC) ages out, due to an incorrect flood next-hop programming across different PFEs, packet loss might be observed after device rebooted or l2ald restarted.
PR NumberSynopsisCategory: lacp protocol
1463791Member links state might be asychronized on a connection between PE and CE in EVPN A/A scenario
Product-Group=junos		In EVPN multihomed active-active (A/A) scenario, Link Aggregation Control Protocol (LACP) enabled on a connection between PE and CE and "sync-reset" configured in CE side, state of member links in PE side might get stuck at "Detached" and same member links in CE side is in "Collecting Distributing" state when EVPN recovered from Core Isolation. This issue rarely happens and causes traffic drop.
PR NumberSynopsisCategory: Label Distribution Protocol
1474204LDP/BFD sessions are not coming up in scaled setup
Product-Group=junos		On MPC10/MPC11 line card, the LDP/BFD sessions are dropped when the fast-lookup-filter has a default term with only accept as action and it is attached to the lo0 interface.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1457681The rpd crash may be observed with traceoption enabled in MPLS
Product-Group=junos		On all Junos platforms, If the traceoption is enabled in MPLS and SNMP polling is going on, and during route lookup match a given route which one is neither router next-hop nor chain next-hop, then rpd crash may be observed. The rpd crash may cause all the routing protocols adjacencies to be reestablished.
PR NumberSynopsisCategory: Multicast Routing
1468737The mcsnoopd crash might be seen if one BD/VLAN is configured as part of EVPN and it has any multicast router interfaces (static/dynamic)
Product-Group=junos		In all Junos platforms where EVPN SMET is supported, the mcsnoopd process might crash if a snooping enabled BD/VLAN which has mrouter port(s) is configured as part of EVPN as extended VLAN/VNI.
PR NumberSynopsisCategory: MX10K platform
1451011JNP10K-LC2101 FPC generates "Voltage Tolerance Exceeded" major alarm for EACHIP 2V5 sensors
Product-Group=junosvae		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 NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1439906FPC might reboot if jlock hog occurs on all Junos VM based platforms
Product-Group=junos		On a JUNOS VM using TSC clocking from the host system, "jlock hog" messages may be seen. This may lead to FPCs reboot.
PR NumberSynopsisCategory: Kernel socket data replication issues for protocols that use
1472519The kernel may crash and vmcore may be observed after configuration change is committed
Product-Group=junos		On all Junos platforms, after committing the configuration change (e.g. removal of protocols like mpls, isis, ldp from the interfaces), then the kernel may crash and vmcore may be observed. This issue also may cause protocol adjacency failure.
PR NumberSynopsisCategory: Kernel Stats Infrastructure
1462986Slow response from SNMP might be observed after an upgrade to 19.2R1 and above
Product-Group=junos		Slow response introduced with PR/1411303 fix, is getting resolved with this PR.
PR NumberSynopsisCategory: QFX platform fabric mgmt for Express ASIC chip
1464650The interface might not come up on FPC restart on QFX10000 platforms
Product-Group=junos		On QFX10000 platforms, on FPC restart process, few of the interfaces does not come up and keeps flapping.
PR NumberSynopsisCategory: QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1466532EBUF parity interrupt is not seen on QFX10K/PTX platforms
Product-Group=junos		On QFX10K/PTX platforms, when EBUF parity error occurs on FPC, EBUF parity interrupt might not be observed and only iCRC error gets printed in log message.
1466810EPR iCRC errors in QFX10000 series platforms might cause protocols down
Product-Group=junos		EPR iCRC errors in QFX10000 series platforms might cause protocols down. FPC will be in wedged state and will not pass traffic on that PFE if hitting this issue. EPR iCRC errors are normal and caused by transient hardware conditions. EPR iCRC errors are not expected to impact the protocols, and only one CRC failed packet will be dropped. But due to incorrect handling of this error, it affects protocols and causes FPC wedge.
PR NumberSynopsisCategory: QFX platform optics related issues
1457266QFX5110 QSFP-100GBASE-SR4 made by Avago cannot linkup
Product-Group=junos		On QFX5110, interface on QSFP-100GBASE-SR4 whose Xcvr vendor is Avago on the QFX side cannot linkup, FEC errors might be seen on the other side.
PR NumberSynopsisCategory: Filters
1480776ARP request packets for unknown host might get dropped in remote PE in EVPN-VXLAN scenario
Product-Group=junos		In EVPN-VXLAN environment, when local CE sends ARP request packets for unknown host, the packets will hit firewall-host queue in remote PE. It might trigger DDoS protection policer violations for firewall-host queue hence the ARP request packets might get dropped.
PR NumberSynopsisCategory: QFX L2 PFE
1475430There might be traffic drop on QFX5110/5120 switches acting as leaf switch in a multicast environment with VxLAN
Product-Group=junos		In a multicast environment where IGMP-snooping is enabled with VxLAN and QFX5110/5120 switches act as leaf switch, there might be traffic drop as the switch might fail to forward the traffic to Assisted Replicator (AR-replicator)/Spines when BGP is flapped on Spine switch. This is a rare issue noticed when the route installation messages are received out-of-order on leaf switch.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1485800krt-nexthop-ack-timeout may not automatically be picked up on rpd start / restart
Product-Group=junos		In some circumstances, primarily when rpd is being restarted. The value for krt-next-hop-ack-timeout may not automatically be picked up. This can be checked by checking the output of "show krt acknowledgement" and examining the value of "Kernel Next Hop Ack Timeout".
PR NumberSynopsisCategory: Resource Reservation Protocol
1434522Traffic loss might happen if p2mp with NSR enabled
Product-Group=junos		In p2mp with NSR scenario, when the switchover happens, the traffic might be lost due to the correct forwarding states is not synchronized to old Backup RE.
1469567Fast reroute detour next-hop down event might cause primary LSP down in particular scenario
Product-Group=junos		In detour protection scenario (Fast-reroute enabled in LSP) in which the incoming detour LSPs that arrives on the primary next-hop merge with the locally originated detour LSP, sometimes after detour LSP next-hop down event the node incorrectly chooses the primary nhop (next hop) as the detour nhop, as a result it could cause brief traffic loss (a few seconds).
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1478279FPC memory leak might happen after executing "show pfe route"
Product-Group=junos		On all Junos platforms, if the command "show pfe route " is executed to dump the Packet Forwarding Engine (PFE) routes, and then the routes get deleted by some events, for example, Virtual Routing and Forwarding (VRF) configuration removal or Border Gateway Protocol (BGP) flap, the FPC memory leak might happen due to this issue. In large scaled scenario, the memory leak will increase by large amount which might be more easier to cause FPC crash.
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1468119Daemons might not be started if "commit" is executed after "commit check"
Product-Group=junos		On Junos from 16.2R1 onwards, if "commit" is executed after "commit check", the daemon (e.g. dhcpd, sampled) might not be started even the related configuration is successfully committed.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1438144(SEEN ONLY ON LEGACY IMAGE) ISSU is failing from 19.1R1 legacy Junos release images
Product-Group=junos		ISSU from 19.1R1 Legacy Junos images impact the commits on the device
PR NumberSynopsisCategory: usf nat related issues
1491036When NAT/SFW rule configured with application-set with multiple applications having different TCP inactivity-timeout, Sessions are not getting TCP inactivity-timeout as per the configured application order.
Product-Group=junos		When NAT/SFW rule configured with application-set with multiple applications having different TCP inactivity-timeout, Sessions are not getting TCP inactivity-timeout as per the configured application order.
 

Modification History

  • First publication date 2020-04-09

  • 01/04/2022: Non-technical changes; formatting modified