Known Limitations

When the device is up and running for a long time, there is a possibility FS gets bad blocks and it is accumulated. When any change is done to it, it reloads and tries to recover the bad blocks from the FS. PR910445

On the MX104 router, scheduler slip is observed when configuration changes are committed. PR1361250

Traffic stops after the volume limit is reached but the traffic resumes after an aggregated Packet Forwarding Engine interface fails. PR1463723

For two tunnels with same TS, all traffic is forwarded on the tunnel that comes up later. PR1467364

It is possible that LFM might flap during MX Virtual Chassis unified ISSU to and from this release. PR1516744

The BGP neighbor flaps during the primary NG-RE reboot, although GRES or NSR is enabled. PR1524791

When an image with the third-party SDK upgrade (6.5.x) is installed, the CPU utilization might go up by around 5 percent. PR1534234

Inconsistent core.python2.7.mpc0 core is seen with stacktrace @ea_wi_precl,@ea_macsec_receive(). PR1534568

The NPC process continuously generates core files at Trinity_Ktree::Trinity_FourWayBlock, Trinity_Ktree::walkSubTree due to the next-hop memory exhaustion with the next-hop explosion. The rpd and srrd processes start hogging and the system becomes unstable. PR1538029

Guidelines are needed for enabling or restarting fib-streaming in low-memory conditions. PR1540478

PTP to PTP noise transfer is passing for impairments profile 400nsp-p_1Hz, but failing for profile 400nsp-p_0.1Hz and lower bandwidth profiles as well. Issue is common to 10G also. PR1543982

Unified ISSU is not supported. There is a major SDK upgrade from 6.3.2 to 6.5.16, due to which the warm boot feature needed for unified ISSU is not supported by vendor. PR1554915

On the MX10003 routers, after a subscriber logs in, the subscriber is allowed to delete the entire AGF service stanza and commit the configurations, leaving the subscribers stuck in the Active state permanently. The user must not be allowed to delete the AGF Service configurations with active UEs. PR1555031

sFlow egress sampling of MPLS packets is not supported on MX Series platforms. PR1556659

Resource deadlock avoided messages are observed during software add. There is no functionality impact. PR1557468

On the MPC11E line cards, the following error message is observed:

On the MPC11E line cards, the following error message is observed:

The RPD process generates core file if the use-for-shortcut command is configured on an SRTE tunnel which uses an SR Algo 0 Prefix SID. PR1578994

SyncE to PTP noise transfer passes for 400 ns p-p amplitude and frequency of 1 Hz but fails for 200 ns p-p amplitude and frequency of 0.005 Hz.PR1566291

G.8273.2 transient response test fails. Issue exists for legacy line cards also. PR1566354

With T-BC across multiple line card, average time error (cTE) test fails as there are other delays introduced causing phase variation across line cards. PR1567662

Junos OS Release 21.1 and lower are running FreeBSD version 11 whereas from Junos OS Release 21.2 onward, the FreeBSD version is 12. Software upgrade to 21.2 or later from 21.1 or earlier must use no-validate CLI option during software image upgrade process. PR1586481

During high route churn in scaled configurations, peer buffer becomes full and statistics request might get dropped by kernel because of their low priority as route updates are prioritized by kernel. This is a design limitation to prioritize route updates over statistics. The application is expected to retry in this scenario after route churn settled down. PR1607362

For MC-LAG to work properly, the mc-ae interface should be configured on both the PE devices. A scenario where the mc-ae interface is deleted, deactivated, or not configured on one of the devices is a case of misconfiguration. Juniper Networks does not support such a scenario because it can lead to traffic loss and other unexpected behavior. PR1536831

On the MPC10 line cards, DMRs or SLRs are not received with an EVPN up MEP on the aggregated Ethernet interface with normalization. PR1543641

Packet loss is seen in the scaled setup with 296 LM sessions with iterator cycle time interval (100 ms). It seems there is degradation in scale number (OAM packet rate at ~5500). At this qualified PPS, now LMR packet loss is observed, but the functionality seems to be fine. To avoid LMR packet loss, reduce the scale number, and OAM packet rate should be less than 5500 PPS. PR1561397

The rpd process might crash. PR1461468

SNMP link up trap message is not observed after a line card reboots when scaled interfaces are present. PR1507780

Convergence time is high when the igmp snooping configuration is deleted. PR1550523

With max number of logical interfaces (4000 GRE tunnel per Packet Forwarding Engine) with following configuration:

1) family inet and associated source and destination for each tunnel.

2) Configure allow-fragmentation statement on one endpoint of the tunnel and configure reassemble-packets on the other endpoint of the tunnel.

If we do deactivate chassis fpc <slot>, we might see SLIP messages while testing inline GRE reassembly feature with GRE interface scaling for MX Series. PR1581042

Unsupported options are displayed under the restart commands. PR1545558

Traffic loss is observed on starting the traffic with PIM disabled under the ingress primary UMH. PR1562759