Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

Learn about open issues in this release for the QFX5130-32CD and QFX5220.

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

Infrastructure

  • The standard "issue" message is not displayed for the initial login attempt, but if that login attempt fails for any reason and the user is re-prompted, then the message is displayed. This seems to be an issue common to QFX5130-32CD. PR1528996

Interfaces and Chassis

  • This issue seen from 20.4R1-EVO in QFX5130-32CD platform. OSPF routes are not learnt when neighborship is formed over IRB interfaces. PR1570498

Layer 2 Features

  • It was observed rarely that issuing a request system zeroize does not trigger Zero Touch Provisioning (ZTP). A simple workaround is to re-initiate ZTP. PR1529246

System Management

  • On the QFX5130-32CD platform running Junos OS Evolved, you cannot clear or reset the disk option specified in the scheduled request node reboot command. The node reboots with the disk option last specified. PR1517596

  • When the evo-pfemand process is restarted due to any error conditions, the channelized interfaces (if configured) flap two times: first during the initialization and the second time after the configuration is programmed. PR1526984

  • QFX5130-32CD Junos OS Evolved-pfemand binding queue complete-deleted objects are seen with hwd::pcsE. PR1531820

  • Intermittently 100G interfaces will not come up between PTX10003-80C and QFX5220-128C after a configuration change and commit. PR1531820

User Interface and Configuration

  • On box validation of the large YANG files on NETCONF through request-yang-validate RPC might not work as validation process might reach out of memory state while loading such YANG files. PR1416972