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

No index entries found.

New and Changed Features

This section describes the new features and enhancements to existing features in Junos OS Release 15.1F3 for the MX Series.


  • New Routing Engine RE-S-X6-64G (MX240, MX480, and MX960)—Starting in Junos OS Release 15.1F4, the Routing Engine RE-S-X6-64G is supported on MX240, MX480, and MX960 routers. This Routing Engine has an increased computing capability and scalability to support the rapid rise in the data plane capacity. The Routing Engine is based on a modular virtualized architecture and leverages the hardware-assisted virtualization capabilities.

    Note: Subscriber services and virtual-chassis support is not available in Junos OS 15.1Fx releases.

    The Routing Engine has a 64-bit CPU and supports a 64-bit kernel and 64-bit applications. With its multicore capabilities, the Routing Engine supports symmetric multiprocessing in the Junos OS kernel and hosted applications.

    Note: The Routing Engine RE-S-X6-64G is supported only on SCBE2, and it is not compatible with the SCB or the SCBE.

  • New rate-selectable MPC MPC7E-MRATE (MX2020, MX2010, MX960, MX480, and MX240)—Starting in Junos OS Release 15.1F4, the rate-selectable MPC MPC7E (Multi-Rate) (model number: MPC7E-MRATE) is supported on MX2020, MX2010, MX960, MX480, and MX240 routers.

    The main features of the MPC7E-MRATE MPC are the following:

    • Line-rate throughput of up to 480 Gbps on MX240, MX480, and MX960 routers.
    • Line-rate throughput of up to 400 Gbps on the MX2000 line of routers.
    • Twelve ports that can each be configured as a 40-Gigabit Ethernet port or as four 10-Gigabit Ethernet ports by using a breakout cable. The ports support quad small-form factor pluggable plus (QSFP+) transceivers.
    • Four ports—0/2, 0/5, 1/2, and 1/5—out of the twelve ports can be configured as 100-Gigabit Ethernet ports.
    • You can configure different combinations of port speeds as long as the aggregate capacity per group of six ports labeled 0/0 through 0/5 does not exceed 240 Gbps. Similarly, aggregate capacity per group of the other six ports labeled 1/0 through 1/5 must not exceed 240 Gbps.

    Note: To use the MPC7E-MRATE MPC, you must download and install the Junos Continuity software package for Junos OS Release 15.1F4.

General Routing

  • Support for virtualization on RE-S-X6-64G (MX240, MX480, MX960, MX2010, and MX2020)—The Routing Engine RE-S-X6-64G supports virtualization for the following platforms:

    • MX240, MX480, and MX960—Junos OS Release 15.1F3 and later
    • MX2010 and MX2020—Junos OS Release 15.1F5 and later

    Virtualization enables the router to support multiple instances of Junos OS and other operating systems on the same Routing Engine. However, for Junos OS Release 15.1F3, one instance of Junos OS, which runs as a guest operating system, is launched by default. The user needs to log in to this instance for operations and management.

    With virtualization of the Routing Engine, Junos OS supports new request and show commands associated with host and hypervisor processes. The commands are related to:

    • Reboot, halt, and power management for the host
    • Software upgrade for the host
    • Disk snapshot for the host
  • Support for the combined operation of Synchronous Ethernet and Precision Time Protocol or hybrid mode (MX104)—A combined operation of Synchronous Ethernet and Precision Time Protocol (PTP), also known as hybrid mode, is supported on the MX104 routers. In hybrid mode, the Synchronous Ethernet equipment clock (EEC) derives the frequency from Synchronous Ethernet and the phase and time of day from PTP (also known as IEEE 1588v2) for time synchronization.

    Synchronous Ethernet and PTP provide frequency and phase synchronization; however, the accuracy in the order of nanoseconds is difficult to achieve through either PTP or Synchronous Ethernet, and they do not support a large number of network hops. Hybrid mode resolves these issues by extending the number of network hops and also provides the clock synchronization accuracy in the order of tens of nanoseconds.

    To configure hybrid mode, include the hybrid synchronous-ethernet-mapping clock-source ip-address interface interface-name1 statement at the [edit protocols ptp slave] hierarchy level.

    To set the Ethernet Synchronization Message Channel (ESMC) from the PTP clock class, include the convert-clock-class-to-quality-level statement at the [edit protocols ptp slave] hierarchy level.

    To override the default PTP clock class to ESMC mapping, include the clock-class-to-quality-level-mapping quality-level ql-value clock-class clock-class-value statement at the [edit protocols ptp slave] hierarchy level, where clock-class indicates the current state of the clock and the quality-level indicates the clock type.

    Note that if the selected Synchronous Ethernet reference fails, the router continues to work in PTP mode. You can use the show ptp hybrid status operational command to find the current operating mode.


    • To switch between the PTP and Synchronous Ethernet modes, you must first deactivate the configuration for the current mode and then commit the configuration. Wait for 30 seconds, configure the new mode and its related parameters, and then commit the configuration.
    • Hybrid mode is not supported on integrated routing and bridging (IRB) and aggregated Ethernet interfaces configured on MX104 routers.
    • Unified in-service software upgrade (unified ISSU) is not supported when clock synchronization is configured for hybrid mode on MX104 routers.
  • Support for PTP over IRB interfaces (MX104)—Starting in Junos OS Release 15.1F5, MX104 routers support Precision Time Protocol (PTP) over integrated routing and bridging (IRB) interfaces. In releases before Junos OS Release 15.1F5, MX104 routers support PTP over physical Ethernet interfaces only.


  • Router telemetry data for hardware and software (MX Series)—Starting in Junos OS Release 15.1F3, you can configure MX Series routers to export telemetry data from supported interface hardware. Line card sensor data such as interface RSVP TE LSP events are sent directly to configured collection points without involving polling. You configure all parameters at the [edit services analytics] hierarchy level. You can configure the exact interfaces and LSPs for export statistics using regular expression resource filter matches. Supported MPC hardware on MX Series routers is MPC1 through MPC6E.


  • Protection against label spoofing or errant label injection across ASBRs (M Series, MX Series, and T Series)—Starting with Junos OS Release 15.1F2, you can use regular BGP implicit and explicit export policies to restrict VPN ASBR peer route advertisement to a given routing instance.

    This is especially useful in the context of Inter-AS VPN Option-B ASBRs because it prevents a peer ASBR in a neighboring AS from spoofing or unintentionally injecting a VPN label intended for a different peer AS or intra-AS into the protected AS. In other words, service providers can configure a common ASBR so it does not accept MPLS packets from a peer ASBR unless the label has been explicitly advertised to the common ASBR.

    Two new commands are introduced to provide this protection: mpls-forwarding at the [edit routing-instances name instance-type mpls-forwarding] hierarchy level and forwarding-context at the [edit protocols bgp group group-name neighbor address], hierarchy level.

  • SAFI 129 NLRI compliance with RFC 6514 (MX Series)—Starting with Junos OS Release 15.1F2, the NLRI format available for BGP VPN multicast is changing from the de facto format of SAFI 128 to SAFI 129 as defined in RFC 6514. SAFI 128 uses length, label, prefix. SAFI 129 uses length, prefix.

    To use SAFI 129, enable the rfc6514-compliant-safi129 statement at any of the following hierarchy levels: [edit protocols bgp], [edit protocols bgp group group-name], or [edit protocols bgp group group-name neighbor address].

  • Latency fairness optimized multicast (MX Series)—Starting with Junos OS Release 15.1F3, you can reduce latency in the multicast packet delivery by optimizing multicast packets sent to the Packet Forwarding Engines. You can achieve this by enabling the ingress or local-latency-fairness option in the multicast-replication configuration statement at the [edit forwarding-options] hierarchy level. The multicast-replication statement is supported only on platforms with the enhanced-ip mode enabled. This feature is not supported in VPLS networks and Layer 2 bridging.

