Release of the QRadar Network Insights 7.3.1 Patch 7 ISO (188.8.131.5281123182336)
This technical note contains installation instructions, new features, and includes a resolved issues list for the release of QRadar Network Insights 7.3.1 Patch 7 ISO (184.108.40.20681123182336). These instructions are intended for administrators who are upgrading from QRadar 7.2.8 Patch 3 or later to QRadar Network Insights 7.3.1 Patch 7 by using an ISO file.
For information on what's new in QRadar products for version 7.3.1, see: https://www.ibm.com/support/knowledgecenter/SS42VS_7.3.1/com.ibm.qradar.doc/c_qradar_ov_whats_new_731.html
About this upgrade
These instructions are intended to assist administrators to update appliances from QRadar 7.2.8 to QRadar Network Insights 7.3.1 Patch 7 by using an ISO file. This ISO can update QRadar SIEM, QRadar Risk Manager, and QRadar Vulnerability Manager products from 7.2.8 to version 7.3.1 Patch 7.
QRadar 7.3.1 Patch 7 uses an ISO file to update hosts to the latest software version. A minimum of QRadar 7.2.8 Patch 1 (or later) is required to be able to upgrade to QRadar Network Insights 7.3.1 Patch 7. Each host must be updated individually.
See QRadar: Software update check list for administrators for a list of steps to review before updating your QRadar deployment.
If you have installed QRadar 7.2.8 version or later, you are not required to install each ISO release to update to QRadar 7.3.1 Patch 7.
|Current Version||ISO Upgrades to QRadar Network Insights 7.3.1 Patch 7?|
|QRadar Network Insights 7.2.8 Patch 3 or later||Yes, use these release notes to complete this process.|
|QRadar Network Insights 7.3.0 (any patch version)||See the QRadar 7.3.1 Patch 7 SFS release notes.|
|QRadar Network Insights 7.3.1||See the QRadar 7.3.1 Patch 7 SFS release notes.|
Figure 1: If you have installed QRadar 7.2.8 or later, you are not required to install each ISO release to update to QRadar 7.3.1 Patch 7.
- The QRadar Console must be updated before you update your QRadar Network Insights appliance.
- If you have a software installation, you need your Red Hat Enterprise ISO and the QRadar Network Insights ISO. Administrators with software installations on their own hardware must read the QRadar Network Insights Install Guide to understand how to partition their systems appropriately.
- QRadar Network Insights must be on QRadar 7.2.8 Patch 3 or later to upgrade.
- The upgrade from QRadar 7.2.8 Patch 3 to QRadar Network Insights 7.3.1 Patch 7 will use a .ISO file. Previously, ISOs were for new appliance installations only, but QRadar 7.3.1 Patch 7 is an exception to this rule because of the Red Hat kernel update requirements.
- The ISO must be mounted to the appliance and run locally on each host.
- The 7.3.1 Patch 7 upgrade will take longer than expected due to the kernel changes to Red Hat 7 Enterprise. Early upgrade customers are reporting 2 to 2.5 hours to upgrade the Console appliance. You should be aware of this longer time frame and plan your maintenance accordingly.
- If power users created utilities or custom scripts for their QRadar deployment, these files should be copied off the system. During the 7.3.1 Patch 7 update, a warning is displayed that only data in /store is going to be preserved. After the appliance reboots, any scripts, 3rd party accounts, or utilities in /tmp, or /, or /root will be deleted. This does not impact ISO files mounted initially using /root because this cleanup only occurs later in the installation procedure.
Before you upgrade
Ensure that you take the following precautions:
- Back up your data before you begin any software upgrade and verify that you have recent configuration backups that match your existing Console version. If required, take an on demand configuration backup before you begin. For more information about backup and recovery, see the IBM QRadar Administration Guide.
- All appliances in the deployment must be at the same software and patch level in the deployment.
- Verify that all changes are deployed on your appliances. The update cannot install on appliances that have undeployed changes.
- A QRadar Network Insights 7.3.1 Patch 7 ISO is available to upgrade from QRadar 7.2.8 Patch 3 or install a new appliance or virtual machine. To complete a new installation, review the QRadar Network Insights Installation Guide.
- If you are unsure of the IP addresses or hostnames for the appliances in the deployment, run the utility /opt/qradar/support/deployment_info.sh to get a .CSV file with information about the QRadar deployment. The CSV file will contain a list of IP addresses for each managed host.
- If you are unsure of how to proceed when reading these instructions or the documentation, it is best to ask before starting your upgrade. To ask a question in our forums, see: http://ibm.biz/qradarforums.
Part 1. Staging files and pretesting your deployment (required)
It is important that you pretest your deployment to ensure that you will not experience unexpected issues when you update to QRadar 7.3.1 Patch 7. A pretest is a common precaution that should be taken before you install an update to locate potential issues. The pretest does not restart services and can be completed without scheduled downtime. The pretest typically takes between 3 to 5 minutes to complete on each appliance. If for some reason your SSH session is disconnected, you can reconnect to the remote host using screen.
The pretest should be completed on all hosts by the administrator before you attempt to upgrade to QRadar 7.3.1 Patch 7.
- Download the QRadar Network Insights 7.3.1 Patch 7 ISO (5+ GB) from the IBM Fix Central website: https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FIBM+Security+QRadar+Incident+Forensics&fixids=7.3.1-QRADAR-QIFFULL-20181123182336&function=fixId&parent=IBM%20Security
NOTE: QRadar Incident Forensics and QRadar Network Insights use the same ISO for both products to upgrade from 7.2.8 to 7.3.1 Patch 7.
- Use SSH to log in to your Console as the root user.
- Type the following command: screen
- To make the directory for the update, type: mkdir -p /media/cdrom
- To verify that you have enough space (5.5 GB), type: df -h /root /var/log | tee diskchecks.txt
- Best directory option: /root
It is available on all appliance types, and is the best option to host the ISO file.
- 2nd best directory option: /var/log
This directory is available on all appliances, but there might not be the required space available.
- DO NOT USE: /tmp, /store/tmp, or /store/transient for your ISO upgrade. These directories are partitioned as part of the upgrade and administrators cannot use them as storage locations or mount points for the ISO file.
If the disk check command fails, retype the quotation marks from your terminal, and 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 a minimum of 5.5 GB of space available in a directory to copy the ISO before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less than 5.5 GB available.
Reminder: Utilities or custom scripts that administrators have created for QRadar should be copied off the system. During the 7.3.1 update a warning is displayed that only data in /store will be preserved. Therefore, scripts, 3rd party utilities in /tmp, or /, or /root will be deleted during the upgrade.
- Best directory option: /root
- If there is not 5.5GB of space in /root or /var/log, the administrator must make directory space for the ISO file.
- Use WinSCP or SCP to copy the ISO to the /root or /var/log directory on the QRadar Network Insights appliance.
- To mount the ISO on all appliances, type mount -o loop /root/Rhe764QRadar7_3_1_20181123182336.stable-7-3-1.iso /media/cdrom
- To pretest the Console appliance, type: /media/cdrom/setup -t
The pretest output is written to the command window. Review this output after the pretest completes.
- Use SSH to open an SSH session to the other appliances in your deployment. QRadar Support recommends that all administrators run the pretest on each host to identify issues before the update begins.
- To pretest the managed host, type: /media/cdrom/setup -t
If an appliance in your deployment fails the pretest, take the recommended action from the pretest utility. The issue must be resolved before the update to 7.3.1 Patch 7 begins to prevent downtime for specific appliances. If there are messages you do not understand or want to discuss further, you can use our forums http://ibm.biz/qradarforums to get advice. Administrators can open a ticket directly with QRadar Support (http://ibm.biz/qradarsupport).
Part 2. Installing the QRadar Network Insights 7.3.1 Patch 7 ISO
These instructions guide administrators through the process of upgrading an existing QRadar Network Insights install at 7.2.8 Patch 1 or later to QRadar 7.3.1 Patch 7. The update on the Console must be completed before you attempt to update QRadar Network Insights.
- Use SSH to log in to the Console as the root user.
- Use SSH to log in to the QRadar Network Insights appliance.
- To run the ISO installer on the Console, type the following command: /media/cdrom/setup
Important: Upgrading from QRadar Network Insights 7.2.8 Patch 1 or later to QRadar Network Insights 7.3.1 Patch 7 can take approximately 1 to 2 hours.
Note: In QRadar 7.3.1 Patch 6, a kernel update was introduced to address issues with appliances failing to log in or list unit files. These issues could prevent the appliance from rebooting. This new kernel does not take effect until the appliance is rebooted. You might need to reboot your system manually for the kernel update to take effect.
To work around this issue, do one of the following:
- If you are able to use SSH, type the following command: systemctl --force --force reboot
- If you are not able to use SSH, you must perform a cold reboot of the appliance. To do this, physically reboot the appliance or use Integrated Management Module (IMM)
A summary of the ISO installation advises you of any issues. If there are no issues, administrators can use SSH to log in to managed hosts and start the installer on each host to run the setup in parallel.
Part 3. Installation wrap-up
- 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 QRadar SIEM.
- To unmount the /media/cdrom directory on all hosts, type: umount /media/cdrom"
- Administrators can delete the ISO from all appliances.
- Review any static routes or customized routing. As mentioned in the administrator notes, all routes were removed and must be reconfigured after the upgrade completes.
- Review all configured iptable rules because the interface names have changed in QRadar 7.3.1 Patch 7 due to the Red Hat Enterprise 7 operating system updates. Any iptables rules that use the Red Hat 6 interface naming conventions must be updated.
Some APAR links in the following table might take 24 hours to display properly after a software release is posted to IBM Fix Central.
|QRADAR||SECURITY BULLETIN||CVE-2018-2952||Multiple vulnerabilities in IBM Java SDK and IBM Java Runtime affect IBM QRadar SIEM|
|QRADAR||SECURITY BULLETIN||CVE-2018-1728||IBM QRadar SIEM is vulnerable to Cross-Site Scripting|
|QRADAR||SECURITY BULLETIN||CVE-2018-8897||IBM QRadar SIEM is vulnerable to Using Components with Known Vulnerabilities|
|QRADAR||SECURITY BULLETIN||CVE-2018-1730||IBM QRadar SIEM is vulnerable to XML External Entity Injection|
|QRADAR||SECURITY BULLETIN||CVE-2018-8034||Apache Tomcat as used in IBM QRadar SIEM is vulnerable to publicly disclosed vulnerability|
|QRADAR||SECURITY BULLETIN||CVE-2018-8036||Apache PDFBox as used in IBM QRadar Incident Forensics is vulnerable to Publicly disclosed vulnerability|
|QRADAR||SECURITY BULLETIN||CVE-2017-1622||The Application framework within IBM QRadar SIEM is vulnerable to Improper Certificate Validation|
|QRADAR VULNERABILITY MANAGER||SEARCHES||IJ11732||"APPLICATION ERROR" WHEN PERFORMING AN ASSET SAVED SEARCH EQUALS
|QRADAR||PROCESSES||IJ11821||BUFFERUNDERFLOW EXCEPTION CAN OCCUR BETWEEN THE ECS-EC AND ECS-EP PROCESSES|
|QRADAR||USER INTERFACE||IJ10166||USERS CANNOT LOG INTO QRADAR DUE TO THREAD DEADLOCK|
|QRADAR||SEARCHES||IJ10862||EXPORTED ASSET SEARCHES CONTAINING A NETWORK FILTER CAN GENERATE BLANK XML OR CSV FILES|
|QRADAR||REPORTS||IJ05334||TABLE REPORT VALUE FORMATTING CAN DISPLAY INCORRECTLY FOR AQL AGGREGATED DATA|
|QRADAR||OFFENSES||IJ09017||OFFENSES NOT GENERATED WHEN USING A CUSTOM EVENT PROPERTY AS OFFENSE INDEX IN HISTORICAL CORRELATION|
|QRADAR NETWORK INSIGHTS||FLOWS||IJ08471||QRADAR NETWORK INSIGHTS CONTENT FLOWS ARE COUNTED AGAINST FLOW LICENSE WHEN THEY SHOULDN'T BE|
|QRADAR||UPGRADES||IJ08432||BACKLEVEL JTDS JAR FILES IN QRADAR 7.3.1 CAN SOMETIMES CAUSE AN OUT OF MEMORY WITH ECS-EC-INGRESS PROCESS|
|QRADAR||OFFENSES||IJ09017||OFFENSES NOT GENERATED WHEN USING A CUSTOM EVENT PROPERTY AS OFFENSE INDEX IN HISTORICAL CORRELATION|
|QRADAR||REPORTS||IJ09036||AQL QUERY WITH AN AGGREGATE THAT IS RUN AGAINST A CURSOR THAT CONTAINS AN AGGREGATE FAILS WITH 'GENRAL FAILURE'|
|QRADAR||REPORTS||IJ08228||CREATING AN AQL QUERY WITH A SUB-SELECT CAN CAUSE DASHBOARD TIMESERIES TO FAIL DUE TO THE GLOBAL VIEW CREATED|
|QRADAR||FLOWS||IJ11163||NETFLOW V9 / IPFIX INITIATOR/RESPONDER OCTET/PACKET FIELD DATA IS NOT PROCESSED BY QRADAR|
|QRADAR NETWORK INSIGHTS||FLOWS||IJ10158||QRADAR NETWORK INSIGHTS (QNI) DECAPPER 'OUT OF MEMORY' INSTANCES CAUSED BY MULTIPLE INSPECTOR COMPONENTS|
|QRADAR||APPLIANCES||IJ00712||A STANDBY HA MANAGED HOST REBUILT FROM THE RECOVERY IMAGE MAY NOT MERGE /STORE/TRANSIENT CORRECTLY CAUSING HA ISSUES|
|QRADAR||APPLIANCES||IJ03438||/OPT/QRADAR/SUPPORT CAN RUN OUT OF FREE SPACE AFTER UPGRADE DUE TO A LARGE NUMBER OF FAILED REPLICATION FILES|
|QRADAR||OFFENSES||IJ10545||OFFENSE SOURCE SUMMARY DISPLAYS INCORRECTLY FOR OFFENSES INDEXED ON REGEX CUSTOM PROPERTIES WITH FIELD TYPE "IP"|
|QRADAR||UPGRADES||IJ10818||CHANGES MADE TO LOGROTATE IN QRADAR 7.3.1 PATCH 6 CAN CAUSE /VAR/LOG AND OR /OPT TO RUN OUT OF FREE SPACE|
|QRADAR||EVENTS||IJ03211||HOSTCONTEXT SERVICES CAN FAIL TO START DURING A HIGH AVAILABILITY (HA) FAILOVER TO SECONDARY EP/FP APPLIAN|
|QRADAR||DATA||IJ08827||HOSTCONTEXT STARTUP ON A MANAGED HOST CAN OCCUR PRIOR TO DATABASE VERIFICATION|
|QRADAR RISK MANAGER||DEVICES||IV93144||QRADAR RISK MANAGER DEVICE BACKUPS CAN FAIL WHEN THERE IS AN EMPTY VALUE IN AN PROTOCOL CONFIGURATION ADDRESS SET|
|QRADAR VULNERABILITY MANAGER||SCANS||IV99512||CONCURRENT SCHEDULED SCANS THAT INCLUDE IP EXCLUSIONS CAN FAIL TO START AT THE SCHEDULED TIME|
|QRADAR VULNERABILITY MANAGER||SCANS||IV91226||QVM SCAN CAN FAIL TO START/PROGRESS WHEN THERE ARE A LARGE NUMBER OF IP ADDRESS SCAN EXCLUSIONS DUE TO A POSTGRES EXCEPTION|
|QRADAR VULNERABILITY MANAGER||REPORTS||IJ09183||VULNERABILITY TRENDING REPORTS CAN SOMETIMES BE BLANK|
|QRADAR VULNERABILITY MANAGER||SEARCHES||IJ08226||CLICKING 'VIEW IN BY' IN A VULNERABILITY SEARCH DASHBOARD NAVIGATES TO INCORRECT QRADAR WINDOW|
|QRADAR VULNERABILITY MANAGER||SCANS||IJ07030||VULNERABILITY SCANS EXPERIENCE A DELAY PRIOR TO COMMENCING WHEN A HIGH NUMBER OF IP EXCLUSIONS ARE DEFINED|
|QRADAR VULNERABILITY MANAGER||SCANS||IJ03246||ALL SCHEDULED SCANS THAT RUN ON DECEMBER 1ST START AT MIDNIGHT NO MATTER WHAT TIME THEY ARE CONFIGURED TO START|
|QRADAR||DATA||IJ10999||UPDATES TO REFERENCE DATA USING CUSTOM EVENT PROPERTIES (CEP) CAN CAUSE CEP AND RULES TO BE RELOADED/TMP|
|QRADAR||OFFENSES||IJ10070||QRADAR CAN STOP GENERATING OFFENSES DUE TO AN INCORRECT NULL CHECK|
|QRADAR||RULES||IJ08227||CUSTOM RULE ENGINE DOES NOT USE LOG SOURCES CONTAINED IN 'OTHER' LOG SOURCE GROUP FOR FUNCTIONAL TEST PARAMETERS|
|QRADAR||USER INTERFACE||IJ10532||WINCOLLECT AGENT 'LAST HEARTBEAT' STATUS DISPLAYS AS "UNAVAILABLE" WHEN WORKING AS EXPECTED|
Where do I find more information?
More support for:
IBM QRadar Network Insights
Component: Release Notes
Software version: 7.3.1
Operating system(s): Linux
Software edition: All Editions
Reference #: 0741177
Modified date: 27 June 2019