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

  • 40g interface does not support EM policy feature, but it will still display in the CLI output of show chassis temp-threshold as it gets created as "et" interface. PR1807219

  • There are no registers in the MX304 PSM to find out feed is connected or not. The only thing that we have in the MX304 PSM is whether the input voltage is zero or not. But that does not confirm whether the feed is connected or not. PR1807254

  • We will see an extra flap of link happening whenever the link come up first time or when we do link enable or disable. This is due to limitation of the marvell device.PR1817595

  • The commit error "Command remap failed" observed on the dual re controller.

    Workaround steps to follow to recover jnu-controller-schema.db:

    • Remove /var/db/vSRX/<versionname_of_satellite_connected> directory from the controller shell.

    • Remove /var/db/jnu_current_sw_version file from the satellite shell.

    • Restart jnu-management from CLI of the satellite.

  • PR1839015

  • When PFE Major/Fatal errors were configured for pfe-reset, MPC7/MPC8/MPC9 FPCs gets into ?HOST LOOPBACK WEDGE? post pfe-reset action triggered by the errors. PR1839071

  • On MX304, during the MIC offline sequence, the following error messages can be intermittently observed for a short period in /var/log/messages [Log] mqss_sched_fab_q_node_is_configured: Queue scheduler node doesn't exist - q_node_num 0 mqss_sched_fab_q_node_is_configured: Queue scheduler node doesn't exist - q_node_num 1 . mqss_sched_fab_q_node_is_configured: Queue scheduler node doesn't exist - q_node_num 255 These error messages are harmless in this context (MIC Offline) and have no functional impact. They can be safely ignored. PR1844325

  • The JNU's design was to bring in the committed config from satellite to controller but it doesn't include the platform-specific default configs that come from various other junos default config files. This configuration is kept local to the satellite. Application match configuration under security policy is one such config for which warning message will be seen in MX controller while using application match as any or any SRX default application. PR1847209

Layer 2 Ethernet Services

  • The issue was seen when test was done back to back GRES within 5 minutes time. This is expected behavior from the system as per current architecture. Wait for sometime before may be 10 minutes or so for subsequent GRES. PR1801234

Platform and Infrastructure

  • With a sensor being subscribed via Junos Telemetry Interface (JTI), after the interface is deleted, deactivated, or disabled, the TCP connection is still established, and the CLI command of show agent sensors still shows the subscription. PR1477790