Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

New and Changed Features

 

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

High Availability and Resiliency (HA)

  • Unified ISSU support for P2-10G-40G-QSFPP PIC and P2-100GE-OTN PIC (PTX5000)—Starting with Junos OS Release 15.1, unified in-service software upgrade (ISSU) is supported on P2-10G-40G-QSFPP PIC and on P2-100GE-OTN PIC on FPC2-PTX-P1A FPC in PTX5000 routers. Unified ISSU enables you to upgrade from an earlier Junos OS release to a later one with no disruption on the control plane and with minimal disruption of traffic.

Interfaces and Chassis

  • Support for including Layer 2 overhead in interface statistics (PTX Series)—Starting in Junos OS Release 15.1, support is added to account for the Layer 2 overhead size (header and trailer) for both input and output interface statistics in PTX Series routers.

  • Support for dual-rate speed (PTX Series)—Starting in Junos OS Release 15.1, support for dual rate for the 24-port 10-Gigabit Ethernet PIC (P1-PTX-24-10GE-SFPP) enables you to switch all port speeds to either 1-Gigabit Ethernet or 10-Gigabit Ethernet. The default is 10 Gbps. All ports are configured to the same speed; there is no mixed-rate-mode capability. You can use either the SFP-1GE-SX or the SFP-1GE-LX transceiver for 1 Gbps. Changing the port speed causes the PIC to reboot.

    To configure all ports on the P1-PTX-24-10GE-SFPP to operate at 1 Gbps, use the speed 1G statement at the [edit chassis fpc fpc-number pic pic-number] hierarchy level. To return all ports to the 10-Gbps speed, use the delete chassis fpc fpc-number pic pic-number speed 1G command.

    [See speed (24-port and 12-port 10 Gigabit Ethernet PIC) and 10-Gigabit Ethernet PIC with SFP+ (PTX Series).]

  • Support for mixed-rate aggregated Ethernet bundles and per-port pseudowire CoS classification on P2-10G-40G-QSFPP PIC and P2-100GE-OTN PIC (PTX5000)—Starting with Junos OS Release 15.1, you can perform the following actions on the P2-10G-40G-QSFPP PIC and the P2-100GE-OTN PIC on PTX5000 routers:

    • Configure the member links with any combination of rates—10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet—on an aggregated Ethernet bundle, thereby enabling egress unicast traffic load balancing based on the egress link rate.

    • Classifying port-based pseudowire class of service (CoS) classification, which includes Layer 3 IPv4, IPv6, and MPLS classification for interfaces with ethernet-ccc encapsulation.

  • Synchronous Ethernet support for P2-10G-40G-QSFPP PIC, P2-100GE-CFP2 PIC, and P2-100GE-OTN PIC (PTX5000)—Starting with Junos OS Release 15.1, synchronous Ethernet is supported on the P2-10G-40G-QSFPP PIC, P2-100GE-CFP2 PIC, and P2-100GE-OTN PIC on FPC2-PTX-P1A FPC in PTX5000 routers. Synchronous Ethernet (ITU-T G.8261 and ITU-T G.8264) is a physical layer technology that functions regardless of the network load and supports hop-by-hop frequency transfer, where all interfaces on the trail must support synchronous Ethernet. It enables you to deliver synchronization services that meet the requirements of the present-day mobile network, as well as future LTE-based infrastructures.

  • CFP-100GBASE-ZR (PTX Series)—In Junos OS Release 13.3R6, 14.1R4, 14.2R3, and 15.1R1 and later, the CFP-100GBASE-ZR transceiver provides advanced dual polarization-quadrature phase shift keying (DP-QPSK) coherent digital signal processing (DSP) and forward error correction (FEC)-enabled robust tolerance to optical impairments and supports 80 km reach over single-mode fiber. The transceiver is not specified as part of IEEE 802.3 but is built according to Juniper Networks specifications. The following interface module supports the CFP-100GBASE-ZR transceiver:

    • 100-Gigabit Ethernet PIC with CFP (P1-PTX-2-100GE-CFP)

    For more information about the interface modules, see the “Cables and Connectors” section in the PTX Series Interface Module Reference.

    [See 100-Gigabit Ethernet 100GBASE-R Optical Interface Specifications and Supported Network Interface Standards by Transceiver for PTX Series Routers.]

IPv6

