Alert Type

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

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description


Junos Software Service Release version 22.4R3-S4 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

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 22.4R3-S4 is now available.

22.4R3-S4 - List of Fixed issues 

PR NumberSynopsisCategory: Application Quality of Experience
1805493IPsec VPN is getting flapped due to warning messages on MIST controlled devices
Product-Group=junos
Severity=Major		On all Junos SRX, vSRX and NFX platforms , commit after deprecated configuration of APPQOE (Application Quality of Experience ) is pushed, will trigger DAX warning on the console which causes iked/kmd process to flap of IPsec VPN ( Internet Protocol Security Virtual Private Network ) and results into traffic outage.
PR NumberSynopsisCategory: BBE state synchronization issues
1811787The process bbe-smgd crash will be observed in the Subscriber login/logout scenario
Product-Group=junos
Severity=Critical		On all Junos and Junos OS Evolved platforms, in a scaled stack-based Subscriber Management scenario (e.g PPPOE, DHCP, PS over LT interface, etc.), the bbe-smgd process crash will be observed with continuous login/logout of a large number of subscribers over a period.
PR NumberSynopsisCategory: Border Gateway Protocol
1761627Increase in task memory observed on 'clear validation database'
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when routing-options session validation is configured, and BGP is configured, task memory usage increases in every iteration on executing 'clear validation database' command.
1778879Junos OS and Junos OS Evolved: Receipt of malformed BGP path attributes leads to a memory leak (CVE-2024-39549)
Product-Group=junos
Severity=Critical		A Missing Release of Memory after Effective Lifetime vulnerability in the routing process daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a malformed BGP Path attribute update which allocates memory used to log the bad path attribute. This memory is not properly freed in all circumstances, leading to a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA83011 [juniper.net] for more information.
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1767785The EOR message is missed for one peer in a scaled BMP scenario
Product-Group=junos
Severity=Minor		On all Junos and Junos OS Evolved platforms with BGP Monitoring Protocol (BMP) enabled in scaled scenario (4K BGP peers, 6 BMP stations), after disabling/enabling BMP, due to timing issues, one out of six BMP stations will not receive End-of-RIB (EOR) message for one peer. This will not impact routing or data forwarding, however will have impact on data collection.
1770976Routes getting stuck in hidden state forever in BMP scenario
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms where BMP (BGP Monitoring Protocol) is configured, the routes are not removed from the RIB (Routing Information Base) even when the damping timer expires and they are stuck in the hidden 
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1784438MX304 not reachable with the power-off failure on the PIC
Product-Group=junos
Severity=Major		When an MX304 LMIC is offline due to a power issue, it may take up to 20 minutes for the LMIC to come back online. You can configure event-options to reduce the time to restart the LMIC. See also: TSB83899 [juniper.net]
PR NumberSynopsisCategory: SRX1500 platform software
1813536Reachability issue observed when trying to ping oversize packet via IRB
Product-Group=junos
Severity=Major		Reachability issue observed when trying to ping oversize packet via IRB
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1808353Traffic drop is seen when "monitor traffic interface" command is issued for an interface on Junos SRX platforms
Product-Group=junosvae
Severity=Major		On Junos SRX4100/SRX4200 platform, starting and stopping the "monitor traffic interface", causes the VPN tunnel or tagged traffic to be dropped. However, keeping the "monitor traffic interface" running, ensures that traffic will function properly. Issue occurs when monitor interface command on an interface is performed on devices that has vlan-tagging configured.
1823978High CPU utilisation by the nsd process observed due to DNS common cache and multiple update handlers
Product-Group=junos
Severity=Major		On Junos SRX platforms, due to common cache feature, more accurate IP address resolutions are being updated to the PFE (Packet Forwarding Engine). However, this led to increased CPU utilisation by the nsd (Network Services Daemon) process. Due to high CPU load, the newly resolved IP addresses may not be updated promptly to PFE leading to traffic loss.
PR NumberSynopsisCategory: idp flow creation, deletion, notification, session mgr intfce
1826377Memory leak will be observed on all SRX platforms when IDP is configured
Product-Group=junos
Severity=Critical		On SRX platforms with IDP (Intrusion Detection and Prevention ) enabled, while processing IDP traffic a memory leak can occur which would lead to regular flow processing being affected as memory depletes eventually. This issue affects the following Junos releases: 21.2R3-S8, 21.4R3-S7/8, 22.2R3-S3/4, 22.3R3-S3, 22.4R3-S2/3, 23.2R2, 23.2R2-S1 and 24.2R1. All other releases are not affected by this issue.
PR NumberSynopsisCategory: ISIS routing protocol
1755864RPD crash due to BGP sharding and SRv6
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when Border Gateway Protocol (BGP) rib-sharding is enabled and segment routing v6 is configured, the routing protocol process (rpd) crashes.
PR NumberSynopsisCategory: jdhcpd daemon
1818919jdhcpd core dumps may be seen on ALQ setups when subscriber synchronization is done
Product-Group=junos
Severity=Major		DHCP ALQ (Active Leasequery) Sessions go down due to core dumps in jdhcpd (Juniper DHCP Daemon). These jdhcpd core dumps may be seen on ALQ setups when subscriber synchronization happens after the TCP (Transmission Control Protocol) connection comes up.
1822178JUNOS_REG:EX4650-48Y:ZTPv6:Failed to reconnect to device as unable to load configuration to device via shelscript from ztp server
Product-Group=junos
Severity=Major		During ZTP, if shell script is used (for config download), it will not work on EX46* platforms However, if the baseline config is downloaded via regular way (as config file and not shell script), it will work.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1804965Traffic loss for VPN going down due to inconsistency between the VPN configuration in the iked and the service-redundancy-group database
Product-Group=junos
Severity=Major		On certain SRX platforms using iked (Internet Key Exchange Protocol Daemon) with IPsec (Internet Protocol Security) and MNHA (Multi-Node High Availability) configured, traffic loss can occur when the VPN (Virtual Private Network) service-redundancy-group becomes active and there is an inconsistency between the VPN configuration in the iked and the service-redundancy-group database. This issue arises if the reconciliation process takes over 5 minutes and the VPN service-redundancy-group switches to backup before completing the reconciliation, especially with a high number of VPN tunnels (up to 16, 000) and VPN IKE traceoptions set to the highest level.
PR NumberSynopsisCategory: Layer 2 Circuit issues
1768323JUNOS and JUNOS EVO-RPD process crash under High Availability Route Engine (RE) scenarios when L2circuits are enabled
Product-Group=junos
Severity=Major		Routing Protocol Daemon (RPD) process crash when l2circuits are enabled in scenarios with backup Route Engine (RE).
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1812482Persistent MAC getting stuck in the SRP state results in traffic loss in the EVPN-VxLAN scenario
Product-Group=junos
Severity=Major		On Junos and Junos Evolved platforms, traffic loss is observed when the Persistent MAC gets stuck in the SRP (Static, Remote, Pinned) state and not removed during the "clear persistence mac' operation for some MACs that are getting added with an incorrect flag: SRP. The issue happens when MAC learning happens on Multihoming peers where 'persistent-learning' is enabled in an EVPN-VxLAN (Ethernet VPN-Virtual Extensible LAN) environment. MAC is just marked as Persistent but not installed in the Persistent database.
1816049MAC addresses learnt on interfaces part of VLAN with MAC limiting by interface and "drop-and-log" action configured are cleared after VLAN description is changed
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when "set vlans switch-options interface-mac-limit packet-action drop-and-log" is configured, changing the Virtual Local Area Network (VLAN) description will cause flush of Media Access Control (MAC) addresses learnt on the interfaces part of the VLAN and traffic impact
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1792672License is lost on NG-RE platforms after device/routing-engine reboot
Product-Group=junos
Severity=Major		On NG-RE (Next Generation Routing Engine) platforms, license is lost after restarting device/routing-engine. If any service depends on that license, that service will be impacted.
PR NumberSynopsisCategory: Express Chip L3 software
1815152Premature graceful RE switchover causes traffic blackhole during software upgrade on PTX platforms with dual RE
Product-Group=junos
Severity=Minor		This issue affects PE-based (Provider Edge) PTX platforms running Junos. During a software upgrade involving dual Routing Engine (RE) systems, if Graceful Routing Engine Switchover (GRES) is performed prematurely, it can lead to a traffic blackhole.
PR NumberSynopsisCategory: QFX L2 PFE
1824023Restricted Proxy ARP feature does not work as expected
Product-Group=junos
Severity=Major		On all Junos QFX5K and EX4K platforms supporting restricted 'proxy-arp' feature, when restricted 'proxy-arp' is enabled on IRB (Integrated Routing and Bridging) interface, hosts within the same subnet will not be able to reach each other.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1798684On Junos QFX5K, EX4100, EX4300, EX4400 and EX4650, Type 5 tunnel traffic loss observed when all IRB interfaces are deleted
Product-Group=junos
Severity=Minor		On all Junos QFX5K, EX4100, EX4300, EX4400 and EX4650 platforms with EVPN-VxLAN (Ethernet Virtual Private Network-Virtual Extensible LAN), deleting the all IRB (Integrated Routing and Bridging) interfaces while still having Type 5 tunnels installed results in Type 5 tunnel traffic loss when Type 5 tunnel MAC (Media Access Control ) is same as global/chassis IRB MAC.
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1727528The rpd process can crash during a race condition when BGP rib-sharding is configured
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when BGP RIB sharding is configured, the rpd process crashes during a rare race condition where multiple threads try to initialise a single global variable. During the rpd crash and restart, all routing protocols will be impacted and traffic disruption will be seen due to the loss of routing information.
PR NumberSynopsisCategory: Resource Reservation Protocol
1820893Detour path is not coming up when detour hop-limit is set to 255 or high value
Product-Group=junos
Severity=Major		detour might not form when hop-limit is set to be high value
PR NumberSynopsisCategory: Scuba fabric software
1803832Traffic blackholing observed due to PFE remaining active despite CM_CMERROR_FABRIC_SELFPING errors
Product-Group=junos
Severity=Critical		On MX2008, MX2010, MX2020 and MX10K platforms with MPC1-9 line cards, the PFE (Packet Forwarding Engine) remains active despite CM_CMERROR_FABRIC_SELFPING errors which leads to a traffic blackholing to that PFE.
PR NumberSynopsisCategory: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1827806mspmand crash on clear/show services sessions" parallel in high scale on MX platforms
Product-Group=junos
Severity=Major		On Junos MX with MS-MPC/MS-MIC cards, when clear service sessions are executed from multiple windows (approx 5 terminals), the PIC reboots and eventually all the service traffic will be impacted.
PR NumberSynopsisCategory: Track usability related J-Web PR, like UI layout, workflow
1823264Unable to Define NAT Policy Address Names Containing Dots or Slashes in J-Web
Product-Group=junos
Severity=Major		On all SRX series platforms enabled with J-Web, NAT (Network Address Translation) policies cannot be edited/added using J-Web if the destination address name contains '.' dot or '/' slash.
PR NumberSynopsisCategory: SRX branch platforms
1819054The ~root/.ssh directory contents is deleted on every reboot
Product-Group=junos
Severity=Major		On all SRX platforms the contents of ~root/.ssh directory is deleted on every reboot. This can cause issues with SSH issues as locally stored public and private keys are deleted (stored on ~root/.ssh by default)
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1788669Traffic drop due to mac-validate failure on MX platforms
Product-Group=junos
Severity=Major		On Junos MX platforms, when subscriber management is enabled and mac-validate is configured on interfaces, traffic drop is seen while attempting to add a new link to an existing AE (Aggregate Ethernet) bundle from a different FPC.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1804263Traffic loss is observed along with error messages on Junos MX platforms with MPC1 to MPC9, LC2101, LC480 (including MX204, MX10003) during any transport LSP change operation
Product-Group=junos
Severity=Major		On Junos MX platforms with MPC1 to MPC9, LC2101, LC480 (including MX204, MX10003) having linecards with more than one PFE (Packet Forwarding Engine) instance in FPC (Flexible PIC Concentrators) and "chained-composite-next-hop" knob OR "preserve-nexthop-hierarchy" knob OR SR-MPLS (Segment Routing - Multiprotocol Label Switching ) OR EVPN (Ethernet Virtual Private Network) over MPLS configuration, traffic loss will be seen due to any transport LSP (Label-switched Path) change operation including interface flaps.
1816378XQSS_CMERROR errors will be seen which might disable PFE
Product-Group=junos
Severity=Major		On MX204, MX10003 and MX platforms with MPC7, MPC8, MPC9, LC480, LC2101, LC2103, MPC10 and MPC11 line cards or EX92xx platforms with EX9200-40XS, EX9200-12QS, EX9253-6Q12C, EX9253-6Q12C-M line cards, SRX5400, SRX5600, SRX5800 platforms with SRX5K-IOC4-10G, SRX5K-IOC4-MRAT line cards, in a scenario where there could be fabric drops because of over-subscription or CRC errors, there could be case when the same tail entry get re-used across packets leading to packet corruption and CM error. This is a corner case and might lead to PFE(Packet Forwarding Engine) disable resulting in traffic loss.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1784818Enrollment attempt from non-root user fails with "[Error] Get CA certificates failed"
Product-Group=junos
Severity=Major		When attempting enrollment of a device onto ATP Cloud with non-root user after previously enrolling and disenrolling with root user, the enrollment may fail with "[Error] Get CA certificates failed".
1821845The system scripts refresh will fail when using load CLI option
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms when the 'edit system scripts' hierarchy configuration is changed using loading a configuration from a file or the terminal using 'load' option, the scripts refresh will fail.
1825728The mgd process crashes while using an FQDN in conjunction with the ephemeral configuration database
Product-Group=junos
Severity=Critical		On all Junos and Junos Evolved platforms, the mgd process crashes when device has an ephemeral configuration database instance and an FQDN (Fully Qualified Domain Name) is used for NTP (Network Time Protocol), radius-server, tacplus-server, etc. in either the main static configuration or the ephemeral configuration database.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1822867After RE switchover the VRRP master and backup router will start functioning as master routers
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved MX platforms configured with VRRP (Virtual Router Redundancy Protocol) and NSR (Non-Stop Routing), after RE switchover or GRES (Graceful Routing Engine Switchover) the master router would starts sending VRRP advertisements with a different priority value. As a result, both the master and backup VRRP routers will begin operating as the master which results in inconsistent traffic routing or packet loss as the system fails to establish a single master node.
PR NumberSynopsisCategory: usf ams related issues
1804616NSD validation failure results into upgrade failure for Junos MX platforms
Product-Group=junos
Severity=Major		On Junos MX240, MX480, MX960 platforms, the Network Security Daemon (nsd) validation fails during upgrades.
 
 

