Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Open Issues

Learn about open issues in this release for PTX Series routers.

For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.

Class of Service (CoS)

  • On all Junos OS Evolved based platforms, in a rare scenario, if the interface or CoS configuration is continuously activated or deactivated, the cosd crash might be observed, impacting the class-of-service feature functionality. PR1566161

  • On the Junos Evolved (PTX10001-36MR, PTX10003, PTX10004, PTX10008) devices, when configuring class-of-service stanza with interface all, the configuration of class-of-service interface all is committed without an error. However, it does not actually set scheduler, classifier, or rewrite policy. PR1592900

General Routing

  • On PTX10008 routers, the subsystem within the Packet Forwarding Engine continues to monitor the ASIC for new interrupts even for the ASIC for which all the interfaces are disabled. On an ASIC that has all the interfaces disabled due to a fatal error, all the new interrupts that are reported after the fatal event must be ignored. PR1470391

  • SNMP get-next request does not work properly when partial indices are given on PTX Series platforms running Junos OS Evolved. PR1535204

  • PTX10008 JNP10K-LC1202 : When applications crash on the FPCs, these application core files generated in a rare scenario might not be transferred to the Routing Engine. This is because the script that transfers core files from the FPC to the Routing Engine fails to create directory on the Routing Engine. This happens when a file with the same name exists on the Routing Engine. PR1540807

  • Intermittent license-check.core files are observed during the device initialization. License daemon restarts and starts providing the required support. There is no service impact. PR1545175

  • The interrupt dp_xx_viqm_intr_req_enq_err might surface up intermittently in the logs, but it can be safely ignored as it surfaces up mostly for a number of scenarios which do not have any service impact. Because of the design of the underlying silicon, this interrupt cannot be completely avoided which have absolutely no service impact in almost all scenarios unless joined by a few other severe interrupts. PR1553943

  • The timingd-lc errors CdaExprClient: grpc api call ExprServerInfoGet failed and CdaExprClient: Failed to fetch server info error:5 are seen on all FPCs after restarting the router or FPC restart. PR1561362

  • On Junos OS Evolved platforms when an MPLS (Multiprotocol Label Switching) p2mp template is configured over the default_p2mp template, the configuration change does not take effect and the old configuration remains active. This is a functionality loss. PR1564795

  • With Junos OS Evolved on PTX10001-36MR, PTX10008 platforms, when the scheduler configuration is not applied to all 8 egress queues of an interface and one or more egress queues has buffer size remainder configuration, the distribution of buffer to egress queues with buffer size remainder is not distributed correctly, which might lead to unexpected tail drops. PR1575798

  • On PTX10008 platforms, when a large number of subscribers attempt to subscribe na-grpcd, core file migh tbe seen. All telemetry subscription connections close and collectors have to subscribe again. PR15783161

  • Minor TransientTraffic drop is seen during MBB of RSVP LSP without optimize-adaptive-teardown delay x configuration statement. PR1590656

  • show snmp mib walk sysDescr shows PTX10001-36MR. Inconsistency in the platform name used in multiple places, version, snmp mibs, etc. PR1597999

  • On PTX10003, the GRE keepalive packet with recursion control bit set gets dropped if the GRE header check is enabled. PR1602353

  • On Junos OS Evolved PTX10008 platform in FMBB (Fast Make-Before-Break) scenario, around 500 ms to 800 ms of traffic loss might be seen if the member link of aggregated Ethernet bundle of the p2mp LSP branches are down. PR1606839

Interfaces and Chassis

  • The local switching traffic sequence number is not reset. PR1560111

  • When the marvd daemon restarts for any reason, the device becomes unreachable because of PCI uncorrectable non-fatal AER errors getting generated on marvd restart and the system reboots without any core file. This is a rare event that occurs if there are marvd crashes. PR1600870

Junos XML API and Scripting

  • On a Junos OS Evolved device, any files scheduled for download using the CLI command request system download might fail due to error. The files can be downloaded using ftp or scp commands on the device. PR1604622

Layer 2 Features

  • If request system zeroize does not trigger zero-touch provisioning, re-initiate the ZTP as a workaround. PR1529246


  • The in-progress change of weighted ECMP to ECMP and vice versa does not take full effect for all routes using the LSPs until all those LSPs currently signaled with non zero bandwidth have gone through at least one of the MBB or clear or disable event. The traffic distribution is not as expected until all the LSPs finish the transition. This is because without any of those triggers, the LSP does not automatically update the next hop based on weighted ECMP configuration, next-hop content of each participation LSP affects the traffic distribution among ECMP paths. The weighted ECMP distribution ratio is not as expected until the adjustment of all LSPs are finished. PR1501860

  • When we configure minimum-bandwidth, the LSP is still resignalled with the previous configured minimum-bandwidth and not the current configured minimum-bandwidth. PR1526004

Network Management and Monitoring

  • On all Junos OS Evolved based platforms, the SNMP polling failures timeout might be observed when the number of outstanding requests to any subagent (mib2d, snmpd-subagent) reaches 500. This impacts the snmp polling functionality. PR1585409

Routing Policy and Firewall Filters

  • In Junos OS Evolved platforms the configuration check fails if more than 8 FCs are configured and CBF is enabled. Junos OS Evolved can support upto 16 FCs with CBF. Therefore, max-forwarding-classes platform-parameters configuration statement is added to the default configuration for Junos OS Evolved platforms. PR1600544

Routing Protocols

  • On Junos OS Evolved platforms, an rpd crash might be seen after reboot of the Junos OS Evolved device when MSDP is enabled. This might cause traffic drop until the rpd comes up after the crash and restores all the routes. PR1536593

User Interface and Configuration

  • When a user tries to deactivate the MPLS related configuration, the commit fails on the backup Routing Engine. PR1519367

  • While performing commit-check for the firewall and interface related configurations, if an operator uses ctrl+C to abort it, the dfwc and dcd might crash after performing another commit-check. This issue happens only with those daemons that follow the message-based commit-check model (such as dfwc, dcd, rdmd and fwa), and has no impact on other daemons. PR1600435