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.

General Routing

  • For the MPC10E card line, the IS-IS and micro-BFD sessions do not come up during baseline. PR1474146

  • IPsec tunnels are not deleted on disabling the AMS physical interface. PR1613432

  • You can configure per-interface egress and per-sid egress SR sensor statistics using the following CLI commands: set protocols isis source-packet-routing sensor-based-stats per-interface-per-member-link egress and set protocols isis source-packet-routing sensor-based-stats per-sid egress. As a result, the (pushed) MPLS label length does not include in the output/Tx octets field that gets exported from the sensor.

    PR1646799

  • After executing the clear vpls mac-table command, not all MAC addresses are learnt for some VPLS instances. PR1664694

  • Few protocol sessions remain down causing traffic loss in certain prefixes after quick arpd process disable and enable. The system can be recovered from erroneous state by executing restart routing gracefully in CLI. PR1665362

  • On all Junos OS Evolved platforms, incorrect sensor base telemetry data are collected when you configure multiple SR-TE tunnels with atleast one uncolored, sharing the same single hop segment list.PR1665943

  • UDP telemetry might not work when you subscribe to /junos/system/linecard/intf-exp/ sensor.PR1666714

  • New CLI commands addition to support Routing Engine and chassis power-cycle under request vmhost hierarchy. PR1686577

  • If you enable MVRP on an MSTP enabled interface, the interface is made part of all the existing instances on the switch. PR1686596

  • Junos OS Evolved release has a limitation of 255 characters for resource names. Increasing the limit has implications on the CLI output and same changes are needed to be propagated to lower layers where the resources are served from. PR1695980

  • When you configure the command set routing-options transport-class auto-createis, rpd creates or deletes tables dynamically. There is a flaw in the delete flow, which does not delete the table from the kernel and when rpd adds the same table next time, the operation is stuck with EEXISTS error, as previous delete was never done. .PR1696199

  • On all Junos OS Evolved platforms supporting MACsec, traffic drop can be seen when you configure MACsec primary and fallback sessions. As a result, there is a higher transmit-delay time of approximately 6 seconds. This is a timing issue and occurs when switching from primary to fallback or vice-versa. When changing the pre-shared-key's Connectivity Association Key (CAK) value in the CLI on the non-key-server side and at the same time key-server generates a new Secure Association Key (SAK) for pre-shared-key due to expiration of sak-rekey timer, that is, sak-rekey and primary to fallback key-switch both occurs at the same time. .PR1698687

  • With the BNG Control Plane User Plane Separation (CUPS) product, you observe an incorrect multicast QoS adjustment with interface-set queuing when you execute the show class-of-service interface-set command on the user plane. PR1714271

  • Whenever a new VLAN is added in between previously configured VLANs, existing context-id which already assigned to existing VLAN context, is assigned for the new VLAN. Therefore, we might see incorrect system-id or bridge-id and this might create an issue.PR1717267

Interfaces and Chassis

  • The link-local address is not assigned for the loopback interface after the upgrade or the device reboot on all Junos OS Evolved platforms. The impact depends on how the loopback interface is used in the configuration. It can cause a connectivity issue and traffic impact when it is used for the routing process.PR1695502

Junos XML API and Scripting

  • L2TP LAC functionality does not work in this release. PR1642991

MPLS

  • When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with routing problem (code=24/2) instead of originating PathErr with notify error (code/subcode=25/3). This does not cause any service impact if the ingress LER might not react adversely to routing problem error (code=24/2).PR1713392

Routing Policy and Firewall Filters

  • On all Junos OS Evolved PTX Series platforms, when the source class usage (SCU) or destination class usage (DCU) firewall filter is configured without payload protocol or TCP/UDP protocol, it does not work properly and gives errors whenever the filters are added or re-activated. When the error is encountered, the installation of other filters is also impacted.PR1699138

Routing Protocols

  • On all Junos OS Evolved platforms, the rpd can crash when protocol independent multicast (PIM), multicast only fast reroute (MoFRR) configuration is present and some network churn event such as continuous interface cost changes, resulting in a change of active and backup paths for equal cost multi-path (ECMP) occurs. There is service impact because of the rpd crash but the system self-recovers until the next crash. PR1676154

  • On all Junos OS Evolved platforms, the commit check fails and blocks LFA itself on one instance if you configure loop-free alternate (LFA) and Remote LFA (RLFA), Per-prefix LFA (PPLFA) in the routing-instance and topology independent LFA (TI-LFA) in the primary instance, along with segment routing and node-link-protection with post-convergence.PR1704521

VPNs

  • The rpd crash happens when multicast VPN is configured with separate route-targets scenario. PR1700345