22.4R3-S4 - List of Known issues 

PR NumberSynopsisCategory: MPC10/11/LC9600 Chassis Category
1805330Multiple error logs will be seen on all the FPCs
Product-Group=junos		On all Junos and Junos OS Evolved ULC-based platforms, after the software upgrade multiple non-service impacting error logs will be seen on the Flexible PIC Concentrator (FPC).

Resolved In: junos:23.4R1-S2
PR NumberSynopsisCategory: Interface related area
1809220Node0 40G interfaces on Junos SRX5K platforms go down after failover
Product-Group=junos		On Junos SRX5400/5600/5800 platforms in cluster, with 40G interface in layer 2 (L2) transparent mode, when the chassis failovers, the interfaces on node0 will remain in a down state and will not come up.

Resolved In: junos:21.4R3-S8 junos:22.2R3-S5 junos:22.3R3-S4 junos:23.4R2-S1 junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Border Gateway Protocol
1756603RPD process crash is seen on high scale peering scenario where the sessions are un-configured/shutdown abruptly
Product-Group=junos		The RPD process crashes on all Junos and Junos OS Evolved platforms in a highly scaled scenario of more than 2000 BGP peers if the BGP sessions are un-configured/brought down abruptly. This leads to loss of routing information and will lead to loss of protocol traffic.

