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 more than 5 minutes to converge and the aggregated Ethernet 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 configuration before we load the new configuration. Recommendation is to if we give channelisation configuration commit wait for the links to come up or atleast the physical interfaces get created on both EVO and Junos OS Routing Engine and then only revert the configuration to dechannlisation and vice versa.PR1665625

  • For GNMI subscriptions, Packet Forwarding Engine doesn't support filtering in subscription paths. So data is streamed from Packet Forwarding Engine ignoring filtering. PR1668911

Infrastructure

  • When upgrading from pre 21.2 to 21.2 and onward, validation and upgrade will fail. The upgrading requires using of 'no-validate' knob. PR1568757

  • Below IPC timeouts logs can be seen for statistics query to kernel(queried from cli or daemons querying internally)when there is config 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 config to avoid IPC timeout errors. # set system stats-timeout-lifetime 15 # commitPR1629930

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 and EX9200 serial 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

Segment Routing

  • You can use IPv6 loopback address only as remote host address and cannot use as transit address in the segment ID (SID) list.

  • An SID stack on ingress supports upto 6 SIDs.

  • The srv6 spring-te sids-stack ping and traceroute commands are supported only in operational mode.

  • You cannot enter duplicate SIDs for srv6 spring-te sids-stack ping and traceroute commands.

  • SRv6 traceroute supports base ISIS instance.

Services Applications

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

VPNs

  • In some scenario(e.g configuring firewall filter) sometimes srx5K might show obsolete IPsec SA and NHTB entry even when the peer tear down the tunnel. PR1432925