Upgrade information

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

The 742_QRadar_FixPack_2020.7.1.20210105144619 SFS file can upgrade QRadar Incident Forensics 7.3.2 (Fix Pack 3 or later), 7.3.3 (Fix Pack 6 or earlier), 7.4.0, or 7.4.1 (Fix Pack 2 or earlier) to QRadar Incident Forensics 7.4.2 Fix Pack 1. 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 Incident Forensics Installation Guide.

See QRadar: Software update check list for administrators for a list of steps to review before you update your QRadar Incident Forensics 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 Incident Forensics Administration Guide.
• To avoid access errors in your log file, close all open QRadar Incident Forensics sessions.
• The QRadar Incident Forensics 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 Incident Forensics Installation Guide.

Installing the QRadar Incident Forensics 7.4.2 Fix Pack 1 Software Update

These instructions guide you through the process of upgrading an existing QRadar Incident Forensics version at 7.3.2 (Fix Pack 3 or later), 7.3.3 (Fix Pack 5 or earlier), 7.4.0, or 7.4.1 (Fix Pack 1 or earlier) to QRadar Incident Forensics 7.4.2 Fix Pack 1.

Important: You are prevented from upgrading to QRadar Incident Forensics 7.4.2 Fix Pack 1 from QRadar Incident Forensics 7.4.1 Fix Pack 2, QRadar Incident Forensics 7.3.3 Fix Pack 7, or QRadar Incident Forensics 7.3.3 Fix Pack 6.

If you attempt to upgrade from one of these unsupported versions, the following error message displays:

--> Finished Dependency Resolution 
Failed to resolve transaction dependencies Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-expression = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-poi = 3.17-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-web = 5.1.13.RELEASE-1Package: qvm-db-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: postgresql96-contrib = 9.6.15Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-context = 5.1.13.RELEASE-1Package: qvm-db-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: postgresql96 = 9.6.15Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-core = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-jdbc = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-web = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-tx = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-jdbc = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-aspects = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-beans = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local)
Requires: jars-spring-core = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-aop = 5.1.13.RELEASE-1Package: qvm-db-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: postgresql96-server = 9.6.15Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-context-support = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-aspects = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-tx = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-aop = 5.1.13.RELEASE-1Package: python-tdb-1.3.18-1.el7.x86_64 (@local) 
Requires: libtdb = 1.3.18-1.el7Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-expression = 5.1.13.RELEASE-1Package: qjars-2020.7.1-20210105144619_ctrh.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-beans = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-context = 5.1.13.RELEASE-1Package: qvm-spring-jars-2020.7.1-20210105144619.el7.x86_64 (qradar-upgrade-local) 
Requires: jars-spring-context-support = 5.1.13.RELEASE-1 
[INFO](testmode) Checking Disk Space... 
[WARN](testmode) WARNING: SET TRANSACTION can only be used in transaction blocks 
[INFO](testmode) Disk space checks adequate 
[WARN](testmode) WARNING: SET TRANSACTION can only be used in transaction blocks 
[ERROR](testmode) sql pretest errored, halting.[6/9] Install & Upgrade Packages failed to complete successfully. Errors: Failed yum transaction test

QRadar Incident Forensics 7.4.2 Fix Pack 1 does not contain all defect fixes from previous QRadar versions. The following issues that are resolved in QRadar Incident Forensics 7.4.1 Fix Pack 2 and QRadar Incident Forensics 7.3.3 Fix Pack 6 are not resolved in QRadar Incident Forensics 7.4.2 Fix Pack 1.

1. Download the software update to install QRadar Incident Forensics 7.4.2 Fix Pack 1 from the IBM Fix Central website: http://www.ibm.com/support/fixcentral/swg/quickorder?parent=IBM%20Security&product=ibm/Other+software/IBM+Security+QRadar+Incident+Forensics&release=All&platform=All&function=fixId&fixids=7.4.2-QRADAR-QIFSFS-20210105144619&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.1 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/742_QRadar_FixPack_2020.7.1.20210105144529.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 all.
   • 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 series, you can update the Console first, then copy the patch to all other appliances and run the patch installer individually on each managed host. The Console must be patched before you can run the installer on managed hosts. When updating in parallel, there is no order required in how you update appliances after the Console is updated.

     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.
4. To ensure that all services are running, on the Admin tab, click Advanced > Deploy Full Configuration.

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 Incident Forensics interface.