Resolved In: evo:22.3X50-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.3R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:20.3X75-D52 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1 junos:24.1R1
PR NumberSynopsisCategory: JUNOS kernel/ukernel changes for DNX
1641238ACX5448: Noticing "Host 0 RTC Battery failure" alarm after few hours of power cycling the chassis
Product-Group=junos		False RTC Battery failure alarm reported on ACX5448 Major Host 0 RTC Battery failure.

Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.4R1-S1 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: MX10K LC2101 Timing
1754400Timingd stuck on master RE
Product-Group=junos		On Junos MX platforms, timingd might become stucked on master RE; however, when master RE is switched to backup RE, this issue is not seen.

Resolved In: junos:22.4R3-S3 junos:23.4R1-S1 junos:23.4R2 junos:24.1R1 junos:24.2R1
PR NumberSynopsisCategory: Security platform jweb support
183253222.4R3-S4: JWEB : While creating services, application protocols are not listed under services for destination zone security policy.
Product-Group=junos		22.4R3-S4: JWEB : While creating services, application protocols are not listed under services for destination zone security policy.

Resolved In: junos:22.4R3-S5
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1822911Aggregated ethernet interface flaps can be seen when IRB interface is activated or deactivated
Product-Group=junos		On all Junos and Junos evolved platforms configured with AE (Aggregated Ethernet) interface and esi "auto-derive type-3-system-mac" knob configured, if an IRB (Integrated Routing and Bridging) interface is activated or deactivated the link aggregation interfaces ( IFL) will get flapped due to which interface traffic gets impacted.

