Open Issues

ACX7509: G.8275.1 FPC Dpll status is incorrectly shown in timingd gencfg ptp centralized command.PR1685675

Suppose a user has disabled RE0 for primary role as follows: set chassis redundancy routing-engine 0 disabled. This prevents RE0 from becoming primary on system boot. Instead RE1 become 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

When ingress policer is configured, to drop ingress traffic, on an interface with upMep the CFM packets generated from the upMep are also dropped due to the policer. This leads to CFM session going down.PR1754938

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 restart.PR1768708

With DHCP trace options enabled in the regression scripts, core file is seen. Issue is random not seen always. This is enabled in script for debugging in production network this is not be enabled by default hence the issue is not seen. Its recommended to enable DHCP trace options only for debugging not otherwise.PR1771121

Following error message is seen with the delete vlan event trigger when configured with multiple vlans with IRB and IGMP snooping/MLD snooping enabled. No functionality impact. Error] compName = "BrcmPlusMcast", tpName = "Irb", msg = " fn = removeMemberFromL3FloodMcastGrp. PR1771915

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

ACX7509 HA has dual feb and LT interface creation uses feb slot id as a keyword in CLI. As per the current design limitation, LT interface cannot be supported on ACX7509 HA platforms(in Junos OS Evolved Release 24.1R1). If user initiates restart evo-pfemand on primary Routing Engine or switchover on ACX7509 HA device, this results in complete traffic drop. PR1778116,PR1778137.

On ACX7100-32C and ACX7100-48L, Precision Time Protocol (PTP) state remains ACQUIRING when the PTP is configured in Hybrid mode (Synchronous Ethernet (SyncE) + PTP) and PTP mode is committed at a time with PTP configuration. PR1783545

ACX7509 :: For all sBFD sessions in scaled setup, to come up after link down event (sBFD FRR) , it is recommended to configure the lo0 interface with default local host ip. PR1788465

During multiple RE (Routing Engine) switch-overs and router reboots, management port of one of the Routing Engines comes up with 100 MBPS speed instead of 1 GBPS speed. There is no functional or stability impact due to this issue. Router monitoring might face a mild performance issue due to this lower speed of management port.PR1789156

L3VPN traffic over tunnels could drop with egress marking error when dynamic tunnels are configured, this is specific to all Junos Evolved ACX7000 variants. This can be checked by issuing show pfe statistics error output. PR1789481

This is a day-1 issue. It exists on all ACX platforms where Juniper Networks servo runs. Once the asymmetry configured at the secondary port, the error propagated to the down stream eventually causes this performance issue of spike. PR1793926

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

On all Junos OS Evolved platforms, when a layer 2 routing-instance is changed to layer 3 routing-instance or vice versa without changing the name of the routing-instance in a single commit, due to a rare timing issue, the rpd process can crash. During the rpd crash and restart, the routing protocols are impacted and traffic disruption is seen due to the loss of routing information. PR1802000

Configuration of a global AS number is necessary when route target filter is enabled. Currently Junos OS CLI 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