Junos OS XML API and Scripting

  • Support for replacing patterns in configuration data within NETCONF and Junos XML protocol sessions (PTX Series)—Starting in Junos OS Release 15.1, you can replace variables and identifiers in the candidate configuration when performing a <load-configuration> operation in a Junos XML protocol or NETCONF session. The replace-pattern attribute specifies the pattern to replace, the with attribute specifies the replacement pattern, and the optional upto attribute indicates the number of occurrences to replace. The scope of the replacement is determined by the placement of the attributes in the configuration data. The functionality of the attribute is identical to that of the replace pattern configuration mode command in the Junos OS CLI.

    [See Replacing Patterns in Configuration Data Using the NETCONF or Junos XML Protocol.]

  • Junos OS SNMP scripts to support custom MIBs (PTX Series)—Starting with Junos OS Release 15.1, you can use Junos SNMP scripts to support custom MIBs until they are implemented in Junos OS. SNMP scripts are triggered automatically when the SNMP manager requests information from the SNMP agent for an object identifier (OID) that is mapped to an SNMP script for an unsupported OID. The script acts like an SNMP subagent, and the system sends the return value from the script to the network management system (NMS).

    [See SNMP Scripts Overview.]

Management

  • Support for enforcing RFC-compliant behavior in NETCONF sessions (PTX Series)—Starting in Junos OS Release 15.1, you can require that the NETCONF server enforce certain behaviors during the NETCONF session by configuring the rfc-compliant statement at the [edit system services netconf] hierarchy level. When you configure the rfc-compliant statement, the NETCONF server explicitly declares the NETCONF namespace in its replies and qualifies all NETCONF tags with the nc prefix. Also, <get> and <get-config> operations that return no configuration data do not include an empty <configuration> element in RPC replies.

    [See Configuring RFC-Compliant NETCONF Sessions.]

  • New YANG features including configuration hierarchy must constraints published in YANG and a new module that defines Junos OS YANG extensions (PTX Series)—Starting in Junos OS Release 15.1, the Juniper Networks configuration YANG module includes configuration constraints published using either the YANG must statement or the Junos OS YANG extension junos:must. Constraints that cannot be mapped directly to YANG’s must statement, which include expressions containing special keywords or symbols such as all, any, unique, $, __, and wildcard characters, are published using junos:must.

    The new junos-extension module contains definitions for Junos OS YANG extensions including the must and must-message keywords. The junos-extension module is bound to the namespace URI http://yang.juniper.net/yang/1.1/je and uses the prefix junos. You can download Juniper Networks YANG modules from the website, or you can generate the modules by using the show system schema operational mode command on the local device.

    [See Using Juniper Networks YANG Modules.]

MPLS

  • New command to display the MPLS label availability in RPD (PTX Series)—Starting with Junos OS Release 15.1, a new show command, show mpls label usage, is introduced to display the available label space resource in RPD and also the applications that use the label space in RPD. Using this command, the administrator can monitor the available labels in each label space and the applications that are using the labels.

    [See show mpls label usage.]

Routing Protocols

  • BGP PIC for inet (PTX Series)—Beginning with Junos OS Release 15.1, BGP Prefix Independent Convergence (PIC), which was initially supported for Layer 3 VPN routers, is extended to BGP with multiple routes in the global tables such as inet and inet6 unicast, and inet and inet6 labeled unicast. When the BGP PIC feature is enabled on a router, BGP installs to the Packet Forwarding Engine the second best path in addition to the calculated best path to a destination. When an IGP loses reachability to a prefix, the router uses this backup path to reduce traffic loss until the global convergence through the BGP is resolved, thereby drastically reducing the outage duration.

    [See Use Case for BGP PIC for Inet.]

  • Multi-instance support for RSVP-TE (PTX Series)—Beginning with Junos OS Release 15.1, multi-instance support is extended to the existing MPLS RSVP-Traffic Engineering (TE) functionality. This support is available only for a virtual router instance type. A router can create and participate in multiple independent TE topology partitions, which allows each partitioned TE domain to scale independently.

    Multi-instance support is also extended for LDP over RSVP tunneling for a virtual router routing instance. This supports splitting of a single routing and MPLS domain into multiple domains so that each domain can be scaled independently. BGP labeled unicast can be used to stitch these domains for service FECs. Each domain uses intra-domain LDP over RSVP LSP for MPLS forwarding.

    [See Tunneling LDP LSPs in RSVP LSPs Overview.]

  • Selection of backup LFA for OSPF routing protocol (PTX Series)—Starting with Junos OS Release 15.1, the default loop-free alternative (LFA) selection algorithm or criteria can be overridden with an LFA policy. These policies are configured per destination per primary next-hop interface or per destination. These backup policies enforce LFA selection based on admin-group, srlg, node, bandwidth, protection-type, and metric attributes of the backup path. During backup shortest-path-first (SPF) computation, each attribute (both node and link) of the backup path, stored per backup next hop, is accumulated by IGP. For the routes created internally by IGP, the attribute set of every backup path is evaluated against the policy configured per destination per prefix primary next-hop interface. The first or the best backup path is selected and installed as the backup next hop in the routing table.

    [See Example-configuring-backup-selection-policy-for-ospf-protocol.]

  • Remote LFA support for LDP in OSPF (PTX Series)—Beginning with Junos OS Release 15.1, you can configure a remote loop-free alternate (LFA) to extend the backup provided by the LFA in an OSPF network. This feature is useful especially for Layer 1 metro-rings where the remote LFA is not directly connected to the PLR. The existing LDP implemented for the MPLS tunnel setup can be reused for the protection of OSPF networks and subsequent LDP destinations thereby eliminating the need for RSVP-TE backup tunnels for backup coverage.

    [See Example-configuring-remote-lfa-over-ldp-tunnels-in-ospf-networks.]

