Troubleshooting
Problem
This article discusses the sequence required to power up QRadar High Availability pairs.
Cause
Starting a QRadar HA appliances in the wrong order will cause a failover to the Secondary appliance. This would require an administrator to fail the Secondary backover to the Primary causing a delay in going active.
Resolving The Problem
The preferred order to start High Availability (HA) appliances deployments is:
- Start up the Primary Console first.
- Start up the Secondary Console.
- For each Managed Host HA Pair, Start up the Primary node first.
- Start up the Secondary High Availability appliance.
- Repeat the process with all other HA pairs.
Where do you find more information?
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"High Availability","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
18 March 2019
UID
ibm10876008