Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Known Limitations

Learn about known limitations 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

  • When you issue show system processes extensive or show chassis routing-engine, idle CPU usage is around 75% in ACX7024. Evo-pfemand process usage is in the range of 9-19%. This is because of the polling threads in evo-pfemand. This behaviour is common across platforms and not ACX7024 specific. The CPU usage numbers are aggravated due to low CPU in ACX7024. There would not be any functional impact because of this. PR1656732

  • Junos OS Evolved follows Make-Before-Break (MBB) mechanism to program next-hop and route to achieve faster convergence. The mechanism installs new forwarding table entry before deleting old one, minimizing traffic loss during route convergence. However, it temporarily increases the number of forwarding paths programed in the Packet Forwarding Engine depending on number of times nexthop or route changes in a short period of time. MBB is applied during link-flaps, graceful restarts (ldp), session flaps (ldp) etc.

    For deployments where the network device is running on the higher end of the tunnel scale limits, a link flap can easily exceed the scale of the device. Once Packet Forwarding Engine exceeds its forwarding table capacity any new nexthop add for a tunnel is ignored, resulting in traffic silent packet drop for those NHs. A link flap though, triggers MBB for only the tunnels associated with that particular link. If we take a worst-case situation that all the links flap at once and all the tunnels are hence undergoing MBB, we have to keep the tunnel limit to half to be absolutely sure not to exceed the limit. PR1660472