IBM Support

QRadar: High Availability cluster creation fails due to hardware class mismatch

Troubleshooting


Problem

When attempting to add a new secondary host into an existing QRadar High Availability (HA) pair, the setup can fail with an error indicating that the hardware classes (HWC) of the two systems do not match.
The HA wizard cannot proceed unless both hosts are assigned the same hardware class.

[HA Setup (P-M----)] [ERROR] 
Remote system hardware type is xx## but the local hardware type is xx##. 
You must re-install the remote host with the same hardware type as the local host.

 

Symptom

Adding the new secondary host fails during the HA wizard.

"/etc/.appliance_name" confirms the host was created as an HA appliance.

"/opt/qradar/bin/myver -hwc" reports different hardware classes between the primary and secondary hosts.

HA wizard logs explicitly show an error about mismatched hardware types.
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtXAAQ","label":"High Availability"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.4.3;7.5.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
29 November 2025

UID

ibm17250816