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

  • G.8275.1- G.8273.2 1PPS cTE performance test might be marginally outside class-C for PTP BC on ACX7100-48L, especially for mixed speed port testing with combinations of 10G / 25G channelized ports and 100G ports. On each reboot, the 1PPS cTE measurement might be within the class-C measurement threshold, or might randomly be out of threshold by a few nanoseconds.PR1607381

  • In a ACX7509 system with dual Routing Engines and FEB, when there is a power fault of primary FEB, a switchover should happen and backup Routing Engine and FEB will take up primary role. Post switchover a VMCore might be generated in the new Backup Routing Engine. This failure should not impact the system uptime. Post Vmcore backup Routing Engine reboots and comes back online. PR1671198

  • ACX7100-48L:Interface takes more time or does not come up after picd restart.PR1673892

  • HQoS - VoQ Statistics issue during scaled configuration with congestion. In scaled HQOS configuration with congestion across all queues due to unavailability of the system level packet buffers, packets are dropped irrespective of the queue priorities. These dropped packets are not be accounted as part of queue statistics.PR1674669

  • Channels of 4x100g channelization flap after they are brought up.PR1693066

  • DTE mask fails for cascaded setup with long run.PR1697093

    • In Layer 3 interface (inet/inet6/mpls), if user configures IEEE802.1p classifier alone, then all the flow (inet/inet6/mpls) is classified. If additional non IEEE802.1p classifier (DSCP/EXP etc.,) is mapped to the same interface, then the unmapped family is not classified and is handled as best effort mode. Workaround: User has to configure classifiers for all the families to do proper classification.

    • In Layer 2 interface (ethernet-switching), if user configures IEEE802.1p classifier alone, then all the flow (l2/v4/v6/exp) is classified. If additional non IEEE802.1p classifier (DSCP/EXP etc.,) is mapped to the same interface, then the unmapped family is not classified and is handled as best effort mode. Workaround: User has to configure classifiers for all the families to do proper classification.

    • PR1713158

  • In ACX7509, when the FEB is ungracefully jacked out first and subsequently plugged in, the newly inserted FEB does not come online after online command is issued for the newly inserted FEB. The FEB stays stuck in onlining state.PR1713885

  • After multiple triggers, 3x100g interface is stuck down. Plugout and reinsert, swapped acacia and wavelength tuned to non-default.PR1723980

  • In the scaled setup with SRv6 micro sid for L3VPN VRFs (~2K) are enabled in single commit, few initial VRF might experience traffic outage. Workaround: Deactivating and re-activating only the failed VRFs resolves the problem. PR1726481

  • On all Junos Evolved platforms, when OSPF (Open Shortest Path First) areas are configured at a high scale, generating a huge number of LSAs (Link State Advertisements), the RPD (route daemon) process is stuck due to high CPU utilization. PR1728573

  • On ACX7509 platforms, with MACsec enabled on the interface, after a restart of the picd deaemon or high Availability switchover of Routing Engine causes traffic to be blocked on MACsec enabled interfaces as well as non-MACsec interfaces. PR1738038

  • [dhcp] [generic_evo] ACX7509 :: DHCP daemon does not run in the new primary Routing Engine post GRES, all DHCPv4 or DHCPv6 sessions are lost. This issue is seen on Junos OS Evolved 23.2R1, while performing GRES on ACX7509 might not work properly for DHCP sessions. PR1740530

EVPN

  • When user wants to toggles the following evpn normalization configuration statement routing-instances <> protocols evpn normalization, it requires deactivate of the specific routing-instance followed by toggling the configuration statement and then activation of the routing-instance..PR1685978

Routing Protocols

  • Redirect-to-ip action in flow-spec routes is not supported for VPNv6 address family.PR1714502

  • With IRB and snooping enabled when MCLAG has Junos OS Evolved and Junos OS based platform as peer the IGMP/MLD group information for IRB is not formed on MCLAG peer which does not receive IGMP/MLD group report directly from connected interface but form the group state based on the MCLAG ICCP updates. The L2 or Snooping IGMP/MLD group membership works but the IRB's group membership for IGMP/MLD is not formed.PR1729195