Release Notes for Juniper Security Director Insights
New Features
This section describes the new features in Juniper Security Director Insights Release 22.2R1.
Install with KVM virt-manager—Security Director Insights Release 22.2R1 or later can be deployed on qemu-kvm (KVM) Release 4.2.1 (Debian 1:4.2-3ubuntu6.23) or later.
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.2R1 Release Notes.
- Supported Security Director Software Versions
- Virtual Machine Specification
- Supported Browser Versions
Supported Security Director Software Versions
Security Director Insights is supported only on specific Security Director software versions as shown in Table 1.
Security Director Insights Software Version |
Compatible with Security Director Software Version |
---|---|
22.2R1 |
22.2R1 |
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 Instructions
For more information about installing Security Director Insights 22.2R1, see Deploy and Configure Security Director Insights with Open Virtualization Appliance (OVA) Files.
For more information about installing Security Director Insights 22.2R1 with KVM, see Install Security Director Insights With KVM virt-manager.
For Security Director Insights upgrade instructions, see Upgrade Security Director Insights
Known Issues
There are no known issues in Security Director Insights Release 22.2R1.
Resolved Issues
There are no fixed issues in Security Director Insights Release 22.2R1.
Hot Patch Releases
Known Issues
This section describes the known issue in Security Director Insights Release 22.2R1 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)
Disable HA via CLI on only primary node.
CLI> (server) ha disable
Change both primary and secondary SDI hostnames with only lowercase letters.
CLI> (server) set hostname <...>
Re-enable HA via CLI from primary node only. See Configure High Availability for Security Director Insights as Log Collector.
After you have enabled HA, check
CLI> (server) ha status
, it should display that both the nodes are up.Perform HA upgrade from primary node. See Upgrade HA.
SDI as analytics and Log Collector (Enable HA via GUI)
Disable HA via GUI. See Disable HA.
Change both primary and secondary SDI hostnames via CLI with only lowercase letters.
CLI> (server) set hostname <...>
Re-enable HA from GUI. See Enable HA.
Wait till SDI HA setup is back online. GUI displays that both the nodes are up.
Perform HA upgrade from primary node. See Upgrade HA.
Resolved Issues
This section describes the resolved issues in Security Director Insights Release 22.2R1 Hot Patch v2.
Resolved Issues
There is a circuit_breaking_exception while running Security Director reports. PR 1727690
Group By "Category" shows No Data even though there are logs with category defined and seen in the events. PR1728499