Alert Type

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

Product Affected

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

Alert Description

Junos Software Service Release version 19.1R3-S1 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

Solution

Junos Software service Release version 19.1R3-S1 is now available.

19.1R3-S1 - List of Fixed issues
PR Number Synopsis Category: EX4300 PFE
1491348 The traffic destined to VRRP VIP might be dropped after the IRB interface is disabled on the initial VRRP primary
Product-Group=junos 		On the EX4300 virtual-chassis scenario, the traffic destined to the VRRP Virtual IP Address (VIP) might be dropped on the Virtual-Chassis if the VRRP IRB interface is disabled on the initial VRRP primary. For details, please refer to the following topology and problem description.
PR Number Synopsis Category: EX2300/3400 PFE
1490689 DHCP binding is failed while verifying DHCPv4 Snooping fucntionality with Pvlan with firewall to block/allow certain IPv4 packets is failed
Product-Group=junos 		TBD
PR Number Synopsis Category: EX2300/3400 platform
1467707 FPCs might get disconnected from EX3400 VC briefly after reboot/upgrade
Product-Group=junos 		On EX3400 Virtual Chassis, during reboot or upgrade, because of a high CPU load in slow path of fxpc, TCP keep alive message is not sent. Hence, it is observed that sometimes a few Virtual Chassis members might get disconnected from the Virtual Chassis briefly and join back in 3-6 minutes.
PR Number Synopsis Category: Customer escalation on hardware from ATAC, CFTS
1426910 Drift messages in ACX2200 which is a PTP hybrid (PTP+syncE) device
Product-Group=junos 		On ACX2200 configured with PTP+SyncE , backup devices might get impacted due to high PDVs. This is observed through drift messages in the router.
PR Number Synopsis Category: NFX LTE Software
1493711 LTE - Package related files are getting missed after image upgrade from D497.1 to 18.4R3.3 porter-2 image
Product-Group=junosvae 		In 18.4R3.3, LTE module is not contained on platform NFX250-ATT-LS1.
PR Number Synopsis Category: QFX Multichassis Link Aggregrate
1488681 MClag consistency check for multiple irb's configured with same vrrp-group
Product-Group=junos 		The MClag consistency check fails if the same vrrp-group is used for multiple irb configurations on Local and Remote REs of the MCLAG topology. This change corrects the defect and makes the MClag consistency check to pass.
PR Number Synopsis Category: QFX PFE L2
1481031 Connectivity is broken through LAG due to members configured with hold-time and force-up
Product-Group=junos 		Connectivity through link aggregation group bundle could break after there is a flap event on the physical ports when one physical member interface is configured with hold-time and the other member interface is having LACP force-up feature configured.
1499422 The FPC will go down when 100G link comes up on the network port of the QFX5110-48S device
Product-Group=junos 		On the QFX5110-48S device running on Junos 19.3R2-S2, 18.2R3-S3 or 18.2R3-S4, the FPC will go down when the 100G link comes up on the network port. This leads to FPC up and down every 90 seconds. During the prolem state running CLI "show chassis fpc detail" will not yield any output for upto 90sec. user@device> show chassis fpc detail. <-------- Empty Once FPC state transition back to online state, the 100G transceivers gets detected and fpc flap is seen again. This behavior is seen continuously as long as 100G transceivers remain connected to the QFX device in question. If 100G interfaces gets disabled from CLI or physically removed from the QFX switch, the FPC flap will no longer be seen. Note: This issue is not applicable when 100G-QSFP is used as a VCP port on QFX5110-48S.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1484523 LACP :: - JDI-_LACP:_-REGRESSION: MUX State in LACP interface does not go to "collecting and distributing" & remains 'attached' after enabling the ae interface
Product-Group=junos 		In 19.1R3 release MUX state of LACP interface will not change sometimes when "force-up" configured.
1485612 QFX 5100 VC/VCF : fpc are going to NotPrsnt state after upgrading the QFX 5100 VC/VCF
Product-Group=junos 		On QFX5100-24Q, there are three PICs: PIC0, PIC1, and PIC2. Ports on PIC0 uses the integrated PHY capability (called PHYLESS) on the Broadcom ASIC. PIC1 and PIC2 have an external PHY capability (called PHY). If PIC1 or PIC2 ports (PHY ports) interfaces used for VCP creation then after upgrade FPC may go to NotPrsnt state due to link not coming up.
1487707 All interfaces stop transmitting traffic on multi-link simultaneously
Product-Group=junos 		On QFX5000 platforms (QFX5100/QFX5110/QFX5120/QFX5200/QFX5210) with point-to-point multi-link scenario, when the switch ingress buffer saturation happens, all interfaces on multi-link stop sending traffic at the same time.
PR Number Synopsis Category: MPC Fusion SW
1491337 The ISSU is not supported on NG-MPC cards wherefrom the release is 19.4R1
Product-Group=junos 		On the MX platforms with MPC2E-NG/MPC3E-NG installed, when performing ISSU (in-service software upgrade) to 19.4R1 release or later, it may cause NG-MPC cards to crash.
PR Number Synopsis Category: Junos Fusion Infrastructure
1454335 SDPD 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 Number Synopsis Category: BBE interface related issues
1498024 Subscribers may be disconnected after one of the AE participating FPCs comes online in a Junos node slicing scenario
Product-Group=junos 		On the MX platforms with node slicing setup, if subscriber services and targeted distribution feature are enabled on an AE interface, if the FPC where one of the AE member ports is located comes online, subscribers that are already online may be disconnected.
PR Number Synopsis Category: BBE Statistics daemon & libraries
1494637 In node slicing setup after GRES has been done, radius interim updates may not carry actual statistics.
Product-Group=junos 		In node slicing setup with MPC5 or newer cards after GRES, radius interim updates may not carry actual statistics.
PR Number Synopsis Category: BBE Remote Access Server
1479486 Verify deleting services via CoA when the specified family-type has been deactivated failed since incorrect number of service sessions are active
Product-Group=junos 		While Verifying deleting services via CoA, when the specified family-type has been deactivated (failed) since incorrect number of service sessions are active. Hence Customer will notice some services are still active even though the family is deleted.
PR Number Synopsis Category: Chotu platform software
1450424 RE-MX2008-X8-128G Secure BIOS Version Mismatch alarms
Product-Group=junos 		After reboot of the MX2008, can see below alarms:- 2019-07-22 05:07:57 UTC Minor VMHost RE 1 Secure BIOS Version Mismatch 2019-07-22 05:07:53 UTC Minor VMHost RE 0 Secure BIOS Version Mismatch 2019-07-22 05:07:53 UTC Minor Mixed primary and Backup RE types labroot@BRAIN-RE0> show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis JN1261F13AFL MX2008 Routing Engine 0 BUILTIN BUILTIN RE-MX2008-X8-128G <<<< 128G Routing Engine 1 BUILTIN BUILTIN RE-MX2008-X8-128G <<<< 128G In certain platforms due to an issue in mfg packaging lastknown bios images are not present in efi_P/efi_S partition.
PR Number Synopsis Category: DNX platform MPLS FRR features
1485444 ACX5448 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 Number Synopsis Category: EVPN control plane issues
1490953 The rpd core might be seen when doing RE switchover after disabling BGP protocol globally
Product-Group=junos 		On EVPN scenario with BGP and routing-instance configured, if BGP protocol is disabled globally and then doing RE switchover, multiple rpd core might be seen. And the rpd does not run on new primary RE. Hence it would affect the traffic and service.
PR Number Synopsis Category: EVPN Layer-2 Forwarding
1484296 Dead next-hops might flood in a rare scenario after remote PEs are bounced
Product-Group=junos 		On all Junos platforms with EVPN-MPLS scenario, due to a timing condition, dead next-hops might flood after remote PEs are bounced. This will affect BUM traffic flooding to remote EVPN PEs.
1495098 VXLAN bridge domain may lose VTEP logical interface after restarting chassisd
Product-Group=junos 		In all Junos platforms with EVPN-VXLAN scenario, VTEP interface might not be installed under the VXLAN bridge domain(BD) after restart process chassisd, which might cause traffic loss. For the reason is that the VTEP physical interface(VTEP IFD) needs to be deleted when the chassisd is restarted, then add back after the restart is completed, and then re-associate VTEP logical interface (VTEP IFL) with corresponding BD. However, the VTEP IFD takes a long time to be added back after restarting. During the absence of IFD, the VTEP IFL will not be recognized by process l2ald. Therefore, it will not be associated with the corresponding VXLAN BD. In this way, even if the VTEP IFD up later does not help, because the whole initialization process has been finished.
PR Number Synopsis Category: Issues related to EX MACsec
1469663 Traffic loss might be seen with framing errors or runts if MACsec is configured on EX4600/QFX5100 platforms
Product-Group=junos 		On EX4600/QFX5100 platforms with Media Access Control Security (MACsec) configured, if there is traffic flowing through the MACsec enabled link, increasing framing errors or runts statistics might be seen in the output of "show interfaces extensive <>" for the affected interface. Traffic loss might also happen due to this issue.
1476719 On EX4300, the output of "show security macsec statisitics" shows high values incorrectly.
Product-Group=junosvae 		On EX4300, the output of "show security macsec statisitics" shows high values incorrectly.
PR Number Synopsis Category: track re issu control procedure bugs
1480561 ISSU 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 Number Synopsis Category: Firewall Network Address Translation
1479824 Issuing the show security nat source paired-address command might return an error.
Product-Group=junos 		On the SRX series platforms with source NAT configuration, issuing the command "show security nat source paired-address ..." may return an error, which is not expected. It's a corner case, and not reproduced all the time.
PR Number Synopsis Category: Firewall Policy
1492436 TCP-Proxy was mistakenly engaged in Unified-Policies when Web-Filtering was configured in a potential match policies.
Product-Group=junos 		TCP-Proxy was mistakenly engaged in Unified-Policies when Web-Filtering was configured in any of the potential policy candidates. For customers who are only utilizing dynamic-applications and EWF in their policy, large performance improvements are seen with this fix.
PR Number Synopsis Category: Security platform jweb support
1499280 Junos OS: Security vulnerability in J-Web and web based (HTTP/HTTPS) services
Product-Group=junos 		Junos OS: Security vulnerability in J-Web and web based (HTTP/HTTPS) services (CVE-2020-1631). Refer to https://kb.juniper.net/JSA11021 [juniper.net] for more information.
PR Number Synopsis Category: Issues related to Jflow Jvision Sensors
1477445 Sampling Process may crash when MPLS/MPLS over UDP traffic is sampled
Product-Group=junos 		When inline-jflow is configured for sampling MPLS traffic, multi-svsc process running on the FPC may crash due to MPLS resend flow referencing to an unavailable memory location. The issue is related only to MPLS traffic profile and has no bearing with any other jflow i.e. IPv4 and v6.
PR Number Synopsis Category: Layer 2 Circuit issues
1498040 The l2circuit neighbor might be stuck in rd state at one end of MG-LAG peer
Product-Group=junos 		In MC-LAG scenario, if the l2circuit is configured with primary-neighbor or backup-neighbor over the MC-LAG link and the l2ckt (l2ciruits control daemon for pseudowire) session of the primary-neighbor or backup-neighbor is flapped continuously (such as clear neighbor ldp and ospf etc..,), one of the remote neighbors may be stuck in RD (the remote pseudowire neighbor is down)status due to race condition between VC(virtual circuit)status update timer and L2ckt intf status change timer. Then, that pseudowire might be down, the traffic might be impacted if the RD pseudowire is not up.
PR Number Synopsis Category: Layer 2 Control Module
1473610 ERP 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.
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1484468 Packet 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 Number Synopsis Category: MPC11 ULC platform software related issues.
1467725 Hotswap between MPC11e and MPC9/8/6 is not supported
Product-Group=junos 		On MX2020/MX2010 platforms, hotswap MPC11e with MPC9/8/6 or vice versa will result in training failures. It is recommended to power-off the chassis before swapping the cards.
PR Number Synopsis Category: OS IPv4/ARP/ICMPv4
1496429 RE crash might be seen when a large number of nexthops are quickly deleted and re-added in large ARP/ND scale scenario
Product-Group=junos 		On all Junos platforms with large ARP/ND scale scenario, if a large number of nexthops are deleted and re-added very quickly (such as a result of link flap), the memory corruption might occur and eventually cause RE crash.
PR Number Synopsis Category: Kernel MPLS / Tag / P2MP Infrastructure
1493053 Backup RE might crash unexpectedly due to a rare timing issue
Product-Group=junos 		The backup Routing Engine might crash unexpectedly due to a rare timing issue during a route churn in the network.
1493431 BGP session might keep flapping between two directly connected BGP peers because of the wrong TCP-MSS in use
Product-Group=junos 		In case the two directly connected BGP peers are established over a one-hop LSP, if the IP layer's MTU is smaller than the MPLS layer's MTU, plus the BGP packets from the host have the DF bit set, the BGP session might keep flapping because of the wrong TCP-MSS in use.
PR Number Synopsis Category: JUNOS Network App Infrastructure (for ping, traceroute, etc)
1484689 Show system buffer command display's all zero in the MX104 chassis and it looks like cosmetic issue as there is no service impact reported
Product-Group=junos 		Corrected the odl tags and buffer data handling while xmlizing the output.
PR Number Synopsis Category: PTX5KBroadway based PFE IPv4, IPv6 software
1479789 Multicast routes add/delete events might cause adjacency and LSPs to go down
Product-Group=junos 		In PTX5000 platform with (FPC2-PTX-P1A | FPC-PTX-P1A), or PTX3000 with FPC-SFF-PTX-P1-A, with PIM scenario, The adjacency relationships of routing protocols and LSPs might go down if add/delete some multicast routes (which can be achieved by flapping interface or protocol) ). It is because that though the routes are deleted, its counter for statistic will not be removed from Junos resulting in memory block for counter exhaustion. And due to the exhaustion, any protocols that are sharing the same memory scope might fail to allocate its own counter, which eventually causes protocol adjacency and LSPs to go down. [TSB17747 [juniper.net]]
PR Number Synopsis Category: Layer 3 issues for VMX
1485706 Interface input error counters are not increasing on MX150
Product-Group=junos 		The input errors on MX150 may be zero under show interfaces extensive output when there are CRC/Align errors on the interface.
PR Number Synopsis Category: Protocol Independant Multicast
1443056 PIM RPF selection for the specific multicast group might get incorrectly applied to other multicast groups
Product-Group=junos 		On all Junos platforms, changing an RPF interface for a particular multicast group using PIM rpf-selection configuration, might cause other multicast groups to take, a newly changed RPF interface.
PR Number Synopsis Category: Issues related to PKI daemon
1489249 Has the risk of service interruption on all SRX platforms with a dual-stacked CA server
Product-Group=junos 		On all SRX products with Online Certificate Status Protocol (OCSP) or Certificate Revocation List (CRL) configured which belongs to a dual-stacked (IPv4/IPv6) Certificate Authority (CA) server, and if one of the IP addresses gets failure, all the services that rely on it might be interrupted, as Junos only selects the first IP from the DNS response message as the IP of the OCSP or CRL.
PR Number Synopsis Category: PTP related issues.
1493743 Dev to check and decide
Product-Group=junos 		ptp-clock-global-freq-tracable leaf value getting False (It is not changing to True) when the internal lock is in Acquiring state on summit1RU/3RU
PR Number Synopsis Category: QFX platform optics related issues
1457266 QFX5110 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. Note : Do not use 19.3R2-S2, 18.2R3-S3 and 18.2R3-S4 for this fix. The fix causes that FPC will go down when 100G link comes up and this leads FPC up and down every 90 seconds. The fix will work on 19.3R2-S3 and 18.2R3-S5 properly.
PR Number Synopsis Category: QFX L2 PFE
1385954 "CMQFX: Error requesting SET BOOLEAN, illegal setting 66" is generated at booting up.
Product-Group=junos 		The following log may be generated at booting up. >> Feb 10 02:15:26 jtac-qfx5100-48s-6q-r2373 : %PFE-3: fpc0 CMQFX: Error requesting SET BOOLEAN, illegal setting 66. This is a cosmetic log and you can ignore the log safely.
1454095 Changing the VLAN name associated with access ports may cause that MAC addresses can not be learned under EVPN-VXLAN scenario
Product-Group=junos 		On the QFX5k platform with EVPN-VXLAN configured, if the VLAN name associated with access ports is changed, then the virtual bridge domain may not be created. Due to this, the MAC addresses will not be learned. This issue will cause traffic loss.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1493258 Traffic loss could be observed in mixed-VC setup of QFX5100 and EX4300
Product-Group=junos 		On QFX5100 & EX4300 platforms, with a mixed-VC scenario there could be traffic loss on the Virtual Chassis port(VCP) when traffic ingress from QFX5100 and egress to EX4300.
PR Number Synopsis Category: RPD Next-hop issues including indirect, CNH, and MCNH
1458595 The rpd crash might be seen if BGP route is resolved over same prefix protocol next-hop in inet.3 table which has both RSVP and LDP routes
Product-Group=junos 		In race condition, if BGP route is resolved over same prefix protocol next-hop in inet.3 table which has both RSVP and LDP routes, when the RSVP and LDP routes are flapping (firstly these routes are down and then up), the BGP route will be re-resolved, and then the rpd crash might be seen.
PR Number Synopsis Category: jflow/monitoring services
1439630 Sampling might return incorrect ASN for BGP traffic
Product-Group=junos 		In a BGP scenario with sampling enabled, incorrect ASN (autonomous system number) might be returned for the traffic originated from an internal prefix. This is because some AS paths and routes don't hold the latest information in the message buffers that srrd (sampling route-record daemon) uses to send to the clients.
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: security-intelligence feature on SRX
1482947 19.2R2:VSRX3.0:SRX-RIAD:ipfd core found at 0x08601e14 in ipid_msg_process (svr=< optimized out>, client_id=< optimized out>, msg=< optimized out>, len=< optimized out>) at ../../../../../../src/pfe-shared/include/jnx/usp/ipid_shared.h:622
Product-Group=junos 		If ipfd core happens with similar stack trace, it is likely that PR1482947 applies, it is self-heal, does not need special action, and does not impact production traffic
PR Number Synopsis Category: SRX-1RU HA SW defects
1487951 If a cluster-id of 16 or multiples of 16 is used the cluster might not come up
Product-Group=junos 		When using the SRX4600 firewall in a cluster, if a cluster-id of 16 or multiples of 16 is being used, the cluster might not come up.
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1466470 VXLAN packet may be discarded with flow caching enabled on MX150 and vMX
Product-Group=junos 		On MX150 and vMX platform, VXLAN(Virtual Extensible LANs) packet may be discarded because flow caching doesn't support VXLAN when flow caching enabled.
1491091 MAC malformation might happen in a rare scenario under MX-VC setup
Product-Group=junos 		On MX-VC setup, if traffic is going through a VCP (virtual chassis port) port and forwarding to an egress port to the destination, while the traffic is handled entirely by the same PFE, MAC malformation might happen.
1492639 In node slicing setup MPLS TTL may be set to zero when the packet goes through AF interface configured with CCC family
Product-Group=junos 		On MX platform, if Junos node slicing and guest network function (GNF) enabled, when MPLS packet goes through circuit cross-connect (CCC) encapsulated Abstracted Fabric (AF) interface MPLS TTL might be set to zero.
PR Number Synopsis Category: Trio pfe multicast software
1478981 The convergence time for MVPN fast upstream failover might be more than 50ms
Product-Group=junos 		On MX platforms which act as Next Generation Mulicast Virtual Private Network (NG-MVPN) Provider Edge (PE) routers, if the hot-root-standby and sender-based-rpf features are configured to enable MVPN fast upstream failover, once the primary multicast flow rate falls below the configured "mvpn hot-root-standby min-rate rate" threshold, the egress PE router is supposed to take switchover action from the primary flows to the backup ones, and the covergence time should be within 50 milliseconds. Due to this issue, the covergence time might be more than 50ms and reach up to several seconds (e.g. 2~3s) in a highly scaled scenario (e.g. the number of the multicast groups undergoing the switchover simultaneously is greater than 250 groups). This will result in more traffic loss than expected.
PR Number Synopsis Category: V44 Satellite Device Infra
1466324 Temperature sensor alarm is seen on EX4300 in Junos Fusion scenario
Product-Group=junosvae 		In Junos Fusion scenario with EX4300 acting as SD, the temperature sensor alarms and logs might be seen due to the wrongly reading about 2-3 degrees lower than the expected. There's no CLI command to clear the alarm and logs.
PR Number Synopsis Category: Virtual Router Redundancy Protocol
1489425 The "vrrp-inherit-from" change operation leads to packets loss when traffic is forwarding to the VIP gateway
Product-Group=junos 		On all Junos platforms with VRRP scenario, if "vrrp-inherit-from" is configured and changing parameters under "vrrp-inherit-from" to another VRRP group, packets loss could happen when traffic forwarding toward to the VIP gateway.
PR Number Synopsis Category: ZT pfe l3 forwarding issues
1474160 An MPC11 crash might occur on MX2K platform using multi-dimensional advanced scale configuration having Inline Keep Alive Sessions
Product-Group=junos 		On an MX2k platform, in a rare scenario, after loading a complex multiple dimensional configuration with scaled Inline KA sessions, an MPC11 crash might occur due to transient condition of change and add of Inline Keep alive sessions.
 

Modification History

2022-03-23: non-technical changes; corrected formatting issue
2020-05-04: First publication date