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 Junos OS Evolved Release 22.1R1 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 enable PTP, port 31 of the ACX7100-32C router gets configured to 1G. The Packet Forwarding Engine chip from the vendor supports only 10G. Hence, the speed gets converted from 10G to 1G on the external PHY. However, there is one limitation. It supports only frame size to 2000 bytes and jumbo frame cannot be supported on port 31 when you enable the PTP mode. PR1593015

  • syncE to PTP and syncE to 1pps noise transfer tests fails for frequencies 1. 0.00781 HZ, 2. 0.01563 HZ, 3. 0.03125 HZ, 4. 0.06156 HZ, and 5. 0.12313 HZ. PR1608866

  • In some corner cases, traffic does not get scheduled equally between the strict priority queues. Priority queue gets configured, completely utilizes the bandwidth, remaining queues are starved, and the traffic completely drops on those queues. In this state, if we configure a second strict high priority queue traffic does not get scheduled equally between the strict priority queues. This is hardware specific Q2C issue. PR1577035

  • Ping and traceroute works with reply mode as ip-udp (applicable to other Junos OS Evolved ACX series). Other reply mode (application-level-control-channel) works when we support BFD over VCCV. For ping, the default mode for MSPW Echo reply is application-level-control-channel. Hence, MSPW L2VPN ping needs reply-mode as ip-udp for the ping to work, as BFD over VCCV is not supported. For traceroute, the default mode is application-level-control-channel. Hence, MSPW L2VPN traceroute needs reply-mode as ip-udp for the traceroute to work, as BFD over VCCV is not supported. PR1642026

  • CCM transmission keeps occurring (for the Up MEP aggregated Ethernet interface case) during FPC restart, as the aggregated Ethernet interface does not get deleted during the FPC restart. The session information already programmed in the hardware does not get deleted. During the FPC restart case, the CCM transmission keeps occurring. Due to this reason, sessions are up on the peer. Whereas in case of physical interface, the sessions get deleted and added back during FPC restart. As a result, the behavior remains different in the physical interface compared to the aggregated Ethernet interface for UP MEP case. PR1627369

  • The ACX platform performs hardware time stamping but the peer device (in this case MX routers) performs software time stamping, which takes more time resulting into high delays. This issue occurs on all the cases where the peer setup performs software time stamping. PR1599777

  • The clear mpls lsp operation is a destructive operation where it wipes off all the existing routes and nexthops in the system, and does a fresh reinstallation. The 10 seconds delay in the traffic restoration for 16,000 Layer 3 VPN routes might be attributed to programming delay in the hardware units combined with software model and the CPU capacity. PR1614413