Open Issues

ACX7509 systems have the ability to do automatic fault-based switchovers when traffic impacting faults are seen on the primary Routing Engine or primary FEB. This ability needs to be disabled if the backup Routing Engine is disabled for primary role.

Suppose a user has disabled RE0 for primary role as follows: set chassis redundancy routing-engine 0 disabledThis prevents RE0 from becoming the primary on system boot. Instead RE1 becomes the primary. Under this scenario, an automatic fault-based switchover from RE1 to RE0 can still happen. The workaround is to disable automatic fault-based switchovers also as follows: set chassis redundancy failover disable. PR1713851.

We observe core file with rpd with BGP flowspec if secondary-independent-resolution is configured.PR1722715

On Junos OS Evolved ACX platforms with GRES (Graceful Routing Engine switchover), after performing GRES switchover jdhcpd does not start on the new primary RE (Routing Engine) due to which DHCPv4/v6 (Dynamic Host Configuration Protocol) session binding is lost resulting in traffic loss.PR1740530

show pfe statistics traffic command displays 0 in Input packets: and Output packets: after Packet Forwarding Engine app (evo-pfemand) restart for some time. Correct values are displayed after the delay.PR1745512

On Junos OS Evolved ACX platforms configured with EVPN-MPLS (Ethernet VPN-Multiprotocol Label Switching) vlan-based EVPN service or EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN), device does not respond to ARP/ND (Address Resolution Protocol/Neighbor Discovery) without any vlan-id tag. Due to this, the ARP or ND response packet gets dropped in LAN network and the local host is not able to resolve the ARP.PR1751135

On ACX7348 and ACX7332 series running Junos OS Evolved, multiple Routing Engine switchover can cause IDEEPROM failure on FPC and PSM, which results in PSM and FPC shown as unsupported.PR1760978

CFM sessions when scaled on ACX7000 Junos OS Evolved Series can get stuck in OK state on catastrophic events which can result in CCM timeouts at the same time. It can be recovered with CFMD process restartPR1768708

When the chassis is headless (No Routing Engines), the behaviour of LEDs in that case is not deterministic.PR1769719

When DHCP traceoptions is enabled, there is a possibility that jdhcpd could generate a core file. It is recommended to enable them only for debugging purpose and disable it immediately once debugging is done.PR1771121

On Junos OS Evolved ACX Series platform in EVPN (Ethernet Virtual Private Network)-VXLAN (Virtual Extensible Local Area Network) scenario in L3VRFs (Virtual Routing and Forwarding) configured with RIB (Routing Information Base) group for route leaks when routing-options multipath is configured the, Type-5 routes advertised through the VRF does not work. There is an impact on the traffic in the VRF when this issue is encountered.PR1773240

Multihop BFD packets by default uses the network-control queue in Junos OS Evolved ACX Series. This setting remains same despite configuring the host-outbound-traffic to a different forwarding-class.PR1776127

Junos Evolved based ACX node acting as ASBR+PE (Autonomous System Border Router + Provider Edge) in MPLS L3VPN (Layer 3 VPN) Inter-AS Option B or C does not install VPN label encapsulation in the Packet Forwarding Engine. Traffic is impacted due to this issue.PR1794718

When multicast packets are transiting ACX7100 devices through VXLAN VTEP or core interface without multicast configurations, errors are seen. Suggested to use DDOS configurations provide with WA. PR1796501

Under certain conditions when DHCP configuration is completely removed, the session database is left in an unusable state. On subsequent reconfiguration of DHCP, subscriber logins fail. In this case a system reboot is required. PR1816246

ACX7348::Telemetry :: Few of the sensors do not get streamed for /components/component/. PR1817427

[evpn-vxlan][dcf12] ACX DC-GW not forwarding traffic received from remote DC-GW after trigger test. PR1817677

BGP passing next-hop path's weight as 0 first and then passing next-hop path's weight as 1 later causes KRT to create 2 different next hops (as weight is now part of next-hop key) and results in installing same route in FIB as primary and backup. PR1745661

Configuration of a global AS number is necessary when route target filter is enabled. Currently Junos OS does not enforce configuring a global AS number and it has been the behavior for a long time. Many unexpected issues might be seen without a global AS number. It's been a recommended practice to configure a global AS number in the field. PR1783375