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

  • You must manually sync NSX or vCenter to view the latest status. PR1285312
  • The global search of Dynamic Address Group (DAG) does not work as expected. PR1285893
  • If there is a change in the login password of NSX Manager, vCenter, or Junos Space, use the Edit NSX Manager page in Security Director to modify the loging password information. Otherwise, NSX Manager sync and DAG update will fail. PR1291965
  • If NSX is integrated in Security Director, you will see several login and logout entries in the audit log. PR1291972
  • Because Security Director is not aware of the IDP licenses installed on the NSX-vSRX device, you must perform the full probe during the IDP signature install. PR1291977
  • If you add NSX Manager and deploy the Juniper Networks services before Security Director installs the IDP signatures, vSRX device is discovered. However, you must install the IDP signature offline, create the IDP policy, and assign the NSX-vSRX devices. PR1291979
  • When you add a NSX Manager having more than 100 security groups, a proxy timeout error is shown on the Security Director UI. You can ignore this error because NSX Manager is added in Security Director. Discard the Add NSX Manager page and do a manual sync of newly added NSX Manager. PR1292036
  • When you add NSX Manager and deploy Security Director as a service manager in NSX, the audit log shows the current shows the Policy Enforcer IP address as the current logged in user. At the back end, the communication between NSX and Security Director happens through REST API. PR1293841
  • If Policy Enforcer is not configured in Security Director and you click the NSX Manager or vCenter page, the page loading icon is shown forever.PR1294177

Modified: 2017-07-19