Alert Type

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

Product Affected

ACX PTX QFX running Junos Evolved Software

Alert Description


Junos Software Service Release version 23.2R1-S2-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 23.2R1-S2-EVO is now available.

23.2R1-S2-EVO - List of Fixed issues 

PR NumberSynopsisCategory: AFT l2lam
1736291Traffic flooding when the hardware MAC table not being synchronized with the software MAC table in the ESI environment
Product-Group=evo		On Junos Evolved QFX5130-32D platform, traffic flooding will be observed due to updates not being performed for the flags in the hardware MAC table resulting in hardware states not being synchronized with software states. This issue is observed when the MAC learned on one ESI (Ethernet Segment Identifier) peer moves to the other peer.
1751135ARP and ND packets are not getting resolved in vlan-based EVPN service on Junos OS Evolved ACX platforms
Product-Group=evo		On Junos OS Evolved ACX platforms configured with EVPN-MPLS (Ethernet VPN-Multiprotocol Label Switching) vlan-based EVPN service or EVPN-VXLAN(Ethernet VPN-Virtual Extensible LAN), device is responding to ARP/ND (Address Resolution Protocol/Neighbor Discovery) without any vlan-id tag. Due to this, the ARP/ND response packet will get dropped in LAN network and the local host will not be able to resolve the ARP.
PR NumberSynopsisCategory: ACX BFD specific issues
1735836The inline IPv4 BFD session is flapping on Junos OS Evolved platforms when hierarchical-scheduler is setup
Product-Group=evo		On all Junos OS Evolved platforms, When inline Bidirectional Forwarding Detection (BFD) mode is enabled and "hierarchical-scheduler" is configured under the interfaces, the IPv4 bfd sessions will begin to flap, and if any dynamic protocols use the BFD, the protocol will also flap as a result, causing traffic outage.
PR NumberSynopsisCategory: Host path software for ACX platform
1736892Traffic congestion on control plane in Junos Evolved ACX platforms
Product-Group=evo		On all Junos Evolved ACX platforms, when hierarchical class of service (HCoS), hierarchical quality of service (HQoS) and BFD or BGP are enabled, control plane traffic is affected.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1747512Traffic loss observed in scenario where default route is received over multiple paths with link protection
Product-Group=evo		On Junos Evolved ACX7K platforms, the default route received over multiple paths with link protection configured on those paths, does not get programmed properly in the PFE (Packet Forwarding Engine) which leads to traffic loss.
PR NumberSynopsisCategory: DNX Multicast
1758659mcsnoopd cored with EVPN-MPLS and VPLS with multicast config
Product-Group=evo		The mcsnoopd application can crash with quick Snooping Routes(scale numbers) ADD, DEL and ADD with IRB Multicast.
PR NumberSynopsisCategory: PRs related to tunnels like GRE, IPIP in EVO control plane
1717782Traffic loss is observed with FTI over IRB as underlay.
Product-Group=evo		In case of FTI (Flexible Tunnel Interface) over IRB (Integrated Routing and Bridging) over ethernet, underlay ifl (logical interface) was pointing to IRB instead of ethernet interface leading to packet loss.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1743913IRB reachability issues may be observed in the EVPN-VXLAN environment when looped ARP comes on ESI-LAG
Product-Group=evo		On Junos and Junos OS Evolved platforms (except MX platforms) with EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) configured, in case of traffic loop conditions, self-generated ARP packets (having physical-IRB MAC as SMAC) may come back to the same node where it originated. Such rare scenarios, when the MAC address of the IRB (Integrated Routing and Bridging) ages out and is cleared from the MAC table, also associated MAC-IP route (IRB route) might get cleaned. This may result in IRB reachability issues as the remote VTEPs (Virtual Tunnel End Point) won't have IRB information of the local VTEP and on the local VTEP, there won't be EVPN database entry and type-2 EVPN advertisements for local IRB towards the remote VTEPs.
PR NumberSynopsisCategory: Express PFE CFM
1763629CFM DMM with AE may not work with ptx10001-36mr
Product-Group=evo		CFM DMM with AE may not work with ptx10001-36mr. For ptx10001-36mr, PPMAN does not have "PFE id to PFE instance" mapping and without valid PFE instance value from ppman, packet-io calculates the next available PFE instance to inject CFM DMM PDU and may inject PDU in PFE which does not have CFM session. This will results into CFM PDU drop in DLU with trap dlu ucode discard.
PR NumberSynopsisCategory: ISIS routing protocol
1738222RPD crashes when multiple ISIS processes are configured
Product-Group=evo		On all Junos and Junos Evolved platforms, RPD crash files are seen during the GRES (graceful restart) event as GRES functionlity is not supported in protocol isis-instance <>.
PR NumberSynopsisCategory: Layer 2 Control Module
1763053LLDP neighborship will not be formed on all Junos devices
Product-Group=evo		On Junos and Junos OS Evolved platforms, LLDP (Link Layer Discovery protocol) neighborship will not come up on local device if the local device is using Junos version lower than 22.3 and remote device is using Junos version 21.4R3-S2 and its subsequent service releases or version higher than 22.3.
PR NumberSynopsisCategory: Protocol Independent Multicast
1720240RPD process crashes on all Junos and Junos OS Evolved platforms after adding static route to the VRF in some scenarios
Product-Group=evo		When static route is added to the VRF (Virtual Routing and Forwarding), and mc-ip (multicast-ip) and the PIM (Protocol Independent Multicast) instance get deleted in some scenarios, the RPD process crash is seen on all Junos and Junos OS Evolved platforms.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1747992The memory consumption increases due to memory leak
Product-Group=evo		On all Junos and Junos OS Evolved platforms, a continuous memory leak is observed due to an allocated socket memory not being freed. This is a minor leak but can lead to significant memory usage on highly scaled setups leading to performance and functional impact including system crash beyond a certain point.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1737119The traffic blackhole will be observed when the SRTE shortcut is configured
Product-Group=evo		On Junos platforms, when the MPLS (Multiprotocol Label Switching) packet reaches the destination router, it will have a label that is unknown to the destination router due to a label POP operation miss at the ingress router resulting in the traffic black hole in the scenario SR-MPLS (Segment Routing With Multiprotocol Label Switching) + traffic engineering shortcut is configured.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1741413The mgd process will crash due to stack overflow on high scale address configuration
Product-Group=evo		On all Junos and Junos OS Evolved platforms with high scaled addresses (360000 global address-book and above) configured over device, mgd (Management Daemon) crash is seen due to stack overflow when whole global address-book configuration is deleted and also while finding the entries of global address-book for a possible completion of CLI command.
 
 

