IBM Support

Release of the QRadar V7.3.2 Interim Fix 02 SFS (

Release Notes


This technical note contains installation instructions, and a list of new features and resolved issues for the IBM Security QRadar V7.3.2 Interim Fix 02 ( SFS. These instructions are intended for administrators who use an SFS file to upgrade from QRadar V7.3.2 to QRadar V7.3.2 Interim Fix 02.


What's new

For information on what's new in QRadar V7.3.2, see the following information:

Upgrade information

QRadar V7.3.2 Interim Fix 02 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 732_QRadar_interimfix- SFS file can upgrade QRadar V7.3.2 to QRadar V7.3.2 Interim Fix 02. 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 .

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 .

Azure Marketplace Images

There is an issue related to incorrect hostnames in QRadar Azure Marketplace images. To resolve, follow this procedure before you upgrade to QRadar V7.3.2:
  1. Download the hostname helper script.
    • If you are installing a Console, download the Console script from Fix Central.
    • If you are installing a managed host, download the managed host script from Fix Central.
  2. Upload the script to your virtual appliance.
  3. To change the file permissions on the script, type the following command.
    • For a Console:
      •   sudo chmod +x
    • For a managed host:
      •   sudo chmod +x
  4. To run the script, type the following command.
    • For a Console:
      •   sudo ./
    • For a managed host:
      •   sudo ./

Installing the QRadar V7.3.2 Interim Fix 02 Software Update

These instructions guide you through the process of upgrading an existing QRadar version at V7.3.2 to QRadar V7.3.2 Interim Fix 02. To update appliances in parallel, see: QRadar: How to Update Appliances in Parallel .

IMPORTANT: QRadar V7.3.2 includes stricter rules for Ariel queries to address APAR IJ13437. You must run the aqlValidator script to determine if any Ariel queries must be updated before you upgrade to QRadar V7.3.2. For more information about the aqlValidator script, see APAR IJ13446 .

If you have auto updates enabled, type the following command to run aqlValidator:


If you don't have auto updates enabled:

  1. Download the latest auto updates bundle from the IBM Fix Central website.
  2. To install the auto updates bundle, follow the instructions in QRadar: How to Manually Install the QRadar Weekly Auto Update Bundle .
  3. Type the following command to run aqlValidator:


  1. Download the software update to install QRadar V7.3.2 Interim Fix 02 from the IBM Fix Central website:
  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, and is not cleaned up if you need to postpone your update. In QRadar V7.3.0 versions /store/tmp is a symlink to the /storetmp partition.

    • 2nd best directory option: /tmp

      This directory is available on all appliances, but in V7.3.0 the version is significantly smaller and moving a file here can cause services to stop. If you leave a file in /tmp for 10 days without completing the SFS update, it might get cleaned up by Red Hat's tmpwatch cron job.

    • 3rd best option: /store/transient

      The store/transient directory was introduced in QRadar V7.2.1 and is allocated 10% of the overall /store directory. However, this directory does not exist on all appliances, such as QFlow or QRadar Network Insights and might not be an actual partition on all appliances.

      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 V7.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.

  4. To create the /media/updates directory, type the following command:
      mkdir -p /media/updates
  5. Use SCP to copy the files to the QRadar Console to the /storetmp directory or a location with 5GB of disk space.
  6. Change to the directory where you copied the patch file. For example,
      cd /storetmp
  7. To mount the patch file to the /media/updates directory, type the following command:
      mount -o loop -t squashfs /storetmp/732_QRadar_interimfix- /media/updates
  8. To run the patch installer, type the following command:

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

  9. Using the patch installer, select all.
    • The all option updates the software on all appliances in the following order:
      1. Console
      2. No order required for remaining appliances. All remaining appliances can be updated in any order that you require.
    • If you do not select the all option, you must select your Console appliance.

      As of QRadar V7.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 V7.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.


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.

Resolved Issues

Due to an issue in QRadar V7.3.0 and V7.3.1, the script did not remove files from the /storetmp directory. This issue is resolved in QRadar V7.3.2. For more information, see QRadar: Files in /storetmp get deleted daily in 7.3.2 .

For a list of APAR links of resolved issues in QRadar V7.3.2 Interim Fix 02, see Authorized Program Analysis Reports .

Some APAR links might take 24 hours to display properly after a software release is posted to IBM Fix Central.

Where do I find more information?

[{"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Release Notes","Platform":[{"code":"PF016","label":"Linux"}],"Version":"7.3","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
08 April 2019