Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Release Notes for Juniper Security Director Insights

 

Product Compatibility

This section describes the supported hardware and software versions for Juniper Security Director Insights. For Security Director requirements, see the Security Director 22.1R1 Release Notes.

Supported Security Director Software Versions

Security Director Insights is supported only on specific Security Director software versions as shown in Table 1.

Table 1: Supported Security Director Software Versions

Security Director Insights Software Version

Compatible with Security Director Software Version

22.1R1

22.1R1

Note

The times zones set for Security Director and Security Director Insights must be the same.

Virtual Machine Specification

Security Director Insights requires VMware ESXi server version 6.5 or later to support a virtual machine (VM) with the following configuration:

  • 8 CPUs

  • 24-GB RAM

  • 1.2-TB disk space

Supported Browser Versions

Security Director and Juniper Security Director Insights are best viewed on the following browsers.

  • Mozilla Firefox

  • Google Chrome

Installation and Upgrade Instructions

For more information about installing Security Director Insights 22.1R1, see Deploy and Configure Security Director Insights with Open Virtualization Appliance (OVA) Files.

For Security Director Insights upgrade instructions, see Upgrade Security Director Insights

Known Issues

There are no known issues in Security Director Insights Release 22.1R1.

Resolved Issues

This section lists the issues fixed in Security Director Insights Release 22.1R1.

  • CON-1248 Not able to enable Security Director Insights high availability (HA). It fails with an error “Server is not reachable or down”.

  • CON-1284 Adding Policy Enforcer to Junos Space is failing.

  • CON-1291 Kafka error is encountered when Security Director Insights is upgrade to Security Director Insights Release 22.1.

  • CON-1293 Performance of Security Director Insights Release 22.1 is not as expected.

  • CON-1279 After upgrading to Security Director Insights Release 22.1, an error “unable to add log collector” is encountered when you try to add Security Director Insights as a logging node in Security Director.

Hot Patch Releases

This section describes the known issues and resolved issues in Security Director Insights Release 22.1R1 hot patches.

Known Issues

This section describes the known issue in Security Director Insights Release 22.1R1 Hot Patch v2.

  • HA upgrade fails when SDI hostname has uppercase letters. PR1743770

    Workaround:

    You must disable HA, change hostname with only lowercase letters, and then enable HA again to successfully upgrade HA.

    SDI as Log Collector only (Only CLI is available)

    1. Disable HA via CLI on only primary node.

      CLI> (server) ha disable

    2. Change both primary and secondary SDI hostnames with only lowercase letters.

      CLI> (server) set hostname <...>

    3. Re-enable HA via CLI from primary node only. See Configure High Availability for Security Director Insights as Log Collector.
    4. After you have enabled HA, check CLI> (server) ha status, it should display that both the nodes are up.
    5. Perform HA upgrade from primary node. See Upgrade HA.

    SDI as analytics and Log Collector (Enable HA via GUI)

    1. Disable HA via GUI. See Disable HA.
    2. Change both primary and secondary SDI hostnames via CLI with only lowercase letters.

      CLI> (server) set hostname <...>

    3. Re-enable HA from GUI. See Enable HA.
    4. Wait till SDI HA setup is back online. GUI displays that both the nodes are up.
    5. Perform HA upgrade from primary node. See Upgrade HA.

Resolved Issues

Table 2 lists the resolved issues in Security Director Insights Release 22.1R1 hot patches.

Table 2: Resolved Issues in Hot Patches

PR

Description

Hot patch version

PR1727690

There is a circuit_breaking_exception while running Security Director reports.

v2

PR1728499

Group By "Category" shows No Data even though there are logs with category defined and seen in the events.

v2

CON-1459

Security Director Insights source IP address is showing incorrect country.

v1

PR1648703

Inconsistency in the number of events exported from Security Director to the CSV files.

v1