Article Detail

Alert Type

SRN - Software Release Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX PTX QFX Series running Junos Evolved software

Alert Description

Junos Software Service Release version 23.4R2-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

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

Solution

Junos Software service Release version 23.4R2-S4-EVO is now available.

See TSB95591 [juniper.net] for the list of Known Issues

23.4R2-S4-EVO - List of Fixed issues

PR Number	Synopsis	Category: "agentd" software daemon
1815195 Minor	The collector will see duplicate entries during the init sync of gNMI subscription on Junos and Junos Evolved platforms Product-Group=evo Severity=Minor	On all Junos and Junos Evolved platforms, 23.2/23.4 release onwards, when gNMI is subscribed for the sensors, duplicate entries are seen. There is no traffic/service impact of the issue.
PR Number	Synopsis	Category: MX YT-ZF Linecards Interface Software Category
1846164 Major	Continuous logging of alarms during a fiber cut with transport devices Product-Group=evo Severity=Major	In a scenario where a fiber link has transport devices to amplify the signal, excessive logging of alarms for an interface can occur. The transport devices will amplify the incoming signal, which isn't valid when the fiber has been cut. This causes the router to receive a good signal and Rx power but it contains no valid data. In response, the interface on the router will attempt to link up repeatedly and after failing multiple retries, which is set per platform, the router will attempt to reinitialize the data path. This causes multiple alarms from the optic to get set and then cleared resulting in alarm logs in the system logs. This can become excessive if the link remains down for an extended period of time. To avoid continuous logging to the system log, after a number of retries the logs will be suppressed. The interface will continue to attempt to link up including reinitializing the the data path, but without the logging. This will allow the interface to link up when the physical link is repaired, and at that point the logs will stop being suppressed
PR Number	Synopsis	Category: EVO interface software
1838394 Major	"bt_mtip_chpcs_hw_clear_stats: failed" error will be seen post rebooting the device Product-Group=evo Severity=Major	On PTX10001-36MR platform, after rebooting the device, "bt_mtip_chpcs_hw_clear_stats: failed" error will be seen. There is no functional impact due to these errors.
PR Number	Synopsis	Category: the replication daemon (repd) for Shared Memory-base
1797189 Major	We may observe repd core (in the "from" release) during ISSU. There are no functional impact due to this repd core Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, repd core observed (in the "from" release) during ISSU.
PR Number	Synopsis	Category: Border Gateway Protocol
1793714 Major	BGP routes may not get advertised when always-wait-for-krt-drain is configured with BGP sharding Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, when 'delay-route-advertisements always-wait-for-krt-drain' is configured, the EoR (End of Record) from the source peer of the routes is not received in the BGP (Border Gateway Protocol) peer which is sent by a BGP speaker to indicate the end of a record or a sequence of updates. This is due to the BGP router advertiser being stuck in the wait-for-inbound-convergence state, which may cause the KRT (Kernel Routing Table) queue to get stuck, thereby halting the advertisement of BGP routes.
1826685 Major	Unexpected behaviour after BGP sessions reset for catastrophic BGP configuration changes Product-Group=evo Severity=Major	On Junos and Junos Evolved platforms, when a catastrophic Border Gateway Protocol (BGP) configuration change occurs, creating a new peer structure due to this configuration change, the BGP state transitions from open-sent to established multiple times (until the local device finishes cleaning the old BGP session). This results in traffic impact as the peer is reset multiple times (until a new peer connection is established).
1839318 Major	BGP import policy does not process the next-hop statement Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, setting next-hop (NH) doesn't work with BGP (Border Gateway Protocol) import policy, if the policy is also modifying community. Due to this, the traffic will not be forwarded to the intended NH.
1841090 Major	The rpd process will crash when secondary route in VRF is auto-exported Product-Group=evo Severity=Major	On all Junos and Junos Evolved platform, the rpd process will crash when an IPv6 (Internet Protocol Version 6) BGP (Border Gateway Protocol) - Labeled route is leaked using rib-groups to VRF (Virtual Routing and Forwarding) table and auto exported to IPv6 VPN(Virtual Private Network) table.
1845169 Major	BGP stops advertising VPN routes to EBGP peer if static route-target-filter as local is configured Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, for MPLS L3 VPN's (Multi Protocol Label Switching L3 Virtual Private Network) if static route-target-filter as local is configured, BGP (Border Gateway Protocol) stops advertising VPN routes to EBGP (External BGP) peer.
PR Number	Synopsis	Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1807892 Major	A route stuck in	A route can get stuck in
1839288 Major	BMP soft assert due to counter reset by clear command Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, when "clear bgp statistics" command is issued while one or more BMP peers are coming up the soft_assert will be hit. This issue has no impact on the traffic or services.
PR Number	Synopsis	Category: PTX10004 platform defects tracking
1782498 Major	[Junos OS Evolved] PTX10004/8/16 - !Minor alarm LED on FPM(Front Panel Module) is glowing Yellow, although there is no active alarms/errors on the system Product-Group=evo Severity=Major	On PTX10004/8/16 EVO platforms, !Minor alarm LED on FPM(Front Panel Module) is glowing Yellow, although there is no active alarms/errors shown by "show system alarms" CLI.
PR Number	Synopsis	Category: Used to track Firewall Filter related PRs in EVO for BCM XGS
1843819 Minor	Flooding is observed when OSPF and VRRP protocol multicast packets are received on STP blocked port Product-Group=evo Severity=Minor	On Junos Evolved platforms of QFX5k (QFX5220, QFX5130, QFX5700, QFX5230, QFX5240), multicast protocol packets received on STP (Spanning-tree-protocol) blocked ports results in flooding.
PR Number	Synopsis	Category: EVO Layer-2 switching for BCM XGS Platforms
1818577 Major	Traffic drop seen after updating firewall filter Product-Group=evo Severity=Major	On QFX platform based on Junos EVO , committing a configuration change that leads to a firewall filter update (i.e. adding or modifying terms), if firewall filter is applied to a loopback interface, packets punted to CPU will be dropped while filter is updated.
PR Number	Synopsis	Category: EVO L3 routing for BCM XGS Platforms
1828017 Minor	The pfemand crash will be observed when "clear bgp neighbor all" command is executed Product-Group=evo Severity=Minor	On all Junos and Evolved platforms, in a scaled setup when the "clear bgp neighbor all" command is executed or "restart l2-learning immediately" is executed, the pfemand crash will be seen which leads to the restarting of the Flexible Packet Forwarding Card (FPC).
1836461 Critical	Evo-fpemand process crashes on committing sflow configuration Product-Group=evo Severity=Critical	On Junos Evolved QFX5K platforms, the evo-pfemand process crashes when there are multiple routes to sflow collector and configuration changes like sflow configuration delete/add happens.
PR Number	Synopsis	Category: EVO VXLAN PFE for BCM XGS Platforms
1849807 Major	VXLAN packets with inner VLAN tag are dropped in transit device Product-Group=evo Severity=Major	On Junos OS Evolved QFX5130, QFX5230 and QFX5240 platforms in EVPN-VXLAN (Ethernet Virtual Private Network with Virtual Extensible Local Area Network) scenarios, when the device is acting as a transit device, VXLAN encapsulated packets with inner VLAN (Virtual Local Area Network) tag are dropped by the inner tag drop filter.
PR Number	Synopsis	Category: PFE L2 forwarding features on BT based platforms
1836051 Critical	BUM traffic to remote leaf vtep in an evpn-vxlan fabric is dropped on all PTX evolved platforms Product-Group=evo Severity=Critical	On all Junos OS Evolved PTX platforms, BUM (broadcast, unknown unicast and multicast) packets destined to remote VTEP (Virtual Tunnel Endpoint) of leaf in an Ethernet VPN Virtual Extensible LAN (EVPN-VxLAN) fabric is dropped when the remote VTEP has an IP address with all 0's in the last octet.
1849188 Major	Traffic loss observed over load-balanced ESI LAG towards Provide Edge router in an EVPN-MPLS path on Junos OS Evolved PTX Series platforms Product-Group=evo Severity=Major	On all Junos OS Evolved PTX platforms, traffic loss occurs in an MPLS-EVPN (Multiprotocol Label Switching-Ethernet Virtual Private Network) environment when load-balanced traffic over ESI-LAG (Ethernet Switch Identifier-Link Aggregation Group) between CE (Customer Edge) and PE (Provider Edge) experiences path changes. When the number of active MPLS load-balance paths between a single-homed PE (Provider Edge) and multi-homed PEs changes between two and three paths, traffic disruption occurs. The issue appears when MPLS paths are either increased from two to three or decreased from three to two in the network connecting these PEs. This issue causes significant traffic disruption, affecting Layer 3 gateway traffic flow over the ESI-LAG between CE and PE devices in the EVPN-MPLS network.
PR Number	Synopsis	Category: Express BT PFE L3 Features
1811245 Major	BGP session on PTX platforms may flap when inline BFD is configured with low BFD timer Product-Group=evo Severity=Major	On Junos OS Evolved PTX platform, the Border Gateway Protocol (BGP) session flap can be seen when inline Bidirectional Forwarding Detection (BFD) is configured under routing instance without loopback interface (lo0) leading to partial traffic drop. The issue is only seen when the interface is within the routing-instance.
1840295 Major	Multihop BFD remains down when it's associated with a static route in the routing instance Product-Group=evo Severity=Major	On Junos Evolved, specifically in PTX platforms (PTX10001/2/3/8/16), the next-hop interface related to the static route is down, and the ARP (Address Resolution Protocol) is deleted. Even if the interface recovers, BFD (Bidirectional Forwarding Detection) will not recover.
1841145 Major	The evo-aftmand-bt/evo-aftmand-bx crash observed with SCU/DCU feature on IPv6 Prefixes Product-Group=evo Severity=Major	On Junos Evolved PTX10001-36MR, PTX10004, PTX10008, PTX10016, PTX10002-36QDD platforms, the evo-aftmand-bt/evo-aftmand-bx process may crash at high scale when source-class-usage (SCU) /destination-class-usage (DCU) features are configured on IPv6 prefixes (25 to 88 bits) due to hardware lookup entry updates from 20 to 40 bytes for additional action information.
1856732 Major	Post configuration changes on an AE interface MPLS traffic is discarded for other interfaces/AE interface on a different FPC Product-Group=evo Severity=Major	On Junos Evolved PTX10008, PTX10016, PTX10004 platforms having JNP10K-LC1201/LC1202 and multiple FPCs (Flexible PIC (Physical Interface Cards) Concentrators), it is observed that when any of the following configuration changes are performed on a given AE (Aggregate Ethernet) interface, this may cause MPLS (Multiprotocol Label Switching) traffic to be dropped on other interfaces or AE interfaces hosted on other FPCs having the same PIC and port number as the intended AE interface members where no such configuration change is made.* When family MPLS is removed from an AE interface, or* When an AE interface with family MPLS configured is deactivated, or* When the IFD (Interface Device) MTU (Maximum Transmission Unit) is modified on the AE interface that has family MPLS configured, or* When "vlan-tagging" is added or removed on an AE interface that has family MPLS configured, or* When "encapsulation" is added or removed on an AE interface that has family MPLS configured PTX10003, PTX10001-36, PTX10002-36QDD are not exposed.MPLS Traffic drops are recorded as 'normal discard' under "show pfe statistics traffic"
PR Number	Synopsis	Category: MX304 Chassis specific platform
1802195 Major	The optics temperature sensor name renamed from 'et-x/y/z' to 'xcvr-x/y/z' Product-Group=evo Severity=Major	On Junos Evolved platforms and MX platforms with LC9600, MPC11 or MX304, the mapping optics temperature sensor name with ifd name is not correct. This PR is for correcting the behaviour and does not have any service impact.
PR Number	Synopsis	Category: MX304 line card platform software
1849915 Major	FPC reboot due to memory leak from telemetry sensor installation/uninstallation Product-Group=evo Severity=Major	On Junos MX204, MX304, MX2010, MX2020, MX10004, MX10008, MX10016 with MPC11, LC2301/LC9600, LMIC16 and LC480 line cards, when installing and uninstalling specific telemetry sensors that export data from LC (Line Card), a few bytes of memory are allocated but not freed, leading to a memory leak. This issue is seen when "sensor-based-stats" is configured and LSP (Link State Path) flaps occur. Each flap triggers repeated installation and uninstallation of the telemetry sensor, accelerating memory consumption. Over time, this exhausts the memory allocated to aft-ulcd process causing FPC (Flexible PIC Concentrator) to reboot.
PR Number	Synopsis	Category: Class of Service
1836528 Minor	FC id goes out of sync between the RE and PFE impacting all CoS features using FC id Product-Group=evo Severity=Minor	On all Junos and Junos Evolved Platform, forwarding-class (FC) identifier (id) goes out of sync between the Routing Engine (RE) and Packet Forwarding Engine (PFE) when software upgrade is performed. When In Service Software Upgrade (ISSU) is performed, FC id goes out of sync between the RE and PFE impacting all class-of-service (CoS) features using FC id. When manual software upgrade is performed (without using ISSU) , this issue will be seen as a cosmetic display issue where the order in which the FC configurations are displayed will differ.
PR Number	Synopsis	Category: DNX L2 related features
1845015 Major	Traffic will be flooded for a prolonged time when mac-table-size is reduced Product-Group=evo Severity=Major	On Junos Evolved ACX platforms, when "mac-table-size" is reduced(to make the size less than the usable MAC), traffic will be flooded for a prolonged time(around 5 mins). Based on remote MAC installation behavior traffic will be impacted.
PR Number	Synopsis	Category: Layer 3 forwarding, both v4+v6
1848599 Major	Default route installation fails on Junos OS Evolved ACX Series platforms Product-Group=evo Severity=Major	On all Junos OS Evolved ACX Series platforms, default route installation fails when repeated default route relearning happens which could be due to reasons like LSP (Label Switched Path) flaps, interface flaps etc. The packets destined for unknown destination are dropped causing outage.
PR Number	Synopsis	Category: sflow issues on ACX platforms
1836394 Major	On ACX EVO devices inline-sampling for sflow does not work with default route advertised via BGP. Product-Group=evo Severity=Major	If Inline-sampling for sflow is used with default route advertised via BGP in ACX device running Junos Evo, then the ingress sampling does not work. There will be issues in monitoring as there will be no datagrams captured.
PR Number	Synopsis	Category: ACX VxLAN Issue
1854255 Major	The evo-pfemand process crashes on ACX platforms without specific trigger Product-Group=evo Severity=Major	On all Junos Evolved ACX platforms, evo-pfemand process crash is seen in a rare scenario when target next-hop is received with type Reject.
PR Number	Synopsis	Category: EVO Class of Services
1850590 Major	High CPU Utilization on RE caused by cosd process after software upgrade Product-Group=evo Severity=Major	On Junos OS Evolved platform, where CoS (Class of Service) configuration is present and software upgrade is performed, high CPU utilization on RE (Routing Engine) (in case of dual RE, observed on master/active RE) is caused by the cosd process, this happens when any action resulting in modification of physical interfaces at the same commit window occurs. This does not impact the forwarding traffic but system utilization is impacted.
PR Number	Synopsis	Category: Issues related to EVO Health Monitoring System
1843884 Major	On rare occasions under load conditions after a switchover, the ehmd process on the standby RE may crash Product-Group=evo Severity=Major	On rare occasions under load conditions, ehmd process in the backup RE (Routing Engine) will crash after a switchover on all Junos OS Evolved platforms. The ehmd process will restart automatically and there will be no impact to proper functioning of the system. There is no workaround to this issue.
PR Number	Synopsis	Category: EVO Netstack FIB Service Daemon
1860358 Major	File Descriptor leak in fibd process leads to core files of different processes such as Jade, SSHd and Stunnel. Product-Group=evo Severity=Major	On Junos OS Evolved platforms, when fibd reaches the process limit on the maximum number of allowed open file descriptors, fibd is unable to open new file descriptors and track new reader processes. Given this, processes such as Jade, SSHd and Stunnel are not found by fibd, triggering the core files for these processes affecting device management and Tx/Rx packet process. The Soft Limit value within the "cat /proc//limits" output command will show the maximum number of file descriptors that fibd can have opened.
PR Number	Synopsis	Category: Distributor related issues
1836997 Major	The rpdagent process is getting restarted after switchover Product-Group=evo Severity=Major	On Junos OS Evolved platforms, a rare race condition can cause a previously added state on master before switchover to arrive late on the new master and after switchover rpdagent restarts which results into traffic loss.
PR Number	Synopsis	Category: software upgrade infra issues
1812515 Major	Boot up issue is seen during a software upgrade in ACX7100-32C/ACX7100-48L platforms running Junos Evolved Product-Group=evo Severity=Major	On ACX7100-32C/ACX7100-48L platforms with Innodisk Solid-State Drive (SSD), during a software upgrade, the system won't handle the partition change post-reboot, and the system will not boot properly.
PR Number	Synopsis	Category: System Management daemon and related issues
1808788 Major	sysapp-mib.re core generated for EVO devices. Product-Group=evo Severity=Major	On all JUNOS-EVO platforms, a sys-app mib core might be generated when running program with large parameters.
PR Number	Synopsis	Category: Issues related to debug utilties - objmon, objshell/Dashboard
1838074 Major	Serial Console Stops Working After Cable Reconnection Product-Group=evo Severity=Major	On Junos OS Evolved platforms, the serial console may stop functioning, displaying a blank output, after one or more physical disconnections and reconnections of the console cable. The use of intermediate cable adapters or unreliable cables can exacerbate this issue.
PR Number	Synopsis	Category: jdhcpd daemon refactored for evo
1816246 Major	[ACX7000 Series] DHCPv4/v6 packets may be dropped because DHCP packets are not routed to kernel after initial jdhcpd starts Product-Group=evo Severity=Major	Under certain conditions, the DHCP session database becomes unstable or JDHCPD not getting IFL/IFD events which cause DHCP packets to fail to route to the kernel and then leads to DHCP packet drop.
PR Number	Synopsis	Category: EVO Services Jflow PRs for defect & enhancement requests
1828032 Major	The flow record outputs are not displayed correctly on Junos Evolved platforms Product-Group=evo Severity=Major	The Jflow record output are not displayed correctly, if the unknown prefix/route hits this sampling interface on Junos Evolved platforms configured with a Default route and Sampling. It has no traffic impact.
PR Number	Synopsis	Category: EVO L2 Control Plane PRs
1828741 Major	In high-scale, high-load environments, the l2ald process may experience hangs during Apstra polling. Product-Group=evo Severity=Major	On all Apstra polled Junos Evolved devices experiencing heavy load. Specifically, when L2ald and l2ald-agent were engaged in high-volume data exchange over the management socket, L2ald becomes unresponsive.
1844623 Major	Stale MAC-IP entries are not cleared in an EVPN-VXLAN scenario when encapsulate-inner-vlan or decapsulate-accept-inner-vlan or both knobs are present Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, when decapsulate-accept-inner-vlan or encapsulate-inner-vlan or both knobs are configured for a VXLAN (Virtual Extensible Local Area Network) and when any action corresponding to MAC-IP entries cleanup takes place, the MAC-IP entries will not be cleaned up from kernel. This will result in anomalies in device and could also lead to a core crash.
1853868 Major	Router flag is not getting set in Neighbor Advertisement message Product-Group=evo Severity=Major	When EVPN (Ethernet Virtual Private Network) routing instance has IRB (Integrated Routing and Bridging) interface with IPv6 (Internet Protocol version 6) address, ICMPv6 NA (Neighbour advertisement) reply from IRB IPv6 address doesn't have router flag. The ICMPv6 NA from IRB IPv6 should have router flag.
PR Number	Synopsis	Category: EVO MACSEC Platform Independent Implementation
1853676 Major	MACSec statistics will not show up in the "show interfaces statistics detail" command output Product-Group=evo Severity=Major	On PTX10008/PTX10016, PTX10001-36MR, PTX-10002-36QDD platforms with MACsec configured, the 'MACSec statistics' will not be displayed int the "show interfaces statistics detail" Junos CLI command output. This will not have any functional impact.
PR Number	Synopsis	Category: Issues related to NTP issues on evo
1761546 Major	NTP association with source address and routing instance configuration is failing. Product-Group=evo Severity=Major	NTP association with source address and routing instance configuration is failing.
PR Number	Synopsis	Category: Express PFE MPLS for EVO platforms
1847169 Major	Traffic going over LDP or LDPoRSVP route matching the CBF is getting impacted when PTX EVO platform working as PHP router with CBF configuration Product-Group=evo Severity=Major	Traffic hitting Penultimate Hop Popping router and matching the class based forwarding (CBF) is affected when Junos OS Evolved PTX platform acting as PHP router with CBF configuration. This will impact traffic going over affected LDP or LDPoRSVP route. Also, it will cause ping and trace route failure.
1861803 Major	Control plane is not properly managing the label 1048575 for MPLS traffic, leading to service impact Product-Group=evo Severity=Major	On PTX Evolved platforms, the control plane is incorrectly using label 1048575 for MPLS (Multiprotocol Label Switching) traffic, this label is being changed to the NULL label 3, as if it corresponds to a non-MPLS packet, resulting in the label being popped, leading to all traffic associated to these MPLS threads to be dropped.
PR Number	Synopsis	Category: event/op/commit scripts, SLAX, netconf issues
1836806 Major	Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP). Product-Group=evo Severity=Major	Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
1840657 Major	jnpr.junos.facts module returns null value for the dictionary key such as hostname/junos_info Product-Group=evo Severity=Major	In Junos EVO platforms with systems running on X based version, jnpr.junos.facts returns null value for the Hostname and Junos Info in remote authenticated users through Radius(AAA).
PR Number	Synopsis	Category: eventd, syslog infra issues
1815238 Major	PTX10004 - Host-name is not updated in picd logs Product-Group=evo Severity=Major	On Junos OS Evolved platforms, host-name was not appended to PICD logs.
PR Number	Synopsis	Category: EVPN control plane issues
1796532 Major	EVPN mac-ip entry flag "Duplicate-Not-Best" not updated after deleting duplicated IRB IP in EVPN_VXLAN MAC-VRF Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, duplicate mac-ip detection for IRB IP is not working since the IP move is not triggered after adding an IP address to the IRB interface.
PR Number	Synopsis	Category: Issues related to EX MACsec
1830395 Major	Commit error on using more than 31 characters authentication-key-chain-name Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, when authentication-key-chain-name is configured with more than 31 characters, commit error is seen due to which MACSEC will not work with the configuration.
PR Number	Synopsis	Category: Express PFE FW Features
1830706 Major	FPC crash will occur when modifying or deleting a filter instance on Junos platforms Product-Group=evo Severity=Major	On all Junos platforms, when a filter instance is modified or deleted, there should not be any old Packet Forwarding Engine (PFE) instances. However, during these operations, old PFE instances are being incorrectly assigned, resulting in incorrect memory address allocation. This leads to an Flexible PIC Concentrator (FPC) crash after committing the configuration, causing traffic loss.
PR Number	Synopsis	Category: Interface Information Display
1631200 Major	The packets for IPv6 'Local statistics'(host-inbound/outbound) are counted against the 'IPv6 transit statistics' in IFL. Product-Group=evo Severity=Major	IFL counter has a counter named "IPv6 transit statistics". It can be confirmed on "show interfaces extensive" command output. However, this counter is originally for IPv6 total statistics(transit + local) and the counter name was wrong from the first. On older releases like 19.1R1, as the support for IPv6 local stats was not available the local stats was always zero. So, the meaning of the counter name was the same to the counting content coincidentally. In latest releases support for IPv6 local stats has been added but the counter name was not changed. As the local stats will not be zero the difference between the meaning of the counter name and the counting content started being visible.
PR Number	Synopsis	Category: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1826194 Major	The rpd crash is observed during upgrade or restart Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, rpd crash is observed during upgrade or restart since kernel takes more time to update ifstate information.
1843627 Critical	Memory Leak observed in - "RTI Await LSI Cookie" when routing instance is added and deleted Product-Group=evo Severity=Critical	"RTI Await LSI Cookie" when routing instance is added and deleted.
PR Number	Synopsis	Category: MX Inline Jflow
1813925 Major	FPC reboots after sensor configuration is removed and readded over a long period on MX and EX9200-15C platforms Product-Group=evo Severity=Major	On all MX platforms with MPC10/MPC11/LC9600, MX304 and EX9200-15C platforms, when any sensor configuration on protocols, for example, MPLS LSP, is configured and removed over a long period, the aftd-trio process starts a memory leak and eventually causes FPC to reboot.
PR Number	Synopsis	Category: Kernel software for AE/AS/Container
1840734 Major	RLT ifl remains down after RLT unit interface configuration is modified Product-Group=evo Severity=Major	On all Junos platforms which support PS over RLT, after modifying or deleting and re-adding a logical interface on RLT interface, the logical interface remains down and the following log messages is seen in the messages log:DCD_CONFIG_WRITE_FAILED: IFL rlt0.0 configuration write failed for an IFL ADD: File exists after configuration change.
PR Number	Synopsis	Category: ISIS routing protocol
1837289 Major	The 'overload advertise-high-metrics' does not work after the graceful restart for ISIS Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms configured with "protocols isis overload advertise-high-metrics" (without timeout) and graceful-restart, IS-IS (Intermediate System to Intermediate System) will start advertising high link metrics immediately as expected. However, when IS-IS is in graceful restart mode either via GRES (Graceful Routing Engine Switchover) switchover or restart routing, the high link metrics are not advertised and IS-IS continues to advertise the usual link metrics even when IS-IS graceful restart is completed. When the issue is hit, the node configured as an overload might be used for transit traffic based on the IGP metric.
1841108 Major	Traffic drop is seen after GRES on ISIS peer Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, in an ISIS(Intermediate System-Intermediate System) graceful restart scenario, helper node sends and programs its locally configured hold-time (180 secs) instead of the "Restart-duration" received as hold-time from DUT (210 secs), due to this incorrect update, the hold timer expires at the helper node before the GR (Graceful Restart) is complete on DUT and it causes a flap of ISIS adjacency on peer/helper Node.
PR Number	Synopsis	Category: jdhcpd daemon
1714260 Major	The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established.
PR Number	Synopsis	Category: jpppd daemon
1854387 Major	The jpppd process will crash with frequent subscribers login/logout Product-Group=evo Severity=Major	On Junos and Junos OS Evolved platforms, the jpppd (Juniper PPP daemon) process crash will be seen after a certain time of subscribers login/logout. The issue could be seen with the applications that write their private data in /mfs/var/sdb/shmem/sdb_intf.ad.db.
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1820882 Major	Traffic drop is seen in an EVPN multihoming scenario when mac-pinning is enabled Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, in Ethernet VPN (EVPN) multihoming scenario with mac-pinning enabled, traffic drop will be seen when the Designated Forwarder role (DF) is changed.
PR Number	Synopsis	Category: Label Distribution Protocol
1817712 Major	MPLS LDP sessions are not established when container-lsp is configured with an already existing lsp-template Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms Label Distribution Protocol (LDP) sessions are not formed due to the configuration of "container-lsp" with an already existing configured lsp-template which has "ldp-tunneling" knob enabled.
PR Number	Synopsis	Category: Issues related to Junos licensing infrastructure
1808956 Major	The syslog "LICENSE_EXPIRED" are not seen when license gets expired" Product-Group=evo Severity=Major
1823449 Major	Licensing usage is not set post reboot until there is an empty commit is done Product-Group=evo Severity=Major	On all Junos OS Evolved platforms, when a reboot is performed, the license usage is not set for features like OSPF, BGP etc. Feature usage is not set again unless the commit is done.
1845079 Major	Unnecessary trace log files related to licenses are generated Product-Group=evo Severity=Major	On Junos platforms agile-licensing infra, when upgrading to 23.4R1 and above, unnecessary trace log files related to licenses are generated. This issue has no impact on traffic.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1854987 Minor	The "in-place-lsp-bandwidth-update" functionality does not work as expected Product-Group=evo Severity=Minor	On all Junos and Junos Evolved platforms with normalization or auto-bandwidth configured for container Label Switched Paths (LSP) members, "in-place-lsp-bandwidth-update" configuration does not work as expected and Make-before-break (MBB) is triggered.
1857867 Major	Traffic loss will be observed when container-LSP with in-place-lsp-bandwidth-update configured Product-Group=evo Severity=Major	On Junos OS and Junos OS Evolved platforms having container-LSP (Label Switched Path) with in-place-lsp-bandwidth-update configured, traffic loss is observed on the transit device when the old instance is deleted on the local device, which is being used even though the new instance was present after MBB (Make-Before-Break) occurred. The issue happens if the in-place-bandwidth-update fails and the old instance's route reference is not cleared due to its active weight, preventing the proper reallocation of traffic to the new instance.
PR Number	Synopsis	Category: Multicast Routing
1845087 Major	MVPN traffic does not recover after clearing forwarding-cache Product-Group=evo Severity=Major	On all Junos Evolved platforms with Multicast Virtual Private Network (MVPN) configured, MVPN traffic does not recover after clearing forwarding-cache using "clear multicast forwarding-cache instance all" command.
PR Number	Synopsis	Category: Packet Based Link Qualification Analysis (PBLQ) on EVO platforms
1844523 Major	Process evo-aftmand-bt crashes on PTX10K evo platforms when command request chassis fpc slot <> pfe-instance <> restart" is executed Product-Group=evo Severity=Major	On PTX10K Evo platforms, when command "request chassis fpc slot <> pfe-instance <> restart" is executed, a crash over the process evo-aftmand-bt is observed and a daemon core file is generated.
PR Number	Synopsis	Category: Issues related to PKI daemon
1839090 Major	Traffic loss due to tunnel establishment failure in HA setup Product-Group=evo Severity=Major	On Junos platforms, during PKI (Public Key Infrastructure) certificate renewal in an HA (High Availability) setup, if the PKI daemon on the secondary node is busy, mismatched certificates will occur. If a failover happens, the mismatched certificates are used for IKE (Internet Key Exchange) tunnel establishment, causing tunnel failure and resulting in traffic loss.
PR Number	Synopsis	Category: Category for QFX5K EVO Platform Software PRs related to Inte
1827725 Major	QFX5130-48C/CM, SFP+ ports are not detected with pilot EVO image. Product-Group=evo Severity=Major	On QFX5130-48C/CM, with certain hardware revisions (P1 prototypes or earlier), SFP+ ports might not be detected due to detection logic relying on hardware revision values. This impacts specific hardware configurations, and the issue was identified in certain EVO image releases.
1862907 Major	QFX5K EVO: ZTP Fail WAN Port , interface does not come up Product-Group=evo Severity=Major	QFX5K EVO: ZTP Fail WAN Port, the interface does not come up.
PR Number	Synopsis	Category: Category for QFX5K EVO Platform Software PRs related to Chas
1757471 Major	[ACX7100 QFX5130 QFX5220] PSM Input Under Voltage Failure is displayed in 'show chassis hardware' but PSM status is OK Product-Group=evo Severity=Major	A "Major" alarm is generated when the input voltage is low. However, the alarm is not cleared when input voltage comes back within the acceptable range and the ower supplies continue to function without any issue.
PR Number	Synopsis	Category: RPD infrastructure issues related to NSR, GRES, switchover,
1848313 Major	OSPF neighbours go down due to link flapping after NSR switchover on Junos OS Evolved platforms with IPSEC configuration Product-Group=evo Severity=Major	OSPF neighborship goes down after NSR (Nonstop routing) switchover due to link flapping on Junos OS Evolved platforms with Dual RE and IPSEC configuration.
PR Number	Synopsis	Category: RPD Interfaces related issues
1850620 Major	When BGP RIB Sharding is enabled, new BGP group/peer added gets stuck at Flags: Product-Group=evo Severity=Major	On Junos OS and Junos Evolved platforms, when BGP RIB Sharding is enabled, new BGP group/peer added gets stuck at Flags: . Route is established but freezes by sending 0 size window and the peer stops sending routes then, after some time the remote side tears the session down.
PR Number	Synopsis	Category: KRT Queue issues within RPD
1801382 Minor	Memory Leak in the rpd Process During Protocol Deactivation/Activation Product-Group=evo Severity=Minor	On all Junos and Junos Evolved platforms, A memory leak occurs during protocol, routing instance, or interface deactivation/activation, linked to improper IPv6 Interface Address (IFA) reference handling in the " ifx_dist_msg " process. This can lead to rpd crashes and service disruptions.
1817807 Major	Routes for secure tunnel interface interface not installed on forwarding-table on SRX platforms Product-Group=evo Severity=Major	On all SRX platforms, after the In-Band Cluster (ICU) upgrade if the system has routes pointing to the secure tunnel interface (st0) interface, or on clearing security IPsec sa on peer router a few routes might have trouble getting installed in forwarding, impacting traffic on the routes that are not installed after the upgrade.
1831421 Critical	Multiple flaps on BGP routes causing traffic blackholing Product-Group=evo Severity=Critical	On all Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) route with PNH1 (Preserve Nexthop Hierarchy) may not be resolved correctly during rapid route fluctuations (e.g., link flaps). Specifically, when the preferred route (Rt1) experiences rapid deletions and re-additions, the system might incorrectly associate the PNH with an outdated route (Rt2).
PR Number	Synopsis	Category: RPD Next-hop issues including indirect, CNH, and MCNH
1838354 Major	Subscriber's session created using the dynamic profile leads to rpd crash Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, rpd (Routing Protocol Daemon) process crashes and crash file is generated. This is usually seen when the subscriber's session is created using the dynamic profile where the dynamic demux interface is configured under 'protocol igmp' (Internet Group Management Protocol) knob.
1858750 Critical	JDI-RCT:EVO:PTX10002-36QDD - app-controller incomplete for EVO APPs seen Product-Group=evo Severity=Critical	Route change is not being sent from routing daemon RIB to forwarding plane FIB in some scenarios after RPD restart. This leads to data out of sync between RIB and FIB causing this problem.
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1771344 Major	Leaked routes via BGP rib-group remains in hidden state even though "loops" is configured with any value greater than one Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms having BGP (Border Gateway protocol) configured, when route is leaked via rib-group from one routing instance to another having the same AS (Autonomous System) number and one of the routing-instances has BGP configured with local-as, it is observed that even after configuring "loops" with any value greater than one as the number of loops option, the route still remains hidden instead of being active which results in traffic drop.
1812124 Major	The rpd process crash is observed when the label received exceeds the configured maximum-labels 16 Product-Group=evo Severity=Major	On Junos and Junos Evolved platforms, the rpd process crash is observed on both REs (Routing Engines) and RE switchover was triggered when maximum-labels under MPLS(Multi Protocol Label System) address family is configured as 16 and an extra label is received.
1839631 Major	Configuration check-out fails when applying "inet6.0 static route" with qualified-next-hop and interface settings Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, commit check for overlapping prefixes will fail to commit when inet6 static route is configured with qualified next-hop and Integrated Routing and Bridging (irb) interface.
1842654 Major	RPD process crash observed with dynamic tunnel configuration with overlap in destination networks under APP based and NHB mode and rollback Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms the rpd (Routing Protocol Daemon) process will crash when dynamic tunnels are configured with overlap in destination networks under APP (Application-based tunnels) based and NHB (Next Hop Based) mode and rollback after some time.
1849202 Major	BGP route still seen in routing table when route not available Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms , the router learns routes through the BGP (Border Gateway Protocol) and has the feature: "BGP RIB Sharding" enabled for IPv4. These routes are stored in the Inet.0 routing table. Later, if the neighbor that announced this route or the protocols associated with the routing table of the used VRF (Virtual Routing and Forwarding) are removed, the route remains in the routing table, and hence traffic is forwarded to the stale routes.
PR Number	Synopsis	Category: show route table commands, tracing, and syslog facilities
1808481 Minor	The error message "sysctl kern.corefile not supported" is seen for multiple daemons during daemon initialisation Product-Group=evo Severity=Minor	On all Junos Evolved platforms, while executing "show log messages", error message "sysctl kern.corefile not supported" is seen which is introduced during daemon initialisation.
PR Number	Synopsis	Category: Resource Reservation Protocol
1819948 Major	LSP re-optimization issue has been observed Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, the LSP (Label Switched Path) re-optimization issue has been observed. LSP bandwidth change is unsuccessful due to bandwidth unavailable RSVP (Resource Reservation Protocol) PathErr.
1820893 Major	The detour path is not coming up when the detour hop limit is set to 255 Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms configured with MPLS/RSVP (Multiprotocol Label Switching/Resource Reservation Protocol), the detour path might not form when the "fast-reroute hop-limit" is set to 255. Thus, traffic loss will be observed when a node or link in an LSP fails, as the detour will not happen.
1823215 Major	Bypass re-optimisation not taking SRLG or fate-sharing into account when protected link is down Product-Group=evo Severity=Major	On all MX and PTX platforms, In RSVP-TE (Resource Reservation Protocol-Traffic Engineering) scenario, when interface protected by bypass LSP (Label Switched Path) goes down, re-optimization of bypass can leads to unexpected path selection due to non consideration of SRLG (Shared Risk Link Group) or fate-sharing information with respect to protected interface during CSPF (Constrained Shortest Path First) path computation, could result in traffic impact due to this unexpected path selection.
1840543 Major	The rpd crash is observed when "expand-loose-hop" knob is configured and rpd is undergoing graceful restart Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, when RSVP (Resource Reservation Protocol) LSP (Label Switched Path) is configured to perform loose hop expansion by enabling "expand-loose-hop" under MPLS (Multi-Protocol Label Switching) LSP knob and "graceful-restart" is configured in routing-options, rpd crash can be seen if it is undergoing graceful restart, causing service impact.
1850130 Major	RSVP authentication check fails if the length of the authentication-key is sixteen characters Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, if the length of the authentication-key is 16 (the maximum allowed is 16 characters), RSVP authentication check fails. Authentication check succeeds if the length of the authentication-key is less than 16.
PR Number	Synopsis	Category: ZT/YT pfe infra issues
1796344 Major	PacketIO PFE process will drop small fragments of TCP and UDP packets destined to the routing engine Product-Group=evo Severity=Major	On platforms running PacketIO PFE process (MPC10E, MPC11E, MX10K-LC9600, MX304 and all Junos OS Evolved platforms), small fragments of TCP and UDP packets destined to the routing engine will be dropped.
PR Number	Synopsis	Category: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1843935 Major	On SRX300 series DHCP relay stops working and generates coredump after upgrading to JunOS 23.4R2-S2.1 Product-Group=evo Severity=Major	On SRX300 series devices, when TACACS accounting is configured, after an upgrade to Junos 23.4R2-S2.1, the DHCP-relay may not work anymore and the shm-rtsdbd process may produce coredumps.
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1702344 Minor	Apply-path special handling for wildcard after a leaf attribute Product-Group=evo Severity=Minor	On EVO platform, if the apply-path config has a wild-card <*> character after an attribute node then, the wild-card character is not processed. Due to which, the apply-path config is not expanded into matching prefixes by ui-infra. Please refer workaround section on how to avoid the issue.
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1799215 Major	The commit fails error can be seen when configuration is modified after commit prepare Product-Group=evo Severity=Major	On all Junos and Junos Evolved platforms, when the user attempts to issue the commit command after modifying the configuration post 'commit prepare', the commit discards the prepared commit cache as it is no longer valid and throws " commit fails" error and proceeds with the regular commit process from scratch.
1842518 Major	The device become unresponsive in a race condition due to maximum process (maxproc) limit Product-Group=evo Severity=Major	On all Junos/Junos OS Evolved platforms, the device becomes unresponsive due to management (mgd) processes being stuck in a deadlock. This leads to the piling up of mgd processes, which eventually exhausts the maximum process limit (maxproc) on the device. The impact is that the device will become unusable due to the maxproc limit being reached.
1847834 Major	Multiple daemons crash upon ephemeral commit Product-Group=evo Severity=Major	On all Junos platforms with ephemeral db support, multiple daemons crash upon ephemeral commit Eg. chassisd, dcd, l2ald, l2cpd, mib2d and transportd causing service traffic impact. The services will self recover after the issue is hit in the network.
PR Number	Synopsis	Category: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1843602 Major	TCP session between syslog server and device remains in closed state Product-Group=evo Severity=Major	On all Junos platforms, a TCP (Transmission Control Protocol) connection issue occurs between the device and syslog server after an idle period exceeding 2 hours. The session gets terminated and remains in a closed state without initiating any new session until the syslog server configuration is deleted and added again. This impacts disruption in log forwarding to the remote syslog server.
1848106 Major	The eventd process crash occurs due to flooding of out of memory logs Product-Group=evo Severity=Major	On all Junos and Junos OS Evolved platforms, eventd process crashes is observed. This happens when eventd process is processing the flooding of out of memory logs generated by any of the processes running on FPC (Flexible PIC Concentrator). This is traffic impacting depending on the process with memory issues.
PR Number	Synopsis	Category: Issues related to NETCONF
1852868 Major	commit confirmed rpc request displays closing tag without opening tag in private mode Product-Group=evo Severity=Major	Fixed xml format in rpc output
PR Number	Synopsis	Category: MX10K linecard
1809644 Major	FPC crash due to race condition on MX platforms with LC480 Product-Group=evo Severity=Major	On MX platforms with LC480, a crash file is generated because of this issue which results in entire ukern reboot. The issue happens due to race conditions. The ukern automatically reboots and the FPC (Flexible PIC Concentrator) comes up online. Traffic loss is observed till the FPC restarts after the ukern crash.
PR Number	Synopsis	Category: Track Windriver Linux issues
1807939 Minor	[MX] daemon.err rshd[618008]: Second port outside reserved range. Product-Group=evo Severity=Minor	RE uses enhanced mode RCMD protocol to communicate with the FPCs, by default. However, the FPC line cards do not understand the enhanced mode rcmd protocol. Hence the below logs generated. daemon.err rshd[618008]: Second port outside reserved range. After the failure, the communication falls back to the normal mode from enhanced mode.There is no production impact due to this issue. The fix has been implemented in the resolved versions, wherein the communication between RE and the FPC will now happen through the normal mode by default.