Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Behavior

 

This section contains the known behaviors, system maximums, and limitations in hardware and software in Junos OS Release 14.1R9 for the M Series, MX Series, and T Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Hardware

  • Support for MIC-3D-8OC3-2OC12-ATM Revision 22 and later—MIC-3D-8OC3-2OC12-ATM Revision 22 is supported only by the following Junos OS releases:

    • Junos OS Release 12.3—12.3R9 and later

    • Junos OS Release 13.3—13.3R6 and later

    • Junos OS Release 14.1—14.1R4 and later

    • Junos OS Release 14.2—14.2R3 and later

    • Junos OS Release 15.1 and later

    You must upgrade to a supported Junos OS release to use MIC-3D-8OC3-2OC12-ATM Revision 22 and later.

Class of Service (CoS)

  • Filtering for Routing Engine sourced packets (MX Series)—Starting in Junos OS Release 14.1, support is added for filtering on Differentiated Services code point (DSCP) and forwarding class for Routing Engine sourced packets. This includes IS-IS packets encapsulated in generic routing encapsulation (GRE). With this change comes a new order of precedence. When upgrading from a previous version of Junos OS where you have both a class of service (CoS) and firewall filter, and both include DSCP or forwarding class filter actions, the criteria in the firewall filter automatically takes precedence over the CoS settings. The same is true when creating new configurations; that is, where the same settings exist, the firewall filter takes precedence over the CoS, regardless of which was created first.

High Availability (HA) and Resiliency

  • The MPC5E, MPC5EQ, and MP6E cards do not support unified ISSU on an MX Series Virtual Chassis.

  • In an MX Series Virtual Chassis configuration, a unified in-service software upgrade (ISSU) from Junos OS Release 14.1 or 14.1R2 to Junos OS Release 14.2 fails with traffic loss. As a workaround, download the latest build of Junos OS Release 14.1R3, which contains a fix for this issue, and perform a unified ISSU to this build from Junos OS Release 14.1R1 or 14.1R2. You can then successfully perform a unified ISSU from the latest build of Junos OS Release 14.1R3 to Junos OS Release 14.2 in an MX Series Virtual Chassis.

Interfaces and Chassis

  • The options alarm low-light-alarm and warning low-light-warning might not work (MX Series) --The options alarm low-light-alarm and warning low-light-warning at the [edit interfaces interface-name optics-options] hierarchy level might not work for the 10G and 100G interfaces of MPC3, MPC4, MPC5, MPC6, MPC7E, MPC8E, and MPC9E on MX Series 3D Universal Edge Routers. These options might not work on MPC3E-3D-NG, MPC3E-3D-NG-Q, MPC2E-3D-NG, and MPC2E-3D-NG-Q when they are installed with Junos Continuity software. This is a known behavior and has no impact on the performance of these line cards.

MPLS

  • Removal of SRLG details from the SRLG table only on the next reoptimization of the LSP–If an SRLG is associated with a link used by an ingress LSP in the router, then on deleting the SRLG configuration from that router, the SRLG gets removed from the SRLG table only on the next reoptimization of the LSP. Until then the output displays Unknown-XXX instead of the SRLG name and a non zero srlg-cost of that SRLG for the run show mpls srlg command.

Software Installation and Upgrade

  • Downgrading to Junos OS Release 12.3 when the configuration includes the targeted-distribution statement—In Junos OS Release 12.3, the targetted-distribution statement at the [edit interfaces demux0 unit logical-unit-number] hierarchy level is misspelled. Starting in Junos OS Release 14.1R5, the spelling for this statement is corrected to targeted-distribution. If you use the misspelled targetted-distribution statement in Junos OS Release 14.1R5 or later, the CLI corrects the spelling to targeted-distribution in your configuration, so existing scripts still work. The correct spelling is not backward compatible; Junos OS Release 12.3 supports only the targetted-distribution spelling. If you downgrade from Release 14.1R5 or later to Release 12.3, all correctly spelled targeted-distribution statements are removed from the configuration, and configuration scripts with the correct spelling fail.

Subscriber Management and Services

  • Commands display different values for the LCP state of a tunneled subscriber on the LAC—The show ppp interface interface-name extensive and show interfaces pp0 commands display different values for the LCP state of a tunneled subscriber on the LAC. The show ppp interface interface-name extensive command displays STOPPED whereas the show interfaces pp0 command displays OPENED (which reflects the LCP state before tunneling). As a workaround, use the show ppp interface interface-name extensive command to determine the correct LCP state for the subscriber.

  • Subscriber management is not supported when the routing protocol daemon (rpd) is running in 64-bit mode. For subscriber management support, rpd must run in 32-bit mode.

  • The all option is not intended to be used as a means to perform a bulk logout of L2TP subscribers. We recommend that you do not use the all option with the clear services l2tp destination, clear services l2tp session, or clear services l2tp tunnel statements in a production environment. Instead of clearing all subscribers at once, consider clearing subscribers in smaller groups, based on interface, tunnel, or destination end point.