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

New and Changed Features

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

Class of Service

  • Change in scaling number for rewrite rules (PTX Series)—Starting with Release 15.1F2, on PTX Series routers, the scaling number for a rewrite rule is reduced by one when the default EXP rewrite is used. This change in scaling number is introduced to:
    • Support all possible combinations of EXP rewrite rules.
    • Fix the issue of incorrect modification of EXP bits of the inner label by the default MPLS EXP rewrite rule during the label pop operation.

Hardware

  • New Routing Engine RE-PTX-X8-64G (PTX5000)—Starting in Junos OS Release 15.1F4, the Routing Engine RE-PTX-X8-64G is supported on PTX5000 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.

    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-PTX-X8-64G is supported only on the new Control Board CB2-PTX.

  • New Control Board support (PTX5000)—Starting with Release 15.1F4, Junos OS supports the Routing Engine RE-PTX-X8-64G with an enhanced Control Board (CB) on PTX5000 routers. The CB supports chassis management and 16 additional 10-Gigabit Ethernet ports with small form-factor pluggable plus transceivers (SFP+) on the front panel of the router to support multichassis applications.

    The enhanced CB consists of the following components:

    • Ethernet switch used for intermodule communication
    • PCI Express bus to connect to the Routing Engine
    • PCI Express switch to connect to the SIBs
    • Switch Processor Mezzanine Board (SPMB)
  • High capacity single-phase AC PDU (PTX5000)—In Junos OS Release 15.1F3, a single-phase AC power distribution unit (PDU)—PDU2-PTX-AC-SP—is introduced to provide power to the PTX5000 chassis. The PDU provides a single-phase AC input connection from the customer’s AC source, an I/O interface to the power supply modules (PSMs), and a DC power connection to the system midplane. The PDU is powered by either eight 30-A or eight 20-A single-phase sources. Each of the eight PSMs connected to the AC PDU receives single-phase input.

  • New horizontal fan tray FAN3-PTX-H (PTX5000)—Starting in Junos OS Release 15.1F3, the FAN3-PTX-H horizontal fan tray is supported on PTX5000 routers.

  • New FPCs FPC3-PTX-U1-L, FPC3-PTX-U1-R, FPC3-PTX-U2-L, FPC3-PTX-U2-R, FPC3-PTX-U3-L, and FPC3-PTX-U3-R (PTX5000)—Starting in Junos OS Release 15.1F3, the FPC3-PTX-U1-L, FPC3-PTX-U1-R, FPC3-PTX-U2-L, FPC3-PTX-U2-R, FPC3-PTX-U3-L, and FPC3-PTX-U3-R FPCs are supported on PTX5000 routers. The FPCs provide the following throughput:

    • FPC3-PTX-U1-L and FPC3-PTX-U1-R—1.0 Tbps
    • FPC3-PTX-U2-L and FPC3-PTX-U2-R—2.0 Tbps
    • FPC3-PTX-U3-L and FPC3-PTX-U3-R—3.0 Tbps

    When installing these third-generation FPCs on the PTX5000 chassis, you must also install the following hardware:

    • New SIB SIB3-PTX5K
    • New horizontal fan tray FAN3-PTX-H

    Some new features provided by these third-generation FPCs can be accessed only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.
    Some of the new features include the following:

    • Filter-based generic routing encapsulation (GRE) for IPv4 and IPv6 tunneling uses firewall filters to provide decapsulation of GRE traffic. The filter-based GRE de-encapsulation also supports routing-instance as an action.
    • promote gre-key statement for configuring gre-key as one of the matches in a filter.
    • gtp-tunnel-endpoint-identifier statement for including hash calculation for IPv4 or IPv6 packets in the GPRS tunneling protocol–tunnel endpoint identifier (GTP-TEID) field hash calculations.
    • Longer configuration ranges for Bidirectional Forwarding Detection (BFD) protocol intervals.
    • Enhanced support for up to two million routes per chassis.
  • New SIB SIB3-PTX5K (PTX5000)—Starting in Junos OS Release 15.1F3, the SIB3-PTX5K SIB is supported on PTX5000 routers.

  • New PIC P3-24-U-QSFP28 (PTX5000)—Starting in Junos OS Release 15.1F3, the PIC P3-24-U-QSFP28 is supported on PTX5000 routers. The P3-24-U-QSFP28 PIC has 24 ports configurable as either 10-Gigabit Ethernet ports or 40-Gigabit Ethernet ports.

    Note: This PIC does not support 100-Gigabit Ethernet ports.

    To install the P3-24-U-QSFP28 PIC, you must have a third-generation FPC installed on your system.

  • New P3-15-U-QSFP28 PIC (PTX5000)—Starting in Junos OS Release 15.1F5, the PIC P3-15-U-QSFP28 is supported on PTX5000 routers that have third-generation FPCs installed.

    Note: To install the P3-15-U-QSFP28 PIC, you must have a third-generation FPC installed on your system.


    Following is the available port configuration for each FPC:

    • FPC3-PTX-U1-L and FPC3-PTX-U1-R—10 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.
    • FPC3-PTX-U2-L and FPC3-PTX-U2-R—10 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.
    • FPC3-PTX-U3-L and FPC3-PTX-U3-R—15 ports configurable as 10-Gigabit Ethernet ports (using a 4x breakout cable), 40-Gigabit Ethernet ports, or 100-Gigabit Ethernet ports.
  • The P1-PTX-24-10G-W-SFPP PIC is supported on third-generation FPCs (PTX5000)—Starting in Junos OS Release 15.1F5, the P1-PTX-24-10G-W-SFPP PIC is supported on PTX Series routers that have third-generation FPCs installed.
  • The P2-10G-40G-QSFPP PIC is supported on third-generation FPCs (PTX5000)—Starting in Junos OS Release 15.1F5, the P2-10G-40G-QSFPP PIC is supported on PTX Series routers that have third-generation FPCs installed.
  • The P2-100GE-OTN PIC is supported on third-generation FPCs (PTX5000)—Starting in Junos OS Release 15.1F5, the P2-100GE-OTN PIC is supported on PTX Series routers that have third-generation FPCs installed.
  • Upgrade of FPCs in an operational PTX5000—Starting in Junos OS Release 15.1F5, you can upgrade the first-generation FPCs or second-generation FPCs to third-generation FPCs in an operational PTX5000.

    You might need to upgrade the following components before you can upgrade the FPCs in a PTX5000:

    • SIBs
    • Fan tray
    • Power distribution unit
    • Power supply module

    (See the PTX5000 Packet Transport Router Hardware Guide.)

  • The ability for third-generation FPCs to interoperate with first-generation and second-generation FPCs (PTX5000)—Starting in Junos OS Release 15.1F5, when third-generation FPCs are installed on a chassis with first-generation and second-generation FPCs, the FPCs can interoperate with each other.

    Note: For the third-generation FPCs to interoperate with the previous FPCs, the enhanced-mode statement cannot be configured on the chassis. Also, the third-generation FPCs can only provide the same functionality as the first-generation and second-genberation FPCs. Any advanced features that third-generation FPCs might provide are disabled.

  • The P1-PTX-2-100G-WDM PIC is supported on third-generation FPCs (PTX5000)—Starting in Junos OS Release 15.1F6, the P1-PTX-2-100G-WDM PIC is supported on PTX Series routers that have third-generation FPCs installed.
  • Integrated photonic line card (IPLC) (PTX3000)—Starting in Junos OS Release 15.1F6, the PTX3000 can provide a fully integrated photonic line system for converged core and metro core packet optical networks running point-to-point and ring topologies. The following optical components are available for the PTX3000:
    • Integrated photonic line card (IPLC) base module—Provides the combined functionality of a 32-port reconfigurable optical add/drop multiplexer (ROADM), optical amplifier, optical equalizer, and optical channel monitor on a single card.
    • IPLC expansion module—Increases the channel capacity of the IPLC node to 64 channels.

    The external optical inline amplifier (optical ILA) provides periodic amplification of the optical line signal to enable long-distance transmission.

    To complete the optical solution, Juniper’s integrated 100G Coherent transponders can be leveraged here, along with the IPLC, IPLC expansion module, optical ILA, and CSD to provide an end-to-end, fully managed packet optical solution.

    You can configure, manage, and monitor the IPLC through Junos Space Connectivity Services Director 2.0.

    Optionally, you can use the Junos OS CLI, or your SNMP management.

  • Third-generation FPCs (PTX3000)—Starting in Junos OS Release 15.1F6, third-generation FPCs are supported on PTX3000 routers. FPC3-SFF-PTX-U1 FPCs (model numbers FPC3-SFF-PTX-U1-L and FPC3-SFF-PTX-U1-R) support 1.0 Tbps of throughput. FPC3-SFF-PTX-U0 FPCs (model numbers FPC3-SFF-PTX-U0-L and FPC3-SFF-PTX-U0-R) support 500 Gbps of throughput.

    Third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) are supported only on a PTX3000 with SIB3-SFF-PTX SIBs. Third-generation FPCs and FPC-SFF-PTX-P1-A first-generation FPCs can interoperate with each other in the same system.

    Some features provided by these third-generation FPCs can be accessed only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level. These features include the following:

    • Filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling.
    • promote gre-key statement for configuring gre-key as one of the matches in a filter.
    • gtp-tunnel-endpoint-identifier statement for including hash calculation for IPv4 or IPv6 packets in the GPRS tunneling protocol–tunnel endpoint identifier (GTP-TEID) field hash calculations.
    • Wider configuration range for Bidirectional Forwarding Detection (BFD) protocol intervals.
    • Support for Layer 3 VPNs. The vrf-table-label statement is supported.
    • Support for destination class usage (DCU) and source class usage (SCU) accounting.
    • Support for up to two million routes in the forwarding table.

    Note: For third-generation FPCs to interoperate with FPC-SFF-PTX-P1-A first-generation FPCs, the enhanced-mode statement cannot be configured on the chassis. Any advanced features that third-generation FPCs may provide are disabled.

  • SIB3-SFF-PTX SIBs (PTX3000)—Starting in Junos OS Release 15.1F6, SIB3-SFF-PTX SIBs are supported on PTX3000 routers. The SIB3-SFF-PTX SIBs are required with third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1). The SIB3-SFF-PTX SIBs also support FPC-SFF-PTX-P1-A first-generation FPCs—third-generation FPCs and FPC-SFF-PTX-P1-A first-generation FPCs can interoperate with each other in the same system.
  • P3-24-U-QSFP28 PIC supported on third-generation FPC (PTX3000)—Starting in Junos OS Release 15.1F6, the P3-24-U-QSFP28 PIC is supported on FPC3-SFF-PTX-U1 FPCs on the PTX3000. The P3-24-U-QSFP28 PIC has 24 ports configurable as either 10-Gigabit Ethernet ports or 40-Gigabit Ethernet ports. To configure the port speed, use the following command:
    [edit chassis]user@host# set fpc slot-number pic pic-number port port-number port-speed (10G | 40G)
  • P1-PTX-24-10G-W-SFPP, P2-10G-40G-QSFPP, and P2-100GE-OTN PICs supported on third-generation FPCs (PTX3000)—Starting in Junos OS Release 15.1F6, the P1-PTX-24-10G-W-SFPP, P2-10G-40G-QSFPP, and P2-100GE-OTN PICs are supported on third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) on the PTX3000.
  • Upgrading to third-generation FPCs and SIBs in an operational router (PTX3000)—Starting in Junos OS Release 15.1F6, you can upgrade to third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) and SIB3-SFF-PTX SIBs in an operational PTX3000.
  • 5-port 100-Gigabit DWDM OTN PIC with CFP2 (PTX3000 and PTX5000)—Starting with Release 15.1F6, Junos OS supports the 5-port 100-Gigabit dense wavelength division multiplexing (DWDM) optical transport network (OTN) PIC (PTX-5-100G-WDM) with CFP2 analog coherent optical (CFP2-ACO) pluggable optics on third-generation FPCs on the PTX3000 and PTX5000 series routers. The 5-port 100-Gigabit DWDM OTN PIC supports the following features:
    • Transparent transport of five 100-Gigabit Ethernet signals with optical channel transport unit, OTU4 (V) framing.
    • Dual-polarization quadrature phase shift keying (DP-QPSK) modulation with coherent receiver and soft-decision forward error correction (SD-FEC) for long-haul and metro applications.
    • International Telecommunication Union (ITU)-standard OTN performance monitoring and alarm management
    • Extensive optical, digital signal processing (DSP) and bit error ratio (BER) performance monitoring statistics for the optical link.

