Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

Learn about open issues in this release 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.

General Routing

  • On all Junos OS Evolved platforms, port LED goes unlit or off instead of amber or on when port is disabled.PR1690655

  • ACX7509 systems have the ability to do automatic fault-based switchovers when traffic impacting faults are seen on primary Routing Engine or primary FEB. This ability needs to be disabled if the backup Routing Engine because of this PR. The workaround is to disable automatic fault-based switchovers also as follows: set chassis redundancy failover disable. PR1713851

  • When ingress policer is configured, to drop ingress traffic, on an interface with upMep the CFM packets generated from the upMep is also dropped due to the policer. This leads to CFM session going down. PR1754938

  • When DHCP trace options are enabled, there is a possibility that jdhcpd could generate a core file. In general, traceoptions must be enabled only for debugging. They must be disabled once debuffing is done.PR1771121

  • This is day-1 issue of Juniper Networks servo. It exists on all ACX Series platforms where Juniper Networks servo runs. Once the asymmetry configured at secondary port, the error propagated to the down stream eventually causes the performance issue of spike.PR1793926

  • When multicast packets are transiting ACX7100 devices through VXLAN VTEP or core file interface without multicast configurations, errors are seen. Suggested to use DDOS configurations provide with workaround. PR1796501

  • On Junos Evolved ACX7348 performing functions such as GRES (Graceful Routing Engine Switchover) or a request node reboot re is graceful, that is there is no traffic impact. PR1817121

  • On ACX7348, ACX7332, or ACX7024 platforms, The SDK (Software Development Kits) initialization fails resulting in evo-pfemand application core file. This typically happens after evo-pfemand application restart or after a Routing Engine switchover.PR1842389

  • On ACX7509 Junos Evolved platforms, picd crash is seen with protocol flaps in case of HA (High Availability) during RE (Routing Engine) switchover, caused due to incomplete initialisation. PR1863708

Infrastructure

  • On all Junos Evolved ACX platforms, modifying an ECMP route triggers the deletion of the old Next Hop route, which can temporarily disrupt traffic flow until the new route is fully established.PR1820482

Routing Policy and Firewall Filters

  • When using input-list we do not report the policer statistics correctly for Routing Engine filters. This is done correctly for interface-specific filter for the same.PR1844737

Routing Protocols

  • Configuration of a global AS number is necessary when route target filter is enabled. Currently Junos OS CLI does not enforce configuring a global AS number and it has been the behavior for a long time. It's been a recommended practice to configure a global AS number in the field.PR1783375

Subscriber Access Management

  • On Junos Evolved platforms, after device has finished booting up with Zero Touch Provisioning (ZTP), authd process crashes and generates a core file.PR1812697