Network Management and Monitoring

  • SNMP support for fabric queue depth, WAN queue depth, and fabric counter (MX240, MX480, MX960, MX2010, and MX2020)—Starting with Release 15.1F3, Junos OS provides SNMP support for WAN queue depth, fabric queue depth, and fabric counter. The following SNMP MIB tables include the associated objects:
    • jnxCosQstatTable table
    • jnxCosIngressQstatTable table
    • jnxFabricMib table

    In addition, this feature supports the following traps for the Packet Forwarding Engine resource monitoring MIBs:

    • jnxPfeMemoryTrapVars
    • jnxPfeMemoryNotifications
  • Support for Timing MIB on MX104 router—Starting in Junos OS Release 15.1F5, MX104 3D Universal Edge Router supports the timing feature. A new enterprise-specific MIB, Timing Feature Defect/Event Notification MIB, has been added to support this feature. The trap notifications are disabled by default. To enable SNMP trap notifications for timing events and defects, include the timing-events statement at the [edit snmp trap-group trap-group object categories] hierarchy level.

Platform and Infrastructure

  • Virtual MX Series router (vMX)—Starting in Junos OS Release 15.1F3, you can deploy vMX routers on x86 servers. vMX supports most of the features available on MX Series routers and allows you to leverage Junos OS to provide a quick and flexible deployment. vMX provides the following benefits:
    • Optimizes carrier-grade routing for the x86 environment
    • Simplifies operations by consistency with MX Series routers
    • Introduces new services without reconfiguration of current infrastructure
  • Performance mode is default for chassis (vMX)—Starting in Junos OS Release 15.1F5, performance mode is enabled by default for the chassis. Performance mode needs more vCPUs and memory to run at higher bandwidth, while lite mode needs fewer vCPUs and memory to run at lower bandwidth. You enable lite mode by configuring the lite-mode option at the [edit chassis fpc 0] hierarchy level.

Subscriber Management and Services (MX Series)

  • New support for Framed-IP-Netmask for access-internal routes (MX Series)—Starting in Junos OS Release 15.1F3, the mask value returned by RADIUS in the Framed-IP-Netmask attribute during PPP negotiation is considered for application to the access-internal route for the subscriber session. In earlier releases, the attribute mask is ignored and a /32 netmask is always applied, with the consequence that the address is set to the value of the Framed-IP-Address attribute returned by RADIUS.

    Now, when the SDB_FRAMED_PROTOCOL attribute is equal to AUTHD_FRAMED_PROTOCOL_PPP, the value of SDB_USER_IP_MASK is set to by default. This value is overridden by the Framed-IP-Netmask value, if present.

    The IP Netmask field in the output of the show subscribers command now displays the default value of or the actual value of Framed-IP-Netmask only when the SDB_FRAMED_PROTOCOL attribute is equal to AUTHD_FRAMED_PROTOCOL_PPP.


  • VPLS dynamic profiles not supported with 64-bit rpd (MX Series)— Starting with Junos OS Release 15.1F3, virtual private LAN service (VPLS) dynamic profiles are not supported with the 64-bit mode routing protocol process (rpd). A new system log error (RPD_DYN_CFG_64RPD_UNSUPPORTED) is displayed when this condition occurs indicating that rpd failed to notify the dynamic configuration clients about its availability to process the dynamic configuration requests. To enable the VPLS dynamic profiles configuration and use 32-bit mode, configure rpd by using the set system process routing force-32-bit command in the CLI.

Related Documentation

Modified: 2016-08-18