- play_arrow JSA Deployment Overview
- play_arrow Bandwidth for Managed Hosts
- play_arrow Virtual Appliance Installations for JSA and Log Manager
- play_arrow Migrating to Docker Enterprise Edition with FIPS
- play_arrow Updating Cryptographic Modules for FIPS
- play_arrow Installations from the Recovery Partition
- play_arrow Reinstalling JSA from Media
- play_arrow JSA Software only Installations
- play_arrow Setting up a JSA Silent Installation
- play_arrow Configuring Bonded Management Interfaces
- play_arrow Network Settings Management
- play_arrow Troubleshooting Problems
Installing a JSA Console or Managed Host
Install JSA Console or a managed host on the JSA appliance that is FIPS enabled.
Software versions for all JSA appliances in a deployment must be same version and patch level. Deployments that use different versions of software is not supported.
Ensure that the following requirements are met:
The correct hardware is installed.
Create a bootable USB flash drive with Red Hat Linux. For more information, see Creating a Bootable USB Drive with Red Hat Linux.
Install JSA with a USB flash drive. For more information, see USB Drive Installations.
You have the required license key for your appliance.
A keyboard and monitor are connected by using the VGA connection.
There are no expired licenses on either the console or the managed hosts.
If you are installing JSA on a Unified Extensible Firmware Interface (UEFI) system, secure boot must
be disabled.
FIPS mode only: After the FIPS installation is complete, you must migrate Docker Community Edition (CE) to Docker Enterprise Edition (EE) on your JSA Console and 4000 appliance. You must ensure you have a Docker EE license. For more information, see Migrating to Docker Enterprise Edition with FIPS.
FIPS mode only (For JSA 7.5.0 GA to JSA 7.5.0 Update Package 7): To install an
appliance with FIPS enabled, add qradar.fips=1
to the
vmlinuz
.