Cluster configuration not synced for F5




For devices that support full configuration synchronization, Indeni will alert if the configuration is out of sync.

Remediation Steps

Log into the device and synchronize the configuration across the cluster.

How does this work?

This alert logs into the F5 device through SSH and retrieves the current state of the configuration synchronization.

Why is this important?

It is normally desireable for clusters to have their configuration synced. Else, changes made on one node in a cluster might not be active in the event of a fail over. This might cause disruption.

Without Indeni how would you find this?

An unsynced cluster could be detected during a failover where old configuration is suddenly activated and this could cause issues with the application delivery. An administrator could verify the cluster member state by logging into the web interface of the device looking in the upper left corner. An synced cluster show "In sync".

View Source Code