Alert Type

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

Product Affected

ACX PTX QFX running Junos Evolved platforms

Alert Description

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

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

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

Review.

Solution

Junos Software service Release version 24.2R2-S1-EVO is now available.

24.2R2-S1-EVO - List of Fixed issues 

PR NumberSynopsisCategory: N/A:hw-balerion-power
1870153
Major
PTX10k2-36QDD showing incorrect Power Status
Product-Group=evo
Severity=Major
On a PTX10k2-36QDD system, the output of "show chassis environment" may incorrectly shows a disconnected PEM's status as "OK" instead of "Check".
PR NumberSynopsisCategory: "agentd" software daemon
1839478
Major
/junos/system/linecard/interface/traffic/ sensor is seeing packet drops but there is no actual drops
Product-Group=evo
Severity=Major
On all MX devices with ULC line cards (MPC10/11 and LC4800/9600), when subscribing to the /junos/system/linecard/interface/traffic/ native telemetry subscription path, the exported data includes the following containers: /interfaces/interface//interfaces/interface/state//interfaces/interfaces/state/counters. The picd and evo-aftmand-bt daemons are responsible for exporting data for these paths. When running the CLI command "show network-agent statistics detail, " it shows packet and byte statistics for each sensor per daemon. The picd daemon reports some drops due to an error in the CLI's data reporting. However, no actual packet drops occur. The issue arises from a bug in the bookkeeping code that tracks packet statistics, causing the CLI to incorrectly show drops even when no packets have been lost. This issue only affects the CLI display and does not impact actual packet transmission.
PR NumberSynopsisCategory: Border Gateway Protocol
1849568
Minor
L3VPN routes are not advertised to peer when BGP sessions with route-target filter flaps
Product-Group=evo
Severity=Minor
On all Junos and Junos OS Evolved platforms, after Border Gateway Protocol (BGP) sessions configured with 'family route-target' flaps, delayed route deletion causes the loss of the Route Target Filter (RTF), preventing the node from advertising L3VPN (Layer 3 Virtual Private Network) and direct routes (e.g., loopbacks and interface routes) to the BGP peer, leading to VPN route loss and service disruption.
1859020
Minor
Incorrect subcode NOTIFICATION is sent when local interface is disabled for which multihop is configured for directly connected peer
Product-Group=evo
Severity=Minor
On all Junos and Junos OS Evolved platforms, when 'multihop' is configured on a directly connected interface towards a peer and the session goes in IDLE state due to no local interface (interface is disabled or down), the log messages shows 'subcode 6 'Other Configuration Change'' instead of 'subcode 9 'Hard Reset''.
1860786
Major
BGP queue deadlock on Junos/Junos OS Evolved/cRPD platforms leading to route advertisement failure and traffic loss
Product-Group=evo
Severity=Major
On all Junos, Junos OS Evolved, and cRPD platforms, due to deadlock in internal processes, BGP (Border Gateway Protocol) route advertisement fails leading to traffic disruption.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1859044
Major
The IPv6 firewall filter applied on loopback 0 Is not processing NS and NA packets.
Product-Group=evo
Severity=Major
On PTX platforms running the Junos Evolved Operating System (OS), an Internet Protocol Version 6 (IPv6) filter applied to the Loopback 0 interface does not process incoming Neighbor Solicitation (NS) and Neighbor Advertisement (NA) packets in the Neighbor Discovery Protocol (NDP), though it does not impact traffic.
PR NumberSynopsisCategory: QFX Access Control related
1851299
Minor
EX3400 Dot1x Radius accounting send incorrect value to the server for Acct-Input-Gigawords/ Acct-Output-Gigawords
Product-Group=evo
Severity=Minor
With Dot1x Radius Authentication and Accounting, when the Stop Accounting (due to disconnect) is sent to the Radius server the Acct-Input-Gigawords and the Acct-Output-Gigawords contains unexpectedly large value.
1872280
Major
The l2ald process crash is observed on non L2NG Junos platforms configured with "native-vlan-id" and "bridge-domains" on an IFL
Product-Group=evo
Severity=Major
On non L2NG (Layer2 Next Generation) Junos EX, MX and SRX platforms, the l2ald (Layer 2 Address Learning Daemon) process crash is observed when an IFL (Logical Interface) configured with "native-vlan-id" and "bridge-domains" and when certain config change takes place in an IFL which maps VLAN (Virtual Local Area Network) index to NULL. The dereferencing of this NULL pointer causes the crash.
PR NumberSynopsisCategory: Device Configuration Daemon
1848768
Major
MTU configuration is not applied from the configuration group after commit and "warning" is seen
Product-Group=evo
Severity=Major
When configuring MTU on interfaces through a configuration-group and commit the changes, those are not saved on the configuration file.
PR NumberSynopsisCategory: Firewall Filter
1856854
Major
MIB2D will see 100% CPU utilization due to MIB2D walk fail
Product-Group=evo
Severity=Major
On PTX3000/PTX5000/PTX10008/PTX10016/QFX10008/PTX1000/PTX10002/QFX10002 platforms, MIB2D will see 100% CPU utilization due to MIB2D walk failure.
PR NumberSynopsisCategory: CoS support on DNX
1867301
Major
Packet drops are seen due to stale entries in multicast group when HCoS is enabled on ACX7100 platforms
Product-Group=evo
Severity=Major
On ACX7100 platforms with Hierarchical Class of Service (HCoS) enabled and Traffic Control Profile (TCP) configured for bridge-domain interface, packet drop occurs due to stale entries of physical interface in multicast group.
PR NumberSynopsisCategory: Firewall support for DNX
1859053
Major
The firewall filter using "next-ip" as an action is not forwarding the packets on Junos Evolved ACX platforms if the "next-ip" is resolved to a static route that points to itself
Product-Group=evo
Severity=Major
On Junos Evolved ACX Platforms, when a firewall filter applied on an interface has the action set to "next-ip" with next-hop IP address defined which is if resolves in a direct route other than any routing protocol and to trigger ARP (Address Resolution Protocol) if static route is configured for this IP which points to itself, packets are not getting forwarded out causing traffic to impact.
PR NumberSynopsisCategory: 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.
1869793
Major
Packet drops are seen for default route when rpf-check loose mode is configured
Product-Group=evo
Severity=Major
On all Junos Evolved ACX platforms with Reverse Path Forwarding (RPF) loose mode and default route configured, packet drop occurs since default route is not considered for RPF lookups.
PR NumberSynopsisCategory: BGP MPLS VPN specific issues
1865858
Major
The FEC leak will be seen on all ACX EVO platforms
Product-Group=evo
Severity=Major
On all Junos OS Evolved ACX platforms, the hardware FEC (Forwarding Equivalence Class) resource leak will be seen when the programming of the MPLS (Multi-Protocol Label Switching) labels associated with the unilist nexthops fails due to any reason, which will lead to FEC resource exhaustion over time. As a result, further unilist NHIDs (Next-Hop IDs) can't be installed in the PFE (packet Forwarding Engine), resulting in traffic loss.
PR NumberSynopsisCategory: 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 NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1857091
Major
evo-aftmand-bt crash on Junos OS Evolved platforms triggered by rapid interface or route changes
Product-Group=evo
Severity=Major
On Junos OS Evolved platforms, the evo-aftmand-bt process crashes in a rare scenario involving rapid interface changes, such as interface flaps, configuration modifications, or reboots occurring within a short time interval. This crash results in a Packet Forwarding Engine (PFE) restart and traffic loss.
1874151
Critical
Rare assert with an Junos Evolved process
Product-Group=evo
Severity=Critical
This is a rare chance of a process panic. This can be seen in Evo apps. If seen in forwarding apps it can result in system reboot and resulting traffic loss.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1859501
Minor
Interfaces with the same outer VLAN ID but different inner vlans or inner-lists/ranges are reporting a commit error
Product-Group=evo
Severity=Minor
On all Junos OS Evolved platforms, When an interface configured with the same outer VLAN ID but with different inner vlans or inner-lists/ranges, reports a commit error.
1867231
Major
Transit multicast traffic is getting blackhole due to peer interface flap
Product-Group=evo
Severity=Major
On Junos OS Evolved platforms, when peer interface flaps which connected to AE (Aggregated Ethernet) interface leading to synchronization of the interface up events with PFE (Packet Forwarding Engine) gets delayed. This issue results in the transit multicast traffic getting blackhole.
1867603
Major
Coredump during LAG disable
Product-Group=evo
Severity=Major
Pre-conditions are: 1. Aggregate Ethernet interface is configured with/without lacp 2. Aggregate Ethernet interface is configured with BFD configs. Trigger is: 3. With the specified configuration, if any config change is issued on AE IFL then it results in aggd core. 4. One such example is [edit interfaces ae2301 unit 0] + disable; There is no work-around, so none is mentined.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1852152
Major
The l2ald-agent process crashes when the scale of IFBDs within a single VLAN exceeds the capacity of the Rx rtsock buffer, causing an overflow
Product-Group=evo
Severity=Major
On all Junos OS Evolved platforms, scaling of IFBDs (Interface Family Bridge Domain) within a single VLAN(Virtual Local Area Network) will result in the formation of rtsock messages that exceed the Rx size of the rtsock buffer (8192 bytes). This will cause the l2ald-agent (Layer 2 Address Learning Daemon) process to crash. There will be no traffic impact.
1859302
Major
EVPN next-hop installation for ESI over VTEP fails after remote device restart on PTX and QFX platforms.
Product-Group=evo
Severity=Major
On all Junos Evolved PTX and QFX series platforms, running EVPN (Ethernet Virtual Private Network) and ESI LAG (Ethernet Segment Identifier Link Aggregation Group) is causing issues with the next-hop installation after restarting of remote or peer devices, which affects the overall network stability and performance.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
1869773
Critical
Applying a Layer2 filter on interface on results in protocol flaps and traffic disruption on other interfaces on the same PFE
Product-Group=evo
Severity=Critical
Applying a Layer2 filter on and interface on Junos OS Evolved PTX platforms results in protocol flaps and traffic disruption on other interfaces on the same PFE. Please refer TSB96988 [juniper.net] for more details.
PR NumberSynopsisCategory: N/A:sw-evo-re-firewall
1844737
Minor
When using input-list we do not report the policer stats correctly for RE filters. This is done correctly for interface-specific filter for the same.
Product-Group=evo
Severity=Minor
When using input-list we do not report the policer stats correctly for RE filters. This is done correctly for interface-specific filter for the same.
PR NumberSynopsisCategory: AAA, auditd issues
1862203
Minor
Radius authentication is failing when Challenge Token is entered
Product-Group=evo
Severity=Minor
On all Junos and Evo platforms, the Radius Multi-Factor Authentication (MFA) failing for user login if the password and token were provided in two separate steps.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1833660
Major
Stale MAC entries may remain in the MAC table of EVPN routing instances after rapid MAC-IP move scenarios
Product-Group=evo
Severity=Major
On all Junos OS and Junos OS Evolved platforms with EVPN-MPLS (Ethernet Virtual Private Network - Multiprotocol Label Switching) setup , stale MAC entries may remain in the MAC table of the EVPN (Ethernet Virtual Private Network) routing instances during rapid MAC-IP move scenarios. This can cause MAC tables to reach their limits preventing new MAC addresses learning and user registration.
PR NumberSynopsisCategory: Express PFE FW Features
1862048
Major
NPU's (Network Processing Unit) KHT (Kernal Hash Table) utilization shows 100% utilization post config commit
Product-Group=evo
Severity=Major
On Junos Evolved platforms, NPU's KHT utilization shows 100% utilization post config commit
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1842389
Major
Evo-pfemand process crashes on ACX7348/ACX7332/ACX7024/ACX7509 platforms
Product-Group=evo
Severity=Major
On ACX7348/ACX7332/ACX7024/ACX7509 platforms, evo-pfemand process crashes after evo-pfemand application restarts or after a RE(Routing Engine) switchover resulting in impact on forwarding traffic.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1863708
Major
The picd process crashes on Junos OS Evolved ACX7509 platforms during RE switchover
Product-Group=evo
Severity=Major
On Junos OS Evolved ACX7509 platforms with GRES (Graceful Routing Engine Switchover) and NSR (Nonstop Active Routing) enabled, picd process crash is seen with protocol flaps during Route Engine (RE) switchover which results in interface going down and further results in protocols going down.
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1846199
Major
Possible SSD 'read disturbance' due to platform_monitor script accessing the drive every 5 sec
Product-Group=evo
Severity=Major
On an ACX7509 system, the system may access the backup SSD (/dev/sdb) frequently -- reducing the useful life of the SSD.
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1846294
Major
Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
Product-Group=evo
Severity=Major
Memory Leak: Memory leak is detected with rpd task blocks "rpd-trace"
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1864295
Major
L2ald process crash is observed upon executing hidden command "show ethernet-switching debug-statistics fast-mac-update" in case the command doesn't have any output
Product-Group=evo
Severity=Major
On all Junos and Junos OS Evolved platforms, the l2ald process crash is observed upon executing the hidden command "show ethernet-switching debug-statistics fast-mac-update" in case the command doesn't have any output.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1844934
Major
Subscribers unable to connect in GNF setup
Product-Group=evo
Severity=Major
On Junos MX platforms with Node Slicing, i.e., GNF (Guest Network Function), and Subscriber Management services enabled, Subscriber bring-up failure can occur when an upgrade is performed from a non-Agile License infra release to a release running Agile-based Licensing. This issue impacts subscriber services and is encountered due to the enforced Hard Licensing feature for node slicing.
PR NumberSynopsisCategory: Multicast Routing
1863470
Major
The rpd crash due to memory corruption in PIM/MSDP network
Product-Group=evo
Severity=Major
On all Junos and Junos Evolved platforms, enabling PIM (Protocol Independent Multicast) or MSDP (Multicast Source Discovery Protocol) may cause a rare memory corruption during the update of the MSDP Source Active route. This issue primarily affects highly scaled environments, leading to rpd (routing protocol daemon) coredumps and potential traffic loss.
PR NumberSynopsisCategory: KRT Queue issues within RPD
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1858750
Critical
Route change is not synced after rpd restart due to rib-fib inconsistency
Product-Group=evo
Severity=Critical
On all Junos OS Evolved platforms, after rpd (Routing Protocol Daemon) restart, the route change is not sent from routing daemon RIB(Routing Information Base) to forwarding plane FIB (Forwarding Information Base). This results in traffic drop.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
PR NumberSynopsisCategory: ACX7000 interface software related issues.
1869296
Major
100G links do not come up with TX LOS on ACX7100-32C platform
Product-Group=evo
Severity=Major
On ACX7100-32C platform, when the device is rebooted, 100G links do not not come up with TX LOS.
PR NumberSynopsisCategory: Express ZX PFE L3 Features
1867003
Major
IS-IS adjacency between CE devices is not established over L2 circuit
Product-Group=evo
Severity=Major
On Junos OS Evolved PTX10003 platform, In scenario where IS-IS (Intermediate System to Intermediate System) adjacency forming between CE (Customer Edge) devices over Layer2 circuit ("encapsulation vlan-ccc") through PTX10003 as a PE (Provider Edge) in this connectivity, IS-IS hello (IIH) packets from host CE incorrectly direct to connected PE instead of forwarding it to the remote CE over this Layer2 circuit. This is causing failure to establish the IS-IS adjacency between the CE devices. In certain upgrade scenarios where a PE device is upgraded to an affected release, the IS-IS adjacency between the CE devices may fail to establish causing service imapct.

 

