Learn about known limitations in this release for vSRX. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
On Microsoft Azure deployments, SSH public key authentication is not supported for vSRX 3.0 CLI and portal deployment. PR1402028
Platform and Infrastructure
When the traffic flow is high (throughput of 2 Gbps or more), reboot of vSRX 3.0 running with Hyper-V on windows server 2016 is not recommended. vSRX 3.0 VM might hang during boot process. We recommend that you schedule a reboot or an upgrade when there is no traffic. As a workaround, to recover the vSRX 3.0 VM, restart the instance again when the traffic stops. PR1394792
The CA profile group imported using J-Web does not populate the group in the Certificate Authority Group initial landing page grid, but all the CA profiles of a group are populated on the Trusted Certificate Authorities landing page. PR1426682
When a dynamic application is created for an edited policy rule, the list of services will be blank when you click the services tab and then the policy grid will be autorefreshed. As a workaround, create a dynamic application as the last action while modifying the policy rule and click Save button to avoid loss of configuration changes made to the policy rule. PR1460214
vSRX Limitations in Junos Space Security Director Integration with vSRX
The following vSRX features are not supported in Junos Space Security Director:
Application QoS (AppQoS)
Layer 2 transparent mode
Specific Security Director limitations with respect to Application Firewall (AppFW), IDP, and UTM features:
UTM database updates are not supported.
Application ID (AppID) custom signatures are not supported.
In Junos Space Security Director for IPsec and routing features, certificates for AutoVPN must be generated from the CLI. All other IPsec settings can be configured using Junos Space Security Director.