Open Issues

On the MX104 platform, when using snmpbulkget or snmpbulkwalk (for example, used by the SNMP server) on a chassisd-related component (for example, jnxOperatingEntry), chassis process (chassisd) high CPU usage and slow response might be seen because of a hardware limitation, which might also lead to a query timeout on the SNMP client. In addition, the issue might not be seen while using an SNMP query for interface statistics. As a workaround, to avoid the issue, use either of the following approaches: Use snmpget or snmpwalk instead of snmpbulkget or snmpbulkwalk and include the -t 30 option when doing the SNMP query. For example, snmpget -v2c -c XX -t 30. Use the -t 30 option with snmpbulkget or snmpbulkwalk. For example, snmpbulkget -v2c -c XX -t 30. PR1103870

Multiple vulnerabilities have been resolved in MQTT (Message Queuing Telemetry Transport) included with Junos by fixing vulnerabilities found during external security research. Please refer to https://supportportal.juniper.net/JSA71655 for more information.PR1651519

In an interop scenario, when using 1G SFP Optic on PIC-2, auto-negotiation should be disabled on the peer. PR1657766

There will be drop of syslog packets seen for RT_FLOW: RT_FLOW_SESSION_CREATE_USF logs until this is fixed. This will not impact the functionality.PR1678453

When LAG is configured with mixed speed interfaces switching to a secondary interface of different port speed, results in a few packet drops for a very short duration. PTP remains lock and there is no further functional impact. PR1707944

In Netconf private edit configuration session, commit RPC fails when unprotect operation is performed. PR1751574

On all Junos and Junos OS Evolved platforms, when rib-sharding is enabled and RT (Route Target) multipath routes containing both indirect and composite next-hop types are processed, the rpd (Routing Protocol Daemon) process will crash due to incorrect handling during the next-hop copy operation from RIB (Routing Information Base) shards to the main RIB thread. An rpd crash results in all routing protocols going down and causes a brief traffic disruption until the rpd process restarts.PR1757915

PR1735843 has fixed a VM core with the reason "panic: deadlres_td_sleep_q: possible deadlock detected". The same issue might also be seen on all other JUNOS vmhost platforms but with a different root cause. PR1776854

On MX104, the AFEB could crash and reboot following a change of PTP GM clock source, which affects traffic forwarding. PR1782868

On MX platforms with MS-MPC/MS-MIC with IPsec (Internet Protocol Security) configured, IPsec traffic loss will be observed if an SA (Security Association) deletion request is sent by the peer just before the SA installation is completed. The issue happens in the scale scenario (4000 tunnels are configured, and when the SA count reaches up to 3900). PR1825835

It should not be a show-stopper for customer release, as there will be no impact on traffic, problem on displaying extra lanes in SNMP query. PR1844751

On MX10004 and MX10008 platforms with JNP10K-RE3 and LC480 line cards, when the device is set up with G8275.1 PTP( Precision time protocol) profile or SyncE (Synchronous Ethernet ) and GRES, performing a GRES switchover causes DPLL-2 to go from "lock" to "unlock." This can lead to a loss of synchronization which can disrupt timing-sensitive services like PTP and SyncE. PR1848235

On MX platforms with MPC5/MPC7 line cards when there are active pseudo wire subscribers and there is a change in the tunnel-services bandwidth configuration, FPC (Flexible Physical Interface Card Concentrators) crash is observed with the subsequent impact on the traffic.PR1849552.

On SRX and MX platforms a rare occurrence issue causes a sudden reboot of the SPC3 (Services Processing Cards) in use leading to packet loss during the card offline period in the reboot process.PR1857890

Mixed type of anchor PFE on APFE config is not supported. PR1861177

On MX chassis with ULC with asymmetry configured on PTP slave ports, we see small spikes which in the TIE values which are more than the expected range. The TIE values however falls within the expected range after few seconds.PR1867423

When a PTP source switchover event occurs either due to a LC reboot or optics removal on the peer side, we see 1 errored PTP packet on the slave end of a Hamilton LC. The errored packet does not cause any PTP performance issue and PTP quickly phase-aligns with new source.PR1869672

On Juniper MX10003 platforms equipped with MIC1, interfaces using QSFP optics fail to come up or remain down after a connected third-party device is rebooted. This behavior results from a timing mismatch, where the software delays link initialization while waiting for a stable optical signal, potentially missing the brief window when the remote device restarts its transmit signal. This is an interoperability issue and may require manual intervention for service restoration.PR1876314

The commit failure "Change in hierarchical-scheduler mode is not allowed" (given in description) can be seen after multiple iterations of loading test config and overriding with baseline config.PR1849110

Day-1 issue, DHCP subscribers are not going down when PFE is disabled where AE with single leg is present with BFD enabled.PR1837994

In some NAPT44 and NAT64 scenarios, Duplicate SESSION_CLOSE Syslog will be seen. PR1614358

Issue is related to only user defined routing-instance. In this case DUT is connected to two remote-servers through the same Routing-instance. when the route for above connection is deleted and added back from the server side, stale connections are seen. This is because when routes are deleted SYN_SENT are not acknowledged but Application closes the socket. when the routes are again added, application creates new sockets and connects to the remote-server, at the same time Previous SYN_SENT got ack and moved to ESTABLISHED state. this causes stale connections. There is no impact-on functionality, Issue is seen only on Junos platform and for only user-defined RI. Infra code need to be changed to handle socket close error conditions that needs more code churn, time and thorough testing. PR1825311

LDP OSPF are in synchronization state because the IGP interface is down with ldp-synchronization enabled for OSPF. user@host> show ospf interface ae100.0 extensive Interface State Area DR ID BDR ID Nbrs ae100.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 10.0.60.93, Mask: 255.255.255.252, MTU: 9100, Cost: 1050 Adj count: 1 Hello: 10, Dead: 40, ReXmit: 2, Not Stub Auth type: MD5, Active key ID: 1, Start time: 1970 Jan 1 00:00:00 UTC Protection type: None Topology default (ID 0) -> Cost: 1050 LDP sync state: in sync, for: 00:04:03, reason: IGP interface down config holdtime: infinity. As per the current analysis, the IGP interface goes down because although LDP notified OSPF that LDP synchronization was achieved, OSPF is not able to take note of the LDP synchronization notification, because the OSPF neighbor is not up yet. PR1256434

On all Junos and Junos Evolved platforms, the aggregate-bandwidth feature does not function as expected when the device is configured as a BGP (Border Gateway Protocol) Route Reflector (RR). Specifically, in scenarios involving BGP multipath bandwidth aggregation for routes originating from VRF (Virtual Routing and Forwarding) instances under the L3VPN ( Layer 3 Virtual Private Network ) address family. PR1877111

An incorrect remote id received from peer results in AUTH failure and this fails the IKE SA setup. This immature IKE SA doesn't go for proper cleanup hence "Not matured" IKE SA piles UP. Restarting the kmd will clear the Not matured SAs.PR1797377

On all MX platforms with MS-MPC (Multiservices Modular PIC Concentrator), when DPD (Dead Peer Detection) is enabled under IPsec/IKE (Internet Key Exchange) VPN settings and for any reason an IPsec SA (Security Association) is deleted, the kmd process crashes. Due to the kmd process restart some disruption in tunnel establishment is seen.PR1869769