Junos OS Release Notes for PTX Series Packet Transport Routers
These release notes accompany Junos OS Release 19.4R3 for the PTX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.
You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.
What's New
Learn about new features introduced in this release for PTX Series routers.
What's New in 19.4R3
There are no new features or enhancements to existing features for PTX Series routers in Junos OS Release 19.4R3.
What's New in 19.4R2
There are no new features or enhancements to existing features for PTX Series routers in Junos OS Release 19.4R2.
What's New in 19.4R1
General Routing
Optimized BGP peer reestablishment (MX Series, PTX Series, and QFX Series)—Starting with Junos OS Release 19.4R1, BGP peers in different groups can close in parallel. The connect/retry algorithm makes 16 attempts instead of 5 to reestablish BGP peers in the first 256 seconds after they go down. Peers can reestablish while cleanup of the Adj-RIB-In routes is in progress. If a peer comes back up before its route has been deleted from the routing table, that route is not deleted. The DeletePending flag in the show route detail and show route extensive command output indicates that a BGP route needs to be processed. PurgePending, PurgeInProgress, and PurgeImpatient flags in the show bgp neighbor command output show the status of the purge of routing table entries.
[See Understanding External BGP Peering Sessions, show bgp neighbor, show route detail, and show route extensive.]
Hardware
Support for 40-Gbps ports to operate at 10-Gbps speed (PTX10002-60C)—You can use the Mellanox 10-Gbps pluggable adapter (model number: MAM1Q00A-QSA) to convert quad-lane-based ports to a single-lane-based SFP+ port. The QSA adapter has the QSFP+ form factor with a receptacle for the SFP+ module. Use the QSA adapter to convert a 40-Gbps port to a 10-Gbps port. You can plug a 10-Gbps SFP+ transceiver into the QSA adapter, which is then inserted into the QSFP or QSFP+ port of the PTX10002-60C router.
High Availability (HA) and Resiliency
View ISSU status during an upgrade (MX240, MX480, MX960, MX2010, MX2020, PTX3000, and PTX5000)—Starting in Junos OS Release 19.4R1, you can use the request system software in-service-upgrade status command to display the status of a unified ISSU. You will need to run this command on the Routing Engine where the unified ISSU was triggered to display the correct unified ISSU log file.
Junos OS, XML, API, and Scripting
Python 3 support for commit, event, op, and SNMP scripts (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, you can use Python 3 to execute commit, event, op, and SNMP scripts on devices running Junos OS. To use Python 3, configure the
language python3statement at the [edit system scripts] hierarchy level. When you configure thelanguage python3statement, the device uses Python 3 to execute scripts that support this Python version and uses Python 2.7 to execute scripts that do not support Python 3 in the given release.The Python 2.7 end-of-support date is January 1, 2020, and Python 2.7 will be EOL in 2020. The official upgrade path for Python 2.7 is to Python 3. As support for Python 3 is added to devices running Junos OS for the different types of onbox scripts, we recommend that you migrate supported script types from Python 2 to Python 3, because support for Python 2.7 might be removed from devices running Junos OS in the future.
[See Understanding Python Automation Scripts for Devices Running Junos OS.]
Automation script library upgrades (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, devices running Junos OS that support the Python extensions package include upgraded Python modules. Python scripts can leverage the upgraded versions of the following modules:
idna(2.8)jinja2(2.10.1)jnpr.junos(Junos PyEZ) (2.2.0)lxml(4.3.3)markupsafe(1.1.1)ncclient(0.6.4)packaging(19.0)paho.mqtt(1.4.0)pyasn1(0.4.5)yaml(PyYAMLpackage) (5.1)
[See Overview of Python Modules Available on Devices Running Junos OS.]
Junos Telemetry Interface
Physical Ethernet interface sensor support on JTI (MX960, MX2020, PTX1000, and PTX5000)—Starting in Junos OS Release 19.4R1, you can use Junos telemetry interface (JTI) and remote procedure calls (gRPC) services or gRPC Network Management Interface (gNMI) services to export physical Ethernet interface statistics from MX960, MX2020, PTX1000, and PTX5000 routers to outside collectors. This feature supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). Both streaming and ON-CHANGE statistics are supported using the following resource paths:
/interfaces/interface/ethernet/state/mac-address(with ON_CHANGE support)/interfaces/interface/ethernet/state/auto-negotiate(with ON_CHANGE support)/interfaces/interface/ethernet/state/duplex-mode(with ON_CHANGE support)/interfaces/interface/ethernet/state/port-speed(with ON_CHANGE support)/interfaces/interface/ethernet/state/enable-flow-control (with ON_CHANGE support)/interfaces/interface/ethernet/state/hw-mac-address (with ON_CHANGE support)/interfaces/interface/ethernet/state/negotiated-duplex-mode (with ON_CHANGE support)/interfaces/interface/ethernet/state/negotiated-port-speed (with ON_CHANGE support)/interfaces/interface/ethernet/state/counters/in-mac-control-frames/interfaces/interface/ethernet/state/counters/in-mac-pause-frames/interfaces/interface/ethernet/state/counters/in-oversize-frames/interfaces/interface/ethernet/state/counters/in-jabber-frames/interfaces/interface/ethernet/state/counters/in-fragment-frames/interfaces/interface/ethernet/state/counters/in-8021q-frames/interfaces/interface/ethernet/state/counters/in-crc-errors/interfaces/interface/ethernet/state/counters/in-block-errors/interfaces/interface/ethernet/state/counters/out-mac-control-frames/interfaces/interface/ethernet/state/counters/out-mac-pause-frames
[See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]
Transceiver sensor support on JTI (MX960, MX2010, MX2020, PTX1000, PTX5000, PTX10000)—In Junos OS Release 19.4R1, you can use Junos telemetry interface (JTI) and remote procedure calls (gRPC) or gRPC Network Management Interface (gNMI) services to export transceiver statistics from MX960, MX2010, MX2020, PTX1000 and PTX5000 routers to outside collectors. This feature supports OpenConfig transceiver model openconfig-platform-transceiver.yang 0.5.0.
Both streaming and ON-CHANGE statistics are supported using the following base path:
/components/components/transceiver/
[See Understanding OpenConfig and gRPC on Junos Telemetry Interface and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]
Support for Segment Routing telemetry statistics and binding SIDs routes for uncolored Segment Routing Traffic Engineering policies (PTX1000, PTX3000, and PTX5000)—Starting in Junos OS Release 19.4R1, Junos OS supports collection of traffic statistics for both ingress IP traffic and transit mpls traffic that take non-colored SR-TE paths on PTX Series routers. Binding SIDs for SRTE paths that have labels as first-hops in their segment lists are also now supported on PTX Series routers.
The show spring-traffic-engineering lsp command now has a tunnel-source filter, to display only the tunnels created from the specified sources by which the SRTE policy was provisioned. Also, the show spring-traffic-engineering lsp detail command now displays information on the source of the tunnel configuration and statistics. By default, traffic sensors and statistic collection are disabled for static SRTE routes. To enable provisioning of JVISION traffic sensors in Junos OS data plane to stream out traffic statistics on SR policies and their Binding-SID routes, enable statistics under telemetry at the [edit source-packet-routing telemetry] hierarchy level, and sensors will be created for both the SRTE policy nexthop and Binding SID that are installed in the forwarding plane.
[See source-packet-routing]
MPLS
update-threshold statement modified to generate IGP update for lower bandwidth reservation (PTX Series)—Starting in Junos OS Release 19.4R1, you can configure the threshold value of the update-threshold statement to accept:
an integer or floating point values up to 3 significant digits after decimal point using the threshold-percent option
an absolute value of bandwidth threshold which generates an IGP update using the threshold-value option
These options are mutually exclusive and can be used for generating an IGP update for lower bandwidth reservations.
[See update-threshold.]
Distributed CSPF for segment routing LSPs (PTX Series)—Starting in Junos OS Release 19.4R1, you can compute a segment routing LSP locally on the ingress device according to the constraints you have configured. With this feature, the LSPs are optimized based on the configured constraints and metric type. The LSPs are computed to utilize the available ECMP paths to the destination.
Prior to Junos OS Release 19.4R1, for traffic engineering of segment routing paths, you could either explicitly configure static paths, or use computed paths from an external controller.
Color-based mapping of VPN services over SRTE (PTX Series)—Starting in Junos OS Release 19.4R1, you can specify a color attribute along with an IP protocol next hop to resolve transport tunnels over static colored and BGP segment routing traffic-engineered (SRTE) label-switched paths (LSPs). This is called the color-IP protocol next hop resolution, where you are required to configure a resolution-map and apply it to the VPN services. Prior to this release, the VPN services were resolved over IP protocol next hops only.
With this feature, you can enable color-based traffic steering of Layer 2 and Layer 3 VPN services.
Support for segment routing features (PTX10002)—Starting with Junos OS Release 19.4R1, PTX10002 router support the following segment routing features:
BGP link-state distribution with SPRING extensions
SRGB for SPRING in IS-IS domain
Anycast and prefix segments in SPRING for IS-IS protocols
IS-IS SPRING and RSVP coexistence
Segment routing policy for traffic engineering on BGP
Static adjacency segment identifier for ISIS and OSPF
Static adjacency segment identifier for aggregate Ethernet member links
Interoperability of segment routing with LDP
RSVP-TE pop-and-forward LSP tunnels
BGP Labeled Unicast traffic statistics collection
Static segment routing label switched path
Interoperability of segment routing with LDP
Topology Independent Loop-Free Alternate for IS-IS and OSPF
MPLS ping and traceroute for segment routing
Anycast and prefix segments in SPRING for OSPF protocols
Configurable SRGBs used by SPRING in OSPF protocols
[See Link-State Distribution Using BGP Overview, Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING, BGP Egress Traffic Engineering, Static Adjacency Segment Identifier for ISIS, Static Adjacency Segment Identifier for OSPF, IS-IS User Guide,OSPF User Guide.]
Routing Protocols
Support for BGP PIC Edge with BGP labeled unicast (MX Series and PTX Series)—Starting with Junos OS Release 19.4R1, MX Series and PTX Series routers support BGP PIC Edge with BGP labeled unicast as the transport protocol. BGP PIC Edge using the BGP labeled unicast transport protocol helps to protect traffic failures over border nodes (ABR and ASBR) in multi-domain networks. Multi-domain networks are typically used in metro-aggregation and mobile backhaul networks designs.
Unnumbered interface support for IS-IS and OSPFv2 with topology-independent loop-free alternate (ACX Series, MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, you can enable IPv4 processing on a point-to-point interface without assigning it an explicit IPv4 address. The router borrows the IPv4 address of another Ethernet or loopback interface already configured on the router and assigns it to the unnumbered interface to conserve IPv4 addresses.
To enable IPv4 processing for unnumbered interfaces include unnumbered-address source at the [edit interfaces [name] unit [name] family inet] hierarchy level.
Support for flexible algorithm in IS-IS for segment routing–traffic engineering (MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, you can thin slice a network by defining flexible algorithms that compute paths using different parameters and link constraints based on your requirements. For example, you can define a flexible algorithm that computes a path to minimize IGP metric and define another flexible algorithm to compute a path based on SPF calculation type to divide the network into separate planes. This feature allows networks without a controller to configure traffic engineering and utilize segment routing capability of a device.
To define a flexible algorithm, include flex-algorithm statement at the [edit routing-options] hierarchy level.
To configure participation in a flexible algorithm include the flex-algorithm statement at the [edit protocols isis segment routing] hierarchy level.
[See Understanding IS-IS Flexible Algorithm for Segment Routing.]
Decouple RSVP for IGP-TE (MX Series and PTX Series)—Starting in Junos OS Release 19.4R1, a device can advertise selective traffic-engineering attributes such as admin-color and maximum-bandwidth, without enabling RSVP, for segment routing and interior gateway protocol (IGP) deployments.
Services Applications
Inline J-Flow scale enhancement (PTX10002)―Starting in Junos OS Release 19.4R1, 100,000 flows per Packet Forwarding Engine are supported.
Support for MPLS, MPLS-IPv4, MPLS-IPv6, and MPLS-over-UDP inline flow monitoring (PTX10002-60C)―Starting in Junos OS Release 19.4R1, you can perform inline flow monitoring for MPLS, MPLS-IPv4, MPLS-IPv6, and MPLS-over-UDP traffic. Both IPFIX and version 9 templates are supported.
[See Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers.]
MPLS-over-UDP inner payload flow monitoring with IPFIX and version 9 formats (PTX10002-60C)―Starting in Junos OS Release 19.4R1, on the PTX10002-60C router, you can perform flow monitoring for MPLS-over-UDP traffic to look past the tunnel header to sample and report on the inner payload at both the transit and egress nodes of the tunnel. This feature supports MPLS IPv4 and IPv6 payloads and both IPFIX and version 9 templates. Only ingress sampling is supported.
[See Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers.]
Software-Defined Networking
Tunnel templates for PCE-initiated segment routing LSPs (PTX Series)—Starting in Junos OS Release 19.4R1, you can configure a tunnel template for Path Computation Element (PCE)-initiated segment routing LSPs and apply it through policy configuration. These templates enable dynamic creation of segment routing tunnels with two additional parameters – Bidirectional forwarding detection (BFD) and LDP tunneling.
With the support for tunnel configuration, the LSPs that you would configure statically can now be automatically created from the PCE, thereby providing the benefit of reduced configuration on the device.
[See Understanding Static Segment Routing LSP in MPLS Networks.]
System Logging
Improved intermodule communication between FFP and MGD (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, intermodule communication is improved to enhance software debugging. To enhance error messages with more context, the exit conditions from libraries have been updated as follows:
Additional information is now logged for MGD-FFP intermodule communication.
Commit errors that previously were only shown onscreen are now logged.
We provide a new operational command, request debug information, to speed up the initial information-gathering phase of debugging.
[See request debug information.]
What's Changed
Learn about what changed in Junos OS main and maintenance releases for PTX Series routers.
What's Changed in 19.4R3-S2
MPLS
Change in auto-bandwidth adjustment (PTX5000)—If auto-bandwidth adjustment fails because of bandwidth unavailable error, the router tries to bring up the LSP with the same bandwidth during the subsequent reoptimization. In earlier releases, when the auto-bandwidth adjustment fails, the current bandwidth is reset to the bandwidth that was already active.
[See rsvp-error-hold-time.]
What's Changed in 19.4R3
General Routing
Trigger alarms when a PTX10008 or PTX10016 router has a mix of AC and DC power supplies—;If you install a mix of AC and DC power supply units (PSUs), Junos OS raises an alarm to indicate that there is a mix of AC and DC power supplies in the router. To fix this alarm, ensure that you install the same type of power supplies.
[See Understanding Chassis Alarms.]
Juniper Extension Toolkit (JET)
Set the trace log to only show error messages (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series)—You can set the verbosity of the trace log to only show error messages using the error option at the [edit system services extension-service traceoptions level] hierarchy.
[See traceoptions (Services).]
Platform and Infrastructure
Control plane DDoS protection packet type option for ARP traffic (PTX Series and QFX Series)—Starting in this release, we've renamed the arp-snoop packet type option in the [edit system ddos-protection protocols] arp protocol group to arp. This packet type option enables you to change the default control plane distributed denial of service (DDoS) protection policer parameters for ARP traffic.
Routing Protocols
Advertising /32 secondary loopback addresses to Traffic Engineering Database (TED) as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—In Junos OS Release, multiple loopback addresses export into lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router-ids instead of prefixes. In earlier Junos OS releases, multiple secondary loopback addresses in TED were added into lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router-id.
What's Changed in 19.4R2
Class of Service (CoS)
We’ve corrected the output of the show class-of-service interface | display xml command. The output is of the following sort: <container> <leaf-1> data </leaf-1><leaf-2>data </leaf-2> <leaf-3> data</leaf-3> <leaf-1> data </leaf-1> <leaf-2> data </leaf-2> <leaf-3> data </leaf-3> </container> will now appear correctly as <container> <leaf-1> data </leaf-1><leaf-2>data </leaf-2> <leaf-3> data</leaf-3></container> <container> <leaf-1> data </leaf-1> <leaf-2> data </leaf-2> <leaf-3> data </leaf-3> </container>.
General Routing
LLDP ON_CHANGE statistics support with JTI (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series)—Enhanced telemetry ON_CHANGE event support provides the following LLDP attributes: - When LLDP is enabled on interfaces, LLDP interface counters are notified along with other interface-level attributes. - ON_CHANGE event reports LLDP neighbor age and custom TLVs, as well as when a neighbor is initially discovered
See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).
Routing Protocols
Advertising 32 secondary loopback addresses to Traffic Engineering Database (TED) as prefixes (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—In Junos OS Release, multiple loopback addresses export into lsdist.0 and lsdist.1 routing tables as prefixes. This eliminates the issue of advertising secondary loopback addresses as router-ids instead of prefixes. In earlier Junos OS releases, multiple secondary loopback addresses in TED were added into lsdist.0 and lsdist.1 routing tables as part of node characteristics and advertised them as the router-id.
What's Changed in 19.4R1
General Routing
Support for full inheritance paths of configuration groups to be built into the database by default (ACX Series, MX Series, PTX Series, and SRX Series)—Starting with Junos OS Release 19.4R1, the persist-group-inheritance option at the [edit system commit] hierarchy is enabled by default. To disable this option, use no-persist-groups-inheritance.
[See commit (System).]
Automatic installation of YANG-based CLI for RIFT protocol (MX Series, QFX Series, and vMX with 64-bit and x86-based servers)—In Rift 1.2 Release, installation of the CLI for RIFT protocol occurs automatically along with the installation of the junos-rift package. In the pre-1.0 releases of the junos-rift package, the RIFT CLI had to be installed separately using request system yang command after installation of the junos-rift package.
Interfaces and Chassis
Updates to the show interfaces and show policer commands (PTX Series)—Starting in Junos OS release 19.4R1, on PTX Series routers, when you issue the show interfaces command or the show policer command, the output does not display the default arp policer (_default_arp_policer_). In earlier releases, when you issue the show interfaces command or the show policer command, the output displays the default arp policer (_default_arp_policer_) though the default arp policer is not supported on PTX series routers.
Change in Fabric Error Handling Behavior (PTX10008, PTX10016, PTX5000 routers (with FPC3-PTX-U2, FPC3-PTX-U3 FPCs), QFX10008, QFX10016, and QFX10002 switches)—Starting in Junos OS release 19.4R1, when the PFE encounters ECC errors or parity errors related to fabric which are fatal, major, or correctable minor errors, the interfaces on the PFE are disabled. You must reboot the FPC manually to recover from the error. If you still face an issue after rebooting the FPC, contact our Customer Service. In earlier releases, when the PFE encounters any error (fatal, major, minor_correctable, minor_transient, and info), the errors were incorrectly classified as info and as a result, ignored.
Routing Protocols
XML RPC equivalent included for the show bgp output-scheduler | display xml rpc CLI command (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—Starting in Junos OS Release 19.4R1, we have included an XML RPC equivalent for the show bgp output-scheduler | display xml rpc CLI command. In Junos OS releases before Release 19.4R1, the show bgp output-scheduler | display xml rpc CLI command does not have an XML RPC equivalent.
[See show bgp output-scheduler.]
Software-Defined Networking
Increase in the maximum value of delegation-cleanup-timeout (PTX Series)—Starting in Junos OS Release 19.4R1, you can configure a maximum of 2,147,483,647 seconds as the delegation cleanup time for a Path Computation Client (PCC). This extends the time taken by the PCC to retain the last provided path over a PCEP session from the last session down time.
With the increase in maximum value of delegation-cleanup-timeout from 600 to 2,147,483,647 seconds, you can benefit during a Path Computation Element (PCE) failover or other network issues that might disrupt the PCEP session with the main active stateful PCE.
[See delegation-cleanup-timeout.]
Known Limitations
Learn about known limitations in Junos OS Release 19.4R3 for PTX Series routers. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
General Routing
On the PTX Platform with FPC Model FPC-PTX-P1-A or FPC2-PTX-P1A, you might encounter single event upset (SEU) event that might cause a linked-list corruption of the TQCHIP. The following syslog message gets 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 The Junos OS Chassis Management Error handling detects such a condition, raises an Alarm, and disables the affected Packet Forwarding Engine entity. To recover this Packet Forwarding Engine entity, restart the FPC. Contact your Juniper support representative if the issue persists even after the FPC restarts. PR1254415
When an FPC goes offline or restarts, FPC x sends traffic to FPC y. The following error messages are seen and 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
In the specific case of semigraceful RCB reboot initiated by the internal shell command vhclient init 0, GRES takes longer than 3 minutes to complete as opposed to 21 seconds. As a workaround, the CLI command request vmhost reboot (graceful) and a jack-out-jack-in of the Routing Engine (ungraceful) do not exhibit this delay. PR1312065
Traffic loss for more than 15 seconds is seen when 50 percent of the aggregated Ethernet links are brought down by restarting multiple FPCs. PR1412578
Because of an issue in the BIOS:QFXS_SFP_00.32_02.01 version, when the watchdog is disabled, the device does not reboot. PR1441963
Call trace is observed during image upgrade from WRL6 to WRL9. PR1442017
When a filter is attached in the outbound direction, GRE encapsulated headers are applied after the filter block in the egress direction. So in this case, it is possible that the filter is evaluated on an old header content (and not on the new GRE encapsulated header) and hence filter evaluation turns true and the new GRE encapsulated gets recirculated for another GRE encapsulation. This issue is difficult to fix as filter block evaluation happens before the new header is attached. PR1465837
For scaled MACs as per the current design, the learn rate is expected. PR1473334
MPLS
Increasing ECMP from 64 to 128 might cause the ingress LSP setup rate to be lower because of an increased number of next-hop changes for the IGP routes using a shortcut. PR1421976
Open Issues
Learn about open issues in Junos OS Release 19.4R3 for PTX Series routers. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
General Routing
Uneven load balancing of traffic might occur if the traffic stream changes only in 0-15 bits of the Layer 3 destination IPv6 address. This limitation might not be visible if the other parameters affecting the load balance change along with L3_DST, such as Layer 3 source IP address, Layer 4 source or destination ports, and so on. PR1065515
Power budget values for a PTX5000 chassis, FPC, and PICs have been revised. For routers operating on limited power, this can change the point where alarms for power-over-budget or insufficient power are raised or cleared. PR1216404
When CFP2-DCO-T-WDM-1 is plugged in a PTX Series PIC, after FPC restarts, the carrier frequency offset TCA is raised even when TCA is not enabled. PR1301471
On a PTX Series router with a third-generation FPC, an error message is displayed when the FPC goes online or offline. PR1322491
On 30-port MACsec-enabled line card (LC1101-M-30C, LC1101-M-30Q, and LC1101-M-96X) of PTX10008 chassis, when the exclude-protocol lacp statement is configured at the [edit security macsec connectivity-association connectivity-association-name] hierarchy level is deleted or deactivated, the LACP protocol's Mux State shown under the output of CLI command show lacp interface, might remain as attached or detached and might not change to distributing state. PR1331412
Alarm action does not work for minor errors after the threshold is changed to 1. PR1345154
The PTX Series platform drops the wireless access point (WAP) heartbeat packets; as a result, the WAP cannot work. PR1352805
It is not possible to stop the ZTP bootstrap process when a PTX10016 or PTX10008 router with many line cards is powered on with the factory-default configuration. PR1369959
The firewall counter for lo0 interface might not increase. PR1420560
The em2 interface configuration causes FPC to crash during initialization and FPC does not come online. After deleting the em2 configuration and restarting the router, FPC comes online. PR1429212
Interface statistics are not getting updated with port-mirroring. PR1431607
There is an increase in traffic loss after a unified ISSU with InterAS Layer 3 VPN OptionB configuration. PR1435578
Memory leaks are expected in this release. PR1438358
The full-resolve tunnel uses chain composite next-hop to program tunnel composite next-hop. Since the chain composite next-hop is created from the resolver, it has to delete logic to save the IPC call to the kernel or Packet Forwarding Engine. If the full-resolve dynamic tunnel (in this case, IPoIP tunnel) is deleted and created within 10 seconds, it reclaims the old tunnel. Consequently, you can see the old statistics of the tunnel. PR1444081
The XML output for colored routes displays <c> instead of colored routes. PR1447156
On PTX10008 and PTX10016 routers, the show snmp mib walk jnxContentsDescr command output does not display the fan controllers. PR1455640
The show route command does not give all the next-hop information in the case of multipath routes. PR1458000
Statistic comparison between CLI and Junos telemetry interface for queue fails as the buffers show incorrect values. PR1460246
Traffic fails with gcm-aes-xpn-128 cipher when you perform an event. PR1460254
On the PTX5000 with FPC3, optics-options syslog and link-down do not work as expected. PR1461404
On the PTX10001 routers, the unionfs filesystem might get full on vmhost because the mail package in the WRlinux 8 continues to fill the mail logs in the unionfs filesystem. This causes the router to hang and traffic goes down. PR1470217
On PTX1000 routers, the vmhost disk usage might keep increasing due to an incorrect sensor path. PR1480217
SNMP index on the Packet Forwarding Engine is 0. This causes the sFlow records to have either Input interface (IIF) or Output interface (OIF) value as 0 in sFlow record data at the collector. PR1484322
The Layer 2 VPN with asynchronous-notification might flap when the link goes up between PE and CE. After Layer 2 VPN flaps, the interfaces with asynchronous-notification might show - Inf dBm laser output power even if the Layer 2 VPN is in the up status. PR1486181
On PTX1000 and PTX10001 routers, port mirroring does not work when the port-mirroring is configured with the firewall filter. PR1491789
On the PTX Series platform using indirect next hop (such as Unilist) as route next hop type for multiple paths scenario (such as BGP PIC or ECMP), the fast reroute session might be enabled in Packet Forwarding Engines. When the version-id or session-id of the indirect next hop is above 256, the Packet Forwarding Engine might not respond to session update, which might cause the session-id to be stuck permanently with the weight of 65535 in the Packet Forwarding Engine. This might lead the Packet Forwarding Engine to have a different view of Unilist against load-balance selectors. Then, either the BGP PIC or the ECMP-FRR might not work properly and traffic might be dropped or silently discarded. PR1501817
On PTX10003 routers, a packetio core file might be generated during the initialization after a system reboot and this might result in a second reboot. PR1505150
while loading the configuration, syslog error messages is seen. Issue is seen in the baseline of the configuration. PR1540064
MPLS
In RSVP LSP with no-cspf configured, the LSP might stay in down state due to loop detection after the link in the path flaps. PR1384929
At high scale, LSP setup rate might be relatively slower in IP-in-IP networks. PR1457992
Routing Protocols
With an aggregated Ethernet interface with BFD configured, the aggregated Ethernet interface and BFD session remain down after the interface is disabled or enabled. PR1354409
The show dynamic-tunnels database command does not show the current value of traffic statistics. It shows the cached value of traffic statistics, which might not be equal to the current value. PR1445705
Post IGP convergence backup IPoIP tunnel remains up. As a workaround, you must deactivate or activate dynamic tunnel. PR1447153
With NSR enabled, if you try to bring up more than 3000 IPv6 peers or more than 8000 BGP IPv4 peers, then the rpd might crash. PR1461436
Resolved Issues
This section lists the issues fixed in Junos OS Release 19.4R3 for the PTX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
Resolved Issues: 19.4R3
General Routing
On the PTX10008 and PTX5000 routers, the output of the show filter index < number> counter command displays value as zero at 28-02-HOSTBOUND_NDP_DISCARD_TERM. PR1420057
On PTX1000 and PTX10002 routers, traffic might get dropped or discarded after transient SIB or FPC voltage alarms. PR1460406
Sampling process might crash when the MPLS or MPLS over the UDP traffic is sampled. PR1477445
The following error message is displayed: /fpc/5/pfe/0/cm/0/BCM8238X/0/BCM8238X_CMERROR_FW_TUNING_STOPPED (0x490001), scope: board, category: functional, severity: major, module: BCM8238X, type: BCM8238X SerDes firmware did not complete tuning. PR1491142
Kernel routing table (KRT) queue stuck after J-Flow sampling a malformed packet. PR1495788
Outbound SSH connection flap or memory leak issue might be observed when pushing the configuration to the ephemeral database with high rate. PR1497575
The error message mpls_extra NULL might be seen when you do add, change, or delete operation during MPLS route. PR1502385
The following error message is observed: PFE_ERROR_FAIL_OPERATION: IFD et-1/0/8: RS credits failed to return: init=192 curr=193 chip=5. PR1502716
On the PTX10008 and PTX10016 routers, a few TCP-based application sessions might flap upon Routing Engine switchover or application sessions bouncing in the backup Routing Engine. PR1503169
On the PTX3000 or PTX5000 router, unable to bring the ports up when plugging in the optic QSFP-100G-LR4-T2 (740-061409). PR1511492
The route update might fail upon HMC memory issue and impact the traffic. PR1515092
On PTX10002-60C and PTX1000 routers, the sFlow adaptive-sampling with the rate limiter statement enabled crosses sample rate 65535. PR1525589
Interfaces and Chassis
When multiple CFM sessions are configured on the physical interface, SNMP walk of ieee8021CFMStack table fails. PR1517046
MPLS
The rpd process might crash in a rare condition under the SR-TE scenario. PR1493721
SNMP trap is sent with incorrect OID jnxSpSvcSetZoneEntered. PR1517667
Routing Protocols
On PTX3000 or PTX5000 line of routers, the ppmd process generates a core file after configuring the sbfd responder on the RE-DUO-2600. PR1477525
The BGP route target family might prevent the route reflector from reflecting Layer 2 VPN and Layer 3 VPN routes. PR1492743
The rpd process might report 100 percent CPU usage with BGP route damping enabled. PR1514635
Resolved Issues: 19.4R2
General Routing
On PTX3000 and PTX5000 platforms, interface might stay down after maintenance. PR1412126
The l2cpd process might crash and generate a core file when interfaces flap. PR1431355
Upgrading fails due to communication failure between Junos VM and host OS. PR1438219
FPC reboot might in the event of J-Lock hog for more than 5 seconds. PR1439929
The 100-Gigabit Ethernet interface might not come up after flapping on PTX5000. PR1453217
The local-loopback test fails with gigether-options. PR1458814
On PTX1000 and PTX10002 devices traffic might get silently dropped and discarded after transient SIB and FPC voltage alarms. PR1460406
The sample/syslog/log action in output firewall filter with packet of size less than 128 bytes might cause ASIC wedge (all packet loss) on PTX Series platforms. PR1462634
PIC might restart if the temperature of QSFP optics is overheated on PTX3000 and PTX5000. PR1462987
FPC might restart during runtime on PTX10000 and QFX10000 platforms. PR1464119
EBUF parity interrupt is not seen on PTX Series platforms. PR1466532
Packet Forwarding Engine error logs prds_packet_classify_notification: Failed to find fwd nh for flabel 48 might be reported when IGMP packets got sampled on PTX5000 platform. PR1466995
Optics measurements might not be streamed for interfaces of a PIC over JTI. PR1468435
The aftd-expr core filed generated at JexprDfwTlvIffBindPoint, JexprHandleFilterBindPoint, EmExprFilterBindPoint, EmEngineCoreGroupManager, EmEngine::performAction. PR1468483
Incorrect counter value is seen for arrival rate and peak rate for DDoS command. PR1470385
A PTX5000 SIB3 might fail to come up in slot 0 and/or slot 8 when RE1 is master. PR1471178
The input-vlan-map or output-vlan-map might not work properly in Layer 2 circuit local-switching scenario. PR1474876
mib2d generates core files while deleting channelized interfaces. PR1479642
Adding or deleting multicast routes might cause adjacency and LSPs to go down. PR1479789
FPC might crash when dealing with invalid next hops. PR1484255
BFD sessions start to flap when the firewall filter in the loopback0 is changed. PR1491575
Infrastructure
Slow response from SNMP might be observed after an upgrade to Junos OS Release 19.2R1 and later releases. PR1462986
Layer 2 Ethernet Services
Member links state might be asynchronized on a connection between PE device and CE device in an EVPN A/A scenario. PR1463791
MPLS
Kernel crashes and the device might restart. PR1478806
BGP session might keep flapping between two directly connected BGP peers because of the incorrect use of the TCP-MSS. PR1493431
Routing Protocols
SSH login might fail if a user account exists in both local database and RADIUS or TACACS+. PR1454177
On PTX3000 and PTX5000, ppmd crashes and a core file is generated after configuring sbfd responder on RE-DUO-2600. PR1477525
The rpd process might crash with BGP multipath and routes withdraw occasionally. PR1481589
Resolved Issues: 19.4R1
Forwarding and Sampling
PFED core files are seen and MIB2D is reported as slow peer due to a Packet Forwarding Engine accounting issue. PR1452363
General Routing
The agentd sensor transmits multiple interface telemetry statistics per FPC slot. PR1392880
On PTX10000, the FPC might restart during run time. PR1464119
On PTX platforms, reclassification policy applied on the route prefixes might not work. PR1430028
The Layer 2 cpd process might crash and generate a core dump when interfaces flaps. PR1431355
On the PTX1000 or PTX10002 devices, the PIC and interfaces might not come up after FPC reboot. PR1441256
On the PTX3000 devices, if the IPLC card is present in the device when you perform the GRES operation, the IPLC card crashes. PR1415145
On PTX3000 and PTX5000, PIC might restart if the temperature of QSFP optics is overheated. PR1462987
Incorrect counter values are observed for the arrival rate and peak rate for DDoS commands. PR1470385
The aggregated Ethernet interface does not have LACP enabled over the circuit cross-connect between R0 and R3. PR1424553
After you reboot the FPC, an interface comes up. PR1428307
On the PTX10000 devices that use the LC1105 line card, you might observe traffic loss. PR1433300
On the PTX10002 devices, chassis alarm is not raised when a PEM is removed or power to the PEM is lost. PR1439198
On the PTX Series devices, the CPU or an interface might become unresponsive on a particular 100-Gigabit port. PR1440526
Interfaces on the PTX Series devices might not come up after the FPC restarts or a port flaps. PR1442159
BCM FW needs to be upgraded to DE2E. PR1445473
Receipt of a malformed packet for J-Flow sampling might create a FPC core file. PR1445585
The option to use wildcard <*> is not available at the group level of the Junos CLI. PR1445651
The jdhcpd process might crash after the show access-security router-advertisement-guard command is issued. PR1446034
Upon steering of underlay dynamic tunnel PNHs to a different set of ECMP NHs, the tunnel that shared the same PNH might send traffic with wrong VLAN. PR1446132
On the PTX Series devices, if sFlow is configured on more than eight interfaces, egress sampling might stop working. PR1448778
Currently, ISIS sends system host name instead of system ID in the OC paths in lsdb or adjacency xpaths in periodic streaming and on change notification. PR1449837
Interfaces might flap after deleting the interface disable configuration. PR1450263
JNP10K-LC2101 FPC generates "Voltage Tolerance Exceeded" major alarm for EACHIP 2V5 sensors. PR1451011
Firewall filter applied at the interface level does not work when entropy level is present in certain scenarios. PR1452716
The FPC might crash when the severity of error is modified. PR1453871
GRPC updates on_change does not work when performing delete operations. PR1459038
On the PTX1000 devices, scaling with 5000 tunnels adds JENCAP error messages in log and drops traffic. PR1459484
Traffic is on hold when the interface flaps interface flap after DRD automatically recovers. PR1459698
The forwarding option is not present in the routing instance type. PR1460181
Hardware failure in CB2-PTX causes traffic interruption. PR1460992
IPv6 ping does not work between CE to CE in the Layer 3 VPN network. PR1466659
Traffic loops for pure Layer 2 packets coming over EVPN tunnel with destination MAC matching IRB MAC. PR1470990
Infrastructure
On all Junos OS VM-based platforms, the FPC might reboot if jlock hog occurs. PR1439906
Interfaces and Chassis
Due to the an issue in DWDM media, if any LAG member interface flaps, the LAG/ae stop receiving the LACP RX packets and fails to come UP. The LAG interface can be recovered by disabling/enabling the LAG interface. PR1429279
Layer 2 Ethernet Services
DHCP requests might get dropped in a DHCP relay scenario. PR1435039
MPLS
On a PTX Series router, the transit packets might be dropped if an LSP is added or changed. PR1447170
Platform and Infrastructure
The REST service might become nonresponsive when the REST API receives several continuous HTTP requests. PR1449987
Packet drops, replication failure or ksyncd crash might be seen on the logical system of a Junos device after Routing Engine switchover. PR1427842
Routing Protocols
PTX Series devices cannot intercept PIM BSR message. PR1419124
The rpd might crash with a change in SRTE configuration. PR1442952
SSH login might fail if a user account exists in both local database and RADIUS/TACACS+. PR1454177
On the PTX1000 devices, the Layer 3 VPN PE-CE link protection exhibits unexpected behavior. PR1447601
The other querier present interval timer cannot be changed in a IGMP/MLD snooping scenario. PR1461590
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
Memory leak might happen if PIM messages are received over an MDT (mt interface) in Draft-Rosen MVPN scenario. PR1442054
Documentation Updates
This section lists the errata and changes in Junos OS Release 19.4R3 documentation for the PTX Series.
Feature Guides Are Renamed as User Guides
Starting with Junos OS 19.4R1, we renamed our Feature Guides to User Guides to better reflect the purpose of the guides. For example, the BGP Feature Guide is now the BGP User Guide. We didn’t change the URLs of the guides, so any existing bookmarks you have will continue to work. To keep the terminology consistent on our documentation product pages, we renamed the Feature Guides section to User Guides. To find documentation for your specific product, check out this link.
Migration, Upgrade, and Downgrade Instructions
This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS. Upgrading or downgrading Junos OS might take several hours, depending on the size and configuration of the network.
Basic Procedure for Upgrading to Release 19.4
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.
Back up the file system and the currently active Junos OS configuration before upgrading Junos OS. This allows you to recover to a known, stable environment if the upgrade is unsuccessful. Issue the following command:
The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the router, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and SSH files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the Installation and Upgrade Guide.
We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.
To download and install Junos OS Release 19.4R3:
- Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:
- Select the name of the Junos OS platform for the software that you want to download.
- 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.
- Click the Software tab.
- In the Install Package section of the Software tab, select the software package for the release.
- Log in to the Juniper Networks authentication system by using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
- Review and accept the End User License Agreement.
- Download the software to a local host.
- Copy the software to the routing platform or to your internal software distribution site.
- 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 composed 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-19.4R3.9.tgzCustomers in the Eurasian Customs Union (currently composed 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-19.4R3.9-limited.tgzReplace 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/pathnamehttp://hostname/pathnamescp://hostname/pathname
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.
You need to install the Junos OS software package and host software package on the routers with the RE-PTX-X8 Routing Engine. For upgrading the host OS on this router with VM Host support, use the junos-vmhost-install-x.tgz image and specify the name of the regular package in the request vmhost software add command. For more information, see the VM Host Installation topic in the Installation and Upgrade Guide.
Starting in Junos OS Release 19.4R3, in order to install a VM host image based on Wind River Linux 9, you must upgrade the i40e NVM firmware on the following PTX Series routers:
PTX3000, PTX5000, PTX10016, PTX10008, and PTX10002-XX
After you install a Junos OS Release 19.2jinstall package, you cannot return to the previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.
Most of the existing request system commands are not supported on routers with RE-PTX-X8 Routing Engines. See the VM Host Software Administrative Commands in the Installation and Upgrade Guide.
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 17.4, 18.1, and 18.2 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3. 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 about EEOL releases and to review a list of EEOL releases, see https://support.juniper.net/support/eol/software/junos/.
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:
Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.
Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.
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.
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.