Resolved In: junos:22.2R3-S5 junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
1824739The traffic is getting duplicated when VPLS to EVPN transition is performed
Product-Group=junos		On Junos and Junos OS Evolved platforms with MPC10, MPC11, LC9600 and MX304-LMIC line cards, during a transition from VPLS (Virtual Private LAN Services) to EVPN (Ethernet Virtual Private Network) or when the MAC (Media Access Control Address) addresses move from a local to a remote state, control MAC addresses are incorrectly programmed in the hardware, leading to traffic duplication and unresolved destination errors.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1737035BGP sessions flap due to license updates
Product-Group=junos		On all Junos platforms, a BGP flap is observed when a license key is upgraded or a new license is added resulting in traffic loss.

Resolved In: evo:23.3R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:20.3X75-D44 junos:21.4R3-S7 junos:22.2R3-S4 junos:23.2R2 junos:23.3R2 junos:23.4R1 junos:24.1R1 junos:24.2R2
PR NumberSynopsisCategory: QFX PFE Class of Services
1786119QFX5k : The pps rate for egress interface becomes zero after removing one of VCP ports
Product-Group=junos		On QFX5k virtual-chassis platforms working with 5e image, the pps rate display output for the egress interface would become zero after removing one of the VCP ports. The traffic is received as expected and it is only not displayed in the output.

