F5 Configuration changes shouldn’t be made to the standby device
This is a real life sample alert from indeni for F5 Load Balancing Methods
You have made configuration changes to the standby device in a device group. This is contrary to best practices as an unplanned config sync can result in an outage. It is best to make changes directly to the active device during an approved maintenance operation.
Manual Remediation Steps:
Make the changes on the active device and sync to the standby device. More information on how to track configuration changes can be found in SOL13946 under “Viewing the commit ID updates”.
How does this alert work?
indeni uses “tmsh run /cm watch-devicegroup-device” to track the commits being made on the standby device and where they are coming from.