Software Licensing

  • Licensing enhancements (PTX Series)—Starting with Junos OS Release 15.1R1, licensing enhancements on PTX Series routers enable you to configure and delete license keys in a Junos OS CLI configuration file. The license keys are validated and installed after a successful commit of the configuration file. If a license key is invalid, the commit fails and issues an error message. You can configure individual license keys or multiple license keys by issuing Junos OS CLI commands or by loading the license key configuration contained in a file. All installed license keys are stored in the /config/license/ directory.

    To install an individual license key in the Junos OS CLI, issue the set system license keys key name command, and then issue the commit command.

    For example:

    To verify that the license key was installed, issue the show system license command.

    For example:

    To install multiple license keys in the Junos OS CLI, issue the set system license keys key name command, and then issue the commit command.

    For example:

    To verify that the license key was installed, issue the show system license command.

    To install an individual license key configuration in a file, issue the cat command:

    For example:

    Load and merge the license configuration file.

    For example:

    Issue the show | compare command to see the configuration, and then issue the commit command.

    For example:

    To verify that the license key was installed, issue the show system license command.

    For example:

    To install multiple license keys in a file, issue the cat command:

    For example:

    Load and merge the license configuration file, and then issue the commit command.

    For example:

    To verify that the license key was installed, issue the show system license command.

    You can also delete or deactivate individual and multiple license keys in the Junos OS CLI by issuing the delete system license keys or deactivate system license keys commands. Do not use the request system license delete command to delete the license keys.

    For example, to issue the delete system license keys command:

User Interface and Configuration

  • Support for displaying configuration differences in XML tag format (PTX Series)—Starting with Junos OS Release 15.1, you can use the show compare | display xml command to compare the candidate configuration with the current committed configuration and display the differences between the two configurations in XML tag format.

    [See Understanding the show | compare | display xml Command Output.]

  • Configuring chassis ambient temperature to optimize the power consumption of FPCs (PTX5000)—Starting with Junos OS Release 15.1, the power management feature of the PTX5000 is enhanced to manage the power supplied to the FPCs by configuring the ambient temperature of the chassis. You can set the ambient temperature of the chassis at 25° C or 40° C. On system initialization, the power manager reads the ambient temperature and allocates power to the FPCs according to the power budget policy at that temperature. If any FPC consumes more power than the configured value for more than 3 minutes, the PWR Range Overshoot alarm is raised for that FPC, and the power manager overrides the configured ambient temperature setting of that FPC and resets its ambient temperature to the next higher level and reallocates power according to the new temperature setting. All the overshooting FPCs remain in the dynamic ambient temperature mode until the next reboot, or until you override it with a CLI command. The power manager then resets the power budget of the FRUs, including the overshooting FPCs, according to the configured ambient temperature setting.

    To configure the ambient temperature, include the set chassis ambient-temperature statement at the [edit] hierarchy level.

    Note

    If ambient temperature is not configured, then default ambient temperature is set as 55° C.

    [See Chassis Ambient-Temperature.]

VPNs

  • Segmented inter-area P2MP LSP (PTX Series) —Starting with Junos OS Release 15.1, P2MP LSPs can be segmented at the area boundary. A segmented P2MP LSP consists of an ingress area segment(ingress PE router or ASBR), backbone area segment (transit ABR), and egress area segment (egress PE routers or ASBRs). Each of the intra-area segments can be carried over provider tunnels such as P2MP RSVP-TE LSP, P2MP mLDP LSP, or ingress replication. Segmentation of inter-area P2MP LSP occurs when the S-PMSI auto-discovery routes are advertised, which triggers the inclusion of a new BGP extended community or inter-area P2MP segmented next-hop extended community in the ingress PE router or ASBR, transit ABR, and egress PE routers or ASBRs.

    [See Example: Configuring Segmented Inter-Area P2MP LSP.]