Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Known Behavior

This section contains the known behavior, system maximums, and limitations in hardware and software in Junos OS Release 14.2R8 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.


  • 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.

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. PR1014295

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.


  • 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.

Network Management and Monitoring

  • On the MX Series, when there is no traffic, the Qdepth statistics output field in the show class-of-service fabric statistics detail command displays count 0 for all the subfields, except the Max count subfield.
  • On MX Series routers, when you configure multiple prefix lists for endpoint independent filtering, all the prefix lists do not get enabled. As a workaround, to configure multiple prefix lists for endpoint independent filtering, ensure that you use a single commit command to commit the configuration of all the defined prefix lists. If you want to include additional prefixes in the prefix lists, delete all the existing prefix lists and add them again.

Routing Protocols

  • Junos OS displays the configured BGP group description pushed by the remote procedure call (RPC) in the show | compare output even after commit is performed. This occurs due to the use of terminating double quotes in the string inputs, in the RPC XML format. Therefore, as a workaround do not include terminating quotes in strings in any RPC XML configuration to avoid this issue. PR1066084

Software-Defined Networking (SDN)

  • On MX Series routers running OpenFlow v1.3.1 software, flow statistics show that the packet flow is increasing even when the output port link is down. PR987753
  • On MX Series routers running OpenFlow v1.3.1 software, the ADPC might create a core file. Configure enhanced IP network services mode to disable the ADPC. PR988256

Subscriber Management and Services

  • 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.
  • On MX Series routers, when you configure the subscriber-awareness statement on a service set by committing the set services service-set service-set-name service-set-options subscriber-awareness statement, the service sessions fail to create. To avoid this issue, on MX Series routers that support the Service Control Gateway solution, ensure that the Junos OS Mobility package software is installed on the router.

    The Service Control Gateway solution is supported only in 14.1X55 releases. For Junos OS Releases 14.2, and 15.1, ensure that the subscriber-awareness statement is not set.

  • 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 clear services l2tp session all and clear services l2tp destination all commands are not intended to be used as a means to perform a bulk logout of L2TP subscribers. We recommend that you do not use either command in a production environment.

System Logging

  • On MX Series routers, when you configure a rate limit for system log messages by setting the message-rate-limit statement for a multiservices interface, ensure that the syslog host option for that interface is configured. This configuration ensures that the system log statistics reflect the rate limit set for the interface.


  • Default export EVPN policy has been removed (MX Series)—Starting in Junos OS Release 14.2R7 and forward, the hidden default EVPN export policy statement (evpn-pplb) has been removed. To enable and configure load balance per packet for EVPN and PBB-EVPN, use the existing policy statements:
    • set routing-options forwarding-table export evpn-pplb
    • set policy-options policy-statement evpn-pplb from protocol evpn
    • set policy-options policy-statement evpn-pplb then load-balance per-packet

    Note: To support EVPN multihoming, you must configure the load-balance per-packet statement.

Modified: 2017-12-12