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 Junos OS Release 22.2R1 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

  • On all MX devices, traffic might be interrupted when you change the configuration from AMS warm-standby to AMS deterministic NAT. PR1597386


  • With local reversion ON, there is a possibility of transit router not informing headend of RSVP disabled link when link flaps more than once. As a workaround, remove the local-reversion configuration.PR1576979

  • The automatic sorting of configuration entries does not work if defined under a group. PR1637730

Platform and Infrastructure

  • Major alarm with XQCHIP(46):XQ-chip[0]: DROP protect_regs error (status=0x8) logs appears. PR1303489

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

  • Deactivating services rpm/rpm-tracking does not remove the tracked route from the routing or forwarding tables. PR1597190

  • Routing Engine-based BFD sessions might flap during switchover when there are large number of BFD, IS-IS, OSPF and LDP packets to be sent out. PR1600684

Routing Policy and Firewall Filters

  • When a hierarchy specified in apply-path is configured in an ephemeral instance, then rpd might not be able to update the prefix-list for the configuration in ephemeral instance. PR1636390

Routing Protocols

  • When we have high scale, the openconfig telemetry sensor /bgp-rib/ used in periodic streaming will cause high cpu usage by RPD. PR1625396

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