24.2R2-S1-EVO - List of Known issues 

PR NumberSynopsisCategory: VXLAN related all L2 PFE PRs on BT based platforms
1855307
Major
The evo-aftmand process crashes on PTX EVO platforms
Product-Group=evo
On all Junos OS Evolved PTX platforms, in EVPN-VxLAN multihoming scenario with "set protocol l2-learning global-evpn-bum-blocking-hold-timer" configured, the evo-aftmand process crashes when the multihomed CE(Customer Edge) interface(s) flaps in quick succession. This will result in traffic loss until the process recovers on its own.

Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: CoS support on DNX
1855256
Minor
ACX7024 is incorrectly writing EXP bits for egress traffic
Product-Group=evo
ACX7024 is incorrectly writing EXP bits for egress traffic

Resolved In:
PR NumberSynopsisCategory: jflow issues on ACX platforms
1858954
Minor
Jflow functionality stops working when configured with sflow
Product-Group=evo
On all ACX Junos Evolved platforms running 24.2R1 and later versions, when both sFlow and JFlow services are configured simultaneously on the device, JFlow stops functioning due to mirror ID allocation conflicts. There won't be any traffic impact; the only problem is that JFlow won't be operational.

Resolved In: evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: DNX platform MPLS FRR features
1881574
Major
Filter configuration with the GRE protocol is not committed
Product-Group=evo
On Junos OS Evolved QFX platforms, when a firewall filter uses as protocol Generic Routing Encapsulation (GRE), the rules will not be installed.

