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 16.1R1 for MX Series.

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

Bridging and Learning

  • Clearing bridge statistics in PBB-EVPN—Junos OS does not support clearing of bridge statistics for provider backbone bridging EVPN (PBB-EVPN).

Routing Protocols

  • BGP advertises inactive routes when advertise-inactive statement is not configured—When BGP advertises a network layer reachability information (NLRI) with a label, and the advertised route resides in routing table such as inet.3, Junos OS automatically advertises such inactive routes even if you have not configured the advertise-inactive statement.

Software Installation and Upgrade

  • Option upgrade-with-config Accepts Only Configuration Files with Extension .text or .xml (MX Series)—In the request system software add command, the upgrade-with-config option does not apply the configuration if the configuration file has the extension .txt. This option accepts only files with the extension .text or .xml.

Subscriber Management and Services

  • 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, 15.1, and 16.1, ensure that the subscriber-awareness statement is not set.

  • Enhanced subscriber management performance and scale (MX Series)—Starting in Junos OS Release 16.1, subscriber management supports a denser subscriber scale per platform, per line card, and per port. It also provides improved performance of call setup rates. These enhancements are available through a software upgrade, which retains feature parity with existing broadband edge implementations, except as noted for “enhanced subscriber management” in these release notes. New hardware is not required.

    The increased scale and faster setup rates apply to PPP client scaling, PPP LAC sessions, LAC and termination and aggregation (PTA) combinations, and PPP client scaling over LNS on the PPP interface for IPv4, IPv6, and concurrent sessions. It also applies to DHCP client scaling stateless address autoconfiguration (SLAAC), IPv6 over Ethernet, and DHCPv4 clients.

  • Dynamic provisioning in Layer 2 wholesaling (MX Series)—Starting with Release 15.1R3, Junos OS does not support dynamic VLAN mapping into VPLS instances. (You can still configure static VLAN interface mapping to VPLS instances.) By extension, dynamic provisioning for Layer 2 wholesaling is also not supported in this release.

    The following example shows the statements that are not currently available (encapsulation vlan-vpls and family vplsat the [edit dynamic interfaces] hierarchy level):

    interfaces {     
    "$junos-interface-ifd-name" {
    unit "$junos-interface-unit" {
    encapsulation vlan-vpls
    vlan-id "$junos-vlan-id";
    family vpls;

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.


  • Traffic stops flowing when different VLAN IDs are configured (PBB-EVPN)—PBB-EVPN does not support different VLAN IDs under I-Component BDs that are extended into different PEs. Packets will not forward properly unless all of the PE VLAN IDs in the extended I-Component have the same value.

Related Documentation

Modified: 2017-07-24