Alert Type
PSN - Product Support Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX, PTX, QFX Running Junos Evolved Software
Alert Description
Junos Software Service Release version 20.4R3-S4-EVO is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 20.4R3-S4-EVO is now available.
20.4R3-S4-EVO - List of Fixed issues
PR Number
Synopsis
Category: Border Gateway Protocol
1645010
Passive BGP session in no-forwarding instance could not come up
Product-Group=evo
When a BGP neighbor is configured in passive mode inside a non-forwarding routing instance, the BGP peer is unable to complete the TCP three-way handshake due to incoming BGP OPEN Message Received into the default primary instance.
1664168
The v4 prefixes might not be advertised over the BGPv6 sessions
Product-Group=evo
On all MX platforms with BGP rib-sharding and update-threading configured, the v4 prefixes might not be advertised over the BGPv6 sessions.
PR Number
Synopsis
Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1653130
The rpd might crash when BMP rib-out monitoring is configured for flow-spec route
Product-Group=evo
On all Junos and Evolved platforms, rpd crash might be seen when BGP monitoring protocol (BMP) rib-out monitoring is configured for the flow-spec route. Since there is no next-hop for flow-spec route core might be seen while generating rib-out feed. Traffic loss might be seen due to this crash.
PR Number
Synopsis
Category: MX Platform SW - FRU Management
1571274
Interfaces might fail to come up on MX240, MX480 and MX960 routers
Product-Group=evo
On MX240, MX480 and MX960 routers, if any I2c issue occurs on the device while rebooting that might cause midplane IDEEPROM read failure, then interfaces might fail to come up. When this issue happens, the error is only logged and no alarm is raised. This might cause unexpected impact.
PR Number
Synopsis
Category: PRs related to Juniper's Ethernet OAM (LFM) implementation.
1643855
Traffic might be impacted due to the RCP session number reaching the maximum limit
Product-Group=evo
If there are communication issues between the primary RE and the backup RE, the RCP process may spawn database sync sessions that exceed 75 sessions on dual RE platforms. This can impact services such as performing a configuration commit may fail.
PR Number
Synopsis
Category: PRs related to software Agentd daemon on EVO
1672783
PDT: TI-S/MOP: Brackla router was not coming up, due to picd, mgd-pfe application failures.
Product-Group=evo
This issue is applicable to PTX10003. Downgrade from 21.4R2-EVO to 20.4R3-EVO fails and few Apps are not started.
PR Number
Synopsis
Category: EVPN Layer-2 Forwarding
1576943
The BUM traffic might be dropped after changing any configuration on the device without router-id configured.
Product-Group=evo
In EVPN-MPLS scenario, if router-id is not configured on the device, BUM (Broadcast, Unknown Unicast, and Multicast) traffic might be dropped after any configuration is changed.
PR Number
Synopsis
Category: Inline Jflow PRs for defect & enhancement requests
1652901
The syslog errors and PPE traps might be observed
Product-Group=evo
On MS-MPC/MPC-3D/MPC1/MPC1E/EX9200-40T/EX9200-40F/SRX5K-SPC-4-15-320/SRX5K-MPC/SRX5K-MPC3-100G10G/SRX5K-MPC3-40G10 linecards, syslog errors and PPE(Packet Forwarding Engine) traps might be observed due to exhaustion of NH partition of memory.
PR Number
Synopsis
Category: ISIS routing protocol
1664152
The rpd crash might be seen on MX platforms
Product-Group=evo
On Junos platforms supporting SRv6 (Segment Routing), the rpd (routing processor daemon) crash may be observed when there is an update in the LSP (Link State PDU) for IS-IS (Intermediate System-Intermediate System). There might be a service impact because of the rpd crash, however, the system will self-recover to a functional state before the next occurrence.
PR Number
Synopsis
Category: l2 forwarding on non atlas platforms
1612738
The process l2ald may crash during routing-instance configuration change
Product-Group=evo
If configuration change in EVPN routing instance may cause existing dynamic mesh group readded to kernel. This cause l2ald core. But this core doesn't affect service and l2ald will return to correct state after core.
PR Number
Synopsis
Category: prs for lacp protocol
1616764
BFD hold-down timer doesn't work properly when LAG is configured
Product-Group=evo
On all devices, if the BFD hold timer is configured, the BFD hold-down timer doesn't work properly.
PR Number
Synopsis
Category: Label Distribution Protocol
1611081
LDP does not support policy import with rib-groups
Product-Group=evo
On all devices, import policy under rib-groups doesn't work for LDP.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1658869
The license might get out of sync between master and backup RE
Product-Group=evo
On all Junos OS Evolved platforms, the license might get out of sync between master and backup RE after the addition/deletion of licenses.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1615326
Standby secondary LSP might be stuck on the same path as primary LSP upon reoptimization
Product-Group=evo
If LSP reoptimization is enabled for the primary and secondary path that is standby, the standby secondary LSP might get stuck on the same path as primary LSP after network change that triggers reoptimization happens.
1664670
Dynamic label space usage crossed the threshold limit of 90 percent
Product-Group=evo
On all Junos and EVO platforms, in warm standby mode, when the MPLS route is learnt on the standby, a label was allocated. As protocols are not running it will not be automatically synced/mirrored. But in case the route is deleted, this was not deallocated back and will result in traffic loss.
PR Number
Synopsis
Category: OSPF routing protocol
1659366
The memory leak and process rpd crash might be observed when the peer interface flaps continuously in the Segment Routing
Product-Group=evo
On all Junos and Junos OS Evolved platforms configured with Segment Routing, when the peer interface flaps continuously, the memory leak might be observed which might lead to the process rpd crash.
PR Number
Synopsis
Category: Routing Information Protocol
1660424
A policy with a policy action "community" configuration may not work
Product-Group=evo
On all Junos and Evolved platforms, when a policy with policy action "community set/add/delete" is configured and the same policy is imported under Routing Information Protocol(RIP) protocol, community configuration may not work.
PR Number
Synopsis
Category: KRT Queue issues within RPD stuck queue, retries due to erro
1583249
The rpd in backup might core and restart
Product-Group=evo
On all Junos and Evolved platforms, the rpd in the backup may core and restart when the forwarding-table is deleted.
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1645296
Traffic drop with EBGP multipath and EBGP paths equal to the maximum-ecmp limit
Product-Group=evo
On all Junos and Junos OS Evolved platforms configured with EBGP multipath and bgp-protect-core under the routing instance, if the number of external paths along with the BGP Prefix-Independent Convergence (PIC) backup paths reaches the maximum ECMP limit, then all the traffic towards the destination is dropped on PFE with the exception of "sw error".
PR Number
Synopsis
Category: Non protocols specific issues in RPD policy options, stateme
1537306
The interface-routes rib-group policy does not work as expected in the VXLAN scenario
Product-Group=evo
On all Junos OS and Junos OS Evolved platforms in the VXLAN scenario, the interface-routes rib-group user-defined policy does not work as expected. This issue will cause all the direct routes to leak from the exported route table to the imported route table.
PR Number
Synopsis
Category: Issues related route resolution routing infrastructure
1658277
Some L3VPN prefixes are not active because nexthop is not usable
Product-Group=evo
If preserve-nexthop-hierarchy knob was deconfigured and if no-propagate-ttl config within VRF is opposite to global config,some routes can be inactive. Secondary nexthops may not be resolved and active, hence L3VPN routes are not active.
1658678
The rpd crash might be triggered when the BGP route resolves over another BGP route
Product-Group=evo
On all Junos and EVO platforms, when the BGP route resolves over another BGP default route such that the default route is an EIBGP load-balanced route, then the resolution loop may go into infinite recursion leading to stack corruption and rpd core.
PR Number
Synopsis
Category: RPD route tables, resolver, routing instances, static routes
1629437
The contributing routes might not be advertised properly if "from aggregate-contributor" is used
Product-Group=evo
On all Junos OS and Junos OS Evolved platforms, if a aggregate route is configured under routing-options, and if "from aggregate-contributor" is used for many contributing routes (e.g. more than 250-300 routes), the policy for these contributing routes might not work properly when the policy is exported. Due to this issue, the contributing routes might not be advertised properly.
PR Number
Synopsis
Category: Resource Reservation Protocol
1638145
LSP over broadcast segment stays down when RSVP setup protection is enabled
Product-Group=evo
When RSVP setup protection is enabled, the LSP over a broadcast segment might stay down, due to a missing function of nexthop check for broadcast segment in code.
1639292
Dynamic bypass LSP might flap at every re-optimization interval
Product-Group=evo
In a RSVP link-protection scenario, when the RSVP interface is configured with static bypass as well as dynamic bypass, if the static bypass is not operational, the dynamic bypass label-switched path (LSP) keeps flapping at every re-optimization interval.
PR Number
Synopsis
Category: Scapa platform specific fabric PRs
1669435
The process fabspoked-pfe crash might be observed while executing CLI commands for fabric statistics
Product-Group=evo
On all Junos OS Evolved platforms, the process fabspoked-pfe crash might be observed while executing CLI commands for fabric statistics. Executing CLI commands specific to the status related to FBC and SIBs will hit this issue.
PR Number
Synopsis
Category: ZT/YT pfe l3 forwarding issues
1635345
Some packets might be dropped inside the l2circuit when the flow label is enabled
Product-Group=evo
On all Junos and EVO platforms, when Flow Label (FL) is enabled, if the egress Provider Edge (PE) is AFT-based FPC then it will receive the packets with Virtual-Circuit(VC) label, flow label, followed by Control Word (CW). If CW is not explicitly disabled then the Mpls-oam Next-Hop (NH) feature on egress PE looks into the CW to determine whether to punt the packet to RE or not. If the first nibble is 0x1 of CW means packets that were expected to be punted to RE which leads to packet drop.
PR Number
Synopsis
Category: Trio Services MPC10/11 interworking with MS-MPC and SPC3
1594380
The next-hop used for lawful intercept might not get installed correctly on PFE of MPC10E/MPC11E line card which does not host the tunnel interface used for flow-tap service
Product-Group=evo
If FlowTapLite is configured on MX Series device with an MPC10E/MPC11E line card and the MPC10E/MPC11E line card does not host the tunnel interface (vt- interface) used for flow-tap service, the next-hop used for lawful intercept might not get installed correctly on Packet Forwarding Engine (PFE) of MPC10E/MPC11E line card when the Law Enforcement Agency (LEA) triggers the dynamic filter generation.
PR Number
Synopsis
Category: Virtual Router Redundancy Protocol
1637735
"show vrrp extensive" doesn't show the next IFL "Interface VRRP PDU statistics"
Product-Group=evo
The "show vrrp extensive" command only shows "Interface VRRP PDU statistics" for the first logical interface. It doesn't show the next logical "Interface VRRP PDU statistics.
1652549
VRRP failover over 2 seconds may be observed
Product-Group=evo
In all Junos and Junos Evolved platforms, VRRP failover over 2 seconds may be observed in case of "fast-interval" configured less than 1 second and "failover-delay" is not configured.
PR Number
Synopsis
Category: Express ZX PFE L3 Features
1665131
PTX10003 load balance v4_dscp and v6_dscp is enabled by default
Product-Group=evo
PTX10003 load balance v4_dscp and v6_dscp is enabled by default. This default behavior may cause traffic loss / out of order / retransmission to some application. To turn it off, please contact JTAC to get PFE commands to disable the hashing as there's no configuration knob to change this behavior. With the fix of this PR: 1. v4_dscp and v4_dp is set default as 0(disabled), config "hash-key family inet layer-4 type-of-service" will enable v4_dscp and v4_dp: set forwarding-options hash-key family inet layer-4 type-of-service 2. v6_dscp and v6_dp is set default as 0(disable), config "hash-key family inet6 layer-3 traffic-class" will enable v6_dscp and v6_dp set forwarding-options hash-key family inet6 layer-3 traffic-class
20.4R3-S4-EVO - List of Known issues
PR Number
Synopsis
Category: Ardbeg platform software related issues.
1597999
PTX10001-36MR: Inconsistency in the platform name used in multiple places, version, snmp mibs, etc.
Product-Group=evo
"show snmp mib walk sysDescr" will show ptx10001-36mr
PR Number
Synopsis
Category: Bowmore specific fabric issues tracking
1672753
PDT: TI-S/MOP: Continous fabspoked-fchip crashes @ zfchip_dev_init, LegacyDriver::init, driver
Product-Group=evo
When we downgrade the Evo version from 21.4R2-S1-EVO to 20.4R2-S3.9 release, the fabspoked is crashing continuously.
PR Number
Synopsis
Category: EVO Netstack FIB Service Daemon
1671024
On Junos Evolved platforms, no connectivity between the default routing instance and other routing instance might happen
Product-Group=evo
On Junos Evolved platforms, if the "import-rib" configuration is used to import routes into the default routing instance from another routing instance, then connectivity may fail between those routing instances.
PR Number
Synopsis
Category: Configd, ffp issues
1672745
PDT: TI-S/MOP: Firewalld cores if filter is deleted before interface binding is deleted.
Product-Group=evo
On 20.4RX release, the DDL must constraints and validation won't take effect if the CDG database is missing on the system. The database file missing is a corner use-case which is not seen commonly. In a situation where the database file is missing, if the firewall filter is deleted prior to deletion of interface filter binding then it leads to firewalld core. Commonly, CDG database file exists on the system and must constraint and validation work as expected. So, in working case the firewall filter deletion will fail if the filter is still binded to an interface. In such a case, firewalld core is totally avoided by validation error during commit.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1672804
The rpd crash might be observed with Container LSPs
Product-Group=evo
On all Junos/EVO platforms, the rpd process might get crash if the Container LSP (Label Switch Path) is associated with an external-controller.
PR Number
Synopsis
Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacpl
1662172
The CPU utilization might increase when a user login and logout to the device continuously
Product-Group=evo
When multiple users log in and log out using SSH public-private key authentication to the device every few seconds, then the CPU utilization might increase on all Junos and Junos OS Evolved platforms.
PR Number
Synopsis
Category: Issues related to mgd, DAX API, DDL/ODL infrastructure, Juno
1627323
Junos Fusion Satellite EX4300 upgrade fails from Aggregate Device MX104
Product-Group=evo
Junos Fusion Satellite Device (SD) EX4300 upgrade fails from Aggregate Device (AD) MX104 with dual-RE.
1641025
Unable to access configure exclusive mode after mgd process is killed
Product-Group=evo
On all Junos OS and Junos OS Evolved devices, when copy-config, get-configuration, and discard-change RPCs run in two parallel NETCONF sessions and the database is also accessed in parallel by two NETCONF sessions, it leads to database corruption and mgd-related services might crash.
PR Number
Synopsis
Category: Issues related to all UI tools (mgd-bsd/cli-bsd, XML and DMI
1630167
Zeroize RPC returns no positive reply
Product-Group=evo
Zeroize RPC returns no positive reply
Modification History
First publication 2022-08-17
20.4R3-S4-EVO: Software Release Notification for JUNOS Software Version 20.4R3-S4-EVO