Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Known Limitations

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

  • The syncE to PTP and syncE to 1pps noise transfer tests fail for frequencies on ACX7100-32C 1. 0.00781 HZ 2. 0.01563 HZ 3. 0.03125 HZ 4. 0.06156 HZ 5. 0.12313 HZ.PR1611911

  • SyncE and Hybrid PTP is not supported on the 1G interface on ACX7024.PR1644975

  • When the original flow egresses out through an aggregated Ethernet interface, the corresponding sampled sflow frame does not reflect the correct egress port number. This happens only when the flow egresses out through an aggregated Ethernet interface. For non-aggregated Ethernet egress interface, this works fine and the sflow frame reflects the correct egress port.PR1647870

  • The syncE to PTP and syncE to 1pps noise transfer tests fail for frequencies 1. 0.00781 HZ 2. 0.01563 HZ 3. 0.03125 HZ 4. 0.06156 HZ 5. 0.12313 HZ. PR1649055

  • The timingd restart is not supported on ACX7024. PR1651554

  • ACX7024: With high scale of Layer 3 VPN VRF instances system CPU usage might continue to be high.PR1655310

  • When you issue show system processes extensive or show chassis routing-engine, idle cpu usage is around 75% in ACX7024. The 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 won't be any functional impact because of this.PR1656732

  • Due to low CPU on ACX7024, the aggregated Ethernet interface takes longer time to come up after deactivate or activate in multi-D scale set up.PR1677809

  • The request system snapshot command is not supported on ACX7024.PR1686610

  • When you issue show system processes extensive or show chassis routing-engine, it is observed that idle cpu utilization might spike upto 18-20% in ACX7024. This is because of the internal 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. This does not have any functional impact when the system runs with high logical interface scale.PR1689073