Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved Software

Alert Description

Junos Software Service Release version 21.2R3-S5-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

Solution

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

21.2R3-S5-EVO - List of Fixed issues 

PR NumberSynopsisCategory: EX4300 Layer 2 implementation
1684072The l2cpd process crash may be observed when disabling RSTP on an interface
Product-Group=evo		On all Junos and Junos Evolved platforms, the l2cpd process may crash and generates the core when disabling RSTP (Rapid Spanning Tree Protocol) on an interface.
PR NumberSynopsisCategory: AFT l2lam
1721704Sending GARP reply packet on a VTEP interface causes flooding in network on QFX5130 and QFX5700 platforms
Product-Group=evo		On Junos OS Evolved QFX5130 and QFX5700 platforms, Gratuitous Address Resolution Protocol (GARP) flooding occurs in the network when it receives a GARP reply packet on a Virtual Tunnel End Point (VTEP) interface.
PR NumberSynopsisCategory: Border Gateway Protocol
1695062Traffic blackholing is observed when removing the BGP routes take a long time to get removed from RIB
Product-Group=evo		On Junos platforms, if a BGP (Border Gateway Protocol) peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as other work in the routing process utilize the CPU.
PR NumberSynopsisCategory: ISIS routing protocol
1696598Wrong SRTE Secondary path weight makes the secondary path active in forwarding table
Product-Group=evo		On all Junos and Junos Evolved platforms, SRTE (Segment Routing Traffic Engineering) Secondary LSP (Label Switched Path) should be only on standby in the forwarding table however it is also active and forwarding traffic due to the wrong metric calculation.
PR NumberSynopsisCategory: jdhcpd daemon
1684521DHCP packets sent to the client have the Option 82 Suboption length set to 0
Product-Group=evo		In all Junos platforms, if a DHCP ( Dynamic Host Configuration Protocol) packet containing an Option 82 Circuit ID or Remote ID made up of Null ASCII values (0x00000005) is received, the system incorrectly sets the length of the option to '0' in responses.
1689005DHCP packets might not be sent to the clients when 'forward-only' is reconfigured under the routing instance
Product-Group=evo		On all Junos platforms, reconfiguring 'forward-only' in any routing instance is leading to deactivate of [default:default] jdhcpd filter. Dynamic Host Configuration Protocol (DHCP) packets might not be sent to the clients.
PR NumberSynopsisCategory: Layer 2 VPN related issues
1654516Routes flapping when configuration changes are applied to custom routing instance
Product-Group=evo		Routes flapping when configuration changes are applied to a custom routing instance.
PR NumberSynopsisCategory: Layer 2 Control Module
1717267Traffic loop is seen due to incorrect root bridge ID
Product-Group=evo		On all Junos and Junos Evolved platforms, in VSTP (Virtual Spanning-Tree Protocol) topology, whenever a new vlan is added in between previously configured vlan group followed by configuring the system-identifier, the bridge priority will change for existing vlans which might give incorrect system ID or bridge ID creating a traffic loop.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1716270mac-move-limit : MMAS flag not getting reset after interface recovers due to l2-learning restart
Product-Group=evo		MMAS Flag will not be displayed for interface after it recovers due to l2-learning process restart
PR NumberSynopsisCategory: Label Distribution Protocol
1666506LDP session stuck in non-existent state when router has multiple addresses configured on loopback interface
Product-Group=evo		When statically configured LDP neighbour and sessions transport address exists between two routers that is having multiple loopback addresses may cause LDP stuck in non-existent state. Deactivating and activating the LDP neighbour configuration can cause LDP session to remain stuck in the non-existent state.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1601096Traffic loss from primary to backup path and vice versa
Product-Group=evo		On all Junos and Junos Evolved platforms, Make-Before-Break operation is added for primary path by this PR for the scenario where the LSP secondary path is active and carrying the traffic and the LSP primary path needs to be resignal.
PR NumberSynopsisCategory: MPLS Openconfig part of RPD.
1667844The RSVP interfaces are not streamed when removing the interface configuration
Product-Group=evo		On all Junos and Junos Evolved platforms, when walking through the bandwidth-reservation leaf in RSVP-TE interface attributes sensor path, there was no check to handle the null case and close that particular streaming and move on to the next interface/sensor path when that particular interface is deleted for which the values are being streamed out. Due to this, stale entries for the RSVP interface paths are streamed out if the interface is deleted. This leads to Open Config Telemetry-related issues.
PR NumberSynopsisCategory: Multicast for L3VPNs
1647149The routing protocol process might stop working when de-activating and activating the same provider tunnel from one to another instance in a single commit
Product-Group=evo		On all platforms when de-activating and activating the same provider tunnel from one to another instance in a single commit, the routing protocol process might stop working.
PR NumberSynopsisCategory: OSPF routing protocol
1705975OSPF routes are not getting installed after the interface is flapped
Product-Group=evo		On all Junos and Junos Evolved platforms, the OSPF (Open Shortest Path First) routes are not getting installed when the interface is flapped multiple times. A deadlock is created when the OSPF routers wait for an LSA (Link State Advertisement) with a P2P (Point-to-Point) link to be advertised from its neighbouring router to add it to its router LSA and at the same time the neighbouring router also waits for an LSA with a P2P link to be advertised to add it to its router LSA. Both the OSPF routers advertise their router LSA without a P2P link and as a result, routes are not getting installed.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1683003The policy-multipath route inherits the attributes of active-route but does not undergo resolution, causing an incorrect metric value
Product-Group=evo		When an active path undergoes resolution with policy-multipath configured, policy-multipath routes are generated which inherit the attributes of active-route and do not undergo route resolution.
 
 

21.2R3-S5-EVO - List of Known Issues 

PR NumberSynopsisCategory: Express BT PFE L3 Features
1651473The BFD session might flap in some scaled system with churn
Product-Group=evo		On all Junos and Junos Evolved AFT (Advanced Forwarding Toolkit) platforms, this is infrastructure enhancement which was done to avoid BFD session flapping during the system churn. Without this infra enhancement, BFD session flap would happen in some scaled system with churn.

Resolved In: evo:20.4R3-S5-EVO evo:21.3R3-EVO evo:21.4R1-S2-EVO evo:21.4R2-EVO evo:21.4R3-EVO evo:22.1R2-EVO evo:22.2R1-EVO evo:22.3R1-EVO junos:21.2R3-S4-J3 junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.3R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1699245The mgd process might crash during commit synchronize
Product-Group=evo		On all Junos and Junos Evolved platforms with dual Routing Engines, during commit script synchronize, the backup Routing Engine mgd get process crashes once the memory leak reaches 65K. When this happens, commit configurations from the primary Routing Engine fail.

Resolved In: evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.3X75-D35 junos:20.3X75-D50 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.2X32-D20 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1 junos:23.2R1

Modification History

First publication 2024-04-14