Junos OS Release Notes for PTX Series Packet Transport Routers

New and Changed Features

• Release 17.2R3 New and Changed Features

• Release 17.2R2 New and Changed Features

• Release 17.2R1 New and Changed Features

Release 17.2R3 New and Changed Features

Release 17.2R2 New and Changed Features

Software Installation and Upgrade

• Device serial number added to DHCP option 60 (PTX1000)—Starting in Junos OS Release 17.2R2, DHCP option 60 (Vendor Class Identifier) includes the serial number of the device when you use zero touch provisioning to automate provisioning of the device configuration and software image. The serial number can uniquely identify the device in a broadcast network. The serial number appears in the format Juniper-model-number. For example, a PTX1000 router numbered DA000 appears as Juniper-ptx1000-DA000.

Release 17.2R1 New and Changed Features

Hardware

• PTX10008 Packet Transport Router—PTX10008 Packet Transport Router provides 3.0 Tbps per slot forwarding capacity for the service providers and cloud operators. The router providesa smooth transition from 10-Gigabit Ethernet and 40-Gigabit networks to 100-Gigabit Ethernet high-performance networks. This high-performance, 13 rack unit (13RU) modular chassis provides 24 Tbps of throughput and 16 Bpps of forwarding capacity. PTX10008 has eight slots for the line cards that can support a maximum of 1152 10-Gigabit Ethernet ports, 288 40-Gigabit Ethernet ports, or 240 100-Gigabit Ethernet ports.

  PTX10008 supports two new line cards, LC1101 and LC1102. The LC1101 line card consists of 30 QSFP+ Pluggable Solution (QSFP28) ports and the LC1102 has 36 QSFP+ ports that support 40-gigabit or 100-gigabit Ethernet optical transceivers.

Class of Service (CoS)

• Support for CoS-based forwarding (PTX10008)—CoS-based forwarding (CBF) enables the control of next-hop selection based on a packet’s class of service field. Starting with Junos OS Release 17.2R1, PTX10008 routers support CBF. CBF can only be configured on a device with eight or fewer forwarding classes plus a default forwarding class. You can implement CBF by specifying next-hop-map at the [edit class-of-service forwarding-policy] hierarchy level and then applying next-hop-map at the [edit policy-options] hierarchy level.

• CoS-based forwarding support for up to 16 forwarding classes (MX Series and PTX routers)—Beginning with Junos OS Release 17.2R1, MX Series routers with MPCs or MS-DPCs, vMX, PTX3000 routers, PTX5000 routers, and VPTX support configuring CoS-based forwarding (CBF) for up to 16 forwarding classes. All other platforms support CBF for up to 8 forwarding classes. To support up to 16 forwarding classes for CBF on MX routers, enable enhanced-ip at the [edit chassis network-services] hierarchy level.

  [See Forwarding Policy Options Overview.]

