Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Open Issues

For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • G.8273.2 Synce to PTP and SyncE to 1PPS Transient Response test fails. PR1681527

  • Class B performance as per G.8273.2 fails for SyncE to PTP and SyncE to 1pps Noise transfer for lower frequencies. PR1681884

  • Class B performance as per G.8273.2 shall be supported only when FEC is enabled on both the primary and secondary ports of the T-BC(default option). PR1683579

  • With sharding enabled, BGP flags like the following are not displayed on active route in show route extensive output: Accepted Multipath MultipathContrib MultiNexthop per shard view, using show route extensive prefix rib-sharding shard-name will show these flags. PR1693207

  • On all Junos OS Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with system services netconf notification enabled will trigger the l2cpd crash. This crash causes the CPU to spike.PR1695057

  • In high scaled (beyond 14000 s,g routes - 7000 ipv4 and 7000 ipv6 )NGMVPN SPMSI scenarios, core might be seen on PTX10003 platforms due to memory getting exhausted. PR1708454

  • On all Junos OS Evolved platforms, when a client sends a neighbor solicitation, the VRRPv3(Virtual Router Redundancy Protocol) node replies with neighbor advertisement and virtual MAC of the wrong interface. There can be some traffic drop because of incorrect virtual MAC entry. PR1708712

  • We might encounter jdhcpd core during initialization. The core in rare, and there is no service impact because of this core (as the process recovers immediately). PR1730717

  • On all Junos OS Evolved platforms, VMcores are seen when MACsec (Media Access Control Security) key-chains and BGP(Border Gateway Protocol) configurations are applied through Netconf. PR1732611

  • Many issues were observed in Junos OS Evolved library regarding the DNS resolution and these are fixed. PR1733616

  • The PFE applications ppman-aft-bt, packetio-bt and aft-healthmonitor-bt on PTX10002-36QDD​​​​​​​ are now renamed to ppman-aft-bx, packetio-bx and aft-healthmonitor-bx. PR1743457

  • Ubuntu 20.04 has a bug realted to cgroups and docker that causes communication issues in a VRF. Alternative is to ether use Ubuntu 22.04 as the host to launch ncPTX or add the following cgroup params at /etc/default/grub as below, update-grub and reboot when running ncPTX on Ubuntu 22.04. GRUB_CMDLINE_LINUX_DEFAULT="maybe-ubiquity cgroup_no_v1=net_prio,net_cls". PR1744602

  • In PTX Junos OS Evolved devices, power is available from the base power allocated. The power allocation for ABPM is small and the ABPM shares the base power. The power is not allocated explicitly. PR1750747

  • When using a Junos OS Evolved device in FIPS mode, key generation using ssh-keygen might fail with the following error: Saving key "/path/to/key/file" failed: error in libcrypto To mitigate this error, use the -o option in ssh-keygen: For example: ssh-keygen -o other options or arguments. PR1756930

  • On all Junos OS Evolved PTX platforms, RIB (Routing Information Base) and FIB (Forwarding Information Base) tables are not synchronized properly, causing the P2MP (Point-to-Multipoint) LSP (label-switched-path) traffic outage when executing the CLI command clear rsvp session.PR1757635

  • The set chassis ambient-temperature command is not supported in PTX10004, PTX10008, and PTX10016 platforms. It will be removed in future releases. PR1767840

  • EEPROM read failures for PSM are not shown on the PSM LED since the LED of the PSM is internally controlled by the PSM firmware and not by the system software. PR1770991

  • On PTX10004, PTX10008, and PTX10016 Junos OS Evolved platforms, after GRES, the backup Routing Engine BITS left over alarms is still in CM alarms even backup RE BITS does not function. The backup RE BITS alarms should be cleared. PR1777209

  • On all Junos OS Evolved platforms, committed configuration files are not preserved post software version rollback operation. The actual configuration is not affected. PR1779593

  • On PTX10008 Junos OS Evolved, there is no fan name in jnxFruName instead it has only fan tray name and FTC. PR1754833

  • On PTX10008 Junos OS Evolved, the FTC and SIB LED status on fan tray does not match with SNMP MIB information. SNMP information always is marked as 2 for FTC and SIB value. LED on FTC module is off. PR1765184

  • During the programming of the firmware, all Pri/Sec/Led/Comm firmware shows as programming even if any one single firmware gets programmed. However, the firmware upgrade will be done only on the firmware that must be programmed based on the current and available versions. PR1774769

  • 1. To avoid a PSU ending up on "Unsupported" state, when a PSU is inserted into a live system, it must be pushed completely in (a little bit beyond the point when LEDs light up), and the thump screw must be tightened completely for proper operation. 2. If a PSU gets into the unsupported state, it can be slightly pulled out, and re-inserted completely after 30 seconds. This will fix the issue. 3. Alternatively, after all the PSUs are completely inserted into the system with their thumb-screws completely tightened, a chassis-level power cycle will result in detection of all PSUs correctly.PR1784345

Infrastructure

  • On all Junos OS Evolved platforms, Transmission Control Protocol (TCP) packets whose size is larger than its interface Maximum Transmission Unit (MTU) will be dropped impacting TCP connections. PR1718999

MPLS

  • On all Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information. PR1698889

  • On all Junos OS Evolved platforms, a memory leak is observed in the traffic engineering database (TED) when the inet table is not cleaned up after routing instance deactivation. PR1701800

Network Management and Monitoring

  • On all Junos Evolved platforms, a cosmetic change is made to an existing syslog message to print more information. The syslog error message that is logged when a user with wrong auth/privacy password sends a SNMP v3 request to router has been changed to add more information. From: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for <username> To: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for <username> , SNMPv3 query from <NMS-ip> to <Router-IP>PR1734549

    .

Routing Protocols

  • When rib (Routing Information Base) contains IPv4 routes with IPv6 next-hops, these routes do not get re-advertised by IPv4 EBGP sessions unless export policy is configured to change it to IPv4 next-hop. PR1712406