Resolved In: junos:22.2R3-S5 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1810169IPv6 NS packets not forwarded to access port due to VXLAN snoop entry
Product-Group=junos		On Junos QFX5120 platforms, when MLD (Multicast Listener Discovery) snooping is enabled, IPv6 NS (Neighbor Solicitation) packets received on the network port are not forwarded to the access port. This issue is caused by a VXLAN (Virtual Extensible Local-Area Network) configuration that incorrectly redirects these packets back to the network port using an RedirectIPMC action. As a result, IPv6 ND (Neighbor Discovery) fails to complete, leading to IPv6 pings not working on the network port and disrupting IPv6 traffic.

Resolved In: junos:21.4R3-S8 junos:22.2R3-S4 junos:22.4R3-S3 junos:23.4R2 junos:24.2R1 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 ISSU Infrastructure
1703229JDI_REG:: QFX5200:: After ISSU upgrade, device is hanged and not able to perform any operations until USB recovery done on device
Product-Group=junos		When TISSU upgrade is done from 22.4 release onwards, the box come up as backup RE.

Resolved In:
PR NumberSynopsisCategory: SRX RTCOM module bugs
1814271srpfe core during SAV longevity testing
Product-Group=junos		when SAV enabled, there is a corner case when pfe memory is not enough, coredump might happen inside rtcom http proxy module due to a race condition.