• Support for class of service (CoS) (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, support is extended for class of service (CoS). CoS is the assignment of traffic flows to different service levels. Service providers can use router-based CoS features to define service levels that provide different delay, jitter (delay variation), and packet loss characteristics to particular applications served by specific traffic flows.

  On a PTX1000 router, you can divide traffic into classes and offer various levels of throughput and packet loss when congestion occurs.

• Support for shaping of traffic exiting third-generation FPCs (PTX1000)—Starting with Junos OS Release 17.2R1, you can shape the output traffic of an FPC3 physical interface on a PTX1000 Packet Transport Router so that the interface transmits less traffic than it is physically capable of carrying. Shaping on all PTX Series router interfaces has a minimum rate of 1 Gbps and an incremental granularity of 0.1 percent of the physical interface speed after that (for example, 10 Mbps increments on a 10 Gbps interface). You can shape the output traffic of a physical interface by including the shaping-rate statement at the [edit class-of-service interfaces interface-name] or [edit class-of-service traffic-control-profiles profile-name] hierarchy level and applying the traffic control profile to an interface.

  [See shaping-rate (Applying to an Interface).]

Forwarding and Sampling

• Support for Bidirectional Forwarding Detection (BFD) (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, support is extended for Bidirectional Forwarding Detection (BFD). The BFD protocol uses control packets and shorter detection time limits to rapidly detect failures in a network. Hello packets are sent at a specified, regular interval by routing devices. A neighbor failure is detected when a routing device stops receiving a reply after a specified interval.

  On a PTX1000 router, you can configure BFD for static routes and for the BGP, IS-IS, OSPF, PIM, and RIP protocols.

General Routing

• OpenConfig: Supporting the BGP model in Junos OS (PTX Series)—Starting in Junos OS Release 17.2R1, the configuration leaf devices defined in the openconfig-bgp.yang and openconfig-bgp-multiprotocol.yang files are supported.

• OpenConfig: BGP routing table support for operational state model (PTX Series)—Starting in Junos OS Release 17.2R1, the OpenConfig BGP RIB routing table supports local-rib for IPv4 and IPv6.The Openconfig-rib-bgp.yang model supports five logical RIBs per address family. There are five tables for IPv4 routes and five tables for IPv6 routes.

High Availability (HA) and Resiliency

• Kernel synchronization performance and debugging enhancements (PTX Series)—Starting in Junos OS Release 17.2R1, the kernel synchronization process (ksyncd) uses multithreading for increased performance, and you can use new CLI commands for ksyncd debugging and recovery. Use the set system kernel-replication no-multithreading command to run ksyncd in single thread mode for debugging purposes. Use the set system kernel-replication system-reboot recovery-failure command to configure the automatic reboot of a standby Routing Engine after receiving a ksyncd initialization error.

  [See kernel-replication.]

• Resiliency Support for LC1101 and LC1102 (PTX10008)—Starting with Junos OS Release 17.2R1, resiliency support is enabled for the following devices:

  • LC1101 and LC1102

  • Switch Interface Boards

• Chassis management—In Junos OS Release 16.1X65 and 17.2R1, the following CLI operational mode commands are supported on a PTX1000 router:

  • show chassis hardware

  • show chassis temperature-thresholds

  • show chassis environment

  • show chassis firmware

Interfaces and Chassis

• Support for packet-forwarding features on LC1101 and LC1102 (PTX10008)—Starting in Junos OS Release 17.2R1, the following key packet-forwarding features are enabled on LC1101 and LC1102 for PTX10008 routers:

  • Basic Layer 2 features and protocols

  • Class of Service (CoS)

  • Firewall filters and policers

  • Hash enhancement

  • Large scaling IPv4 and IPv6 forwarding information base (FIB)

  • Layer 3 VPNs

  • MPLS

  • Sampling and port mirroring

• Fabric management support (PTX10008)—Starting in Junos OS Release 17.2R1, you can set up and manage the fabric connections between the Packet Forwarding Engines of LC1101 andLC1102 in the PTX10008 routers. Fabric management includes collecting fabric status and statistics, monitoring health of the hardware, and responding to CLI queries. It also tracks addition and removal of FRUs from the router and monitors faults in the data plane. It is enabled by default and can be monitored by using the following commands:

  • show chassis fabric summary

  • show chassis fabric fpcs fpc fpc-slot

  • show chassis fabric sibs

  • show chassis fabric errors

  • show chassis fabric reachability

• Support for LC1101 and LC1102 with Routing and Control Board (RCB) (PTX10008)—Starting with Junos OS Release 17.2R1, the PTX10000 Routing and Control Board (RCB) is supported on PTX10008 routers. The PTX10008 chassis can run with one or two RCBs. A fully redundant system requires a second RCB. When two RCBs are installed, one RCB functions as the master and the second as the backup. If the master RCB is removed, the backup starts and becomes the master. The RCB integrates the control plane and Routing Engine functions into a single management unit. The RCB handles system control functions such as environmental monitoring, routing Layer 2 and Layer 3 protocols, alarm and logging functions, and other functions required to manage the operation of a chassis.

• Support for 10-Gigabit Ethernet on LC1101 - 30C line card (PTX10008)—Starting in Junos OS Release 17.2R1, PTX10008 routers support 10-Gigabit Ethernet interfaces in addition to 40-Gigabit Ethernet and 100-Gigabit Ethernet interfaces on the LC1101 - 30C line card.

  When a particular PE chip or Packet Forwarding Engine is working in mode A to support 10-Gigabit Ethernet, ports 6, 7, 16, 17, 26, and 27 at the PE0 to PE5 level are non operational. However, once the PE goes into mode D, these ports become operational and can operate at 40-Gigabit Ethernet, or 100-Gigabit Ethernet speed.

  For 10-Gigabit Ethernet, you must configure the port using the channelization command. Because there is no port-groups option for the 100-Gigabit Ethernet line card, you must use individual port channelization commands.

  In 30C line card, by default FPC comes up in mode D, when you channelize the first port in any PE, the FPC restarts and the corresponding PE comes up in mode A. Further channelization in that PE does not restart the FPC. However, if you channelize some another ports in another PE, then the whole FPC restarts again. If you undo the channelization of all ports in any PE , then the FPC gets restarted and the corresponding PE comes up in mode D, which is the default mode.

  Note

  If any mode changes (A to D or D to A) occur at the PE, the line card automatically performs a cold reboot.

• Support for channelizing the 40-Gigabit Ethernet ports (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, the PTX1000 Packet Transport Router supports 10-Gbps, 40-Gbps, and 100-Gbps port speeds, enabling service providers to organically distribute peering points throughout the network. You can channelize four 10-Gigabit Ethernet interfaces from the 40-Gigabit Ethernet interfaces. By default, the 40-Gigabit Ethernet interfaces are named et-fpc/pic/port. The names of the channelized 10-Gigabit Ethernet interfaces appear in the format: et-fpc/pic/port:channel, where channel is a value from 0 through 3.

  To configure a port speedof 40-Gbps or 10-Gbps, use the set chassis fpc slot pic pic-slot port 0..71 channel-speed (10g|40g) command.

  You can also configure 24 out of the 72 ports to operate at 100-Gbps speed.

• Support for packet-forwarding features (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, the PTX1000 Packet Transport Router supports the following key packet forwarding features:

  • Basic Layer 2 features and protocols

  • Class of service (CoS)

  • Firewall filters and policers

  • Hash enhancement

  • Large scaling IPv4 and IPv6 forwarding information base (FIB)

  • Layer 3 VPNs

  • MPLS

  • Sampling and port mirroring

• Support for configuring multiple port speeds on PTX1000—Starting in Junos OS Release 16.1X65 and 17.2R1, PTX1000 Packet Transport Router supports 10-Gbps, 40-Gbps, and 100-Gbps port speeds, enabling service providers to organically distribute peering points throughout the network. To configure the port speed, use the speed [10G | 40G | 100G] statement at the [edit chassis fpc slot-number pic pic-number port port-number] hierarchy level. The default port speed is 10G.

  Support for configuring local loopback on PTX1000—In Junos OS Release 16.1X65 and 17.2R1, to enable local loopback, use the loopback local configuration statement on PTX1000 interfaces. The PTX1000 supports only local loopback, not remote loopback. Configure the statement at the [edit interfaces interface-name gigether-options] hierarchy level.

• Support for aggregated Ethernet (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, support is extended for aggregated Ethernet. The Junos OS implementation of 802.3ad balances traffic across the member links within an aggregated Ethernet bundle based on the Layer 3 information carried in the packet. This implementation uses the same load-balancing algorithm used for per-flow load balancing.

  On a PTX1000 router, you can configure the member links of an aggregated Ethernet bundle with any combination of rates—also known as mixed rates. The bandwidth that is provided by an aggregated Ethernet bundle can be utilized completely and efficiently when the links are configured with different rates.

• Support for DCU accounting and SCU accounting (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, the destination class usage (DCU) accounting and source class usage (SCU) accounting are supported on PTX1000 routers.

  You can maintain packet counts based on the entry and exit points for traffic passing through your network. Entry and exit points are identified by source and destination prefixes grouped into disjoint sets, which are defined as source classes and destination classes. SCU counts packets sent to customers by performing lookups on the source IP address and the destination IP address. SCU accounting enables you to track traffic originating from specific prefixes on the provider core and destined for specific prefixes on the customer edge. DCU counts packets from customers by performing lookups of the IP destination address. DCU accounting enables you to track traffic originating from the customer edge and destined for specific prefixes on the provider core router.

  Note

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

• Support for unicast RPF (PTX1000)—Starting in Junos OS Release 17.2R1, 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.

IPv6

• IPv6 statistics on PTX1000, PTX3000, PTX5000, and PTX10008 with third-generation FPCs—Starting in Junos OS Release 17.2R1, you can obtain the transit IPv6 statistics at both the physical interface and logical interface levels on third-generation FPCs (FPC3-PTX-U2 and FPC3-PTX-U3 on PTX5000 and FPC3-SFF-PTX-U0 and FPC3-SFF-PTX-U1 on PTX3000), PTX1000, and PTX10008 by using both a CLI command and SNMP MIB counters. Use the show interfaces statistics command to display both physical interface and logical interface statistics. You can view only logical interface statistics if you use SNMP MIB counters. However, for aggregated Ethernet interfaces, the accounting is not done at the level of the child links and, thus, IPv6 statistics for child links are not displayed.

  To start getting IPv6 statistics on third-generation FPCs, use the route-accounting statement at the [edit forwarding-options family inet6] hierarchy level. PTX Series routers with first-generation and second-generation FPCs do not display IPv6 statistics for physical interfaces or logical interfaces, and transit statistics on child links in aggregated Ethernet interfaces are also not taken into account.

  Note

  Egress IPv6 statistics are not taken into account in case of MPLS POP where IPv6 traffic is encapsulated within MPLS and MPLS is stripped off before the plain IPv6 traffic is forwarded.

  [See route-accounting and show interfaces extensive.]

Layer 2 Features

• Support for Layer 2 protocols (PTX10008)—Starting in Junos OS Release 17.2R1, L2 circuit and L2VPN are supported on PTX10008 routers.

Layer 3 Features

• BGP (PTX1000)—In Junos OS Release 16.1X65 and 17.2R1, BGP is an exterior gateway protocol (EGP) for routing traffic between autonomous systems (AS). You can configure BGP at the [edit protocols bgp] hierarchy level.

  OSPF (PTX1000)—The IPv4 OSPF protocol is an interior gateway protocol (IGP) for routing traffic within an autonomous system (AS). PTX1000 routers support OSPFv1, OSPFv2, and OSPFv3. You can configure OSPF at the [edit protocols ospf] hierarchy level.

  Synchronization between OSPF and LDP (PTX1000)—LDP distributes labels in non-traffic-engineered applications. Labels are distributed along the best path determined by OSPF. If the synchronization between LDP and OSPF is lost, the label-switched path (LSP) goes down. Therefore, LDP and IS-IS synchronization are beneficial.

  To advertise the maximum cost metric until LDP is operational for LDP synchronization, include the ldp-synchronization statement at the [edit protocols ospf interface interface-name] hierarchy.

  IS-IS (PTX1000)—The IS-IS protocol is an interior gateway protocol (IGP) for routing traffic within an autonomous system.

  Synchronization between IS-IS and LDP (PTX1000)—LDP distributes labels in non-traffic-engineered applications. Labels are distributed along the best path determined by IS-IS. If the synchronization between LDP and IS-IS is lost, the label-switched path (LSP) goes down. Therefore, LDP and IS-IS synchronization are beneficial.

  To advertise the maximum cost metric until LDP is operational for LDP synchronization, include the ldp-synchronization statement at the [edit protocols isis interface interface-name] hierarchy.

• Support for Layer 3 protocols (PTX10008)—Starting in Junos OS Release 17.2R1, Layer 3 protocols are supported on PTX10008 routers. Layer 3 protocols include the Multiprotocol Label Switching (MPLS), Layer 3 Virtual Private Network (L3VPN), Bidirectional Forwarding Detection (BFD), Layer 2 Virtual Private Network (L2VPN), Point-to-multipoint (P2MP), Fast ReRoute (FRR), Operations, Administration and Maintenance (OAM), Protocol Independent Multicast (PIM), Internet Group Management Protocol (IGMP), Adaptive Load Balancing (ALB), and so on.

Management

• Support for LSP events and properties sensor for Junos Telemetry Interface (PTX3000 and PTX5000 routers)—Starting with Junos OS Release 17.2R1, you can export statistics for LSP events and properties through the Junos Telemetry Interface. Only gRPC streaming for this sensor is supported. You can export statistics for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. To export data through gRPC, use the /mpls/lsps/ or /mpls/signal-protocols/ set of OpenConfig subscription paths. Use the telemetrySubscribe RPC to specify telemetry parameters and provision the sensor. If your device is running a version of the Junos OS with an upgraded FreeBSD kernel, you must download the Junos Network Agent software package, which provides the interfaces to manage gRPC subscriptions. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models.

  [See Guidelines for gRPC Sensors.]

• Support for device family and release in Junos OS YANG modules (PTX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the module’s prefix. Device families include junos, junos-es, junos-ex, and junos-qfx.

  [See Understanding Junos OS YANG Modules.]

• Support for LSP statistics for Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 17.2R1, you can stream telemetry data for LSPs through UDP and gRPC. To provision an LSP statistics sensor for UDP streaming, include the resource /junos/services/label-switched-path/usage/ statement at the [edit services analytics sensor sensor-name] hierarchy level. Use the mpls/lsps/constrained-path/tunnels/tunnel/ path to provision a sensor for streaming LSP statistics through gRPC. If your Juniper Networks device is running a version of Junos OS with the upgraded FreeBSD kernel, you must download the Junos Network Agent package, which provides the interfaces to manage gRPC subscriptions. For both UDP and gRPC streaming, you must also configure the sensor-based-stats statement at the [edit protocols mpls] hierarchy level. Support for the LSP statistics sensor was previously introduced in Junos OS Release 15.1F6 and Junos OS Release 16.1R4.

  [See Overview of the Junos Telemetry Interface.]

• Support for routing protocol processes task memory utilization sensor for Junos Telemetry Interface (PTX Series)—Starting in Junos OS Release 17.2R1, you can stream telemetry data through gRPC for routing protocol process (RPD) task memory usage. Include the /junos/task-memory-information/ path to provision a sensor to stream data through gRPC. UDP streaming for this sensor is not supported. If your Juniper Networks device is running a version of Junos OS with the upgraded FreeBSD kernel, you must download the Junos Network Agent package, which provides the interfaces to manage gRPC subscriptions. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models. OpenConfig paths are used to define telemetry parameters for data streamed through gRPC. This functionality was previously introduced in Junos OS Release 16.1R3.

  [See Guidelines for gRPC Sensors.]

• Support for gRPC streaming for Junos Telemetry Interface firewall filter statistics (PTX3000 and PTX5000)—Starting with Junos OS Release 17.2R1, you can use gRPC interfaces to provision sensors to subscribe to and receive firewall filter telemetry data. Traffic-class counter statistics are also collected. Use the /junos/firewall/firewall-stats/ path to provision a sensor for firewall filter statistics. If your Juniper Networks device is running a version of Junos OS with the upgraded FreeBSD kernel, you must download the Junos Network Agent package, which provides the interfaces to manage gRPC subscriptions. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models. OpenConfig paths are used to define telemetry parameters for data streamed through gRPC. This functionality was previously introduced in Junos OS Release 16.1R4.

  [See Guidelines for gRPC Sensors.]

• Support for the Junos Telemetry Interface (PTX1000)—Starting with Junos OS Release 17.2R1, you can you can provision sensors through the Junos Telemetry Interface to export telemetry data for several network elements without involving polling. You can stream data through UDP or gRPC.

  Only the following sensors are supported on PTX1000 routers:

  • Physical interfaces statistics

  • Label-switched-path (LSP) statistics

  • Network processing unit (NPU) memory

  • NPU memory utilization

  • CPU memory

  To provision sensors to stream data through UDP, all parameters are configured at the[edit services analytics] hierarchy level. To provision sensors to stream data through gRPC, use the telemetrySubscribe RPC to specify telemetry parameters for a specified list of OpenConfig command paths. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module and YANG models.

  [See Overview of the Junos Telemetry Interface.]

• Support for queue statistics for logical interface sensors for Junos Telemetry Interface (PTX3000 and PTX5000 routers)—Starting with Junos OS Release 17.2R1, logical interface sensors also collect egress and ingress queue statistics. Both UDP and gRPC streaming are supported. Queue statistics, including for per-unit queuing and hierarchical queuing, are exported when a queuing structure is configured on a logical interface. To provision a logical interfaces statistics sensor for UDP streaming, include the resource /junos/system/linecard/interface/logical/usage/ statement at the [edit services analytics sensor sensor-name] hierarchy level. To provision a sensor for gRPC streaming, include /interfaces/interface[name='interface-name']/subinterfaces/ in the subscription path. Use the telemetrySubscribe RPC to define telemetry parameters for gRPC streaming. If your Juniper Networks device is running a version of Junos OS with the upgraded FreeBSD kernel, you must download the Junos Network Agent package, which provides the interfaces to manage gRPC subscriptions.

  [See Overview of the Junos Telemetry Interface.]

MPLS

• MPLS inter-AS link protection (PTX Series)—Starting in Junos OS Release 17.2R1, MPLS inter-AS link protection is supported. Link protection is essential in an MPLS network to ensure traffic restoration in case of an interface failure. The ingress router will then choose an alternate link through another interface to send traffic to its destination.

  For an MPLS inter-AS environment, link protection can be enabled when labeled-unicast is used to send traffic between autonomous systems (ASs). To configure link protection on an interface, the protection statement is introduced at the [edit protocols bgp group group-name family inet labeled-unicast] hierarchy level.

  [See protection.]

• Support for filter-based GRE for IPv4 and IPv6 tunneling (PTX Series)—In Junos OS Release 16.1X65 and 17.2R1, the filter-based generic routing encapsulation (GRE) for IPv4 and IPv6 tunneling uses firewall filters to provide de-encapsulation of GRE traffic. The configuration of filter-based GRE de-encapsulation supports the routing-instance statement as one of the attributes.

  Note

  Configuring filter-based GRE for IPv4 and IPv6 tunneling is supported only when the enhanced-mode statement is configured at the [edit chassis network-services] hierarchy level.

• MPLS inter-AS link protection (PTX1000)—Starting in Junos OS Release 17.2R1, MPLS inter-AS link protection is supported. Link protection is essential in an MPLS network to ensure traffic restoration in case of an interface failure. The ingress router will then choose an alternate link through another interface to send traffic to its destination.

  For an MPLS inter-AS environment, link protection can be enabled when labeled-unicast is used to send traffic between autonomous systems (ASs). To configure link protection on an interface, the protection statement is introduced at the [edit protocols bgp group group-name family inet labeled-unicast] hierarchy level.

• LDP support (PTX1000)—Starting in Release 17.2R1, Junos OS supports LDP on the PTX1000. The Label Distribution Protocol (LDP) is a protocol for distributing labels in non-traffic-engineered applications. LDP enables routers to establish label-switched paths (LSPs) through a network by mapping network-layer routing information directly to data link layer-switched paths. For more information, see the MPLS Applications User Guide for Routing Devices.

• RSVP support (PTX1000)—Starting in Release 17.2R1, Junos OS supports RSVP on the PTX1000. RSVP is a resource reservation setup protocol that is used by both network hosts and routers. Hosts use RSVP to request a specific class of service (CoS) from the network for particular application flows. Routers use RSVP to deliver CoS requests to all routers along the datapath. RSVP also can maintain and refresh states for a requested CoS application flow. For more information, see the MPLS Applications User Guide for Routing Devices.

• ECMP (64-way) with configurable Layer 3 hash options (PTX1000)—Starting in Release 17.2R1, Junos OS supports configuration of 64 equal-cost multipath (ECMP) next hops for RSVP and LDP LSPs on the PTX1000. To configure the maximum limit for ECMP next hops, include the maximum-ecmp next-hops statement at the [edit chassis] hierarchy level.

  To view the details of the ECMP next hops, issue the show route command. The show route summary command also shows the current configuration for the maximum ECMP limit.

• MPLS capabilities (PTX1000)—Starting in Release 17.2R1, Junos OS supports MPLS capabilities on the PTX1000. MPLS provides both label edge router (LER) and label-switching router LSR and provides the following capabilities:

  • Object access method, including ping, traceroute, and Bidirectional Forwarding Detection (BFD)

  • Fast reroute (FRR), a component of MPLS local protection

    Both one-to-one local protection and many-to-one local protection are supported.

  • Loop-free alternate FRR

  • 6PE and 6VPE devices

  • Layer 3 VPNs for both IPv4 and IPv6

• IPv6 tunneling over an MPLS-based IPv4 network (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, tunneling enables you to connect IPv6 sites over an IPv4 MPLS-enabled backbone. IPv6 packets are carried over an IPv4 MPLS tunnel. To enable this service, you need to deploy provider edge (PE) routers that can run IPv4, MPLS, and BGP toward the core and IPv6 toward the edge.

  [ See Example: Tunneling IPv6 Traffic over MPLS IPv4 Networks]

• Egress peer engineering of service labels (such as BGP and MPLS) and egress peer protection for BGP-LU (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, you can enable traffic engineering of service traffic, such as MPLS LSP traffic between autonomous systems (ASs), by 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 perform an IP lookup to determine a new egress interface.

  [See Configuring Egress Peer Traffic Engineering by Using BGP Labeled Unicast and Enabling MPLS Fast Reroute.]

Multicast

• Support for Internet multicast (PTX Series)—Starting in Junos OS Release 17.2R1, the mpls-internet-multicast routing instance type uses ingress replication provider tunnels to carry IP multicast data between routers through an MPLS cloud, using MBGP. Previously this feature was supported only on PTX Series routers with third-generation FPCs installed. Now this feature is supported when first-generation FPCs or second-generation FPCs are installed with third-generation FPCs on a PTX Series router.

  [See Multiprotocol BGP MVPNs Overview.]

  Note

  For the third-generation FPCs to interoperate with the previous FPCs, the enhanced-mode statement cannot be configured on the chassis. To support Internet multicast, the MPLS core-facing interfaces must be third-generation FPCs.

Network Management and Monitoring

• Support for inline active flow monitoring (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, you can use the export capabilities of inline active flow monitoring with IP Flow Information Export (IPFIX) to define a flow record template suitable for IPv4 or IPv6 traffic. The flow record template provides the flexibility for future enhancements and the ability to add new attributes to inline active flow monitoring without changing to a newer version.

• Support for SNMP (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, SNMP versions 1, 2, and 3 are supported on the PTX1000. SNMP enables you to monitor network devices from a central location. Junos OS includes an SNMP agent that provides remote management applications with access to detailed information about the devices on the network.

• Junos Space Service Now (PTX1000)—In Junos OS Release 16.1X65 and 17.2R1, PTX1000 routers support Junos Space Service Now. TheJunos Space Service Now is an application that runs on the Junos Space Network Management Platform to automate fault management and accelerate issue resolution.

  [ See Junos Space Service Now.]

• Support for accounting profiles (PTX1000)—Starting in Junos OS Release 17.2R1, 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.

• SNMP support for monitoring tunnel statistics (PTX Series)—Starting in Junos OS Release 17.2R1, SNMP MIB jnxTunnelStat supports monitoring of tunnel statistics for IPv4 over IPv6 tunnels. This is a new enterprise-specific MIB, Tunnel Stats MIB, that currently displays three counters: tunnel count in rpd, tunnel count in Kernel, and tunnel count in the Packet Forwarding Engine. This MIB can be extended to support other tunnel statistics. The MIB is defined in jnx-tunnel-stats.txt. This MIB is attached to jnxMibs.

Routing Policy and Firewall Filters

• Hop-limit firewall filter match condition supported (PTX Series)—Starting in Junos OS Release 17.2R1, you can configure a firewall filter using the hop-limit and hop-limit except match conditions for IP version 6 (IPv6) traffic (family inet6).

  Note

  The hop-limit and hop-limit except match conditions are supported on PTX series routers when enhanced-mode is configured on the router.

  [See Firewall Filter Match Conditions for IPv6 Traffic.]

• Support for firewall filter with match conditions (PTX1000)—Starting in Junos OS Release 16.1X65 and 17.2R1, you can configure a firewall filter with match conditions for IP version 4 (IPv4) traffic.

• Support for the no-decrement-ttl tunneling attribute (PTX1000)—Starting in Junos OS Release 17.2R1, 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

• Support for BGP link-state distribution with SPRING extensions (PTX Series)—Starting in Junos OS Release 17.2R1, BGP link-state extensions export segment routing topology information to software-defined networking controllers. Controllers can get the topology information by either being a part of an interior gateway protocol (IGP) domain or through BGP link-state distribution. BGP link-state distribution is supported on inter-domain networks and provides a scalable mechanism to export the topology information. This feature benefits networks that are moving to source packet routing in networking (SPRING) but also have RSVP deployed, and continue to use both SPRING and RSVP in their networks.

  [See Link-State Distribution Using BGP Overview.]

• Support for SRGB in SPRING for IS-IS (PTX Series)—Starting with Junos OS Release 17.2R1, you can configure the segment routing global block (SRGB) range label used by source packet routing in networking (SPRING). Currently Junos OS allows you to configure only node segment indices. The value of the start label depends on the dynamic label available in the system. The labels from this SRGB range are used for SPRING in the IS-IS domain. The labels advertised are more predictable and deterministic across the segment routing domain.

  • To configure the starting index value of the SRGB label block, use the start-label start-label-block-value statement at the [edit protocols isis source-packet-routing srgb] hierarchy level.

  • To configure the index range of the SRGB label block, use the index-range value statement at the [edit protocols isis source-packet-routing srgb] hierarchy level.

  [See source-packet-routing.]

• Support for anycast and prefix segments in SPRING for IS-IS protocols (PTX Series)—Starting in Junos OS Release 17.2R1, there is support for anycast segment identifiers (SIDs) and prefix SIDs in source packet routing in networking (SPRING). Currently there is support for node segments in Junos OS supports node segments for IPv4 and IPv6 when they are explicitly configured under the [edit protocols isis source-packet-routing node-segments] hierarchy. Now you can provision prefix SIDs along with node SIDs to prefixes that are advertised in IS-IS protocols through policy configuration. Anycast SID is a prefix segment that identifies a set of routers. You can configure explicit-NULL flag on all prefix SID advertisements and configure shortcut for SPRING routes using family inet-mpls or family inet6-mpls .

  [See Support for SRGB, Anycast, and Prefix Segments in SPRING for IS-IS Protocol.]

• Support for unique AS path count (PTX Series)—Starting with Junos OS Release 17.2R1, you can configure a routing policy to determine the number of unique autonomous systems (ASs) present in the AS path. The unique AS path count helps determine whether a given AS is present in the AS path multiple times, typically as prepended ASs. In earlier Junos releases it was not possible to implement this counting behavior using the as-path regular expression policy. This feature permits the user to configure a policy based on the number of AS hops between the route originator and receiver. This feature ignores ASs in the as-path that are confederation ASs, such as confed_seq and confed_set.

  To configure AS path count, include the as-path-unique-count count (equal | orhigher | orlower) configuration statement at the [edit policy-options policy-statement policy_name from] hierarchy level.

• Support for IS-IS segment routing on PTX1000—Starting in Junos OS Release 16.1X65 and 17.2R1, 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:

  • source-packet-routing—Enable the source packet routing feature.

  • node-segment—Enable source packet routing at all levels.

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

  • no-advertise-adjacency-segment—Disable advertising of the adjacency segment on all levels for a specific interface.

• BGP advertises multiple add-paths based on community value (PTX1000)—Beginning with Junos OS 17.2R1, you can define a policy to identify eligible multiple path prefixes based on community values. BGP advertises these community-tagged routes in addition to the active path to a given destination. If the community value of a route does not match the community value defined in the policy, then BGP does not advertise that route. This feature allows BGP to limit the number of multiple paths that are processed and not advertise more than 20 paths to a given destination. You can limit and configure the number of prefixes that BGP considers for multiple paths without actually knowing the prefixes in advance. Instead, a known BGP community value determines whether or not a prefix is advertised.

• Selective advertising of BGP multiple paths (PTX1000)—Beginning with Junos OS Release 17.2R1, you can restrict BGP add-path to advertise contributor multiple paths only. Advertising all available multiple paths might result in a large overhead of processing on device memory and is a scaling consideration, too. You can limit and configure upto six prefixes that the BGP multipath algorithm selects. Selective advertising of multiple paths facilitates Internet service providers and data centers that use route reflector to build in-path diversity in IBGP.

• Support for BGP to carry flow-specification routes (PTX1000)—Starting in Junos OS Release 17.2R1, BGP can carry flow-specification network layer reachability information (NLRI) messages on PTX1000 routers. Propagating flow routes as BGP NLRI messages in essence enables the propagation of firewall filters which protects the system against denial-of-service (DOS) attacks.

Security

• Firewall filter support (PTX10008)—Starting in Junos OS Release 17.2R1, you can define firewall filters on the PTX10008 routers that defines whether to accept or discard packets. You can use firewall filters on interfaces, VLANs, routed VLAN interfaces (RVIs), link aggregation groups (LAGs), and loopback interfaces.

Services Applications

• Support for inline J-Flow version 9 flow templates (PTX5000 and PTX3000)—Starting in Junos OS Release 17.2R1, you can use inline J-Flow export capabilities with version 9 flow templates to define a flow record template suitable for IPv4 or IPv6 traffic.

  [See Configuring Flow Aggregation to Use Version 9 Flow Templates on PTX Series Routers.]

Software Installation and Upgrade

• Zero Touch Provisioning (PTX1000)—Starting in Junos OS Release 17.2R1, ZTP is supported to automate the provisioning of the device configuration and software image with minimal manual intervention.

  When you physically connect a router to the network and boot it with a default configuration, the router attempts to upgrade the Junos OS software image automatically and autoinstall a configuration file from the network. The router uses information that you configure on a Dynamic Host Configuration Protocol (DHCP) server to locate the necessary software image and configuration files on the network. If you do not configure the DHCP server to provide this information, the router boots with the pre-installed software and default configuration. The Zero Touch Provisioning process either upgrades or downgrades the Junos OS version.

  [See Understanding Zero Touch Provisioning and Configuring Zero Touch Provisioning.]

User Interface and Configuration

• Monitoring, detecting, and taking action on degraded physical 100-Gigabit Ethernet links to minimize packet loss (PTX1000)—Starting with Junos OS Release 17.2R1, 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

• Layer 3 VPN support (PTX1000)—Starting in Release 17.2R1, Junos OS supports Layer 3 VPN on the PTX1000 router. A Layer 3 VPN is a set of sites that share common routing information and whose connectivity is controlled by a collection of policies. The sites that make up a Layer 3 VPN are connected over a provider’s existing Internet backbone.

  In Junos OS, Layer 3 VPNs are based on RFC 4364, BGP/MPLS IP Virtual Private Networks (VPNs). This RFC defines a mechanism by which service providers can use their IP backbones to provide Layer 3 VPN services to their customers.

  [See Understanding Layer 3 VPNs.]

Changes in Behavior and Syntax

• Forwarding and Sampling

• General Routing

• Interfaces and Chassis

• Management

• Network Management and Monitoring

• Routing Protocols

• Subscriber Management and Services

Forwarding and Sampling

• In Junos OS Release 17.2R2, and later, the SelectorID field (element id: 302) is sent instead of the Bytes field (element id: 1) in the system scope of version-ipfix Option template records for all PTX Series Routers. All other elements of the template remain the same.

General Routing

• Support for deletion of static routes when the BFD session goes down (PTX Series)—Starting with Junos OS 17.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session-down message.

Interfaces and Chassis

• Value of sysObjectID now displays jnxProductNamePTX1000 (PTX1000)—Starting in Junos OS Release 17.2R1, the value of sysObjectID is now displayed as jnxProductNamePTX1000 instead of jnxProductPTX1000 (which is an incorrect value), as shown in the following example:

  The sysObjectID value is updated to jnxProductNamePTX1000 to maintain synchronization across devices (or routers) belonging to the PTX Series.

• Change in command outputs after a health check failure (PTX5000)—Starting in Junos OS Release 17.2R1, when a health check fail for a PSM is detected on a PTX5000 router, until a system reboot or restart chassisd occurs, the following changes are displayed in the command outputs:

  • The output of the show chassis environment pdu displays the reason for the health check fail and the following information:

  • The status of the PSM which failed the health check is set to offline and the output of show chassis alarms command displays the following existing alarm:

  After a system reboot or restart chassisd, the router checks the PSM register 0x1D bit-0:

  • The output of the show chassis environment pdu displays the reason for the health check fail and the following information for the PSM:

• Restart FPC option supported on PTX1000 router—In Junos OS Release 17.2R2, you can reboot the FPC gracefully using request chassis fpc restart slot slot-number command on a PTX1000 router. Note that request chassis fpc (online|offline) slot slot-number command is not supported, which means only restart option is supported, but online and offline options are not supported. See [request chassis fpc.]

Management

• Junos OS YANG module namespace and prefix changes (PTX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the module’s prefix. In earlier releases, Junos OS YANG modules used only a unique identifier to differentiate the namespace for each module, and the prefix for all juniper-command modules was jrpc.

  Device families include junos, junos-es, junos-ex, and junos-qfx. The Junos OS YANG extension modules, junos-extension and junos-extension-odl, use the junos device family identifier in the namespace, but the modules are common to all device families.

  [See Understanding Junos OS YANG Modules.]

• Changes to the rfc-compliant configuration statement (PTX Series)—Starting in Junos OS Release 17.2R1, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. If you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level and request configuration data in a NETCONF session on a device running Junos OS Release 17.2R1 or later, the NETCONF server sets the default namespace for the <configuration> element in the RPC reply to the same namespace as in the corresponding YANG model.

  [See Configuring RFC-Compliant NETCONF Sessions and rfc-compliant.]

• Enhancement to the Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 17.2R1, the values displayed in the oper-status key-value field of data streamed through gRPC for the physical interfaces sensor have changed.

  The following values are now displayed to indicate the operational status of an interface:

  • operational status up—UP

  • operational status down—DOWN

  • operational status unknown—UNKNOWN

• Enhancement to NPU memory sensors for Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 17.2R1, the path used to subscribe to telemetry data for network processing unit (NPU) memory and NPU memory utilization through gRPC has changed. The new path is /components/component[name="FPC<fpc-id>:NPU<npu-id>"]/

  [See Guidelines for gRPC Sensors.]

Network Management and Monitoring

• SNMP syslog messages changed (PTX Series)—In Junos OS Release 17.2R1, two misleading SNMP syslog messages have been rewritten to accurately describe the event:

  • OLD - AgentX master agent failed to respond to ping. Attempting to re-register
    
    NEW - AgentX master agent failed to respond to ping, triggering cleanup!

  • OLD - NET-SNMP version %s AgentX subagent connected
    
    NEW - NET-SNMP version %s AgentX subagent Open-Sent!

  [See the MIB Explorer.]

• Update to SNMP support of apply-path statement (PTX Series)—In Junos OS Release 17.2R1, the SNMP implementation for the apply-path configuration statement supports only two lists:

  • apply-path "policy-options prefix-list <list-name> <*>"

    This configuration has been supported from day 1.

  • apply-path "access radius-server <*>"

    This configuration is supported as of this release.

• Need to reconfigure SNMPv3 configuration after upgrade (PTX Series)—In Junos OS Release 17.2R2, you might need to reconfigure SNMPv3 after upgrading from an earlier release to this release. Reconfiguration is necessary only if you are using SNMPv3 and if the engine ID is based on the MAC address because the engine ID is changed. It used to be that customers had to reconfigure SNMPv3 every time after a reboot. That problem is now fixed. If you upgrade, you must still reconfigure SNMPv3, but only once—if you have already reconfigured SNMPv3 in an earlier release, you do not need to reconfigure SNMPv3. To reconfigure SNMPv3, use the delete snmp v3 command, commit, and then reconfigure SNMPv3 parameters.

  [See Configuring the Local Engine ID.]

Routing Protocols

• Syslog error message RPD_ISIS_PREFIX_SID_CNFLCT to resolve conflicting prefix segment advertisement (PTX Series)—Starting in Junos OS Release 17.2R2, the RPD_ISIS_PREFIX_SID_CNFLCT syslog error message is emitted only when the prefix segment advertisement from the remote node is conflicting with an advertisement from the self node. This conflict happens because the same prefix segment index is assigned on different IP addresses or different prefix segment indexes are assigned to the same IP address. To rectify this conflict, identify the remote node in the network originating the conflicting prefix segment advertisement and change the prefix segment index on the local node or on the remote node.

  [See Example: Configuring Anycast and Prefix Segments in SPRING for ISIS.]

Subscriber Management and Services

• DHCPv6 lease renewal for separate IA renew requests (PTX Series)—Starting in Junos OS Release 17.2R3, the jdhcpd process handles the second renew request differently in the situation where the DHCPv6 client CPE device does both of the following:

  • Initiates negotiation for both the IA_NA and IA_PD address types in a single solicit message.

  • Sends separate lease renew requests for the IA_NA and the IA_PD and the renew requests are received back-to-back.

  The new behavior is as follows:

  1. When the reply is received for the first renew request, if a renew request is pending for the second address type, the client stays in the renewing state, the lease is extended for the first IA, and the client entry is updated.

  2. When the reply is received for the second renew request, the lease is extended for the second IA and the client entry is updated again.

  In earlier releases:

  1. The client transitions to the bound state instead of staying in the renewing state. The lease is extended for the first IA and the client entry is updated.

  2. When the reply is received for the second renew request, the lease is not renewed for the second address type and the reply is forwarded to the client. Consequently, when that lease ages out, the binding for that address type is cleared, the access route is removed, and subsequent traffic is dropped for that address or address prefix.

  [See Using DHCPv6 IA_NA with DHCPv6 Prefix Delegation Overview.]

Known Behavior

• Hardware

• High Availability (HA) and Resiliency

Hardware

• Enhanced resiliency and system snapshot (PTX1000)—The 2 x 64-GB SSDs installed in the PTX1000 support the request vmhost snapshot command, which creates a recovery snapshot of the currently running and active file system partitions, and the request vmhost snapshot recovery command, which recovers the primary disk from the snapshot content stored in the backup disk. In addition, the 64-GB SSDs support enhanced hardware resiliency through storage partitioning and redundancy.

  Earlier versions of the PTX1000 have 2 x 32-GB M.2 SATA SSDs. PTX1000 routers with 32-GB SSDs do not support the request vmhost snapshot and request vmhost snapshot recovery commands, and do not support enhanced hardware resiliency. To determine the size of the SSDs installed in your device, issue the show vmhost hardware CLI command. The capacity of Disk1 and Disk2 is displayed in the output as 32.0 GB if 32-GB SSDs are installed, and the capacity is displayed as 50.0 GB if 64-GB SSDs are installed.

  [See the Junos OS Software Installation and Upgrade Guide.]

High Availability (HA) and Resiliency

• Residual and baseline statistics loss from ISSU—Using unified ISSU to upgrade to Junos OS Release 17.2R1 or later will result in a loss of residual and baseline statistics for interfaces, interface set specific statistics, and BBE subscriber service statistics because of an update to the statistics database.

  [See Unified ISSU System Requirements.]

• ISSU restrictions—Unified ISSU is not supported for upgrading Junos OS 17.2R1 to 17.2R2.

Known Issues

• General Routing

• Interfaces and Chassis

• Platform and Infrastructure

• Routing Protocols

General Routing

• While you upgrade from Junos OS Release 15.1F-based images to Junos OS Release 16.x and later releases or downgrading from Junos OS Release 16.x to Junos OS Release 15.1F images, if the validate option is enabled, the chassis process (chassisd) might crash and the upgrade or downgrade might fail. This issue is not seen if both base and target images are from Junos OS Release 15.1F or Junos OS Release 16.x and later. PR1171652

• Occasionally QSFP28+ interfaces can run into clock stretch and will be disabled with an i2c-accel sync access failed error message. PR1181493

• This is a resiliency feature. If more than 10 FO CRC errors are seen in an interval of 30 seconds, then CMERROR infra raises an alarm and an appropriate action is taken. PR1197865

• On MX Series routers with MPC7E, MPC8E, MPC9E and on PTX Series routers with FPC3-PTX-U2/FPC3-PTX-U3, which could lead to the generation of core files. It is hard to reproduce. The interrupt code is optimized to avoid the unnecessary call to prevent the issue. PR1208536

• A PTX Series third-generation FPC might receive noise on the FPC console port and interpret it as valid signals. This might cause a login failure on the console port and generate core files, or even reloads. PR1224820

• On a PTX Series router with a faulty power supply module (PSM), the PSM might generate excessive interrupt requests. Because hardware interrupt requests are processed by the chassisd, excessive interrupt requests might cause chassisd to restart when the condition persists more than 200 seconds. PR1226992

• PTX Series with the FPC-PTX-P1-A or FPC2-PTX-P1A FPC might encounter a single event upset (SEU) event, which can cause a linked-list corruption of the TQ CHIP. The following syslog message is reported. Jan 9 08:16:47.295 router fpc0 TQCHIP1: Fatal error pqt_min_free_cnt is zero Jan 9 08:16:47.295 router fpc0 CMSNG: Fatal ASIC error, chip TQ Jan 9 08:16:47.295 router fpc0 TQ Chip::FATAL ERROR!! from PQT free count is zero jan 9 08:16:47.380 router alarmd[2427]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 0 Fatal Errors - TQ Chip Error code: 0x50002 Jan 9 08:16:47.380 router craftd[2051]: Fatal alarm set, FPC 0 Fatal Errors - TQ Chip Error code: 0x50002, Junos OS Chassis Management Error handling does detect such a condition, raises an Alarm, and disables affected Packet Forwarding Engine entity. To recover this Packet Forwarding Engine entity, a restart of the FPC is needed. Soft errors are transient or non-recurring. FPCs experiencing such SEU events do not have any permanent damage. Contact your Juniper support representative if the issue is seen after an FPC restart. PR1254415

• On rare occasions, upon reboot, the kernel cannot create sysfs entries for the SSDs in the system. This might result in the system entering panic mode and hanging. PR1261068

• When an FPC goes offline or restarts, FPC x sends traffic to FPC y. The following error messages are seen on the destination FPC. A corresponding alarm is set on the destination FPC. Specific to PTX10000, the transient alarm gets set when this condition occurs. The alarm clears later because the source FPC goes offline. Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Error (0x210613), module: PE Chip, type: Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Cmerror Op Set: PE Chip: PE1[1]: FO:core intr: 0x00000010: Grant spray drop due to unspray-able condition error Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Error (0x210614), module: PE Chip, type: Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Cmerror Op Set: PE Chip: PE1[1]: FO:core intr: 0x00000008: Request spray drop due to unspray-able condition error. PR1268678

• On PTX5000 with a third-generation FPC in rare condition, the FPC might crash during lo0.0 inet6 input filter. PR1268875

• Sometimes l2cpd core files are generated when LLDP neighbors are cleared. PR1270180

• Interfaces might go down when the Packet Forwarding Engine encounters TOE::FATAL ERROR (TOE is a module in Packet Forwarding Engine, and the fatal error can be caused either by a software issue or hardware issues such as memory parity errors or others). Reboot the line card to recover the service when you experience the issue. PR1300716

• On PTX10000 Series routers with FPC LC1101 - 30C / 30Q / 96X installed, the 10-Gigabit Ethernet interface might flap when the interface is active and it is set to 100-Gbps speed. PR1315079

• Over a period of time, network events such as route flaps and MBB scenario cause the Packet Forwarding Engine heap memory to get fragmented. This change improves memory management and reduces the chance of memory fragmentation. PR1318595

• This is an expected behavior for TQ-chip ASICs. It is primarily due to the strict-high priority queue and the shared shaper. Credits that are unused by an output queue (that is, the actual rate for the queues is less than transmit rates) will cause the queue's credit bucket to hit its maximum value. When a queue hits it maximum credit value, the remaining credits will be distributed to other queues. After the other queues get transmit credits, they can start transmitting. Thus, with the TQ chip and the shared shaper it is virtually impossible to completely shut off a queue through the guaranteed rate mechanism. PR1319923

• On PTX Series routers with first-generation and second-generation FPCs and with CoS used, a high-priority queue might not get the entire configured bandwidth. PR1324853

• PTX3000 reports Chip to Chip Link (CCL) CRC errors while FPC3-SFF-PTX-1X is taken offline through a CLI command or by pressing the offline button. The syslog error is generated by an FPC just before it goes offline, so there is no detectable traffic loss. *** messages *** Apr 2 08:43:00 fpc4 CMSNGFM: cmsngfpc_fm_send_spry_ctrl_ack: ev_id:11 fm_st:ALL fm_type:FPC_OFF fm_op:DEL Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 0 detected link error for S00F0_0(11,0,11)->FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: Logging statistics for FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: SOT:0x0000037649c2c43e Apr 2 08:43:00 fpc2 CCL: FrameCnt:0x00000000000419dc Apr 2 08:43:00 fpc2 CCL: LastCRCErrCnt:0x00000003 Apr 2 08:43:00 fpc2 CCL: AggrCRCErrCnt:0x0000000000000003 Apr 2 08:43:00 fpc2 CCL: AggrBERCnt:0x0000000000000001 Apr 2 08:43:00 fpc2 CCL: pe0-Avg-28nm-link-10-18 CRC error history (last 5 polls): Apr 2 08:43:00 fpc2 CCL: 0x0 0x0 0x0 0x0 0x3 Apr 2 08:43:00 fpc2 CCL: FEC Uncorrectable FEC Correctable Apr 2 08:43:00 fpc2 CCL: 00000004, 00000000 Apr 2 08:43:00 fpc2 CCL: 00000000, 00000000 Apr 2 08:43:00 fpc2 BEGIN Rx serdes info for asic pe0-0 serdes 18 Apr 2 08:43:00 fpc2 Signal & port condition for serdes_num 18 Apr 2 08:43:00 fpc2 Rx Signal : Signal Not OK Apr 2 08:43:00 fpc2 Rx Electrical Idle : High Apr 2 08:43:00 fpc2 Rx Frequency Lock: Set Apr 2 08:43:00 fpc2 Rx Port : Ready Apr 2 08:43:00 fpc2 DFE TAPs : -- snip -- Apr 2 08:43:00 fpc2 CCL: FrameCnt:0x0000000000041a0d Apr 2 08:43:00 fpc2 CCL: LastCRCErrCnt:0x00000003 Apr 2 08:43:00 fpc2 CCL: AggrCRCErrCnt:0x0000000000000003 Apr 2 08:43:00 fpc2 CCL: AggrBERCnt:0x0000000000000001 Apr 2 08:43:00 fpc2 CCL: pe0-Avg-28nm-link-14-22 CRC error history (last 5 polls): Apr 2 08:43:00 fpc2 CCL: 0x0 0x0 0x0 0x0 0x3 Apr 2 08:43:00 fpc2 CCL: FEC Uncorrectable FEC Correctable Apr 2 08:43:00 fpc2 CCL: 00000004, 00000000 Apr 2 08:43:00 fpc2 CCL: 00000000, 00000000 Apr 2 08:43:00 fpc2 BEGIN Rx serdes info for asic pe0-0 serdes 22 Apr 2 08:43:00 fpc2 Signal & port condition for serdes_num 22 Apr 2 08:43:00 fpc2 Rx Signal : Signal Not OK Apr 2 08:43:00 fpc2 Rx Electrical Idle : High Apr 2 08:43:00 fpc2 Rx Frequency Lock: Set Apr 2 08:43:00 fpc2 Rx Port : Ready Apr 2 08:43:00 fpc2 DFE TAPs : -- snip -- Apr 2 08:43:00 fpc2 CCL: Logging errors for FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: BER Err Apr 2 08:43:00 fpc2 CCL: Frame Lock Loss Apr 2 08:43:00 fpc2 CCL: Align Loss Apr 2 08:43:00 fpc2 CCL: Header Comparison Error Apr 2 08:43:00 fpc2 CCL: Header Preamble Error Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 0 detected link error for S00F1_0(14,0,14)->FPC02FE0(1,00) Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 1 detected link error for S00F0_0(11,0,11)->FPC02FE1(0,00) Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 1 detected link error for S00F1_0(14,0,14)->FPC02FE1(1,00) User@PTX3000> show chassis hardware detail Hardware inventory: FPC 0 REV 43 750-057064 ACPV7514 FPC3-SFF-PTX-1X CPU BUILTIN BUILTIN SMPC PMB FPC 2 REV 40 750-057064 ACPJ9145 FPC3-SFF-PTX-1X CPU BUILTIN BUILTIN SMPC PMB FPC 4 REV 43 750-057064 ACPR8506 FPC3-SFF-PTX-1X CPU BUILTIN BUILTIN SMPC PMB SIB 0 REV 10 750-057067 ACPJ8829 SIB3-SFF-PTX SIB 1 REV 10 750-057067 ACPJ8683 SIB3-SFF-PTX SIB 2 REV 10 750-057067 ACPJ8843 SIB3-SFF-PTX SIB 3 REV 10 750-057067 ACPJ8920 SIB3-SFF-PTX . PR1348733

• When NSR is configured, packets might be dropped because of reverse path forwarding (RPF) during Routing Engine switchover.PR1354285

• If firewall filter is configured, in a rare condition, the host interface might be wedged on a PTX Series router with third-generation FPCs. PR1354580

• Traffic loss is greater than 50 ms (around 200 to 300 ms) for IP routes pointing to a unilist of composites with indirect next hops in a link-down scenario . In this case, the Packet Forwarding Engine does not perform the local repair and waits for the rpd to install the new next hops. PR1383965

Interfaces and Chassis

• 1. Delay Measurement support for 5-port 100G DWDM PIC and 5-port 100G DWDM MIC is *ONE TIME Delay Measurement*. This means that customers intending to measure Delay 2 points must ensure that the link is up on both sides and then conduct this test one time. The result value is valid one time once the test is finished. The test result on CLI is not valid after one time measurement as the old result might show up on the Routing Engine CLI. 2. remote-loop-enable must be configured first on the remote end. 3. Each time a customer wants to verify this, the test has to be repeated. 4. Processing delays in each mode are different: HG-FEC [For 5-port 100G DWDM MIC] being highest, SDFEC in the interim and GFEC being least for the same cable length. 5. In summary, any breakage in Transmit or Receive path during the delay measurement test will hinder delay measurement. This is true for all FEC modes - GFEC, SD-FEC, HGFEC. 6. Currently SNMP walk is not available for delay measurement. PR1233917

• Junos OS upgrade involving Junos OS Release 14.2R5 (and later 14.2 maintenance releases) and Junos OS Release 16.1 (and later mainline releases) with CFM configuration can cause the cfmd to crash after the upgrade. This is due to an old version of /var/db/cfm.db. PR1281073

Platform and Infrastructure

• In scaled FIB setups, IS-IS graceful restart might abort on the restarting node with T3-timer expiry log, because of hold-time expiry on IS-IS GR-helper peers. May 20 01:22:55.992972 T3 Restart timer expired (graceful restart aborted). This is because of the time taken by the rpd to learn routes from the FIB on rpd startup that were installed by a previous instance of the rpd. IS-IS does not get to initialize and send hellos because of this delay, causing holdtimer-expiry at helpers. {master}[edit] user@router# run show route forwarding-table summary | match user May 20 03:07:26 user: 801650 routes user: 403638 routes user: 6 routes. PR1277933

• Every load override and rollback operation increases the refcount by 1, and after it reaches the maximum value of 65,535, an mgd crash might be observed and the session might get terminated. When mgd crashes, the active lock might remain up preventing any further commits. PR1313158

Routing Protocols

• With Shared Risk Link Group (SRLG) enabled under corner conditions, after executing the command clear isis database is executed, the rpd might crash because the IS-IS database tree gets corrupted. PR1152940

Resolved Issues

• Resolved Issues: 17.2R3

• Resolved Issues: 17.2R2

• Resolved Issues: 17.2R1

Resolved Issues: 17.2R3

General Routing

• PTX1000 : ch_get_product_attribute.324: Cannot find chassisd error message occurs when images are loaded. PR1217505

• On PTX Series routers, chassisd thread does not get CPU resources for 200 seconds, and, as a result, multiple chassisd core files are generated. PR1226992

• The validation-state:unverified routing entry might not be shown with proper location in the output of the show route command. PR1254675

• Error messages might be seen on PTX5000 FPC3 with 48x10G/12x40G(LWO)QSFP+ PIC inserted. PR1273575

• 100GBase-ER4 (740-045420) is shown as UNKNOWN when the CLI command show chassis hardware is executed in Junos OS Release 15.1R5. PR1280089

• FPC cards might go offline because of fabric healing in a PTX3000 router with a SIB-SFF-PTX-240-S. PR1282983

• The PTX SPMB might crash after an FPC replacement is followed by a SIB restart. PR1283553

• Periodic export of IPFIX flow packets with high octet values. PR1286427

• LSP traffic might silently drop and get discarded after a link goes down in the bypass path. PR1291036

• The rpd might generate a core file while restarting. PR1291110

• Incorrect SNMP OID values are sent in SNMP traps for removal or insertion of front panel display on PTX Series routers. PR1294741

• LINK LED is red when the port is disabled on PTX Series routers. PR1294871

• The rpd might crash after interface or BGP flapping. PR1294957

• The chassisd might run out of memory and restart on a PTX1000 router. PR1295691

• On a PTX5000 or on an Ethernet Synchronization Message Channel (ESMC), the clock does not get locked when the source interface is a member link of an aggregated Ethernet bundle. PR1296015

• An mgd core file is generated when downgrading from Junos OS Release 17.3-20170721 to Junos OS Release 16.1X65D40.2. The mgd core file is overwritten if downgrading is attempted multiple times. PR1296504

• On a PTX1000, upgrade from Junos OS Release 16.1X65D45 to Junos OS Release 17.3-20170721 fails frequently when sampling is enabled. PR1296533

• Alarms and syslog errors are seen with the strict-high priority on an AF4 queue, on the oversubscription cases (1X100G egress to 1X10G egress setup). PR1297343

• Link errors alarm messages might be seen after migrating to FPC3 on PTX3000. PR1298841

• The disable-pfe action after hybrid memory cube (HMC) fatal errors might have a system-wide impact on PTX Series routers. PR1300180

• PTX Series FPC3 drops MPLS packets when the maximum transmission unit is less than the MPLS packet size on the outgoing interface with IPv4 traffic. PR1302256

• Heap memory leak might be observed on PTX Series FPCs during a multicast route installation into the Packet Forwarding Engine. PR1302303

• On a PTX3000, the powering of a FPC (PTX-IPLC-B-32) card might cause the other FPCs to reboot. PR1302304

• The third-generation FPC (FPC3-SFF-PTX) might not boot on a PTX3000 router that has the Control Board or Routing Engine. PR1303295

• On PTX3000 and PTX5000 routers, the 100-Gigabit Ethernet interfaces might not come up. PR1303324

• If MPLS LSP self-ping is enabled (self-ping is enabled by default), the kernel might panic with an error message Fatal trap 12: page fault while in kernel mode. PR1303798

• Repeated log messages %PFE-3 fpcX expr_nh_index_tree_ifl_get and expr_nh_index_tree_ipaddr_get are observed when sampled packets are discardedbecause of the configured firewall filter log (or syslog) statement. PR1304022

• PTX3000 with the RCB-PTX-X6-32G Routing Engine might be unable to recognize the integrated photonic line card (IPLC) or bring it online. PR1304124

• Some error messages might be observed on an EVPN-VXLAN setup. PR1307014

• The interface hold-time down timer configuration does not work properly on a PTX5000 router with an optical interface. PR1307302

• PTX10000: Don't bounce FPC without warning or alarm for different port speed settings. PR1311875

• The rpd generated core files observed after multiple session flaps on a scaled setup. PR1312169

• Too many logs are generated after many VM-host-client-related commands are related. PR1315128

• The RIB and FIB might get out of synchronization because the KRT asynchronous queue is stuck. PR1315212

• The Packet Forwarding Engine on a third-generation FPC on a PTX3000 or PTX5000 or on a PTX10000 line card might be disabled if the interface connecting to the Packet Forwarding Engine goes down. PR1315823

• The physical interfaces might generate framing errors when ports are connected to an odd interface. PR1317827

• After an FPC is powered on, (or connected to or disconnected from the network), the output of the show chassis hardware command shows No Power. However, the FPC comes up after some time. PR1319156

• The rpd might crash when the OpenConfig package is upgraded with JTI streaming data in the background. PR1322553

• JSA10864 2018-07 Security Bulletin: Junos OS: MPC7/8/9, PTX-FPC3 (FPC-P1, FPC-P2), PTX3K-FPC3 and PTX1000: The line card might crash when it received specific MPLS packets (CVE-2018-0030). PR1323069

• On PTX1000, the local time on an FPC might be different from the local time on Junos OS VM or VM host. PR1325048

• PTX MKA sessions are not coming up, after CA parameters such as transmit-interval, key-server-priority are changed. PR1325392

• MPLS traceroute fails across PTX Series routers. PR1327609

• On PTX5000 with third-generation FPCs, PTX10000, and PTX1000 routers, output firewall filters that are configured with syslog and discard actions do not perform the syslog action. PR1328426

• The line card on a PTX10000 might reboot continuously if HMC BIST fails after you upgrade to Junos OS Release 17.2R1 or later. PR1330618

• Link instability is experienced after a link-down event on a PTX Series device. PR1330708

• Next-hop programming issue during link flapping on PTX Series routers. PR1333274

• PTX5000 FPCs might reboot in certain rare scenarios when an interface-specific policer is configured. PR1335161

• A member link of an IPv4 unilist next hop might be stuck in Replaced state after the interface flaps. PR1336201

• Disabling a breakout 10-Gigabit Ethernet port on et-0/0/5 unexpectedly disables another breakout 10-Gigabit Ethernet port on et-0/0/5. PR1337975

• The FPC, FPC2, FPCE on PTX Series does not forward traffic. PR1339524

• Link goes down on PTX3000 or PTX5000 with FPC3 inserted after the router reboots or link flapping occurs. PR1340612

• The interface might flap continuously after the device robbots. PR1342681

• MPLS traceroute for P2MP LSPs configured with link protection causes the FPC to crash. PR1348314

• BFD sessions do not come up on a PTX3000. PR1352112

• The interfaces on the 15-port 100-Gigabit Ethernet PIC might come up after a delay of around 60 seconds. PR1357410

• The route might be in a stuck state, and the route installation might fail with traffic loss, after the BGP neighbor and the route experience flapping. PR1362560

• The rpd might crash in a large-scale environment. PR1363803

• The traffic is still forwarded through the member link of an aggregated Ethernet bundle interface even with the "Link-Layer-Down" flag set. PR1365263

• Layer 3 VPN traffic is dropped because the selector weight was set to 65,535 after one core-facing interface was down. PR1380783

Infrastructure

• The PTX Series router might be in an abnormal state because of the malfunction of the protection mechanism for F-Label. PR1336207

Interfaces and Chassis

• Interface flapping occurs during Routing Engine switchover if the member links of an aggregated Ethernet interface are configured with framing settings. PR1287547

• 100-Gigabit Ethernet interfaces might not come up when otn-options laser-enable is configured on PTX Series routers. PR1297164

MPLS

• The rpd might crash on backup Routing Engine because of memory exhaustion. PR1328974

• The rpd might crash when MPLS traceoption is configured. PR1329459

• MPLS LSP statistics are not shown in the output of the show mpls lsp ingress statistics command. PR1344039

• Some LSPs might be stuck on the upstream devices after interfaces flap on downstream devices. PR1349157

Platform and Infrastructure

• Continuous log messages are displayed. For example: tftpd[23724]: Timeout #35593 on DATA block 85. PR1315682

• Running the request support information (RSI) command through console port might cause system crash and reboot. PR1349332

• A traffic black-hole condition occurs along with the output of JPRDS_NH:jprds_nh_alloc(),651: JNH[0] failed to grab new region for next hop messages. PR1357707

• Next hop index allocation failed: private index space exhausted through incoming ARP requests to management interface (CVE-2018-0063). PR1360039

Routing Protocols

• A few BFD sessions flap while coming up after the FPC restarts or reboots. PR1274941

• The rpd crashes and generates core files multiple times when you receive an OPEN message from an existing BGP peer. PR1299054

• With BGP LU FRR in an inter-AS scenario, a very high FRR time is visible after the link is up. PR1307258

• The rpd might constantly consume high CPU in a BGP setup. PR1315066

• The primary path of an MPLS LSP might switch to another address. PR1316861

• The rpd might crash after the passive interface is deactivated under IS-IS. PR1318180

• The rpd might crash if SRLG information is in the IS-IS protocol. PR1337849

VPNs

• In a specific CE device environment in which asynchronous notification is used, after the link between the PE and CE devices goes up, the Layer 2 circuit flaps repeatedly. PR1282875

Resolved Issues: 17.2R2

General Routing

• The request vmhost zeroize and request vmhost zeroize both commands might work only on the local Routing Engine. PR1197152

• User-configured TPID is not being applied on a single-tagged VLAN interface. PR1237687

• An FPC major alarm might be seen with the error messages DLU: ilp memory cache error and DLU: ilp prot1 detected_imem_even error. PR1251154

• PTX1000 does not match an outer tag if an inner tag exists. PR1252443

• The kernel log message mastership: sent other Routing Engine mastership loss signal might be printed on the backup Routing Engine of the PTX5000 router. PR1260884

• Sometimes SDN-Telemetry subsystem does not respond to management requests while issuing show agent sensors. PR1266058

• Graceful restart for FPC is provided on PTX1000. PR1266097

• SPMB ukern panics during ASIC error recovery. PR1268253

• The log message sdk-vmmd: %USER-3: is_platform_Next-Gen RE: Platform found as Next-Gen RE is logged with error severity. PR1271134

• MPLS TTL is reset to 255 on third generation PTX FPCs when the protocols mpls no-propagate-ttl command is configured. PR1287473

Infrastructure

• The show system users CLI output displays more users that are not using the router. PR1247546

Layer 2 Ethernet Services

• Messages l2cpd[2486]: task_connect: task MVRP l2ald ipc./var/run/l2ald_control addr /var/run/l2ald_control: No such file or directory is filling up syslog. PR1278189

MPLS

• The rpd might crash if the MPLS LSP path changes. PR1295817

Routing Protocols

• The rpd might crash on platforms with 64-bit X86 Routing Engine, if IPv6 is configured. PR1224376

Resolved Issues: 17.2R1

General Routing

• Junos Telementry Interface: Frequent disconnections are seen in MQTT when the logical interface sensor is provisioned for a longer duration. PR1238803

• On PTX Series platform, add 'set' parameter (optional) to CLI command request system software add. It provides a way to install multiple software packages and software add-on packages at the same time. PR1246675

• 10-Gigabit Ethernet interfaces on a QSFP28 PIC might not come up after a system reboot or a PIC restart. PR1263413

• An incorrect range of voltages is used for proper PE voltages. PR1263675

MPLS

• The rpd process terminates and generates a core file if there are a large number of RSVP LSPs. PR1257367

Documentation Updates

• Protocol-Independent Routing Properties

Protocol-Independent Routing Properties

• Support for deletion of static routes when the BFD session goes down (PTX Series)—Starting with Junos OS Release 17.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session down message.

Migration, Upgrade, and Downgrade Instructions

• Basic Procedure for Upgrading to Release 17.2

• Upgrade and Downgrade Support Policy for Junos OS Releases

• Upgrading Using Unified ISSU

• Upgrading a Router with Redundant Routing Engines

Basic Procedure for Upgrading to Release 17.2

When upgrading or downgrading Junos OS, use the jinstall package. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide. Use other packages, such as the jbundle package, only when so instructed by a Juniper Networks support representative.

1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:

   https://www.juniper.net/support/downloads/

2. Select the name of the Junos OS platform for the software that you want to download.
3. Select the release number (the number of the software version that you want to download) from the Release drop-down list to the right of the Download Software page.
4. Select the Software tab.
5. In the Install Package section of the Software tab, select the software package for the release.
6. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
7. Review and accept the End User License Agreement.
8. Download the software to a local host.
9. Copy the software to the routing platform or to your internal software distribution site.
10. Install the new jinstall package on the router.Note

    We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

    All customers except the customers in the Eurasian Customs Union (currently comprised of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package:

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-17.2R3.9.tgz

    Customers in the Eurasian Customs Union (currently comprised of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (Limited encryption Junos OS package):

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-17.2R3.9-limited.tgz

    Replace the source with one of the following values:

    • /pathname—For a software package that is installed from a local directory on the router.

    • For software packages that are downloaded and installed from a remote location:

      • ftp://hostname/pathname

      • http://hostname/pathname

      • scp://hostname/pathname (available only for Canada and U.S. version)

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 16.1, 16.2, and 17.1 are EEOL releases. You can upgrade from Junos OS Release 16.1 to Release 16.2 or even from Junos OS Release 16.1 to Release 17.1. However, you cannot upgrade directly from a non-EEOL release that is more than three releases ahead or behind.

To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information on EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.

Upgrading Using Unified ISSU

Unified in-service software upgrade (ISSU) enables you to upgrade between two different Junos OS releases with no disruption on the control plane and with minimal disruption of traffic. Unified in-service software upgrade is only supported by dual Routing Engine platforms. In addition, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled. For additional information about using unified in-service software upgrade, see the Understanding High Availability Features on Juniper Networks Routers.

For information about ISSU support across platforms and Junos OS releases, see the In-Service Software Upgrade (ISSU) Web application.

Upgrading a Router with Redundant Routing Engines

If the router has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation as follows:

1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Product Compatibility

• Hardware Compatibility

Hardware Compatibility

To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guide and the Interface Module Reference for the product.

To determine the features supported on PTX Series devices in this release, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at: https://pathfinder.juniper.net/feature-explorer/.

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.