Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


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

  • In a scaled setup with LDP over RSVP configuration and maximum-ecmp as 32 or 64, line card CPU usage can remain high for extended duration on link flap operation. In this duration, LACP might take 5+ minutes to converge and the AE bundle to be active. PR1624219

  • If proper gap is given between channelisation and dechannelisation the issue is not seen. Proper gap means allowing the system to complete the previous config before we load the new config. Recommendation is to if we give channelisation config commit wait for the links to come up or atleast the ifd's get created on both evo and RE side and then only revert the config to dechannlisation and vice versa.PR1665625

  • For GNMI subscriptions, PFE doesn't support filtering in Subscription paths. So data is streamed from PFE ignoring filteringPR1668911

  • RE-S-X6-128G-K does not support enabling encryption with GRES. You must enable encryption on each Routing Engine.PR1676928

  • On all Junos and Junos OS Evolved platforms, if OSPF (Open Shortest Path First) has segment routing with TI-LFA (Topology-Independent Loop-Free Alternate) protection enabled for gr-interfaes (Generic Routing Encapsulation tunnels), it is possible that we do not compute TI-LFA backup path when the primary or backup paths are over gr-interfaces. Not having TI-LFA backup paths effects convergence times during failures.PR1685064

  • MVRP on PVLAN promiscuous port is not supported. If MVRP is configured on promiscuous port, then hosts connected to secondary VLAN ports will not be able to reach external world through promiscuous port carrying primary VLAN tags. PR1693345


  • When you upgrade from earlier release to Junos OS Release 21.2 and later, validation and upgrade might fail. As a workaround, use no-validate configuration statement before you upgrade. PR1568757

  • Below IPC timeouts logs can be seen for statistics query to kernel (queried from CLI or daemons querying internally) when there is configuration churn, or large number of IPCs getting exchanged between kernel and pfe in the system. if_pfe_msg_handler: pfe_peer_msg_handler error: error for msg type type, msg subtype subtype, opcode op and peer index index Default IPC timeout value in kernel for IPC statistics request is 10s. This can be incremented to larger value by setting below hidden configuration to avoid IPC timeout errors. set system stats-timeout-lifetime 15 and commit. PR1629930


  • With local reversion ON, there is a possibility of transit router not informing headend of RSVP disabled link when link is flapped more than once. Work around is to remove local-reversion configuration. PR1576979

Platform and Infrastructure

  • In some scenarios with MPC, major alarm and following messages are generated. This major error is triggered due to parity error, and the impacted queue might drop packets. This might impact the forwarding, to recover MPC card need to be rebooted. PR1303489

  • On MX Series and EX9200 Series platforms, under Ethernet VPN (EVPN) environment, packets routed using IRB interface could not be fragmented due to media maximum transmission unit (MTU) problem. PR1522896

  • After a switchover event, when ppmd calls sendmsg system call to transmit the protocol packets, it gets blocked long enough that a few sendmsg calls cumulatively take up around 7 to 8 seconds. This indirectly impacts the BFD session because the BFD session has a Routing Engine-based detect time of 7.5 seconds to expire. PR1600684

Routing Protocols

  • When routing-options transport-class fallback none is not configured - do not configure more than 10 transport-classes. Or advertise more than 10 distinct colors in SRTE or FlexAlgo. PR1648490

Services Applications

  • In Junos OS Release 17.4 and forward, subscriber sessions on the LNS that send an ICRQ that includes RFC5515 AVPs might fail to establish a session. The client will receive a CDN error "receive-icrq-avp-missing-random-vector" in response. PR1493289

User Interface and Configuration

  • On all Junos OS and Junos OS Evolved platforms configured with persist-group-inheritance, which is enabled by default from Junos OS Release 19.4R3 and later, might lead to mustd process crash in highly scaled configuration. PR1638847