Resolved In: junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: SRX branch platforms
1803966The cl interface goes down when the dl interface is disabled for link failover
Product-Group=junos		On the SRX300 series platforms and SRX550 supporting the LTE Mini-Physical Interface Module (Mini-PIM), the cellular interface (cl) goes down when the dialer interface (dl) interface is disabled for link failover.

Resolved In: junos:24.2R2 junos:24.3R1 junos:24.4R1
1811858Monitored-Status keeps Up after CTL link down in branch model SRX HA
Product-Group=junos		After CTL link down, Monitored-Status in "show chassis cluster interfaces" keeps showing "Up" state.

Resolved In: junos:23.2R2-S2 junos:23.4R2-S3 junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on ZT/YT
1810029[MX960] An explanation of the following messages VBFMAN:SEND_CLIENT: PacketL2Inject Failed. error:Invalid argument and VBFMAN:PFE_EVENT_BULKING: Sending of PFE event bulked message to SMGD Failed len:0
Product-Group=junos		Vbfman bulks event notification before sending them to smgd. If buffer is not yet full then it starts a timer, to bulk the events. But an another event comes before timer expires and it fills buffer the it sendout notification in that context itself. As a result when timer expires it doesn't have any more buffer to sendout. These were harmless error messages now it will be logged as debug message.

Resolved In: evo:24.2R2-EVO evo:24.3R1-EVO evo:24.4R1-EVO junos:24.2R2 junos:24.3R1 junos:24.4R1
PR NumberSynopsisCategory: Issues related to NETCONF
1800859Configuration push to device using RPC resulted in incorrect policy order
Product-Group=junos		On all Junos and Junos OS Evolved platforms,  RPC command with default-operation replace uses load update instead of load override from Junos 21.1 onwards. Policies could get incorrectly reordered impacting traffic, because load update does not honor the replace: tag present in configuration file loaded.

Resolved In: evo:24.2R1-S1-EVO evo:24.2R2-EVO evo:24.3R1-EVO junos:21.4R3-S9 junos:24.2R1-S1 junos:24.2R2 junos:24.3R1
PR NumberSynopsisCategory: video monitoring feature
1822738PFE goes to disabled state with multicast multi-threaded traffic with video monitoring configuration
Product-Group=junos		On all Junos MX platforms with MPC2, MPC3, MPC4, MPC5 and MPC6 line cards and video monitoring configuration enabled, the Packet Forwarding Engine(PFE) goes in to disabled state when multicast traffic with more than 10 downstream interfaces. This leads to traffic loss.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO junos:22.2R3-S5 junos:24.2R2 junos:24.4R1
PR NumberSynopsisCategory: VSRX platform software
1819545vSRX 3.0 with Junos release below 24.2R1 on KVM not booting up correctly in recent Linux Distributions
Product-Group=junos		Starting in QEMU 8.1, SMBIOSv3 is enabled by default with a 64-bit entrypoint. Junos OS versions below 24.2R1 only support 32-bit SMBIOS entrypoints, so they will fail to boot on systems using KVM alongside QEMU versions at or above 8.1.

Resolved In:

Modification History

First publication 2024-09-12