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 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.

Content Security

  • Avira is not supported for SRX4700 in Junos OS release 24.4R1-S2. PR1851627

General Routing

  • Multiple vulnerabilities have been resolved in MQTT included with Junos by fixing vulnerabilities found during external security research. Refer to https://supportportal.juniper.net/JSA71655. PR1651519

  • Right after rebooting one of SRX4600 at high availability setup, CTL link might keep down. PR1802158

  • On SRX4100 and SRX4200 devices, MNHA Conn State and ICL are down after 48+ hours of device being up with background traffic due to BFD flaps at regular intervals. PR1822662

  • On SRX4600 device, if a few high-priority queues handle excessive traffic, those queues can become stuck, leading to packet drops. PR1823577

  • On SRX300 line of devices configured with native-vlan-id, after upgrading an SRX300 line of devices to Junos OS release 23.4R1 or higher, the native-vlan-id option disappears from the interface settings. If native-vlan-id was set before the upgrade, the device keeps the setting but it does not apply it to the interface. Deleting native-vlan-id causes a syntax error. The native-vlan-id feature doesn't work, and if a custom VLAN ID (other than 1) is used then traffic for that VLAN will be affected. PR1847366

  • CLI show security firewall-authentication users all-logical-systems-tenants shows null output for all-logical-systems-tenants filter, use show security firewall-authentication users all instead. PR1849954

  • On SRX Series Firewall and MX platforms a rare occurrence issue causes a sudden reboot of the SPC3 in use leading to packet loss during the card offline period in the reboot process.PR1857890

Network Management and Monitoring

  • Multiple stale sessions occur when two hosts use the same user-defined instance and routes are added or deleted on the server side. PR1825311