Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Open Issues

date_range 09-Nov-22

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.

EVPN

  • On all Junos OS Evolved platforms that support EVPN-MPLS (Ethernet Virtual Private Networks -Multiprotocol Label Switching) services, during switchover or layer 2-learning restart, some EVPN next hops are not correctly associated with routing-instance in Routing Engine impacting the traffic forwarding.PR1633344

  • On performing Graceful Routing Engine swithchover on ACX7509 platform with EVPN services, some logical interfaces are missing. The logical interfaces come up post reboot.PR1646722

  • On ACX7024 devices, pseudo wire setup and tear down rate might be low. This is due to system CPU limitation. PR1659593

General Routing

  • On ACX7509 devices, some of the interfaces from 16x100G and 20XSFP56 do not go down after evo-pfemand restart. PR1592388

  • On ACX7509 devices, after multiple FPC online or offline, FPCs go to fault state.PR1616227

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

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

  • If a FEB goes to fault state due to a power-fault (real or artificially triggered for testing), then the subsequent FEB offline can take a few minutes (instead of completing within a minute for a normal offline). There is no other collateral due to this. A FEB online subsequent to the delayed offline works normally and the FEB becomes fully functional again. PR1671719

  • On ACX7000-32C, ACX7100-48L platforms, vlan-id all configuration option is not supported in VPLS vlan configuration. PR1679972

  • Sometimes when the access interface is deactivated and reactivated in quick succession DHCPv6 packets get dropped in the Routing Engine. It does not recover automatically, the DHCP process has to be restarted to recover from this situation. PR1692278

User Interface and Configuration

  • The system might ask for your password when you try to save configuration file.PR1665008

footer-navigation