This is a real life sample alert from indeni
Preemption in clustering means that if this device’s health is degraded and there’s a fail over in the cluster to another member, and then later this device’s health is restored, it will attempt to assume priority in the cluster. This can have some negative impacts, such as constant fail overs in a cluster (if the health issue resumes) as well as issues with surrounding equipment (that are no longer “sure” which member is the active one).
Manual Remediation Steps:
Disable Auto Failback under Traffic Groups.
How does this alert work?
indeni reviews the configuration for any features that are enabled or disabled that are known to cause issues. This is essentially a “best practice” type alert. In the example above, a best practice for configuring F5 LTMs is being verified.