Upgrading JSA to 7.5.0 UP8
SUMMARY You must upgrade all of the JSA products in your deployment to the same version.
Determine the minimum JSA version that is required for the version of JSA to which you want to update.
-
Click Help > About to check your current version of JSA.
To ensure that JSA upgrades without errors, verify that you use only the supported versions of JSA software.
Important:
-
Software versions for all JSA appliances in a deployment must be the same version and fix level. Deployments that use different JSA versions of software are not supported.
-
Custom DSMs are not removed during the upgrade.
-
After you upgrade to JSA Update Package 8, WinCollect 7.3.1 managed agents do not receive updates from encrypted JSA managed hosts.
Upgrade your JSA Console first, and then upgrade each managed host. In high availablity (HA) deployments, when you upgrade the HA primary host, the HA secondary host is automatically upgraded.
The following JSA systems can be upgraded concurrently:
-
Event processors
-
Event collectors
-
Flow processors
-
Data nodes
-
App hosts
What to do next:
-
Unmount /media/updates by typing the following command:
umount /media/updates
-
Delete the SFS file.
-
Perform an automatic update to ensure that your configuration files contain the latest network security information. For more information, see Checking for New Updates.
-
Delete the patch file to free up space on the partition.
-
Clear your web browser cache.
FIPS mode only To verify that the FIPS mode is enabled, run the following command.
fips-mode-setup --check
If the FIPS mode is disabled, run the following command, and then reboot your system to enable the
FIPS mode.
/opt/qradar/bin/qradar_fips_toggle.sh enable
If you have custom syslog-ng configuration files, update your files to ensure compatibility with the new
syslog-ng syntax in version 3.23.
-
Determine whether there are changes that must be deployed. For more information see “Deploying Changes” in Juniper Secure Analytics Administration Guide.