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 Security Director Release 18.1R2.

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

  • Grid column filter does not work for Internet Explorer 11. PR1161079

  • Cluster devices are discovered in different domains. PR1162407

  • After you upgrade Security Director, the custom column is not visible in the firewall rule grid. PR1256789

  • You must manually synchronize NSX with the vCenter server to view the latest restart or power off status. PR1285312

  • The global search for a dynamic address group does not work as expected. PR1285893

  • Any Service Groups notification sent from NSX to Security Director triggers an RPC update job for each vSRX device, instead of a single job with all the related vSRX devices. PR1288407

  • If there is a change in the login password of NSX Manager, vCenter, or Junos Space, then use the Edit NSX Manager page in Security Director to modify the login password information. Otherwise, synchronization of NSX Manager and dynamic address groups update fails.PR1291965

  • If NSX is integrated with Security Director, several login and logout entries are observed in the audit log. PR1291972

  • If you delete an NSX service, the associated firewall or IPS policies created by Security Director are also deleted. If you need a copy of the NSX-created group firewall or IPS policies, you must clone them manually before deleting the NSX service. PR1291974

  • As Security Director is not aware of the IDP licenses installed on the NSX Manager with vSRX VM, you must perform the full probe during the installation of the IDP signature. PR1291977

  • If the Policy Enforcer VM is down or the NSX services are down when there is a change in the service group membership in NSX, you cannot trigger an event to vSRX to poll for the latest service group members from the feed server. PR1295882

    Workaround: Perform one of the following actions to trigger events to vSRX instances:

    • Modify the description of the service group when the services or Policy Enforcer VM is down.

    • Log in to the vSRX device by using the SSH command and execute the following command:

      request security dynamic-address update address-name Dynamic-Address-Name

  • Application firewall OCR fails when the OVER WRITE option is selected.

    Workaround: You can choose the RE_NAME option and proceed with the rollback or import. PR1324941

  • When you try to add device-specific values for child domains in variable addresses or zones, the changes are not saved in the user interface. PR1330389

  • NAT pool is not shown in the OCR screen if the used address has conflicts. PR1330392

  • While upgrading log collector from Security Director Release 17.2R2 to Security Director Release 18.1R1 using a log collector upgrade script, if log collector reboots during the upgrade, then the Security Director node addition procedure fails. PR1350341

  • Importing variables from CSV is not working as expected. PR1350890

  • Dashboard widget preferences are not retained after upgrading log collector from Security Director Release 17.1R1 to Security Director Release 18.1R1. PR1350292

  • In the Job Management page, Date and Time filter for columns is not working as expected. PR1350906

For known issues in Policy Enforcer, see Policy Enforcer Release Notes.

Modified: 2018-07-31