Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Open Issues

Learn about open issues in Junos OS Evolved Release 21.4R3 for ACX Series routers.

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


  • On enabling EVPN VXLAN in a Junos OS Evolved system, a default route in primary instance pointing to management interface might result in anomalies in Junos OS Evolved database. PR1622035

  • On performing GRES on ACX7509 platform with EVPN services, some logical interfaces are missing. Physical interfaces come up post reboot.PR1646722

General Routing

  • ACX7509: Some of the interfaces from 16x100G and 20XSFP56 do not go down after evo-pfemand restarts. PR1592388

  • The picd might generate a core file if an FPC is switched off and restarted with a scale configuration, a route, or a MAC entry. Picd comes up automatically and user intervention is not required. PR1602352

  • The command show system processes extensive shows high short term CPU utilization. Values can range from 50 percent or higher for evo-pfemand. This is a single CPU view. As the ACX7509 system is a multi-core CPU, this has no impact on performance. PR1603899

  • Interfaces map to the same Ethernet PHY flap when you modify any one of the interfaces speed. For example, when you remove speed (10g) on port 5 and then apply the same speed on the 20xsfp56 card, the interface 0-7 flaps. There can be a combination of speed as initial configuration. However, a link flap is observed within the ports of the port groups if the speeds of any port are reconfigured to other speeds. To avoid such a situation all the ports of the port group can have single-speed or do not reconfigure the speed within the port group. PR1608223

  • In ACX7509, after multiple FPCs go online or offline, FPCs move to fault state. PR1616227

  • A major alarm is reported for a fully populated dual Routing Engine or dual FEB system in Junos OS Evolved Release 21.4R1. A fully redundant (dual Routing Engine or dual FEB) ACX7509 feature is not available in Junos OS Evolved Release 21.4. This alarm can be ignored for the backup Routing Engine or FEB. PR1622133

  • After restarting the picd or rpd agent application, multiple object-info anomalies for evo-pfemand are seen. PR1628843

  • In ACX7509 and in scaled setup if you restart FPC, the FPC gets stuck after ungraceful FPC OIR. PR1633117

  • In ACX7509, on multiple FPC restarts, links do not come up with FEC errors. PR1639666

  • On Junos OS Evolved devices with EVPN-VXLAN, if there's a default route in primary instance pointing to management interface, you need to enable a policy to prevent it from being used for VXLAN resolution when there is any churn in the IP underlay.PR1657222

  • In high DHCP traffic scenario, the jdhcpd process might get stuck at 99 percent if you enable traceoptions for DHCP that lead to network outage for the DHCP clients. PR1658087

Platform and Infrastructure

  • On Junos OS platforms with MPC10, MPC11, and MPC LC-9600 linecards and all Junos OS Evolved platforms configured with TWAMP. MPC10 or MPC11 linecard might crash when the TWAMP client tries to create a session with the TWAMP server. PR1667716

  • As a result of change in design, time issues upon installing ECMP nexthop in Junos OS Release 21.4R3 were seen. In certain scenarios, if there are multiple scale configurations seen with Unilist next hop indices with aggregated Ethernet logical interfaces, then for some of the next hops, hardware programming might fail. Therefore, programming of all routes pointing to the Unilist next hop will also fail. Similar issue has been identified and fixed in the PR1637301 with certain design changes. PR1677123 and PR1677855

User Interface and Configuration

  • On Junos OS Evolved platforms, when vlan-bridge and corresponding logical interface is configured, a link is created between them. When you delete the logical interface using the load-override method, you won't be able to back up the link information in the system. When you recreate the same logical interface, the link creation might not happen. Delete the logical interface and recreate the same using load-update to recover from the issue.PR1647853