Important: QRadar Suite Software: Mandatory hardware check required prior to upgrade

News

Abstract

QRadar Suite Software minimum hardware requirements have been updated in version 1.10.18 and later. Administrators with 1.10.17 or earlier must confirm that minimum hardware requirements are met before you begin any upgrade.

Content

Urgency

Critical: Users on affected versions are unable to progress the upgrade or can experience an outage without meeting the minimum hardware requirements.

Affected products

Administrators must alert their teams to validate the hardware requirements on the following versions:

QRadar Suite Software 1.10 all pack versions; also known as Cloud Pak for Security
Cloud Pak for Security all versions prior to 1.10

FAQ

What are the hardware requirements?

The hardware requirements are outlined in the hardware requirements documentation.

Why have the hardware requirements changed?

We have experienced that the previous minimum specifications were insufficient to handle QRadar Suite Software seamless upgrades and runtime capabilities without compromising quality or service levels. Therefore, the hardware requirements have been revised, simplifying and standardizing the deployment model for the product suite.

Can the environment be resized while it's running?

Yes, environments can be resized without a system outage by shutting down each node individually to resize.

How do you resize to the new requirements?

Refer to Red Hat documentation for Control Plane and Worker steps

What happens if an upgrade is triggered on a system that does not meet the minimum hardware requirements?

If an upgrade is triggered without meeting the minimum hardware requirements, there is a risk that the upgrade will stall.

If the upgrade stalls, please run the following commands:

oc patch iscguard cp4s-upgrade --type=merge -p '{"spec":{"generation":"1.10.18.0"}}' -n <CP4S_NAMESPACE>

oc exec deploy/cp-serviceability -n <CP4S_NAMESPACE> -- /opt/bin/modify_deployment --token=$(oc whoami -t) -k noobaa -a noobaa -c coreResources -r requests.cpu:100m -r requests.memory:400Mi

If upgrade does not continue and system function restored please contact IBM Support.

Can I maintain my current QRadar Suite Software version?

You can control whether an operator is upgraded seamlessly by configuring an approval strategy so you do not need to take the later 1.10 updates.

We apologize for any inconvenience that this hardware requirement causes for administrators. If you need assistance or have questions, you can contact Support for assistance and attach logs from the environment in question to your case.

Related Information

Installing Cloud Pak for Security

[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"","label":""}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.10.0;and future releases","Type":"MASTER"}]

Tips