Known Limitations
Learn about known limitations in this release for MX Series routers.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
General Routing
-
MX-SyncE lock status shows
LOCKED
under thechassis synchronization extensive
command when synchronization Ethernet source fails with the DUT configured with G.8275.1 profile. PR1509356 -
Changing the scaled firewall profiles on the fly does not release the TCAM resources as expected. PR1512242
-
LFM might flap during the MX-VC ISSU. PR1516744
-
PTP to PTP noise transfer test fails. PR1543982
-
MX upgrade failure with limited free disk space occurs. PR1582554
-
Interface hold-down timers cannot be achieved for less than 15 seconds on MPC11E at FRS. PR1444516
Infrastructure
-
Software Image Upgrade from versions 21.1 (or earlier) to version 21.2 (or later) requires the
no-validate
statement. PR1586481
MPLS
-
The rpd process might crash after you change the network service configuration. PR1461468
Platform and Infrastructure
-
Traffic might drop due to the QX-chipset MPC memory error. PR1197475
-
The following error message occurs:
PR1575316sw-vpls: Renult:mx10008: Err] dispatch_event_handler(684): EA[1:0].disp[0] PRIMARY_TIMEOUT (PPE 4 Zone 18).
-
Deactivating services rpm/rpm-tracking does not remove the tracked route from the routing or forwarding tables. PR1597190
Routing Protocols
-
If you do not execute the
restart routing
command after you configureenhanced ip
might result in a label inconsistency leading to the rpd process to generate core file. PR1577451
VPNs
-
During ISSU from Junos OS Release 18.4R1 to Junos OS Release 19.1, traffic through IPSEC VPN fails. PR1416334