Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

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

  • On MX10008 and MX10016 platforms with JNP10K-LC480 Line Card installed, the remote end of the Ethernet link of the JNP10K-LC480 Line Card goes down when an ISSU (Unified In-Service Software Upgrade) is performed from Junos OS 24.4R2 (or earlier) to Junos OS 25.2R1 (or higher). This causes traffic disruption. PR1880150

  • 1. Exit the CLI and start the session again. 2. Enter configuration mode and then return to operational mode. 3. Run the 'restart management' command. PR1890951

  • NETCONF Server reply to get operation pointed to /components/component[name=""]/state/will not include any OPTICAL_CHANNEL type component data. PR1897729

Class of Service (CoS)

  • When an AE is configured in HCOS mode and COS traffic-control-profile configuration is also attached to IFLSETs of that AE in a single config commit operation, following error log can be seen on the FPC hosting AE member IFDs: [Error] COS SCHED : CosSchedNode::create - adding child node on parent active token:6549 child node: type:IFLSET nodeIndex:4 parent schedMode:Port parent maxLevels:1 node schedLevel:2 The error log appears because in the log, the "parent maxLevels" value is less than the "node schedLevel" value. This happens because AE is still in a transient state moving to HCOS mode when IFLSET config message is also received simultaneously by the FPC software. However once AE has moved to HCOS mode, the IFLSET config message is replayed by the software. The software states are set correctly then and no functional issues are seen. This is thus a false alarm in the given scenario. Issue is applicable for all MX Trio AFT based FPCs - MPC10, MPC11, LC9600, LC4800, MX304. If we want to avoid the error log, we can do a 2-step commit where we activate HCOS on AE interface first and commit, then later activate COS config on AE iflset and commit. PR1905468

Infrastructure

  • When upgrading from releases before Junos OS Release 21.2 to Release 21.2 and onward, validation and upgrade might fail. The upgrade requires using the 'no-validate' option to complete successfully. https://kb.juniper.net/TSB18251 PR1568757

Routing Protocols

  • "advertise-external" feature control-knob behaves at a different scope when a Junos router is acting as pure-PE or RR/ASBR mode for a VPN family. In pure-PE mode, the knob works on per advertised-to-group basis. i.e. an inactive EBGP-route is advertised to a BGP group only if advertise-external is enabled for that group. In RR/ASBR mode, the knob works on global basis, i.e. if it is enabled for any group, an inactive EBGP route in <vrf>.inet.0 is leaked to bgp.l3vpn.0 with the VRF's RD and (assuming unique-RD in use) it is a candidate for advertisement to all BGP groups, export-policy permitting, even if advertise-external is not enabled for those groups. Because there is no path-hiding in bgp.l3vpn.0 table due to unique-RD, advertise-external feature does not further control advertisement of the route to each BGP group. PR1880531

User Interface and Configuration

  • VMX file copy sftp reports error ssh: Could not resolve hostname sftp: Name does not resolve . file copy sftp://10.85.211.4/home/labroot/junk.txt . ssh: Could not resolve hostname sftp: Name does not resolve error: file-fetch failed error: could not fetch local copy of file. PR1869005