Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

19.4R3-S5: Software Release Notification for JUNOS Software Version 19.4R3-S5

0

1

Article ID: TSB18131 TECHNICAL_BULLETINS Last Updated: 14 Dec 2021Version: 3.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX
Alert Description:
Junos Software Service Release version 19.4R3-S5 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
Risk Risk Description
Low/Notification - No defined time impact to take action Software Release Notification
Impact Impact Description
Low/Notification - Monitor the situation but no action needed Software Release Notification

Solution:

Junos Software service Release version 19.4R3-S5 is now available.

19.4R3-S5 - List of Fixed issues

PR Number Synopsis Category: JUNOS bugs found in UAC integration
1585158 Unified-access-control(UAC) authentication might not work post system reboot
Product-Group=junos
Post reboot on vSRX devices, UAC authentication might not work as expected. Unauthenticated traffic is not redirected to UAC module.
PR Number Synopsis Category: EX4300 PFE
1515234 DHCP binding does not happen after GRES.
Product-Group=junosvae
After GRES, interfaces may flap due to which DHCP bindings may be lost.
1597548 Broadcast traffic might be discarded when a firewall filter is applied to the loopback interface
Product-Group=junos
On EX4300 platforms, when a firewall filter for broadcast traffic with discard action policer is applied to the loopback interface, all broadcast packets (including Layer 2 forwarding packets, such as DHCP discover packets) that match this filter rule might be dropped.
1598251 VLAN tagged traffic might be dropped with service provider style configuration
Product-Group=junos
On EX4300 platforms with both enterprise style and service provider style configurations, an interface with enterprise style IFL and flexible-vlan-tagging configured, VLAN tagged traffic might be dropped due to incorrect programming in the system.
1601005 The VRRP packets might not be forwarded when "mac-move-limit" knob is configured
Product-Group=junos
On EX4300 platforms, if the device worked as a layer 2 transit switch between VRRP routers and the knob "mac-move-limit" is configured, the VRRP packets might not be forwarded after clearing ethernet-switching table.
PR Number Synopsis Category: EX4300 Filters implementation
1578859 The dcpfe crash is observed on Junos QFX/EX platforms
Product-Group=junos
On Junos QFX/EX platforms, the dcpfe crash may be seen. This is due to the interface flaps that on which a large number of mac-based VLAN clients registered. When it happens, the dcpfe crash, and the PFE(Packet Forwarding Engine) will restart, then all the traffic related to the PFE may be dropped. After that, the PFE could be self-recovery.
PR Number Synopsis Category: EX4300 Layer 2 implementation
1592133 The DHCP relay may not work if it connects with the server via type 5 route which with AE interface as the underlay interface
Product-Group=junos
On EX4300MP platforms, if an AE interface is configured as the underlay interface for the type 5 route that is used to connect the DHCP relay and server, the DHCP relay might not work which will result in the DHCP client failing to obtain an IP address.
PR Number Synopsis Category: EX2300/3400 PFE
1594353 Storm control profile might not be applied on EX2300 platforms
Product-Group=junos
On EX2300 platforms, storm control profile might not be applied hence there might be CPU high usage or packets loss issues on the device if there is large amount of broadcast or unknown unicast packets arriving the device.
1598346 The backup VC member may not learn mac-address on a master after removing a VLAN unit from the SP style AE interface which is part of multiple VLAN units
Product-Group=junos
On EX2300/3400/4300MP/4400 and QFX5100/5110/5200 VC platforms, if removing a VLAN unit from the SP style AE interface which is part of multiple VLAN units, the backup member might not learn mac-address on a master and start processing packet to that mac as unknown unicast. In this case, flooding will happen in the VLAN which might cause traffic loss due to the limited bandwidth.
PR Number Synopsis Category: Accounting Profile
1521223 Logical interface statistcs for as(aggregated sonet) are displayed double value then expected.
Product-Group=junos
On MX series with Junos 16.2 or later version, when using as(aggregated sonet) interface, logical interface statistcs for member links of as interface are displayed double value then expected
PR Number Synopsis Category: MPC Fusion SW
1586403 Traffic drop after enabling flexible-queuing-mode on MPC2E linecards
Product-Group=junos
MPC2E NG PQ & Flex Q with MACsec dropping 50 percent of traffic after enabling flexible-queuing-mode on both 1G and 10G.Changed the port speed for MACSEC MIC from 1G to 10G to increase the XQIF queue size to 32. On MX platform with MPC2E NG line cards and MACSEC MIC, traffic drop of about 50 percent may be seen when flexible-queueing-mode is enabled and a traffic is sent at the rate of more than 5Gbps.
1602939 The PFE might be disabled by a detected major CMERROR event while ungracefully removing the MIC from MPC2E-3D-NG/MPC3E-3D-NG
Product-Group=junos
On MPC2E-3D-NG/MPC3E-3D-NG with the certain chipset based MIC (like 20x1G MIC and 2x10G MIC), the PFE may be disabled while ungracefully removing the MIC from the MPC (e.g. without taking the MIC offline from CLI or with a MIC button).
PR Number Synopsis Category: Category for tracking AMR related issues.
1537386 AMR packets not going through expected path after interface flap.
Product-Group=junos
Core will be seen when upgrade is done from a release where fix is not present to a release where fix is present. To do ISSU between releases where core cant be avoided disable apbr config and enable after upgrade. We can disable apbr with the following commands, delete security advance-policy-based-routing profile For zone based apbr: delete security zones security-zone advance-policy-based-routing-profile For policy based apbr: delete security advance-policy-based-routing from-zone policy
PR Number Synopsis Category: BBE interface related issues
1577289 Traffic loss might be seen when subscriber service over AE bundle interface(s)
Product-Group=junos
On MX platforms with subscriber scenario, traffic loss might be seen if configuring dynamic-profile over AE bundle interface(s) (several thousand subscribers upon on the ports). This defect could be seen when changing AE child links while the kernel is busy deleting the old AE link members, and not pseudo ifl (logical interface) with new AE member links.
PR Number Synopsis Category: Bi Directional Forwarding Detection (BFD)
1516556 The remaining BFD sessions of the aggregated Ethernet interface flap continuously if one of the BFD sessions is deleted.
Product-Group=junos
On QFX10000 platforms, if multiple sub-interfaces of the same Aggregated Ethernet (AE) interface belong to different routing instances, and these sub-interfaces are configured with the same IP address and configured with separate Bidirectional Forwarding Detection (BFD) sessions, the remaining BFD sessions will flap continuously if one of these BFD sessions is deleted.
1522261 BFD with authentication for BGP flaps after GRES or NSR switchover on the NG-RE and SCBE2 setup.
Product-Group=junos
On the devices with NG-RE (Next Generation Routing Engine) and SCBE2 (Enhanced Switch Control Board), when BFD authentication for BGP is enabled, the BFD may flap after the NG-RE switchover. The switchover should be GRES or NSR switchover. After the flap, the device could be self recovery.
PR Number Synopsis Category: Border Gateway Protocol
1556656 Route validation states might flip between VALID/INVALID/UNKNOWN in some corner case
Product-Group=junos
In BGP Resource Public Key Infrastructure (RPKI) Origin Validation Scenario, in certain corner case, if there are periodic SerialNotifies received from the RPKI server then some ROA's that are stable in the RPKI cache server are deleted in Juniper router and then are relearned after some time. Due to this route validation state might flap and cause traffic impact.
1581578 BGP replication might be stuck in rare and timing conditions
Product-Group=junos
On all platforms with dual Routing Engines running Junos OS or Junos OS Evolved, BGP Nonstop-Routing replication might be stuck in a rare and timing case. BGP session(s) on the primary Routing Engine are stuck in "SoWait" state, and BGP session(s) on the backup Routing Engine cannot sync with the primary Routing Engine. From the BGP peer side, the BGP session(s) will break after hold-time expiry (90 seconds by default). This defect could be seen after the following series of events happen. * BGP NSR replication starts while primary Routing Engine (BGP session) is busy reading packets (i.e. protocol data unit). * Primary Routing Engine (BGP session) requests to stop reading at PDU boundary. * While BGP session on primary Routing Engine is waiting to read complete packet (remaining bytes), the TCP sync connection (between primary and backup BGP) flaps (i.e., PDU boundary is NOT read before the flap).
1582506 The rpd crash may be seen if next-hop self is used without using extended-nexthop and the routing table has IPv4 routes with IPv6 nexthops
Product-Group=junos
On all Junos and Junos EVO platforms, if "extended-nexthop" is used in BGP scenario, an IPv4 route with IPv6 next-hop may be received, when this route is advertised to a peer without "extended-nexthop" enabled, and if next-hop self export policy is configured towards the peer, the rpd might crash, and the rpd might not start after multiple coredumps.
1592123 The rpd crash might be seen if BGP peer flaps
Product-Group=junos
On all Junos platforms, when a BGP peer flaps, if the received routes are changed by the BGP process from active to inactive while cleaning up these received routes, the rpd crash might be seen.
PR Number Synopsis Category: MX Platform SW - FRU Management
1472949 During ISSU, FPC might restart during switchover to other RE
Product-Group=junos
In MX10003 with ISSU scenario, some protocol adjacencies might flap during vmhost software ISSU if the available FPC host linux memory is not enough or < 2.2GB before triggering ISSU via CLI as the FPC might reboot.
PR Number Synopsis Category: Virtual-chassis platform/chassisd infrastructure PRs for MX
1569556 member-id cannot be set when configuring MX-VC for the first time
Product-Group=junos
In MX-VC scenario, setting member-id with the command "request virtual-chassis member-id set member 1" may not work when configuring MX-VC for the first time. This may happen as the new SCB cards may have uninitialized VC Data Blocks.
PR Number Synopsis Category: PTX Chassis Manager
1602292 Junos OS: PTX10002-60C System: After upgrading, configured firewall filters may be applied on incorrect interfaces (CVE-2021-31382)
Product-Group=junosvae
On PTX10002-60C System, after upgrading to an affected release, a Race Condition vulnerability between the chassis daemon (chassisd) and firewall process (dfwd) of Juniper Networks Junos OS, may update the devices interfaces with incorrect firewall filters. This issue only occurs when upgrading the device to an affected version of Junos OS. Refer to https://kb.juniper.net/JSA11250 for more information.
PR Number Synopsis Category: Class of service in forwarding daemon
1599857 Traffic loss might be observed if per-unit-scheduler is configured on AE interface
Product-Group=junos
On all Junos platforms with per-unit-scheduler support, when per-unit-scheduler is configured on AE interface, after cosd restart or NSR switchover, unbind/bind of scheduler over child interface of AE might occur. In NSR switchover scenario, traffic loss may be seen.
PR Number Synopsis Category: QFX Access Control related
1574480 Private VLAN configuration might fail in certain scenario
Product-Group=junos
On all Junos platforms if 802.1X authentication is configured globally using the set protocol dot1x interface all command and if trunk interface is configured with vlans then Private VLAN configuration might fail.
1587837 Process dot1xd crash might be seen and re-authentication may be needed on EX9208 platform
Product-Group=junos
On EX9208 platform with fusion scenario where around 30,000 mac-radius authenticated sessions are established, process dot1xd might crash and the users may need to have re-authentication due to relevant memory not getting freed when dot1x is deleted on any interface, which causes a memory leak and leads the crash.
PR Number Synopsis Category: QFX Control Plane VXLAN
1584595 MAC address of the end-host is wrongly programmed in forwarding table after ESI failover
Product-Group=junos
End-hosts might not communicate via Ethernet VPN with Virtual Extensible LAN encapsulation (EVPN-VxLAN) domain after Ethernet Segment Identifier (ESI) failover. This issue affects QFX5000 platforms only. Please refer to restoration steps when this issue is encountered.
PR Number Synopsis Category: QFX xSTP Control Plane related
1592264 xSTP might not get configured when enabled on a interface with SP style configuration on all platforms
Product-Group=junos
On all Junos and EVO platforms, if xSTP is enabled on interface with service provider(SP) style configuration and the interface has multiple IFLs(units) each having different families then xSTP might not be configured on the interface and commit might fail with the following error message: "XSTP : Interface <> is not enabled for Ethernet Switching"
PR Number Synopsis Category: Device Configuration Daemon
1534787 The configuration might not be applied after deleting all existing logical interfaces and adding a new logical interface for an IFD in a single commit.
Product-Group=junos
If there are logical interfaces (IFLs) configuration for a physical interface (IFD), after deleting all existing IFLs and adding a new IFL for this IFD in a single commit, the new configuration might not be added, and the old configuration might not be deleted in the kernel.
PR Number Synopsis Category: Host path software for ACX platform
1584509 IPv4 Traffic loss with packet size more than 1410 on ACX5448
Product-Group=junos
On ACX5400 series platform when there is traffic surge, due to packet reassembly failures in the VMHOST, traffic loss might be seen. The ACX5400 software consists of Windriver Linux (WRL) 64-bit kernel with KVM hypervisor support providing the host operating system environment. The JUNOS runs as a VM on top of WRL host (VMHOST). As per the architecture the traffic from the Junos control plane will pass through the VMHOST and further to PFE to exit via the WAN interface. The internal interface between the Junos and VMHOST is of MTU 1500 due to which control packets exceeding 1500 MTU are to be fragmented and sent to VMHOST but it fails.
PR Number Synopsis Category: ACX LAG infrastructure
1589168 Traffic might get forwarded through the member links in down state after new member links are added to AE interface on ACX710/ACX5400
Product-Group=junos
On ACX5400 (i.e., ACX5448/ACX5448-D/ACX5448-M) and ACX710 Universal Metro Routers, if some existing member links within an aggregated Ethernet (AE) interface are in down state, after adding new member links into the AE interface, traffic might get forwarded through the member links in down state and cause traffic drop.
PR Number Synopsis Category: Covers Application classification workflows apart from custo
1573157 The srxpfe/flowd process might crash when Sky-ATP is used
Product-Group=junos
On all SRX Series devices with Sky-ATP used, the srxpfe/flowd process might crash. This issue happens only if the RTCOM session also ends up being processed by JDPI due to policy. Note, RTCOM is used by UTM, RTlog (Security log), and SkyATP services. And, Juniper Networks Deep Packet Inspection (JDPI) module (Decoder) is used by AppSecure services, APBR, SecIntel, etc.
PR Number Synopsis Category: Control Plane for Node Virtualization
1580168 MPC7E/8E/9E/11E line card might be stuck in "Unresponsive" state in a Junos Node Slicing setup
Product-Group=junos
There are two issues resolved in this PR. Issue 1: In a Junos Node Slicing setup, after assigning MPC7E/8E/9E/11E line card to a guest network function (GNF), a file containing GNF information might be copied to line card with incomplete content during card booting up and it cannot be updated with correct values in subsequent booting as well. It is a rare timing issue (e.g., it may happen if the line cards copy the file from routing engine in Base System (BSYS) while BSYS is populating the file with GNF information.) The issue could cause the MPC7E/8E/9E/11E line card to be stuck in "Unresponsive" state. Issue 2: In a Junos Node Slicing setup with MPC7E/8E/9E/11E line card, after assigning these line cards to a GNF or BSYS or activating/deactivating network-slices, duplicate entries could be added into some files in card (i.e., /etc/hosts.equiv and /root/.rhosts files in card). Over time (maybe years), these files could occupy large disk space and lead to the line card booting up issue.
PR Number Synopsis Category: Junos Evolved socket replication
1558814 EVO-NSR: BGP NSR : RPD Core seen after RE switchover
Product-Group=junos
The core is seen when "traceoptions" config is enabled with high scale, and routing is restarted/exiting with the knob being set.
PR Number Synopsis Category: EVPN control plane issues
1534021 The route table shows additional paths for the same EVPN or VXLAN type 5 destination after upgrading from Junos OS Release 18.4R2 S3 to Junos OS Release19.4R1 S2.
Product-Group=junos
When upgraded from 18.4R2-S3 to 19.4R1-S2, EVPN/VXLAN type 5 routes show additional paths to the same destination. The behaviour can cause a traffic impact in some certain routes leaking scenarios.
1594326 Transit Traffic gets dropped post disabling one of the PE-CE link on a remote Multi-Home PE in EVPN-MPLS A-A setup with Dynamic-List NextHop configured
Product-Group=junos
In an EVPN A/A ESI multihoming scenario with dynamic list next hop (DLNH)configured,when one of the multihomed CE-PE links goes down on remote MH-PEs, then traffic loss might be seen. https://kb.juniper.net/TSB18115
1597300 Traffic loss might be seen if AE bundle interface with ESI is disabled on master RE followed by a RE switchover
Product-Group=junos
On all Junos platforms traffic loss might be seen if AE bundle interface with ESI is disabled on master RE followed by a RE switchover.
PR Number Synopsis Category: EX Chassis chassism/chassisd
1556558 FPC with power related faults might get on-lined again once Fabric Healing has off-lined the FPC
Product-Group=junos
In rare cases of power related failures on the FPC, Fabric Healing will detect and try to heal this fault condition by performing an offline/online FPC event. If the same FPC fails again within 10 minute period, fabric auto-healing attempt is considered failing and the FPC will get off-lined to avoid further operational impact. If during the power offline event, the faulty FPC gets disconnected ungracefully due to the hardware power fault, the FPC might attempt an on-lined request again after 5 minutes. There may be traffic impact due to this issue.
PR Number Synopsis Category: EX4400 PFE software
1603015 On EX4400 dot1x authentication may not work on EVPN/xlan enabled endpoints.
Product-Group=junos
On EX4400 dot1x authentication may not work on EVPN/xlan enabled endpoints. The issue is due to EAPOL packets received on VxLAN ports are not processed in hostpath.
PR Number Synopsis Category: Express pfe Analyzer features
1592693 MPLS traffic might get discarded on passive monitoring interface on QFX10002/QFX10008/QFX10016 switches
Product-Group=junos
If passive monitoring is configured on QFX10002/QFX10008/QFX10016 switches, and both "family mpls" and "family inet" are configured on logical interface (IFL) of passive monitoring interface, due to a timing issue on sequence of family creation message pushing to Packet Forwarding Engine (PFE), sometimes the "family mpls" creation message might be pushed to PFE ahead of the "family inet" creation message. In this case, some MPLS properties are not set correctly in PFE. So, the MPLS traffic will get discarded on passive monitoring interface.
PR Number Synopsis Category: Express PFE L2 fwding Features
1584197 Junos OS: QFX Series and PTX Series: FPC resource usage increases when certain packets are processed which are being VXLAN encapsulated (CVE-2021-31361)
Product-Group=junos
An Improper Check for Unusual or Exceptional Conditions vulnerability combined with Improper Handling of Exceptional Conditions in Juniper Networks Junos OS on QFX Series and PTX Series allows an unauthenticated network based attacker to cause increased FPC CPU utilization by sending specific IP packets which are being VXLAN encapsulated leading to a partial Denial of Service (DoS). Refer to https://kb.juniper.net/JSA11223 for more information.
PR Number Synopsis Category: SRX4100/SRX4200 platform software
1547953 On vSRX2.0, vSRX3.0, SRX1500, SRX4100, SRX4200, SRX4600 running chassis cluster in Junos OS Release 18.3 or later, multiple messages of "LCC: ch_cluster_lcc_set_context:564: failed to lock chassis_vmx mutex 11" are generated in the chassisd log file. These messages may recur after every few seconds and they do not have any impact on system operation.
Product-Group=junos
On vSRX2.0, vSRX3.0, SRX1500, SRX4100, SRX4200, SRX4600 running Chassis Cluster in Junos 18.3 or later, multiple messages of "LCC: ch_cluster_lcc_set_context:564: failed to lock chassis_vmx mutex 11" are generated in the chassisd log file. These messages may reoccur after every few seconds and they do not have any impact on system operation.
PR Number Synopsis Category: IDP attack detection in the subscriber qmodules
1598867 Custom attack IDP policies might fail to compile
Product-Group=junos
On SRX-Series devices, custom attack IDP policies might fail to apply and compile.
PR Number Synopsis Category: IDP policy
1599954 IDP policy compilation is not happening when a commit check is issued prior to a commit
Product-Group=junos
On SRX platforms, IDP policy compilation is not loaded when a commit check command is run before commit command.
1601380 The srxpfe might crash while the IDP security package contains a new detector
Product-Group=junos
On all SRX platforms, the srxpfe process might crash and generate a core dump while installing the IDP security package which has the new detector version.
PR Number Synopsis Category: Integrated Routing & Bridging (IRB) module
1565213 The new master RE post switchover might go into DB mode (or crash) on EX platforms
Product-Group=junos
On EX and EX-VC platforms, if post routing engine switchover, MAC address is configured to IRB interface (for ex: set interface irb.500 mac 00:11:22:33:44:55) on new master RE, then the new master RE might crash or go into DB mode.
1593539 IPv6 neighbor might remain unreachable in VRRP for IPv6 scenario
Product-Group=junos
In the scenario where VRRP for IPv6 is configured over IRB interface, the IPv6 neighbor might remain unreachable.
PR Number Synopsis Category: jdhcpd daemon
1587982 The DHCP client might be offline for about 120 seconds after sending the DHCPINFORM message
Product-Group=junos
In a Juniper device acting as DHCP relay scenario, when 'always-write-giaddr' is not configured on the relay, the DHCPDISCOVER message sends after the DHCPINFORM message might be dropped for about 120 seconds.
1588813 Delegated prefix ipv6 address is missing in accounting stop messages
Product-Group=junos
DP (Delegated prefix) is cleared when underlying session (dhcpv6 over ppp) ifl is deconfigured. DP is not seen in Radius accounting stop messages.
1590421 The DHCP ALQ Queue may get stuck causing subscriber flap
Product-Group=junos
On MX platforms with DHCP ALQ, the ALQ(Active Lease Query) TCP Queue may get stuck. This may cause the subscribers from Backup BNG(Broadband Network Gateway) not to be able to sync with Master BNG and eventually causing the subscribers in Master to start going down and result in a major outage.
PR Number Synopsis Category: JFlow bug tracker for SRX platforms
1463689 The flowd might coredump frequently on SRX340
Product-Group=junos
On an SRX340 and SRX1500 devices with J-Flow version 9 configured, the flowd process might generate core files frequently when the device is busy.
PR Number Synopsis Category: Health-Monitoring related issues
1570526 The jinsightd process might be stuck with high CPU process utilization
Product-Group=junos
On the MX/PTX Series platforms, the jinsightd process might be stuck with high CPU process utilization if the services jinsightd is enabled in the Junos Telemetry Interface (JTI) scenario.
PR Number Synopsis Category: jl2tpd daemon
1532750 Destination lockout functionality does not work at the tunnel session level when CDN code is received.
Product-Group=junos
Destination should be lockout state when CDN received with proper error code. We have hidden knob to trigger destination in lockout state.
1596972 "show services l2tp tunnel extensive", "show services l2tp session extensive" and "show subscribers accounting-statistics" commands do not work on LTS
Product-Group=junos
In a subscriber management environment CLI commands "show services l2tp tunnel extensive", "show services l2tp session extensive" and "show subscribers accounting-statistics" do not work on LTS (L2TP tunnel switch).
PR Number Synopsis Category: Adresses ALG issues found in JSF
1598017 ALG traffic might be dropped
Product-Group=junos
On SRX-Series devices, ALG traffic might be dropped when incoming packet contains "HTTP/" and "rn" characters in data or NAT slipstream packets.
PR Number Synopsis Category: Application aware Quality-of-Service
1597875 The flowd core may be seen if the AppQOS module receiving two packets of a session
Product-Group=junos
On SRX platforms, during the parallel processing of packets of a session by the AppQOS module, the AppQOS module doesn't handle this properly and result in flowd core which impacts all services.
PR Number Synopsis Category: Flow Module
1543051 The flowd process might crash due to session table corruption
Product-Group=junos
On all SRX platforms, when tunnel interface is down, the tunnel session is not uninstalled from the session table but the tunnel session memory is freed. During the session lookup in fast path for packet processing, the tunnel session is matched but the flowd/srxpfe process (responsible for traffic forwarding in SRX) may crash when it tries to use this tunnel session.
1572240 The srxpfe process might crash during route churn
Product-Group=junos
On the vSRX3.0 or SRX5K platforms, the flowd/srxpfe process might crash if massive configuration(route table delete) changes and pumping the traffic at the same time. Traffic loss might be seen during the flowd/srxpfe process crash and restart.
1573842 The flowd/srxpfe process might crash when clearing the TCP-Proxy session
Product-Group=junos
On the SRX platforms, the flowd/srxpfe process might crash when clearing the TCP-Proxy session. Traffic loss might be seen during the flowd/srxpfe process crash and restart.
PR Number Synopsis Category: JSR Infrastructure
1555904 SPC3 might not come up after the system reboot
Product-Group=junos
On SRX-Series devices with SPC3, after the system reboot SPC3 might not come up.
PR Number Synopsis Category: IPSEC/IKE VPN
1586324 Memory leaks on the iked process on SRX5000 Series with SRX5K-SPC3 installed
Product-Group=junos
On SRX5000 Series with SRX5K-SPC3 installed, when IPsec VPN is configured, memory leaks might occur on the iked process.
PR Number Synopsis Category: Security platform jweb support
1591145 Junos OS: J-Web: A path traversal vulnerability allows an authenticated attacker to elevate their privileges to root (CVE-2021-31385)
Product-Group=junos
An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in J-Web of Juniper Networks Junos OS allows any low-privileged authenticated attacker to elevate their privileges to root. Please refer to https://kb.juniper.net/JSA11253 for more information.
1592021 Junos OS: J-Web allows a locally authenticated attacker to escalate their privileges to root. (CVE-2021-0278)
Product-Group=junos
An Improper Input Validation vulnerability in J-Web of Juniper Networks Junos OS allows a locally authenticated attacker to escalate their privileges to root over the target device. Please refer to https://kb.juniper.net/JSA11182 for more information.
1594516 Junos OS: J-Web allows a locally authenticated attacker to escalate their privileges to root. (CVE-2021-31372)
Product-Group=junos
An Improper Input Validation vulnerability in J-Web of Juniper Networks Junos OS allows a locally authenticated J-Web attacker to escalate their privileges to root over the target device. Refer to https://kb.juniper.net/JSA11237 for more information.
1597221 [J-Web] a custom application name contains "any" is listed under Pre-defined Applications
Product-Group=junos
In J-Web, custom application info is usually listed under "Custom-Applications". However, if the application name contains "any", it is listed under "Pre-defined Applications".
1599434 J-Web may not display customer defined application services if one new policy is created
Product-Group=junos
On SRX Series platform, a custom-defined application-set is not listed in J-Web security policy configuration wizard.
1602228 J-web application might crash with httpd core-dumps
Product-Group=junos
On SRX-Series devices, the J-web application might crash and generate httpd core-dumps when "set system no-compress-configuration-files" is configured.
1603993 Radius users might not be able to view/modify configuration via J-web
Product-Group=junos
On SRX-Series devices, when Radius server is used for authentication with login-class "Juniper-Local-User-Name" then users might not be able to view/modify configuration via J-web.
1604929 On all SRX platforms, some widgets in JWeb might not load properly for logical systems users
Product-Group=junos
On all SRX platforms, some widgets in JWeb might not load properly for logical systems users
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1596483 Mcscnoopd might crash during deleting/adding layer-2 forwarding configuration after performing ISSU
Product-Group=junos
In layer-2 forwarding configuration with ISSU scenario, Gencfg provides a generic way for applications to store interface state information (blobs) which needs to be sent to PFE/PIC/REs/daemons. In some rare cases, after performing ISSU, the Gencfg key (handed/generated by the kernel, a kind of layer-2 token) info might be inconsistent between the l2ald and master/backup kernel due to the state sync issue, then the Gencfg might send the blobs with this wrong key to the kernel during adding/deleting the layer-2 forwarding configuration. Then the kernel might return the wrong messages (e.g. next-hop lookup) to mcsnoopd, this will cause mcsnoopd to crash, the services/functions based on multicast will be impacted.
PR Number Synopsis Category: Label Distribution Protocol
1598174 The LDP replication session might not get synchronized when dual-transport is enabled
Product-Group=junos
On all Junos platforms with NSR configured, when "dual-tranport" is configured under protocols ldp and the inet-lsr-id/inet6-lsr-id is different from the router-id, the Label Distribution Protocol (LDP) replication session might not get synchronized and causing traffic loss during RE switchover.
1601854 VPLS connection might get down if knob "dual-transport" is configured
Product-Group=junos
On all Junos platforms with NSR configured, if knob "dual-transport" is configured under "protocols ldp" and the inet-lsr-id/inet6-lsr-id is different from the router-id, VPLS connection on peer device might get down and traffic loss would occur during RE switchover.
PR Number Synopsis Category: Issues related to Junos licensing infrastructure
1582419 Junos OS and Junos OS Evolved: A vulnerability in the Juniper Agile License Client may allow an attacker to perform Remote Code Execution (RCE) (CVE-2021-31354)
Product-Group=junos
An Out Of Bounds (OOB) access vulnerability in the handling of responses by a Juniper Agile License (JAL) Client in Juniper Networks Junos OS and Junos OS Evolved, configured in Network Mode (to use Juniper Agile License Manager) may allow an attacker to cause a partial Denial of Service (DoS), or lead to remote code execution (RCE). Refer to https://kb.juniper.net/JSA11219 for more information.
PR Number Synopsis Category: Port-based link layer security services and protocols that a
1596755 Traffic loss might happen periodically in MACsec used setup if Routing Engine is working under a pressure situation
Product-Group=junos
On MX10003 routers with MACsec used scenario, traffic loss might happen periodically if Routing Engine is working under a pressure situation (rpd memory occupied around larger than 70%), which might cause the message of Secure Association Key (SAK) of MACsec to be vetoed by kernel that causes one of pair (RX/TX) Secure Association (SA) number missing. Moreover, the missing SA number is still available in the system, so whenever SA number is rollover to it (SA number is rollover between 0 to 3), traffic loss might happen due to invalid SA pair.
PR Number Synopsis Category: Mobile Edge mobiled related issues
1592345 The mobiled daemon might crash after switchover is performed for an AMS interface or crash occurs on service PIC where the AMS member interfaces are present
Product-Group=junos
With warm standby being configured for an aggregated multiservices (AMS) interface, if switchover is performed for the specified warm standby AMS interface or crash occurs on the service PIC where the AMS member interfaces are present, the mobiled daemon might crash. The mobiled daemon will restart automatically and be self-recovered after crash.
1601785 Unable to commit configuration due to error Check-out failed for Mobility process
Product-Group=junos
Unable to commit configuration due to error Check-out failed for Mobility process. If mobility process dependent process (like CUPS) are configured, then we don't see this PR.
PR Number Synopsis Category: Multi Protocol Label Switch OAM
1530382 The ping mpls rsvp command does not take into account lower MTU in the path
Product-Group=junos
MPLS ping over rsvp LSP with sweep option is failing to fetch the right MTU.
PR Number Synopsis Category: Multicast for L3VPNs
1567584 Type7 messages may not be sent from egress PE resulting in Type 3/5 messages not created for some S, Gs in source PEs
Product-Group=junos
On all Junos OS platforms, if MVPN type 6 and type 7 were intended for local PE router (i.e rt import is local PE address) and later rt import community gets updated (route should be of same NLRI) to remote PE, and further the route itself gets deleted, then it could lead to total c-multicast count to underflow if multiple routes undergo similar operation. Further MVPN type 6 and type 7 routes may be suppressed and not sent out.
PR Number Synopsis Category: MX10K platform
1490749 FPC went offline and dumped core when the PIC was offlined via CLI
Product-Group=junos
The QSFP based ports gets corrupted, due to SFPP detach procedure call for all ports on PIC while destroying ports for PIC offline. It seems the device was designed to be such that when destroying one port or QSFP, it ends up QSFP destroy for all ports.
PR Number Synopsis Category: Neo Interface
1576370 MIC specific alarms are not cleared after MIC reboot
Product-Group=junos
An alarm raised due to a transient HW problem with MIC does not get cleared automatically after MIC restart.
1595682 The interface down might be delayed after performing the "set interface disable" command
Product-Group=junos
On MX platforms with MPC4E/MPC7E line cards used, if performing the "set interface disable" command to disable an interface, the interface down might be delayed. As a result the link down event detection in peer will be delayed. This can cause traffic loss during this delay interval.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1551193 VM might crash if file is shared between host operating system and guest operating system using virtFS
Product-Group=junos
On Virtual Machines (VM) based platforms running Junos images, file might not be shared between host operating system and guest operating system via Virtual Filesystem (virtFS). When this issue happens, device might be restarted.
1563647 Memory corruption of any binary in /usr/bin/ or /usr/sbin/ may be triggered when a recovery snapshot is being copied to the OAM volume or system while it's in heavily stressed condition
Product-Group=junos
Memory corruption of a binary from /usr/bin/ or /usr/sbin/ directory can occur if such binary is invoked when a recovery snapshot creation is in progress. The exact symptoms will be different depending on the exact binary and JUNOS version - some programs will show an error, and some programs will crash every time it is executed. Such memory corruption will be persistent until the affected Routing Engine is restarted. Please refer to TSB17954 (https://kb.juniper.net/TSB17954) for further details. In addition to recovery snapshot, a device reboot could also be a possible trigger when the system is under heavier read operations across the mounted packages.
PR Number Synopsis Category: IPv6/ND/ICMPv6 issues
1538421 Cluster failover causes active node to be stuck in secondary-hold
Product-Group=junos
In SRX platforms with cluster scenario, cluster failover might fail, causing traffic loss, if a Secure Tunnel (ST) interface is used in the Virtual Router(VR) instance and that ST interface is flapped to down before cluster failover. Note: A secure tunnel interface (st0) is an internal interface that is used by route-based VPNs to route cleartext traffic to an IPsec VPN tunnel.
PR Number Synopsis Category: TCP/UDP transport layer
1527246 During RE switchover the new master RE may suddenly crash
Product-Group=junos
On all Junos platforms, due to a rare problem in TCP socket replication between REs (Routing Engine) and MD5 digest processing on the backup RE in NSR configuration, the new master RE might crash during RE switchover and cause an outage.
1557881 Junos OS: Upon receipt of specific sequences of genuine packets destined to the device the kernel will crash and restart (vmcore) (CVE-2021-0283, CVE-2021-0284)
Product-Group=junos
A buffer overflow vulnerability in the TCP/IP stack of Juniper Networks Junos OS allows an attacker to send specific sequences of packets to the device thereby causing a Denial of Service (DoS). Please refer to https://kb.juniper.net/JSA11200 for more information.
1595649 Junos OS: Upon receipt of specific sequences of genuine packets destined to the device the kernel will crash and restart (vmcore) (CVE-2021-0283, CVE-2021-0284)
Product-Group=junos
A buffer overflow vulnerability in the TCP/IP stack of Juniper Networks Junos OS allows an attacker to send specific sequences of packets to the device thereby causing a Denial of Service (DoS). Please refer to https://kb.juniper.net/JSA11200 for more information.
PR Number Synopsis Category: OSPF routing protocol
1592424 The remote LFA (loop-free-alternate) backup path might not be formed
Product-Group=junos
With OSPF remote LFA feature enabled, when ABR (area border router) with the primary interface and the secondary interface are in different OSPF areas, if the secondary interface is supposed to be chosen as part of the Remote-LFA path then the remote LFA backup path might not be formed.
1601187 The rpd process might be stuck at 100% in OSPFv3 scenario
Product-Group=junos
On all Junos and Evo platforms with OSPFv3 (Open Shortest Path First version 3) used, if there are multiple Router LSAs (Link-State Advertisement) from the same peer, the rpd process might be stuck at 100% during the Router LSAs update.
PR Number Synopsis Category: Express Chip L3 software
1593244 BFD session might flap during RE switchover
Product-Group=junos
On QFX10K platforms with GRES/NSR enabled, BFD session might flap during RE switchover. This issue has service impact.
PR Number Synopsis Category: PTP related issues.
1499815 Announce messages are transmitted out at the rate of 1pps instead of 8pps on PTP master port with G.8275.1 profile
Product-Group=junos
With G.8275.1 profile, when the PTP stream 4 is deleted/deactivated/disabled, the announce rate of all master ports of the same slot reduces from 8 pps to 1 pps thereby impacting downstream clients. Deactivate and activate PTP configuration to recover from the issue.
1592657 Using the BITS interface from backup RE for clock recovery might not work
Product-Group=junos
On MX platforms with dual Routing Engine (REs), with Graceful Routing Engine Switchover (GRES) enabled and in Precision Time Protocol (PTP) Hybrid mode, if using the building-integrated timing supply (BITS) interface from backup RE for clock recovery, that will not work.
PR Number Synopsis Category: Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1598019 Dropping socket connection due to keepalive timer expiration with port 33015
Product-Group=junosvae
Dot1x is disabled for a platform but still, l2ald process trying to connect with dot1x due to that we are seeing Syslog messages continuously.
PR Number Synopsis Category: QFX platform fabric mgmt for Express ASIC chip
1577315 The port might not get brought down immediately during some abnormal type of linecard reboot on QFX10K platforms
Product-Group=junos
On QFX10K platforms, if some system internal error is encountered (e.g., kernel software fault), it may result into some abnormal types of linecard reboot. The port might not get brought down immediately after the reboot start, and it will lead to traffic blackhole due to this issue.
PR Number Synopsis Category: Interface related issues. Port up/down, stats, CMLC , serdes
1582105 Some 40G ports may not be channelized successfully on the QFX5100 platforms
Product-Group=junos
On the QFX5100 platforms, some 40G ports may not be channelized successfully and may stay down after upgrading host OS along with Junos OS using ZTP or doing manually via CLI.
PR Number Synopsis Category: QFX access control list
1583440 Firewall filter not programmed after deleting a large filter and adding a new one in a single commit on QFX5K platforms
Product-Group=junos
On QFX5k platforms, if a large filter that is applied to one or more interfaces is deleted and another large filter is applied in a single commit, both filters need to exist at the same time in Ternary Content-Addressable Memory (TCAM) for a brief period. If the size of both filters combined is bigger than the available TCAM space, the second filter will not be programmed in hardware, and functionality expected from the filters will not be available. This is a hardware limitation and this software fix only adds additional syslogs to indicate that the firewall is not programmed.
1592463 The IPv4 fragmented packets might be broken if PTP transparent clock is configured
Product-Group=junos
On QFX5K platforms with PTP transparent clock enabled, the IPv4 fragmented packets of UDP datagram might be broken by PTP in some rare scenario, and the corrupted packets will be a part of the payload.
1606256 Multicast streams may stop flooding in VXLAN setup
Product-Group=junos
In VXLAN with multicast used scenario, multicast traffic might not get flooded if the multicast IP is in one of the IP range (224.0.0.32 - 224.0.0.255). This is because a newly introduced dynamic filter only works for non-VxLAN traffic.
PR Number Synopsis Category: QFX L2 PFE
1580352 DHCP packets might be dropped if dynamic filter 'dyn-dhcpv4_v6_trap' is applied on the interface
Product-Group=junos
DHCP packets might be dropped when dynamic filter 'dyn-dhcpv4_v6_trap' is applied and software-based learning CLI is enabled on the interface.
1596643 "fpc0 bcm pkt reinsert failed" log written in the log messages in an aggressive way
Product-Group=junos
The error messages will be seen if the impacted switch found connected to another one through a trunk connection in which all Vlans are allowed, the impacted switch receives VSTP packets for non-configured VLANs. Those messages are informative messages and will be harmless.
1596773 Traffic might be dropped after backup FPC is rebooted in a VC scenario
Product-Group=junos
If the egress firewall filter with policier is configured on the AE interface on QFX5K/EX46XX platforms, traffic might be dropped after the backup FPC is rebooted in a virtual chassis scenario.
1597261 The interface might not be brought up when QinQ is configured
Product-Group=junos
The interface might not be brought up if Q-in-Q is configured on Broadcom chipset based QFX/EX platforms except EX2300 (The affected platforms: QFX3500/QFX3600/QFX5100/QFX5110/QFX5120/QFX5130/QFX5200/QFX5210/EX3400/EX4300/EX4600/EX4650).
1600892 Two copies of broadcast ARP packets are sending to the other VTEPs
Product-Group=junos
On EX2300/3400/4300/46XX and QFX5000 Series platforms in EVPN/VXLAN scenario, the L2 Leaf devices might send two copies of broadcast ARP packets to other VTEPs.
PR Number Synopsis Category: QFX L3 data-plane/forwarding
1561722 Junos OS: QFX5000 Series: Traffic from the network internal to the device (128.0.0.0) may be forwarded to egress interfaces. (CVE-2021-31371)
Product-Group=junos
Juniper Networks Junos OS uses the 128.0.0.0/2 subnet for internal communications between the RE and PFEs. It was discovered that packets utilizing these IP addresses may egress an QFX5000 Series switch, leaking configuration information such as heartbeats, kernel versions, etc. out to the Internet, leading to an information exposure vulnerability. Refer to https://kb.juniper.net/JSA11236 for more information.
PR Number Synopsis Category: QFX EVPN / VxLAN
1589702 LLDP packets drop on SP style interface for QFX devices
Product-Group=junos
On QFX platforms with VxLAN Ports configured in SP style, LLDP neighbor ship may not be formed due to wrong IFL allocation in hostpath. This can cause LLDP packet drops.
PR Number Synopsis Category: KRT Queue issues within RPD
1554981 The rpd process may crash if the BGP route is resolved over a tunnel
Product-Group=junos
On all Junos platforms, the rpd process might crash if the BGP route is resolved over the tunnel (e.g. IPIP, GRE, and UDP).
1572130 High CPU usage may occur on rpd for routes that use static subscriber
Product-Group=junos
On all Junos platforms in subscriber scenario, routes that use static subscriber demux or ge interfaces as qualified next-hop may be stuck due to the error "Destination address required" after GRES/ISSU. This may cause high CPU usage for rpd. The rpd restarts itself and system recovers automatically.
PR Number Synopsis Category: RPD route tables, resolver, routing instances, static routes
1523896 The VRF label is not assigned at ASBR when the inter AS is implemented.
Product-Group=junos
On all Junos platforms, with inter AS option A or option B implemented, virtual routing and forwarding (VRF) label embedded in composite-next-hop might be ignored when knobs 'protect core' and 'chained-composite-next-hop' are configured. As a result, VRF label for customer edge (CE) could not be assigned to customer IP at autonomous system border router (ASBR). Please refer to workaround provided when this issue hit.
PR Number Synopsis Category: RPM and TWAMP
1541808 The rmopd process memory leak might be seen if the TWAMP client is configured.
Product-Group=junos
If TWAMP (Two-Way Active Measurement Protocol) client is configured, memory leak in rmopd process may be observed after executing "request services rpm twamp start client" command.
PR Number Synopsis Category: SW PRs for SCBE3 fabric
1593821 Fabric errors will be generated after swapping MPC10E with MPC7E in the same slot
Product-Group=junos
In MX240/MX480/MX960 routers with SCB3E scenario, if MPC7E is swapped with MPC10E in the same slot or the MPC10E is inserted into an empty slot, the fabric link-training for the line-card impacted will failure and fabric links will not come up. This will cause not be able to send traffic over fabric.
PR Number Synopsis Category: Secure Web Proxy functionality on Junos
1585542 Secure Web proxy continue sending DNS query for unresolved DNS entry even after the entry was removed
Product-Group=junos
On SRX series device, Secure Web proxy continue sending DNS query for unresolved DNS entry even after the entry was removed.
PR Number Synopsis Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1600619 The Multiservices card doesn't drop the TCP ACK packet received as a reply to the self-generated TCP keepalive
Product-Group=junos
On MX with Multiservices card (MS-PIC/MS-MPC) installed, when the user's TCP session is passing the Multiservices card, TCP tickle functionality tries to extend TCP session after the inactivity-timeout expires by sending self-generated TCP keepalive packets to both parts of TCP connection and expecting the TCP ACK to be seen from both parts. While the expected behavior is to drop that TCP ACK packet on Multiservices card upon receiving, it sends to another part of TCP connection, this causes confusion and inability to extend TCP session, and then causes impact on long-lived TCP sessions with low volume of traffic.
PR Number Synopsis Category: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1574321 DS-Lite throughput degradation might be seen on MS-MPC
Product-Group=junos
On MX240, MX480, MX960, MX2008, MX2010 and MX2020 platforms with MS-MPC, when sending DS-Lite softwire session under heavy load in MS-MPC, throughput performance for DS-Lite in MS-MPC is dropped about 80 percent. Packets drop might be seen.
1582030 Junos OS: MX Series: Traffic drops will be observed if MS-MPC/MS-PIC resources are consumed by certain traffic causing a partial DoS (CVE-2021-31369)
Product-Group=junos
On MX Series platforms with MS-MPC/MS-MIC, an Allocation of Resources Without Limits or Throttling vulnerability in Juniper Networks Junos OS allows an unauthenticated network attacker to cause a partial Denial of Service (DoS) with a high rate of specific traffic. If a Class of Service (CoS) rule is attached to the service-set and a high rate of specific traffic is processed by this service-set, for some of the other traffic which has services applied and is being processed by this MS-MPC/MS-MIC drops will be observed. Please refer to https://kb.juniper.net/JSA11231 for more information.
1598720 The packet loop might be seen after receiving the PCP request packets which are destined to softwire concentrator address
Product-Group=junos
On MX platforms with MS-MPC/MS-PIC, the packet loop might be seen after receiving the PCP Mapping request packets to service-set where pcp rule is not configured and the packet loop might cause high CPU utilization.
PR Number Synopsis Category: Remote Access VPN issues on SRX
1599398 httpd-gk core might be observed when ipsec vpn is configured
Product-Group=junos
On SRX-Series devices with ipsec vpn configured when vpn_config is NULL, httpd-gk core might be observed.
PR Number Synopsis Category: SSL Proxy functionality on JUNOS
1597111 The flowd might core dump if application-services security policy is configured
Product-Group=junos
On SRX platforms, the flowd might core dump if application-services security policy is configured. The traffic outage would occur if this issue is hit.
PR Number Synopsis Category: MPC7/8/9 Interface Issues
1546704 The 40G or 100G interfaces might flap during ISSU if PTP is deactivated on the interfaces on MX/EX92 platforms
Product-Group=junos
On MX/EX92 platforms with MPC7/8/9 or similar chips, if PTP configuration was previously used and then deactivated for 40G or 100G interfaces, the interfaces might flap during ISSU.
1574279 QSFP 4x10G interface might not come up after FPC reboot
Product-Group=junos
On EA-based MX platforms with QSFP module, QSFP 4x10G interface fails to come up after FPC reboot.
PR Number Synopsis Category: SRX-1RU platfom related protocol, QoS, filtering features et
1595462 Node1 fpc0(SPM) goes down after ISSU and RG0 failover
Product-Group=junos
On SRX TVP platforms, after ISSU (In-Service Software Upgrade), traffic outage might happen after RG0 failover from node0 to node1.
PR Number Synopsis Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1589105 The VPLS BUM traffic not replicated on all branches in the multicast tree with MPC10/MPC11 line Cards
Product-Group=junos
VPLS routing instances create flood tokens for forwarding Broadcast/Unknown Unicast/Multicast (BUM) traffic to remote PEs over MPLS core. Starting from Junos software 19.4R3 release and above, MPC10/MPC11 is supported as a member-link in the replication tree bound to the flood token. Due to certain flaws in software implementation, the BUM traffic does not get forwarded to all remote PEs post any network churn event that leads to underling MPLS forwarding path change.https://kb.juniper.net/TSB18114
PR Number Synopsis Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1596645 Wrong Input/Output Octets and Packets in Interim-update may be observed if a subscriber is present in multiple PFE instances
Product-Group=junos
In Enhanced Subscriber Management environment with interim-update configured, if a subscriber is present over multiple PFE instances (e.g. configure subscriber interface over aggregated Ethernet bundle), which is hosting in Push-model MPC that supports Next-Gen Broadband-Edge Statistics (e.g. MPC2E-NG/MPC3E-NG, MPC5E/7E/8E/9E), the wrong Input/Output Octets and Packets count in Interim-update may be observed. Please note that this issue is only applicable for releases 20.1 and prior. The code was restructured on 20.2 and post, so the issue is no longer applicable.
PR Number Synopsis Category: Trio pfe stateless firewall software
1588708 The traffic might not failover with shared-bandwidth-policer enabled on AE
Product-Group=junos
On all MX platforms, when having a shared-bandwidth-policer attached to an AE interface as an interface policer, the traffic might not be policed as expected after AE child member link changes (add/delete/Up/Down). This is caused by missing interface policer update.
1598830 The service filter might get wrongly programmed in PFE due to a rare timing issue in enhanced subscriber management environment
Product-Group=junos
In enhanced subscriber management environment, if a service filter is applied to a dynamic service set, the service filter instance will be created on Packet Forwarding Engine (PFE) based on the configured service filter template. If the configured service filter template is changed at the same time a service filter instance is instantiated, the service filter might get wrongly programmed in PFE due to a rare timing issue. This issue could cause the service failure.
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1525824 The following error message is observed when alarms after interface reset: 7836 ifl 567 chan_index 8 NOENT & jnh_ifl_topo_handler_pfe(13015): ifl=567 err=1 updating channel table nexthop.
Product-Group=junos
When the VRRP MACs will be deleted, the VRRP feature will be disabled from the IFL. We are seeing this issue as part of deletion of VRRP feature. During VRRP feature disable process, Ifl_entry should be present. But here we can see that ifl delete has been happened first and then VRRP feature disable is happening. To avoid this, implementing precheck for the ifl_entry and also will be cleaning up the vrrp entry as part of sw_entry and hw_entry deletion.
1568324 The L2TP tunnel might not work with filter-based encapsulation
Product-Group=junos
On all MX platforms, the L2TP tunnel will not work with filter-based encapsulation for the breakout interface. This issue is seen as the parsing logic in PFE (Packet forwarding engine) for getting the tunnel parameters could not handle breakout interface scenarios.
PR Number Synopsis Category: Trio pfe l3 forwarding issues
1462219 CCL: LAG traffic load balance on failed child links more than 6% among child link (18.2X75-D50.6/.8)
Product-Group=junos
The amount of LAG load balancing traffic going through each member link may deviate more than 6%. This issue is introduced by the fix for PR1435322.
1558899 Some transmitting packets may get dropped due to the "disable-pfe" action is not invoked when the fabric self-ping failure is detected
Product-Group=junos
On the Trio-based line card with more than one PFEs, if there is a fabric self-ping failure detected on one of the PFE, the chassisd will disable all the IFD (physical interfaces) associated with the PFE to prevent blackhole and report a major CMERROR. Because the affected PFE is still active, and some applications (like BFD over AE across multiple FPCs/PFEs) are still using the PFE to transmit packets, the packets will get dropped due to all interfaces being disabled.
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1569903 During rare circumstances, the mgd process might crash and generate a core file on Junos devices connected with Contrail Service Orchestration (CSO)
Product-Group=junos
On all Junos devices connected with Contrail Service Orchestration (CSO), during rare circumstances when get-configuration rpc and commit are run together, the mgd process might crash and generate a core file (or dump file).
PR Number Synopsis Category: Virtual Router Redundancy Protocol
1578126 ARP resolution failure might occur during VRRP failover
Product-Group=junos
On Junos platforms with VRRP failover-delay configured, changing VRRP mastership might cause peer device to re-learn VIP ARP entry on old master interface due to timing issue.
PR Number Synopsis Category: VSRX platform software
1564117 Fabric probe packets might be processed incorrectly when power-mode-ipsec (PMI) is enabled
Product-Group=junos
On SRX-Series devices with PMI enabled, the fabric probe packets used by HA (High-availability) control plane might be processed incorrectly.
PR Number Synopsis Category: usf ams related issues
1590890 NAT service might not happen after performing AMS switchover or deactivating/activating NAT service
Product-Group=junos
Network Address Translation (NAT) service might not take effect when executing Aggregated Multiservices Interface (AMS) switchover or bouncing NAT service. When this issue happens, duplicate NAT entries could happen. Possible restoration method is already provided. However, please arrange a maintenance window if AMS switchover or NAT service bouncing is necessary.
PR Number Synopsis Category: usf nat related issues
1599603 MX SPC3 applications for protocol ICMP is not detected and does not allow user to modify inactivity-timeout values.
Product-Group=junos
MX SPC3 applications for protocol ICMP is not detected and does not allow user to modify inactivity-timeout values.
 

19.4R3-S5 - List of Known issues

PR Number Synopsis Category: BBE multicast related issues
1537846 The NGMPC2 process generates the core file at bv_entry_active_here::bv_vector_op:: gmph_reevaluate_group:: gmph_destroy_client_group.
Product-Group=junos
If PFE processes distributed igmp pseudo ifl delete, it attempts to delete all associated multicast flows. On a scaled setup, deleting several thousand multicast flows hogs CPU for long time that it is killed by the scheduler, resulting in core. This is a rare condition, seen only on scaled distributed igmp setup.
1545394 JDI BBE REGRESSION : NGMPC2 core seen@gmph_group_aggregate_client_state: gmph_reevaluate_group:: gmph_destroy_client_group:: gmph_destroy_group_client_groups
Product-Group=junos
When subscribers running distributed imp logging out at high rate, sometimes because of RE control plane to line card msg out of order, we can see line card have too much work to do to deleting pseudo-if before all its subscribers, hogging CPU too long that it is killed by scheduler, thus crash. This is a rare condition.
PR Number Synopsis Category: MIBs related to BBE
1535754 Snmp mib walk for jnxSubscriber OIDs returns a general error.
Product-Group=junos
Snmp mib walk for jnxSubscriber OIDs returns General error
PR Number Synopsis Category: Border Gateway Protocol
1607777 With rib-sharding enabled any commit will flap all BGP sessions with 4 byte peer-as (AS number 65536 or greater)
Product-Group=junos
On all Junos platforms, if both rib-sharding and 4-byte peer-as (AS number 65536 or greater) are configured then BGP peers with 4-byte peer-as might flap whenever any configuration change occurs.
PR Number Synopsis Category: Device Configuration Daemon
1601566 The dcd process might crash and FPC might be stuck in ready state on MX platforms
Product-Group=junos
On MX platforms in Junos Fusion scenario, if targeted-distribution is configured for AE/vlan-demux/PPPoE interfaces whose underlying legs are on FPC numbers greater than 32 (for ex: ge-101/0/0) then the dcd process might crash and FPC might be stuck in ready state.
1608281 Memory leak on dcd process occurs when committing configuration changes on any interfaces in a setup with AMS interface configured
Product-Group=junos
With aggregated multiservices interface (AMS) configured, the memory leak on dcd daemon occurs when making configuration changes on any interface. The leak rate is slow and depends on the scale of the IFLs on AMS interfaces (e.g. if there are 8 AMS physical interfaces with 8000 logical interfaces, the leak is about 5MB on each commit), which may lead to dcd crash.
PR Number Synopsis Category: Firewall Filter
1601761 The snmpwalk may not get polling the mib for dual-stack interface
Product-Group=junos
On all Junos devices, the snmpwalk may not work for on dual-stack interface if the interface filter name is the same for input list filters.
PR Number Synopsis Category: SRX4100/SRX4200 platform software
1554716 Certain SRX4100, SRX4200 and JRR200 devices SSD may encounter "buffer I/O error" leading to drive failure
Product-Group=junos
Certain SRX4100, SRX4200 and JRR200 device solid-state drives (SSD) may fail with "buffer I/O error" after approximately 3.22 years (Power_On_Hours of 28224) in service due to SSD firmware error. The failed device can be recovered with a power cycle, however failure may reoccur 42 days (1008 hours) later. The impacted SSD firmware version is MG02.
PR Number Synopsis Category: idp flow creation, deletion,notification, session mgr intfce
1579055 Global data SHM utilization increase quickly and FTP traffic might impacted
Product-Group=junos
On SRX platforms, if IDP and FTP ALG are enabled, the FTP data channel might not be established as IDP memory for data utilization increases quickly. It happened intermittently.
PR Number Synopsis Category: Signature Database
1594283 IDP signature DB update fails
Product-Group=junos
On SRX Branch platforms, it is unable to use latest signature pack due to IDP DB failing to update.
PR Number Synopsis Category: IPSEC/IKE VPN
1530684 On all SRX Series devices using IPsec with NAT traversal, MTU size for the external interface might be changed after IPsec SA is re-established.
Product-Group=junos
On all SRX series devices using IPsec with NAT Traversal, MTU size might be changed to a lower value for the ike external interface after IPsec SA is re-established.
PR Number Synopsis Category: Security platform jweb support
1606271 On All SRX platforms, if you make a change in JWeb and refresh the page, the changes will not appear in the configuration
Product-Group=junos
On All SRX platforms, if you make a change in JWeb and refresh the page, the changes will not appear in the configuration. Instead, you will get a message that a commit is pending.
PR Number Synopsis Category: Label Distribution Protocol
1529944 The rpd may crash if deactivating the routing-instance with LDP configured
Product-Group=junos
On all Junos platforms with LDP configured in the routing-instance, rpd might crash if deactivating the routing-instance which has IPv4 address routes of LDP.
PR Number Synopsis Category: Multiprotocol Label Switching
1598207 Sometimes MPLS LSP may go down due to a timing issue when a protected link goes down
Product-Group=junos
When a protected link goes down, MPLS gets tunnel local repair message from RSVP and trigger CSPF computation. Next, MPLS gets link protection information through RRO notification. If MPLS receives TED notification first before RRO notification, then CSPF computation fails. Since the link protection flag is not set, MPLS thinks it is an unprotected link and brings down the LSP.
PR Number Synopsis Category: MX104 Software - Chassis Daemon
1604901 Chassisd CPU raise up to 70% when do SNMP walk on jnxOperatingTable on MX104..
Product-Group=junos
When do a snmpwalk on jnxOperatingTable on MX104, the chassisd cpu may go up to 70%. In MX104 device total number of entries fetched during this walk is ~1000 entries. This snmpwalk takes more time to complete the SNMP polling. Due to MX104 available memory & processor we could see chassisd spike during snmpwalk.
PR Number Synopsis Category: Neo Interface
1541382 With hold time configuration, the ge Interfaces remain down on reboot.
Product-Group=junos
With hold time configuration, GE Interfaces from MPC cards which use MIC driver (such as MPC2E/3E NG, MPC Type 1, MPC Type 2) may go down.
PR Number Synopsis Category: Track Mt Rainier RE platform software issues
1604701 Operation like "request system reboot oam" doesn't work on NG-RE
Product-Group=junos
In NG-RE VMHost architecture JUNOS runs as a VM on Linux host. The architecture is fundamentally different from JUNOS running baremetal. Some features in baremetal junos (Eg RE1800) has not been fully qualified in vmhost junos. Thus some functions like "request system snapshot recovery xxx" and "request system reboot oam" doesn't work as desired Please refer to "Installing, Upgrading, Backing Up, and Recovery of VM Host" section in below link for snapshot and recovery procedure. https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/concept/installation_upgrade.html The primary/recommended/qualified method is using "request vmhost snapshot xxx" and "request vmhost reboot xxx".
PR Number Synopsis Category: RPD Next-hop issues including indirect, CNH, and MCNH
1602007 The IPv6 traffic might be impacted on the QFX/PTX platforms when an IPv6 route resolves over a dynamic tunnel
Product-Group=junos
On the QFX/PTX platforms, if an IPv6 route resolves over a dynamic tunnel, and the forwarding route for the dynamic tunnel is a direct interface route, if the interface is not configured with an IPv6 address, then the dynamic tunnel might be in down state.
PR Number Synopsis Category: IPSEC functionality on M/MX/T ser
1557216 Script fails while committing the IPSec authentication configuration as the algorithm statement is missing.
Product-Group=junos
On all Junos platforms except MX Series routers and SRX Series devices with FIPS mode enabled, the manual IPsec functionality might not work because no authentication algorithm is configurable for IPsec.
PR Number Synopsis Category: MX10003/MX204 Platform SW - Chassisd s/w defects
1315577 MX10003 : Despite of having all AC low/high PEM, "Mix of AC PEMs" alarm is raised
Product-Group=junosvae
When there is an input failure on one of the AC PEMs (low or high) its wrongly categorized as "Mix of AC PEMs", so instead of "PEM <> input failure" you will see "Mix of AC PEMs" alarm raised.
PR Number Synopsis Category: Trio pfe l3 forwarding issues
1602357 Unbalanced egress traffic on AE interfaces and ECMP interfaces for AFT based MPC10/11 cards might be seen for the unbalanced unilist routes.
Product-Group=junos
If traffic ingresses an AFT based MPC (MPC10/11) and egresses an AE interface then traffic distribution across the members may be unbalanced And for ECMP traffic too, it may be unbalanced over unbalanced unilist routed members.
PR Number Synopsis Category: Configuration management, ffp, load action
1585479 After image upgrade device might fail to come up due to certain configurations
Product-Group=junos
On all Junos platforms dual-re/chassis cluster scenario the RE/node might fail to come up at the first time reboot after software upgrade if NTP is configured as fully qualified domain name (FQDN) and the following configuration is present. "set system name-resolution no-resolve-on-input"
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1555685 The chassisd core dump might be observed if PIC number 2 or 3 is used on MX204
Product-Group=junos
On MX204, if PIC number 2 or 3 is used for an interface under groups, the chassisd process might crash.
Modification History:
Updated information only 2021-12-14
First publication 2021-07-30
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search