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 SRX Series devices.

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

Infrastructure

  • SRX550HM interfaces LED of ge-0/0/6-9 will auto turn off after device bootup some minutes.PR1634965

  • Earlier implementation of kvmclock with vDSO which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate.PR1691036

  • FIPS mode is not supported in this release for SRX SME devices.PR1697999

  • Mount Command from Shell mode is not supported for nfs in BSD12 based SRX320, SRX300, SRX345, SRX340, and SRX380 platforms. PR1701361

  • On SRX platforms, log streaming to the Juniper Security Director Cloud fails on TLS when DNS re-query is performed.PR1708116

  • For case when input traffic is more and output traffic is expected equal to maximum capacity of egress interface, please set the shaping explicitly equal to interface maximum capacity if default shaping does not work. PR1712964

  • On SRX platforms, Interface speed stays 100Mbps when removing speed and duplex command separately. PR1715247

  • In DNS response packets from the DNS server, the DNS flags do not have RA (Recursion Available) enabled. SRX discovers that this RA flag is disabled, and processes it as an error. The SRX then sends another DNS query to the second DNS server.PR1716171

  • On SRX4600 and SRX5K platforms, the L2 channel error counter will increase when some unknown family packets received by interfaces.PR1729284

J-Web

  • Certificate Management issues. As a workaround, you can use CLI to create, delete, or re-enroll certificates. PR1738316

VPNs

  • Tunnel debugging configuration is not synchronized to the backup node. It needs to be configured again after RG0 failover. PR1450393

  • First time when we add this command the existing active connections are not changed, only the new connection after this command will be taken into effect. PR1608715