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 

Resolved Issues

This section lists the issues that have been fixed in the Junos OS Release 18.2R1.

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

Licensing

  • On all SRX models, including vSRX instance, in rare cases you might find that the routing engine CPU utilization becomes high after renewing a license key. PR1325236

Interfaces and Routing

  • The minimum source-threshold and destination-threshold value for tcp syn-flood in the set security screen ids-option command has changed from 1 to 4. PR1349327

Platform and Infrastructure

  • During an upgrade from Junos OS 17.3R1 to 17.4R1, if there is a specific AppSecure configuration, configuration errors might prevent HA cluster devices from booting up normally. PR1317563

  • The request message all message command does not work properly when executed using REST API because the vSRX instance does not support the XML equivalent of the remote procedure call (RPC) command. PR1324627

    The vSRX instance now supports the following new XML tag to support the RPC command: <rpc><request-message-all><message>test</message></request-message-all></rpc>.

  • On vSRX instances, and SRX1500, SRX4100, and SRX4200 Series devices, you might find that NTP synchronization fails after a period of time and switches to the local clock.PR1331444

  • When deploying a vSRX instance in a KVM or Contrail environment with the vhost_net NIC driver, the vSRX might process and forward all unicast packets which were flooded to the port, regardless of the destination MAC address. PR1344700

Routing Policy and Firewall Filters

  • On all SRX models, including vSRX instances, when source address is configured for a name-server configuration, the source address is not actually used for the DNS lookup. In addition, the security dns-cache table will not be populated, and security policies are unable to use the FQDN addresses. PR1328925

Modified: 2018-06-28