Upgrade information

QRadar 7.4.1 Fix Pack 2 resolves reported issues from users and administrators from previous QRadar versions. This cumulative software update fixes known software issues in your QRadar deployment. QRadar software updates are installed by using an SFS file, and updates all appliances attached to the QRadar Console.

The 741_QRadar_FixPack2_2020.3.2.20201112005343 SFS file can upgrade QRadar 7.3.0, 7.3.1, 7.3.2, 7.3.3 (Fix Pack 6 or earlier), 7.4.0 or 7.4.1 to QRadar 7.4.1 Fix Pack 2. However, this document does not cover all of the installation messages and requirements, such as changes to appliance memory requirements or browser requirements for QRadar. To review any additional requirements, see the QRadar Upgrade Guide.

See QRadar: Software update check list for administrators for a list of steps to review before you update your QRadar deployment.

Before you begin

Ensure that you take the following precautions:

• Back up your data before you begin any software upgrade. For more information about backup and recovery, see the QRadar Administration Guide.
• To avoid access errors in your log file, close all open QRadar sessions.
• The QRadar software update cannot be installed on a managed host that is at a different software version from the Console. All appliances in the deployment must be at the same software revision to update the entire deployment.
• Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed.
• If this is a new installation, review the instructions in the QRadar Installation Guide.

Installing the QRadar 7.4.1 Fix Pack 2 Software Update

These instructions guide you through the process of upgrading an existing QRadar version at 7.3.0, 7.3.1, 7.3.2, 7.3.3 (Fix Pack 6 or earlier), 7.4.0 or 7.4.1 to QRadar 7.4.1 Fix Pack 2. To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel.

Note: Installing the software update for the first time will require more time than previous releases. This is a result of architectural changes in QRadar 7.4.0.

1. Download the software update to install QRadar 7.4.1 Fix Pack 2 from the IBM Fix Central website: http://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+Vulnerability+Manager&release=All&platform=All&function=fixId&fixids=7.4.1-QRADAR-QRSIEM-20201112005343&includeSupersedes=0&source=fc
2. Use SSH to log in to your Console as the root user.
3. To verify you have enough space (5GB) in /store/tmp for the QRadar Console, type the following command:

   df -h /tmp /storetmp /store/transient | tee diskchecks.txt

   • Best directory option: /storetmp

     It is available on all appliance types at all versions. In QRadar 7.4.0 versions /store/tmp is a symlink to the /storetmp partition.

If the disk check command fails, retype the quotation marks from your terminal, then re-run the command. This command returns the details to both the command window and to a file on the Console named diskchecks.txt. Review this file to ensure that all appliances have at minimum 5GB of space available in a directory to copy the SFS before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less that 5GB available.

Note: In QRadar 7.3.0 and later, an update to directory structure for STIG compliant directories reduces the size of several partitions. This can impact moving large files to QRadar.

1. To create the /media/updates directory, type the following command:

   mkdir -p /media/updates

2. Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with 5GB of disk space.
3. Change to the directory where you copied the patch file. For example,

   cd /storetmp

4. To mount the patch file to the /media/updates directory, type the following command:

   mount -o loop -t squashfs /storetmp/741_QRadar_FixPack2_2020.3.2.20201112005343.sfs /media/updates

5. To run the patch installer, type the following command:

   /media/updates/installer 

   Note: The first time that you run the software update, there might be a delay before the software update installation menu is displayed.

6. Using the patch installer, select the patch option that you want to use.
   • The all option updates the software on all appliances in the following order:
     1. Console
     2. Remaining appliances.

   • If you do not select the all option, you must select your Console appliance.

     As of QRadar 7.2.6 Patch 4 and later, you are only provided the option to update all or update the Console appliance. Managed hosts are not displayed in the installation menu to ensure that the Console is patched first. After the Console is patched, a list of managed hosts that can be updated is displayed in the installation menu. This change was made starting with QRadar 7.2.6 Patch 4 to ensure that the Console appliance is always updated before managed hosts to prevent upgrade issues.

     If you want to patch systems in parallel, you can update the Console first, then copy the patch to all other appliances and run the patch installer individually on each managed host. There is no order required in how you update appliances after the Console is updated. The Console must be patched first before you can run the installer on managed hosts.

     If your Secure Shell (SSH) session is disconnected while the upgrade is in progress, the upgrade continues. When you reopen your SSH session and rerun the installer, the patch installation resumes.

Installation wrap-up

1. After the patch completes and you have exited the installer, type the following command:

   umount /media/updates

2. Clear your browser cache before you log in to the Console.
3. Delete the SFS file from all appliances.

Results

A summary of the software update installation advises you of any managed hosts that were not updated. If the software update fails to update a managed host, you can copy the software update to the host and run the installation locally.

After all hosts are updated, send an email to your team to inform them that they will need to clear their browser cache before they log in to the QRadar SIEM interface.