Known Behavior

This section contains the known behavior and limitations in Junos Space Security Director Release 17.1.

• You must disable OpenNMS before installing integrated Log Collector.

  Procedure

  To disable OpenNMS :

  1. Select Network Management Platform > Administration > Applications.

     The Applications page appears.

  2. Right-click Network Management Platform and select Manage Services.

     The Manage Services page appears.

  3. Select Network Monitoring and click the Stop Service icon.

     The network monitoring service is stopped and the status is changed to Disabled.

  Note: You must ensure that the Network Management Platform and Security Director are already installed on a JA2500 or virtual machine.

• The Enable preview and import device change option is disabled by default. To enable this option, select Network Management Platform > Administration > Applications. Right-click Security Director and click Modify Application Settings. Under Update-Device, select the Enable preview and import device change option.
• If you restart the JBoss application server manually in a six-node setup one-by-one, the Junos Space Network Management Platform and the Security Director user interface are launched, within 20 minutes, and the device reconnects to the Junos Space Network Management Platform. You can edit and publish the policies. Once the connection status and the configuration status of all devices are UP and IN SYNC respectively, click Update Changes to update all security-specific configurations or pending services on SRX Series devices.
• To generate reports in the local time zone of the server, you must modify /etc/sysconfig/clock to configure the time zone. Changing the time zone on the server by modifying /etc/localtime is not sufficient.
• High availability for SRX Series devices is not supported in Release 17.1 of Policy Enforcer.
• After installing the Policy Enforcer Release 17.1 OVA image, you must manually start the following commands service commands:

  	service sd_event_listener start
  	service ssh_listener start
  

• If you have access permissions for firewall or NAT policy but do not have permission to create objects, you cannot configure address, service, and other objects in firewall or NAT policy.PR1140318
• If you configure the inactivity timeout parameter as never and do not logout the session, instead close the browser, your session is shown as active until you logout. PR1152754
• After you upgrade Security Director, only Super users can view the data in dashboard and event viewer.

  Workaround: Enable "View device logs" permission under "Event Viewer". PR1159530

• Grid column filter is not working in Internet Explorer 11 browser. PR1161079
• Cluster device must not be allowed to get discovered in different domains PR1162407
• Upgrading Log Collector or Indexer from Security Director Release 15.2R1 to Security Director Release 15.2R2 does not update the version as expected. LogCollector is upgraded to Security Director Release 15.2R1 to Security Director Release 15.2R2. However, the version is displayed as Security Director Release 15.2R1 under Security Director > Administration > Logging Management > Logging nodes page. PR1182608
• First time invocation of monitoring pages and the Top Compromised hosts dashboard widget shows the "An Error occurred while requesting the data error. PR1239956
• Custom column is not visible in the firewall rule grid after Security Director upgrade. PR1256789
• The Top compromised hosts widget in dashboard might not list all the realm. PR1262410
• The uploaded schema tar must be in the "/dmi/<device-type>/releases/<schema-version>/" folder. If not installation will be success, but the schema loading will be failed which results in failure of loading Modify configuration window. PR1268413