Resolved In: evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: DNX SRv6 PFE
1836457
Major
Traffic is dropped without entering the SRv6 dynamic tunnel
Product-Group=evo
On all ACX platforms all the traffic directed towards a SRv6 (Segment Routing IPv6) dynamic tunnel it's not getting forwarded inside the tunnel and gets dropped.

Resolved In: evo:25.2R1-EVO
PR NumberSynopsisCategory: EVO Netstack icmpd
1822994
Minor
DNS (Domain Name System) resolution fails when nameserver is reachable via a routing instance bound to a line card port on releases prior to 24.1R1-Junos OS Evolved
Product-Group=evo
On Junos OS Evolved based platforms, while using ping, traceroute, or other utility that requires host name resolution, an error is raised indicating hostname resolution has failed.

Resolved In: evo:22.4R3-S7-EVO evo:23.2R2-S4-EVO evo:23.4R2-S5-EVO
PR NumberSynopsisCategory: Issues related to debug utilties - objmon, objshell/Dashboard
1835388
Major
The Netconf output for xml format shows tag under ping failure situation
Product-Group=evo
On all Junos OS Evolved platforms, the Netconf output for xml format shows tag under ping failure situation. It is only an XML display output issue and has no impact to network traffic.

Resolved In: evo:23.2R2-S4-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R2 junos:25.1R1 junos:25.2R1
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1865403
Major
Memory leak is observed when Telemetry is configured
Product-Group=evo
On all Junos and Junos Evolved platforms having Telemetry configured, the memory allocations in 512 bytes slab that are seen to be growing in problem state, are related to write on a unix domain socket (internal to application). Since the data is not read, the send buffer keeps growing and the associated memory does not gets released. Every telemetry response from the producer does a 1 byte write on this socket and over a period of time the send buffer gets full. The default size of the unix socket send buffer is set to 512MB. But there is no functional impact.

