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.3R3-S3-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.3R3-S3-EVO is now available.

21.3R3-S3-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: Border Gateway Protocol
1648471An RPD crash was observed on all Junos platforms
Product-Group=evo		An rpd crash might be observed on all Junos platforms once the RPKI configuration is activated along with BGP SRv6 at the same time.
1659441Routing Process Daemon (rpd) crashes and restarts when a specific timing condition is hit with BGP configuration
Product-Group=evo		On all Junos platforms and all Junos Evolved platforms, Routing Process Daemon (rpd) crashes and restarts when BGP (Border Gateway Protocol) is configured and a specific timing condition is hit for secondary route. This issue might cause a traffic impact.
1665610BGP labeled-unicast inactive routes might not be advertised when add-path is configured
Product-Group=evo		On all Junos and Junos Evolved platforms, by default, inactive routes from inet.3 are advertised in BGP. When add-path is configured, inactive routes from inet.3 are no longer advertised, this behavior is unexpected.
1669615RPD crash might be observed due to multiple sequences of flap events
Product-Group=evo		On all Junos and Junos Evolved platforms, when BGP update-threading is enabled and executed a certain sequence of flap events like flapping ISIS adjacencies, LDP, iBGP peers, clearing ARP table, interface flap for an hour by turning OFF and ON laser which triggers the rpd crash. It is a rare case.
1679646The AGGREGATOR attribute will not be set correctly when the independent-domain is configured
Product-Group=evo		On all Junos and Junos OS Evolved platforms, in BGP(Border Gateway Protocol) deployments with the "independent-domain" and aggregate routes configured under routing-instance, the AGGREGATOR attribute encapsulated within the ATTR_SET will not be populated correctly. This can result in unintended behavior or service impact because the BGP neighbors receiving this update may discard it as it is not RFC complaint.
PR NumberSynopsisCategory: EVO Layer-2 switching for BCM XGS Platforms
1687475QFX EVO: vlan tag of transit IGMP report will be removed when igmp-snooping is enabled.
Product-Group=evo		On QFX series switch running on EVO, vlan tag of transit IGMP report will be removed when igmp-snooping is enabled.
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1661210Traffic drop might be seen due to slow TCP reestablishment after a topology change
Product-Group=evo		On all Junos Evolved platforms, a topology change that affects a Transmission Control Protocol (TCP) connection, the peer might take time to realize the connection is terminated, and TCP reestablishment might be slow. This might affect the TCP related (Ex: LDP/BGP) protocols traffic.
PR NumberSynopsisCategory: Distributor related issues
1658426Routes in RIB and FIB table may go out of sync on all Junos Evolved platforms and causes a traffic impact
Product-Group=evo		On all Junos evolved platforms, routes in RIB (Routing Information Base) and FIB (Forwarding Information Base) are not in sync when it is running over long period of the time (200+ days) with a constant route churn. It causes a traffic impact due to stale entries. (See Also https://kb.juniper.net/TSB69942 [juniper.net]).
PR NumberSynopsisCategory: Zookeeper related issues
1678880RE reboot, rpd crash, etc. can be seen if the volume of zookeeper logs is high on Junos Evolved platforms
Product-Group=evo		Undesirable and impactful behavior such as kernel crash, RE (Routing-Engine) reboot, rpd crash, etc. can be seen if the volume of recorded zookeeper logs is high in the /run/zookeeper/conf/default/version-2 directory.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1649234The kernel crash would be observed in an EVPN multi-homed scenario
Product-Group=evo		On QFX10002/QFX10008/QFX10016 (only QFX10K) platforms, when Assisted Replication (AR) feature as Replicator role is used in an Ethernet VPN (EVPN) multi-homed scenario, there would be out-of-bound memory access issue observed which could result in the kernel crash leading to the service impact.
PR NumberSynopsisCategory: Control plane EVPN multicast
1670435EVPN multicast traffic may get impacted because of routes getting stuck in the kernel routing table (krt) queue
Product-Group=evo		On all Junos and Junos Evolved platforms with Ethernet Virtual Private Network(EVPN) enabled, in the presence of certain triggers like rpd restart, rollback of configuration etc., EVPN multicast routes might get stuck in the kernel routing table (krt) queue due to which the corresponding routes in the forwarding table may point to 'fictitious' next hops, resulting in traffic disruption.
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1663050The rpd core may be seen when there is a synchronization issue
Product-Group=evo		On Junos ACX710 device, the rpd core may be seen. The rpd keeps running and there is no functional impact.
PR NumberSynopsisCategory: Platform infra to support jvision
1686766MPC10E line card will reboot due to the sensord crash
Product-Group=evo		On MX platforms with MPC10E line card, for sensor installed by health-mon causing sensord crash resulting in the MPC10E line card reboot.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1675861Traffic flow will be affected as interfaces will be removed from VLAN
Product-Group=evo		On all Junos and Junos-Evolved platforms, when both vlan name (vlan name having vlan-id-list under "edit vlans" hierarchy) and vlan-id-list having overlapping vlan IDs are added to the interface, traffic will be affected when the vlan name is deleted from the interface.
PR NumberSynopsisCategory: Label Distribution Protocol
1671187LDP Traffic will be blackholed when the L-ISIS/L-OSPF route changes due to interface level configuration
Product-Group=evo		On all Junos and Junos Evolved platforms running Segment Routing (SR), with "set protocols ldp sr-mapping-client" configured, and when interface level configuration changes are done leading to Labeled-ISIS /Labeled-OSPF route change, Labeled Distribution Protocol (LDP) traffic will be blackholed.
1680574In an LDP -> BGP LU stitching scenario, Multiple LSPs will not be installed in the forwarding table, even if BGP Multipath and ECMP are enabled
Product-Group=evo		On all Junos and Junos OS Evolved Platforms, when BGP LU (Labeled Unicast) routes are exported to LDP (Label Distribution Protocol) to perform LDP->BGP-LU stitching, LDP installs only one NH(Next Hop) in the forwarding table instead of multiple NHs, even when BGP Multipath and ECMP are enabled. This issue will be seen for both EBGP (External Border Gateway Protocol) and IBGP (Internal Border Gateway Protocol) multipaths on PTX platforms and for only iBGP multipaths on all other platforms.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1690458On a controller based MPLS setup with container LSPs, rpd daemon crashes after LSP deletion occurs
Product-Group=evo		On all Junos-based platforms, in a scenario where an external controller is provisioned, rpd crashes when an externally controlled container LSP (Label Switched Path) is deleted and the software tries to update its status.
1697982[MX]L2VPN ping is failing when UHP rsvp LSP is used
Product-Group=evo		MPLS L2VPN ping is getting failed when MX is egress. In egress, RE verifies whether received label is VC label or not. For most of the platforms, tunnel label will be removed in PFE before punting the echo request packet to RE. But in this platform, tunnel label is not removed hence RE verifies this tunnel label and it is returning no-mapping.
PR NumberSynopsisCategory: OSPF routing protocol
1700966OSPF stuck in InitStrictBFD state for the neighbor which doesn't send LLS header
Product-Group=evo		When Strict BFD (Bidirectional Forwarding Detection) for OSPF (Open Shortest Path First) configured on all Junos OS and Junos OS Evolved platforms, and one or more OSPF neighbors don't support Link-Local Signaling ("LLS", RFC5613), the adjacency with these neighbor(s) might stuck in InitStrictBFD state upon adjacency initialization. Neighbor doesn't support LLS, hence it doesn't attach the LLS header, which is a pre-requisite for Strict BFD.
PR NumberSynopsisCategory: Path computation client daemon
1678874The rpd process crashes when a delegated LSP with IPv6 install prefix is configured
Product-Group=evo		On all Junos and Junos Evolved platforms, when a LSP (Label Switched Path) is configured with IPv6 install prefix and the management of the LSP is delegated to a PCE (Path Computational Element) controller, rpd process crashes.
PR NumberSynopsisCategory: Resource Reservation Protocol
1661954A LSP might get stuck in the CSPF path computation stage
Product-Group=evo		A label-switched path (LSP) might get stuck in the Constrained Shortest Path First (CSPF) computation and might not finish the session setup. The LSP retry continues to fail when no error feedback is received from downstream routers.
1685182RSVP path tear is not encapsulated by the MPLS header when bypass is configured
Product-Group=evo		On all Junos and Junos Evolved platforms, RSVP(Resource Reservation Protocol) path tear is not encapsulated by the MPLS(Multiprotocol Label Switching ) header, when "no-enhanced-frr-bypass" is configured on the routers that undertake FRR(fast re-route) procedures after the failure.
PR NumberSynopsisCategory: PTX10K RE EVO Issues
1677295Unexpected storage media comsumption caused by system application log
Product-Group=evo		When the system disk usage reaches certain level, the auto log clean up process within the system will remove some application logs as an automated clean up procedure. However, some application logs require a specific way to be removed and the existing clean up procedure might leave those application log grows unbounded.
 
 

21.3R3-S3-EVO - List of Known issues

PR NumberSynopsisCategory: Category for QFX5K EVO Platform Software PRs related to Chas
1616209Unified led scheme for QFX5220/QFX5130
Product-Group=evo		Port LED behavior in QFX5220/QFX5130 is changed to unified led scheme. One caveat is that there is no red led color support and hence for xcvr fault port LED will be OFF and when beacon is enabled in fault state, port LED is Green blinking. There are two caveats in led behavior, 1. When interface is disabled, led is off instead of amber lit. 2. When interface is channelized and partially up, earlier LED was blinking green. Now it was steady amber.

Resolved In: evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1

Modification History

First publication 2022-12-21