Open Issues

For PTX10001-36mr, the software driver reads the voltage threshold erroneously causing the "Host 0 Voltage Threshold Crossed" alarm to present on the device. PR1592258

PTX10008 : EVO CB1, SIB0 and FPC0 (JNP10K-LC1201) went to fault after system power outage in lab.PR1749793

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.PR1822994

On all Junos OS Evolved platforms, host-originated L3 (Layer 3) traffic is marked with DSCP(Differentiated Services Code Point) value 48 [INET 110b] in the IP header, even if class-of-service host-outbound configuration is not present. Host-originated L2 (Layer 2) traffic is marked with IEEE 802.1p value 0 in the header, even if class-of-service host-outbound configuration is not present.PR1837443

When multiple SIBs are offlined in succession, at times it can result in continuous traffic drops.PR1849563

DNS resolution for traceroute does not work for a router using the mgmt_vrf with 23.4R2-EVO. PR1858650

On all Junos OS Evolved based platforms, when the RE (Routing Engine) node experiences switchover, offline/online transitions, or rebooting, a 'Sysman.re' crash file might appear in rare cases and could cause traffic impact. PR1859095

An LSI IFL remains in RPD even after being deleted by the interface manager daemon. It is visible in show interface routing but not in show interfaces, indicating that RPD still holds the IFL despite its removal elsewhere. rpd-agent does not send a delete message to RPD due to a reference count issue. Another daemon?likely l2ald?still holds a reference to the IFL. rpd-agent only sends the delete once all references are cleared, which doesn't happen in this case. The fix is to send a "delete pending" message from rpd-agent to RPD. RPD will treat this as a delete and remove the IFL, ensuring consistency across the system.PR1866522

A PTX10003-160C with high protocols scaling number, its FPC might not restart properly. An example of a high scaling number is a L2VPN gateway with more than 9000 outbound labels.PR1881324

In Junos OS Evolved, ARP resolution requests are throttled on FPC per logical interface level that is if resolution request on a logical interface expires then a throttle timer is started on that logical interface and no other resolution request could be generated on that logical interface when throttle timer is running. In this issue RE netstack is sending packets to FPC with hint to resolution request for already resolved IP address and triggering throttle timer. So resolution request for second IP address on same logical interface could not be generated for some time which is triggering phone-home application 10 seconds time out.PR1883158

The aggregate DDOS statistics for ISIS and BFD might not reflect accurate values due to inherent design limitations.PR1887330

For any given filter term, the maximum term size is limited to 512KB. When the cumulative size of an individual term?including match conditions, match values, and actions?exceeds this limit, the firewallD compiler cannot process the filter, resulting in an error and preventing the filter from being programmed in the PFE. The actual size of each term depends on various combinations of the configured match conditions and values. Therefore, it is not possible to provide a specific size limit that would prevent these issues, as the required size varies significantly based on the particular configuration.PR1906528

On Junos Evolved PTX devices, next-hop churn, such as adding and deleting routes, can lead to the exhaustion of available pfetokens. These tokens are claimed but not released, which causes low pfetoken availability. This issue results in traffic drops and unexpected system behaviour.PR1833330

When cli "set forwarding-options family inet route-accounting" is enabled for v4 stats accounting, the streaming of path /interfaces/interface/subinterfaces/subinterface yield v4 stats as 0: interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv 4/state/counters/in-octets: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv 4/state/counters/in-pkts: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv 4/state/counters/out-octets: 0 interfaces/interface[name=et-4/0/1]/subinterfaces/subinterface[index=0]/ipv 4/state/counters/out-pkts: 0PR1917717

Please use tcp-flags "(!syn&!ack&!fin&!rst&!psh&!urg)" instead tcp-flag 0x0 as part of firewall match condition. PR1892066

On Junos Evolved dual-RE platforms, when a replacement Routing Engine (RMA) or previously used RE is inserted and the new RE already contains local user accounts with the same usernames as users configured on the current primary RE, the SSH files (.ssh/authorized_keys, .ssh/id_rsa, .ssh/id_rsa.pub) are not synchronized or merged. As a result, passwordless SSH login between Routing Engines fails, and commands such as 'request routing-engine login re1' prompt for a password, even though the system login user configuration is identical and fully synchronized on both REs.PR1849300