Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1X49-D10.

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

Application Layer Gateways (ALGs)

  • On SRX5400, SRX5600, and SRX5800 devices, the SQL ALG is disabled by default in Junos OS Release 15.1X49-D10. PR1093193

Chassis Cluster

  • On SRX5400, SRX5600, and SRX5800 devices, all interfaces of the RG0 secondary node go down when the connection between the kernel of the primary node and the ksyncd of the secondary node fails. PR1084660

Flow-Based and Packet-Based Processing

  • On SRX5400, SRX5600, and SRX5800 devices, when the SPU works in high stress, the internal event queue becomes full and the event is lost. Because there is no retransmission mechanism for the internal event, this leads to a stuck session. The stuck session is recovered by up layer applications. For example, when the TCP session of the log module is stuck, the log message cannot be sent. After 30 seconds, the log module detects this and restarts the new connection to send the log message.

    As a workaround, for next-generation SPCs, the maximum concurrent sessions that need Layer 7 processing are 3000 per SPU. This number varies for different platforms. PR1060529

  • On SRX5400, SRX5600, and SRX5800 devices in a chassis cluster with seven Services Processing Cards (SPCs) and multiple IPv6 policies (around 90 policies), when you reboot the device, flowd core files are generated. After the Switch Control Boards (SCBs) identify SPCs and initialize the SPC hardware, the Routing Engine policies are synchronized with the Packet Forwarding Engine. Therefore, one or more SPCs from either the primary node or the secondary node generate flowd core files. As a result, when all SPCs in the primary node or the secondary node undergo a reset, some of the flowd core files might again be generated. This issue does not occur after the chassis cluster is stable and all SPCs are online.

    After you reboot the device, some SPUs might stay in offline state and generate flowd core files.

    As a workaround, do the following:

    1. Disable the control and fabric links.
    2. Deactivate the IPv6 policies and then reboot the affected node.
    3. After all images are online and the chassis cluster is stable, activate the IPv6 policies.

    PR1089272

J-Web

  • On SRX5400, SRX5600, and SRX5800 devices, when you go to the Monitor>NAT>Source NAT page and click the Resource Usage tab, all Pool type values in the grid are displayed as PAT. J-Web fails to recognize the non-PAT pool. PR1036621

Security

  • On SRX5400, SRX5600, and SRX5800 devices, Junos OS Release 15.1X49-D10 uses newer versions of OpenSSL that have improved security features. These features consume higher amounts of memory per session. For example, when you use SSL forward proxy, the session scaling numbers are less compared to Junos OS Release 12.1X47 and Junos OS Release 12.3X48 session scaling numbers. PR1084348

System Logging

  • On SRX5400, SRX5600, and SRX5800 devices in a chassis cluster, when you run the request system configuration rescue save command, the following error message is displayed: command is not valid on the srx5800. However, the functionality works as expected. PR1097154

Related Documentation

Modified: 2016-12-21