How To
Summary
Occasionally, you might find devices are stuck in the discovery queue for longer periods of time than usual. There can be several causes for stuck devices in discovery. One such cause involves incorrect Cluster Leader (CL) database records, where the CL lists an appliance as passive, although the appliance is, in fact, active. If an appliance is incorrectly listed as passive on the CL, replication propagates that record throughout the cluster. Once an incorrect record is replicated throughout the cluster (assuming replication works correctly), the entire cluster now labels an appliance passive, which can cause discovery problems. This article addresses this particular "stuck discovery" cause.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
02 February 2023
UID
125176707