Open Issues

General Routing

• In ACX5000 devices, some next-hop routes do not get installed properly and generates the following error message in the LPM mode:

  content_copy zoom_out_map

  Failed to h/w update ip uc route entry

  For the default route, if the route changes from ecmp to non-ecmp HOLD nexthop, the Packet Forwarding Engine gets into a corrupted ecmp nexthop.

  PR1365034

• On ACX5448 devices, MAC learning or aging might stop in the Layer 2 domain after excessive MAC movements or continuous interface flaps. There might be unexpected flooding traffic when the issue occurs. PR1480235

• Due to BRCM KBP issue route, lookup might fail. PR1533513

• On ACX devices, traffic issue might be observed with downstream devices when you configure the Precision Time Protocol(PTP) (G.8275.1 PTP profile) along with PHY timestamping and Multiprotocol Label Switching (MPLS) terminated on 10G interface. The transit PTP ipv4 packets gets updated with incorrect Correction Factor(CF). The issue might be restored by disabling the PHY stamping. However, disabling might impact the PTP performance. PR1612429

• For ACX5448 VM Host-based platforms, starting with Junos OS 21.4R1 release or later, the ssh and root login are required for copying line card image from Junos VM to Linux host during installation. The ssh and root login are required during installation. Use the deny-password option instead of deny option as default root-login option under the ssh configurtion to allow internal trusted communication. PR1629943

• On ACX5048 and ACX5096 devices, Junos OS does not support interface speed 10m on 1G interface. PR1633226

• Convergance time might be more than 60 seconds for IS-IS TILFA node protection testing. PR1634033

• In case of routing instance type EVPN or EVPN-VPWS, the system automatically creates one default routing instance apart from EVPN and/or EVPN-VPWS routing instance. In the output of the show snmp mib walk jnxVpnInfo command, the number of configured routing instances are always one more than the number of EVPN and/or EVPN-VPWS instances configured in the system.

  PR1659466

• On ACX5448 and ACX710 devices, all types of delegated BFD sessions configured on routing-instance other than the default routing-instance might not come up. PR1633395

• On ACX5448 device, if a firewall has a log action and applied on the physical interface or lo0 interface, the LDP neighbor cannot go up. PR1648968

• In case of routing instance type EVPN or EVPN-VPWS, system automatically creates one default routing instance apart from EVPN and/or EVPN-VPWS routing instance. Hence, in the output of the show snmp mib walk jnxVpnInfo command, the number of configured routing instances are always one more than number of EVPN and/or EVPN-VPWS instances configured in the system. PR1659466

• Some of the interfaces get zero status in the output of the monitor interface traffic command. Sending traffic across all interfaces and applying speed of 100m on all 1g copper ports, clears the interfaces status. PR1661617