Known Limitations
Learn about known limitations in Junos OS Release 21.2R1 for ACX7 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
The internal switch does not support hot swap. Removing internal switch PCI device or power down the main board does not trigger any signal to evo-pfemand. The user space application cannot detect this fault. PR1554516
-
Egress IP MTU exception and fragmentation is not supported. Outgoing IP packets bigger than the configured interface MTU does not get fragmented. PR1558327
-
For ACX7100-48L, on configuring or unconfiguring PTP TC, interface needs reinitialization and therefore it is expected to see interfaces go down and come up. PR1558603
-
ACX7100-48L :: Multicast : IPv6 multicast traffic loss on downstream receiver along with inconsistent forwarding S,G route entry on the ACX7100-48L device. The following limitation is applicable only for IPv6 multicast.
The hardware limitation for IPv6 multicast is, the route entry (In-Intf, S1, G1) programmed as (In-Intf, *, G1).
-
It means when multiple sources for the same group are in the same incoming interface and the OIF sets are different, there could be potential traffic loss.
-
When multiple sources for the same group are in the same incoming interface and the OIF sets are same, then there is no potential traffic loss expected.
-
Where can we place the ACX7100-48L device in the network only for IPv6 multicast.
-
ACX7100-48L acts as RP or FHR:
-
When acting as RP, there is a possibility that RPT prune and SPT join happens, which could result in above limitation mentioned. So ACX7100-48L cannot be placed as RP or FHR.
-
-
ACX7100-48L acts as LHR:
-
The OIF set is not different for different (S1, G1) entries, hence overwriting the same (In-Intf, *, G1) in hardware can result in no traffic loss.
When moving from RPT tree to SPT tree, the (S1,G1) entry moves to a different IIF interface, hence we program different (In-Intf, *, G1) entry in hardware and there is no expectation of traffic loss.
-
-
-
ACX7100-48L and ACX7100-32C does not support micro bfd with
no-dedicated-mac-for-micro-bfd
. When packets received with no-dedicated mac, ACX7100-48L and ACX7100-32C does not accept and punt to the host path, micro bfd session does not come up. So configuring the configuration statementno-dedicated-mac-for-micro-bfd
on the peer router if the device is ACX7100-48L and ACX7100-32C is not supported. PR1566672 -
The firewall filter can only be implemented by adding the micro bfd dedicated MAC to VRRP TCAM table. But VRRP TCAM is limited in size only 11 entries in balanced profile), reserving one entry for storing the micro bfd reduces the VRRP TCAM size by 1 and might impact the scale. PR1569841
-
When a high scale of routes are dependent on a ECMP group or unilist, few streams might observe 8-9 seconds traffic drop during ECMP member link flap. PR1573295