23.2R1-S2-EVO - List of Known issues 

PR NumberSynopsisCategory: Key Management Daemon
1728605Crash file is generated when local certificate keychain is missed repeatedly
Product-Group=evo		On all Junos platforms (M/MX series, ACX series, PTX series, SRX series, T series MX-VC) where kmd is set as control plane daemon which is responsible for IPSec (Internet Protocol Security)related operations, a core file is generated due to continuous failures for a certificate request.

Resolved In: evo:23.2R2-EVO evo:23.3R2-EVO evo:23.4R1-EVO junos:21.2X33-J4 junos:21.2X33-J5 junos:23.2R1-S2 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: QFX L2 PFE
1711860The dcpfe process will crash due to memory fragmentation
Product-Group=evo		On Junos and Junos OS Evolved platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces will flap.

Resolved In: evo:23.4R1-EVO junos:23.4R1
PR NumberSynopsisCategory: KRT Queue issues within RPD
1745509rpd core at #2 0x00007f9b2512742c in __assert_fail_base (fmt=0x7f9b2528bae8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55be37507a48 "nh_idx_t_getval(nhid) == nh_idx_t_getval( rt_nexthops_nhid(rtnh))", file=0x55be375077e8 "../../../../../../../../src/l ayer3/usr.sbin/rpd/lib/krt/ common/krt_ack.c", line=1306, function=) at assert.c:92
Product-Group=evo		RPD core is sometimes seen if there are many unilist nexthop with identical key values but different metric in Evo, esp when ACK is requested for those nexthops

Resolved In: evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R2-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: RPD API infrastructure
1715599Inconsistent RPD core found in rt_walk, task_job_run_job_bg, task_scheduler
Product-Group=evo		rpd may generate core when running slow related gribi toby scripts in fusion system. Running same scripts in manually deployed testbed will not trigger rpd core.

Resolved In:
PR NumberSynopsisCategory: PTX10K specific platform PRs
1720276Application failure would occur on Routing Engine switchover
Product-Group=evo		On Junos OS Evolved platforms, application failure would be observed if it exits without cleaning up the zookeeper contents. This is a rare issue, however can have potential impact depending on the application which fails.

Resolved In: evo:21.4R3-S4-EVO evo:22.2X100-EVO evo:22.3X50-EVO evo:22.3X80-D39-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.3R1
PR NumberSynopsisCategory: Ephemeral Database
1751141Load replace via XML NetConf will not work
Product-Group=evo		On all Junos and Junos OS Evolved platforms, the load replace operation through XML NetConf will fail.

Resolved In: evo:22.3R2-S2-EVO evo:22.3R3-S1-EVO evo:22.3X50-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.3R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:22.2R3-S3 junos:22.3R2-S2 junos:22.3R3-S2 junos:22.4R2-S2 junos:22.4R3 junos:23.2R1-S2 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1740289The 'load replace' operation might result in mustd and mgd crash
Product-Group=evo		On Junos and Junos Evolved platforms with 'apply-group' configured, the mustd and mgd processes might crash when the 'load replace' operation is performed. When this happens, 'apply-groups' will get deleted internally and the respective hierarchies will not be notified.

Resolved In: evo:21.3R3-S5-EVO evo:21.4R3-S4-J5-EVO evo:21.4R3-S5-EVO evo:21.4X1-EVO evo:22.3R2-S2-EVO evo:22.3R3-S1-EVO evo:22.3X50-EVO evo:22.3X80-D39-EVO evo:22.3X80-D40-EVO evo:22.4R3-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:20.3X75-D52 junos:20.4R3-S9 junos:21.2R3-S7 junos:21.2X32-D20 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S4 junos:22.2R3-S3 junos:22.3R2-S2 junos:22.3R3-S1 junos:22.4R2-S2 junos:22.4R3 junos:23.2R1-S1 junos:23.2R1-S2 junos:23.2R2 junos:23.3R1 junos:23.4R1

Modification History

First Publication 2023-11-29