General Routing

  • Support for virtualization on RE-PTX-X8-64G (PTX5000)—Starting with Junos OS Release 15.1F3, the Routing Engine RE-PTX-X8-64G for PTX5000 supports virtualization.

    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

Interfaces and Chassis

  • Support for including LOCAL-FAULT and REMOTE-FAULT information (PTX Series)—Starting in Junos OS Release 15.1F3, PTX Series routers add the ability to display LOCAL-FAULT and REMOTE-FAULT information in the output of the show interfaces et-fpc/pic/port command.
  • Support for configuring chassis temperature thresholds (PTX Series)—Starting in Junos OS Release 15.1F3, the chassis [fpc| sib| cb] statement is supported to define the thresholds at which the fans change speeds, the system is shut down, or an alarm is sent. The chassis [fpc| sib| cb] threshold action to take configuration statement is configured at the [edit] hierarchy level.

  • Support for configuring the port speed (PTX5000)—Starting in Junos OS Release 15.1F3, the port speed configuration statement is used to configure the port speed on interface modules that support multiple port speeds. The port-speed 10G | 40G | 100G configuration statement is configured at the [edit chassis fpc slot-number pic pic-number port port-number] hierarchy level.

  • Support for configuring interface loopback (PTX5000)—Starting in Junos OS Release 15.1F3, the loopback (local | remote) configuration statement is used to specify whether local or remote loopback is enabled. Specifying this information enables you to test the transceiver cable connection from the far end to the retimer interface without changing the cable. The loopback (local | remote) configuration statement is configured at the [edit interfaces interface-name gigether-options] hierarchy level.

  • Support for configuring the LED on a port to flash (PTX5000)—Starting in Junos OS Release 15.1F3, the led-beacon command causes the LED for the specified port to flash green. This enables you to physically locate a specific optic port on the PIC. The led-beacon configuration statement is configured at the [edit interfaces interface-name (with port number)] hierarchy level.

  • Support for DCU and SCU accounting (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F5 for PTX5000 and Junos OS Release 15.1F6 for PTX3000, destination class usage (DCU) and source class usage (SCU) accounting are supported on routers that have third-generation FPCs installed.

    Note: DCU and SCU accounting are supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

  • Support for unicast RPF (PTX Series)—Starting in Junos OS Release 15.1F6, you can configure unicast reverse path forwarding (RPF) to reduce the impact of denial of service (DoS) attacks on PTX Series routers that have third-generation FPCs installed.

    Note: Unicast RPF is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

  • Support for configuring port speed (PTX3000)—Starting in Junos OS Release 15.1F6, the port speed configuration statement is used to configure the port speed on PICs that support multiple port speeds. The port-speed (10G | 40G | 100G) configuration statement is configured at the [edit chassis fpc slot-number pic pic-number port port-number] hierarchy level.
  • Support for configuring interface loopback (PTX3000)—Starting in Junos OS Release 15.1F6, the loopback (local | remote) configuration statement is used to specify whether local or remote loopback is enabled. Specifying this information enables you to test the transceiver cable connection from the far end to the retimer interface without changing the cable. The loopback (local | remote) statement is configured at the [edit interfaces interface-name gigether-options] hierarchy level.
  • Support for configuring the LED on a port to flash (PTX3000)—Starting in Junos OS Release 15.1F6, the led-beacon command causes the LED for the specified port to flash green. When the LED lights green, you can physically locate a specific optic port on the PIC. You configure the led-beacon statement at the [edit interfaces interface-name (with port number)] hierarchy level.
  • Synchronous Ethernet clock synchronization on third-generation FPCs (PTX3000)—Starting in Junos OS Release 15.1F6, Synchronous Ethernet clock synchronization is supported on third-generation FPCs (FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1) on the PTX3000.

Management

  • Junos Telemetry Interface enhancements (PTX Series)—Junos Telemetry Interface enables you to export telemetry data from supported interface hardware. Line card sensor data, such as interface events, are sent directly to configured collection points without involving polling. All parameters are configured at the [edit services analytics] hierarchy level. Starting with Junos OS Release 15.1F6, you can export LSP statistics and firewall filter statistics. To enable the exporting of LSP statistics, include the resource /junos/services/label-switched-path/usage statement at the [edit services analytics sensor sensor-name] hierarchy level. Only dynamically configured LSPs and RSVP LSPs are supported. Statistics are not collected for P2MP LSPs, LDP LSPs, or static LSPs. To enable the exporting of firewall filter statistics, include the resource /junos/system/linecard/firewall/ statement at the [edit services analytics sensor sensor-name] hierarchy level. Only interfaces configured on FPC3 are supported. FPC2 is not supported.

MPLS


  • Egress peer engineering of service labels (BGP, MPLS) and egress peer protection for BGP-LU (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F4 for PTX5000 and Junos OS Release 15.1F6 for PTX3000, you can enable traffic engineering of service traffic, such as MPLS LSP traffic between autonomous systems (ASs), using BGP labeled unicast for optimum utilization of the advertised egress routes. You can specify one or more backup devices for the primary egress AS boundary router. Junos OS installs the backup path in addition to the primary path in the MPLS forwarding table, which enables MPLS fast reroute (FRR) when the primary link fails. It provides support for the FRR protection backup scheme to do an IP lookup to determine a new egress interface.

  • Support for IS-IS segment routing (PTX Series)—Starting with Junos OS Release 15.1F5, IS-IS segment routing support is enabled through MPLS. Currently, label advertisements are supported for IS-IS only. IS-IS creates an adjacency segment per adjacency, per level, and per address family (one each for IPv4 and IPv6). Junos OS IS-IS implementation allocates node segment label blocks in accordance with the IS-IS protocol extensions for supporting segment routing node segments and provides a mechanism to the network operator to provision an IPv4 or IPv6 address family node segment index. To configure segment routing, use the following configuration statements at the [edit protocols isis] hierarchy level:
    • no-advertise-adjacency-segment—Disable advertising of the adjacency segment on all levels for a specific interface.
    • node-segment—Enable source packet routing at all levels.
    • source-packet-routing—Enable the source packet routing feature.
    • use-source-packet-routing—Enable use of source packet routing node segment labels for computing backup paths for normal IPv4 or IPv6 IS-IS prefixes and primary IS-IS source packet routing node segments.
  • Support for IPv6 tunneling over an MPLS-based IPv4 network (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F5 for PTX5000 and Junos OS Release 15.1F6 for PTX3000, IPv6 tunneling over an MPLS-based IPv4 network using IPv6 Provider Edge (6PE) is supported on routers that have third-generation FPCs installed.

Multicast

  • SAFI 129 NLRI compliance with RFC 6514 (PTX Series)—Starting with Junos OS Release 15.1F2, the Network Layer Reachability Information (NLRI) format available for BGP VPN multicast is changing from the de facto format of Subsequent Address Family Identifier (SAFI) 128 to Subsequent Address Family Identifier (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].

Network Management and Monitoring

  • Support for accounting profiles (PTX Series)—Starting in Junos OS Release 15.1F6, you can configure accounting profiles to collect data on PTX Series routers that have third-generation FPCs installed.

    Note: Configuring accounting profiles is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

Routing Policy and Firewall Filters

  • Support for firewall feature matching on gre-key (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F3 on PTX5000 and Junos OS Release 15.1F6 on PTX3000, the promote gre-key statement is supported to configure gre-key as one of the matches in a filter. When promote gre-key is configured and gre-key is used in any of the terms in a filter, the entire filter is compiled in a way that optimizes its performance for gre-key matching. The promote gre-key configuration statement is configured at the [edit firewall family family-name filter filter-name] hierarchy level.
  • Support for configuring the GTP-TEID field for GTP traffic (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F3 for PTX5000 and Junos OS Release 15.1F6 for PTX3000, the gtp-tunnel-endpoint-identifier statement is supported to configure the hash calculation of IPv4 or IPv6 packets that are included in the GPRS tunneling protocol–tunnel endpoint identifier (GTP-TEID) field hash calculations. The gtp-tunnel-endpoint-identifier configuration statement is configured at the [edit forwarding-options hash-key family inet layer-4] or [edit forwarding-options hash-key family inet6 layer-4] hierarchy level.
  • Support for the no-decrement-ttl tunneling attribute (PTX Series)—Starting in Junos OS Release 15.1F6, you can configure the no-decrement-ttl tunneling attribute for filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling.

    Note: The no-decrement-ttl tunneling attribute is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

Routing Protocols

  • IS-IS purge originator identification TLV (PTX Series)—Beginning with Release 15.1F4, Junos OS supports RFC 6232, Purge Originator Identification TLV for IS-IS, which defines a type, length, and value (TLV) for identifying the origin of a purge initiated by the IS-IS protocol. You can configure this feature to add this TLV to a purge along with the system ID of the Intermediate System (IS) that has initiated the purge. This makes it easier to locate the origin of the purge and its cause.
  • Restricting LSP flooding over IS-IS interfaces (PTX Series)—Beginning with Junos OS Release 15.1F5, the IS-IS protocol can restrict flooding of LSAs to control sharing of routes between multiple level 2 metro ring networks. You can segregate both level 1 and level 2 networks into flood groups by using area IDs as tags to identify a flood group. Configure interfaces with specific area IDs to modify the flooding behavior as per your requirements. For example, when a router is connected to f metro ring networks, by default all the routers in the five rings are flooded with all LSP routes. You can configure five distinct flood groups on the ring-facing interfaces on the pre-aggregation device to restrict LSP flooding to a specific area. Configure area IDs on interfaces to segregate them into flood groups. LSPs that belong to the specified area only are flooded through these interfaces. However, self-originated LSPs are not affected by this configuration.
  • BGP labeled unicast supports stack of labels (PTX Series)—Beginning with Release 15.1F5, Junos OS supports RFC 3107, Carrying Label Information in BGP-4, that allows stacking of multiple labels in the BGP unicast label. In earlier Junos OS releases, only one label per prefix was supported in the BGP unicast label. Junos OS now supports a label stack of up to five labels per prefix in the BGP labeled unicast updates. BGP labeled unicast updates with more than five labels are not supported, and Junos OS sets their state to hidden. This feature allows the use of BGP unicast label stack to control packet forwarding in the network and to reflect the BGP unicast label stack routes to its clients without changing the next hop.
  • Micro loop avoidance when IS-IS link fails (PTX Series)—Beginning with Release 15.1F5, Junos OS allows a device to defer IS-IS route download when an IS-IS link fails–to avoid micro loops. When local links go down, the IS-IS protocol floods an entire area with the database. If the node connected to the local interface that has failed converges faster than the neighboring node, then the connected node redirects traffic to the converged path. This redirection can result in micro looping of traffic until the neighboring node converges. When the primary path of a protected node fails, the connected node, does not need to converge quickly if the configured backup path is not impacted. In this case, traffic flow towards a converged path is deferred until all other nodes are converged.
  • System performance enhancements for rpd, Packet Forwarding Engine, and kernel (PTX Series)—Beginning with Junos OS Release 15.1F6, performance of the routing protocol process (rpd), the Packet Forwarding Engine, and the kernel is enhanced to speed up the process with which the rpd learns the route states and changes, and reflects these changes in the ASIC-based Packet Forwarding Engine residing in the line cards. The key enhancements are faster route download rates when a router comes up after a reboot, or when you add a new line card, and faster update of the data plane in convergence scenarios. We recommend disabling daemons, such as Layer 2 address learning process (l2ald) and connectivity-fault management process (cfmd) —if they are not required— to improve system performance. Though these enhancements are mainly for the MX Series, other platforms might see some performance improvements as well.

    To maximize route download performance, increase the priority of the route-install job in the krt module of rpd. To increase the route-install job priority, configure the dynamic-route-install-job-priority statement at the [edit routing-options forwarding-table] hierarchy level. The dynamic-route-install-job-priority option is disabled by default. You can also specify the threshold-length and the recover-length.

    • threshold-length—The priority of a job in the krt-queue is increased when the number of entries in the krt-queue exceeds this value. By default, the threshold-length is 50000.
    • recover-length—The priority of a job in the krt-queue is restored to the default priority when the number of entries in the krt-queue falls below this value. By default, the recover-length is 45000.

    The dynamic-route-install-job-priority configuration option is available in Junos OS 15.1F6 and later 15.1F releases only. Configuring the dynamic-route-install-job-priority option might not be required in future software releases because of system changes. Therefore, this option might not be available in Junos OS Release 16.1 and later releases.

Services Applications

  • Support for inline-jflow (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F4 on PTX5000 and Junos OS Release 15.1F6 on PTX3000, you can use inline-jflow’s export capabilities with IP Flow Information Export (IPFIX) to define a flow record template suitable for IPv4 or IPv6 traffic.

  • Enhancements were made to inline jflow to support large scale profiles (PTX Series with third-generation FPCs)—Starting in Junos OS Release 15.1F6, the maximum flow sessions available increases to 800 thousand for 2 Tbps third-generation FPCs and 1.2 million for 3 Tbps third-generation FPCs.

Software-Defined Networking

  • Dynamic acquisition of network topology (PTX Series)—Starting in Junos OS Release 15.1F4, the network topology abstraction daemon (ntad) provides the functionality to dynamically acquire the network topology. The NorthStar Controller runs Junos OS in a virtual machine (VM) that uses BGP-LS (the preferred protocol) or OSPF/IS-IS to learn the network topology. In Junos OS, BGP-LS or IGP publishes the acquired topology it learns into the traffic engineering database, which provides an in-memory representation of the network topology. The network topology abstraction daemon produces a copy of the traffic engineering database that the topology server uses.
  • Standby and secondary LSPs (PTX Series)—Starting in Junos OS Release 15.1F4, standby and secondary LSPs provide an alternate route in the event the primary route fails. The tunnel ID, from node to node, and IP address of a secondary or standby LSP are identical to that of the primary LSP. However, secondary and standby LSPs have the following differences:
    • A secondary LSP is not signaled until the primary LSP fails.
    • A standby LSP is signaled regardless of the status of the primary LSP.
  • PCC multiple template support (PTX Series)—Starting in Junos OS Release 15.1F4, you can create LSP templates to define a set of LSP attributes to apply to all PCE-initiated LSPs that provide a name match with the regular expression (regex) name specified in the template. By associating LSPs (through regex name matching) with an LSP template, you can automatically enable or disable LSP attributes across any LSPs that provide a name match with the regex name.
  • IGP-based topology discovery (PTX Series)—Starting in Junos OS Release 15.1F4, the NorthStar Controller supports dynamic topology acquisition by using routing protocols (IS-IS, OSPF, and BGP LS) to obtain real-time topology updates.
  • PCC delegation of auto-bandwidth and TE++ (PTX Series)—Starting in Junos OS Release 15.1F4, a TE++ LSP includes a set of paths that are configured as a specific container statement and individual LSP statements, called sub-LSPs, which all have equal bandwidth. For TE++ LSPs, a normalization process resizes the LSP when either of the following two triggers occurs:
    • A periodic timer occurs.
    • Bandwidth thresholds are met.

    These triggers elicit one of the following responses:

    • No change is required.
    • LSP splitting—add another LSP and distribute bandwidth across all the LSPs.
    • LSP merging—delete an LSP and distribute bandwidth across all the LSPs.

    For a TE++ LSP, the NorthStar Controller displays a single LSP with a set of paths. The LSP name is based on the matching prefix name of all members. The correlation between TE LSPs is based on association, and the LSP is deleted when there are no remaining TE LSPs.

User Interface and Configuration

  • Monitoring, detecting, and taking action on degraded physical 100-Gigabit Ethernet links to minimize packet loss (PTX3000 and PTX5000)—Starting with Junos OS Release 15.1F6, you can monitor physical link degradation (indicated by bit error rate (BER) threshold levels) on Ethernet interfaces, and take corrective actions if the BER threshold value drops to a value in the range of 10-13 to 10-5.

    The following new configurations have been introduced at the [edit interfaces interface-name] hierarchy level to support the physical link degrade monitoring and recovery feature on Junos OS:

    • To monitor physical link degrade on Ethernet interfaces, configure the link-degrade-monitor statement.
    • To configure the BER threshold value at which the corrective action must be triggered on or cleared from an interface, use the link-degrade-monitor thresholds (set value | clear value) statement.
    • To configure the link degrade interval value, use the link-degrade-monitor thresholds interval value statement. The configured interval value determines the number of consecutive link degrade events that are considered before any corrective action is taken.
    • To configure link degrade warning thresholds, use the link-degrade-monitor thresholds (warning-set value | warning-clear value) statement.
    • To configure the link degrade action that is taken when the configured BER threshold level is reached, use the link-degrade action media-based statement.
    • To configure the link degrade recovery options, use the link-degrade recovery (auto interval value | manual) statement.

    You can view the link recovery status and the BER threshold values by using the show interfaces interface-name command.

VPNs

  • Support for Layer 3 VPN (PTX3000 and PTX5000)—Starting in Junos OS Release 15.1F5 for PTX5000 and Junos OS Release 15.1F6 for PTX3000, Layer 3 VPN is supported on routers that have third-generation FPCs installed.

    Note: Layer 3 VPN is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

  • Flow-aware transport pseudowire for BGP L2VPN and BGP VPLS (PTX Series)— Starting with Junos OS Release 15.1F2, the flow-aware transport (FAT) label that is supported for BGP-signaled pseudowires such as L2VPN and VPLS is configured only on the label edge routers (LERs). This causes the transit routers or label-switching routers(LSRs) to perform load balancing of MPLS packets across equal-cost multipath (ECMP) paths or link aggregation groups (LAGs) without the need for deep packet inspection of the payload. The FAT flow label can be used for LDP-signaled forwarding equivalence class (FEC 128 and FEC 129) pseudowires for VPWS and VPLS pseudowires.

Related Documentation

Modified: 2017-03-22