Resolved In: evo:22.3X50-EVO evo:22.3X50-J3-EVO evo:22.3X80-D47-EVO evo:22.3X80-D49-EVO evo:23.4R2-S5-EVO evo:24.4R2-EVO evo:24.4X200-D10-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:23.4R2-S5 junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1853879
Major
The IRB VGA is not shown after deleting one of the IRB interfaces with the same VGA address configured
Product-Group=evo
On Junos OS Evolved platforms, when two different IP addresses under an IRB interface are configured with the same virtual-gateway-address (VGA), and one of the IP addresses is deleted, the VGA IP address gets cleaned up in the router/switch resulting in traffic loss in the remaining address entry.

Resolved In: evo:22.2R3-S7-EVO evo:23.2R2-S5-EVO evo:23.4R2-S5-EVO evo:24.4R1-S2-EVO evo:24.4R2-EVO evo:25.1R1-EVO evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1808773
Minor
On ACX7348/ACX7332 all traffic is blocked on FPC after RE Switchover
Product-Group=evo
On ACX7348/ACX7332 with MACsec enabled in channelized interfaces, after performing a double RE switchover (primary RE swap to backup and then back to active), traffic in FPC1 stops in being forwarded.

Resolved In: evo:23.4R2-S5-EVO evo:24.4R1-EVO junos:23.4R2-S5 junos:24.2R2-S1 junos:24.4R1
PR NumberSynopsisCategory: authd (AAA) library code
1860913
Major
The authd process crashes when /etc/resolv.conf file is empty
Product-Group=evo
On Junos OS Evolved ACX platforms, when DHCP (Dynamic Host Control Protocol) local server is configured and the /etc/resolv.conf file is empty with no data/domain information the authd process crash observed. There will be no forwarding traffic impact due this issue and there will be no issue to existing sessions. However, new sessions will have login issue.

Resolved In: evo:23.4R2-S5-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.2R2-S2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: QFX5K EVO Platform Timing related
1829734
Major
QFX5130-48CM: High correction field errors in PTP packets during link flaps
Product-Group=evo
On Junos Evolved TD4 platform (QFX5130-48CM), intermittent link flaps cause the hardware link scan to malfunction, resulting in incorrect high values in the Correction Field (CF) of Precision Time Protocol (PTP) packets, causing improper timestamping. This impacts system time inaccuracies across the network and the overall timing synchronization of the network until remediated.

Resolved In:
PR NumberSynopsisCategory: PTX10K specific platform PRs
1701983
Minor
The snmp mib walk jnxOperatingState on fan tray X returns running(2), although fan tray X speed is set to full-speed
Product-Group=evo
On all Junos Evolved platforms, snmp mib walk jnxOperatingState on Fan Tray X returns running(2), although fan tray X speed is set to full-speed. It is expected runningAtFullSpeed(5) when fan tray speed is set to full-speed.

Resolved In: evo:21.4R3-S3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.3R3 junos:23.1R2 junos:23.2R1 junos:23.3R1

 

Modification History

First publication 2025-06-11