Troubleshooting
Problem
After you deploy changes, the secondary host of High Availability clusters transition to the "Unknown" state temporarily. This article explains how the temporary state is expected behavior and why it occurs.
Symptom
From the System and License Management menu, the Standby host shows the "Unknown" state after a deployment.
QRadar Deployment Intelligence (QDI) also alerts about the "Critical" health status of the nonactive host with status "UNKNOWN".
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":"PF016","label":"Linux"}],"Version":"All Versions"}]
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.
Was this topic helpful?
Document Information
Modified date:
12 December 2022
UID
ibm16841285