Forum Discussion
BIG-IP : iControl sync operation executed against non-sync'd cluster
F5 BIG-IP LTM VE v11.4.0 on ESXi
I am working with a 2-node BIG-IP cluster.
I am using iControl API ( .NET/C code ) to manipulate a 2-node BIG-IP cluster.
All operations are directed to the floating-VIP and so arrive at the cluster's primary node.
First, I update a data-group-file, next I re-cache the data-group, and finally I issue a sync command :
SystemConfigSync.synchronize_to_group()I am wondering what is the expected result for a cluster that was already in a non-synchronized state before I initiated any of my iControl operations ?
By "non-synchronized state" I mean that the primary node sync status is green, and the secondary node sync status is yellow "Changes Pending".
The iControl sync operation returns an error with little detail, but potentially could it fail to sync because the secondary is in a more current state than the primary ?
- Baltostar, use synchronize_to_group_v2 Synchronize the configuration from the specified device to the given group. This method causes the configuration for the specified device to be pushed to all members of the given device group. If force is true, then the configuration will be pushed unconditionally. If force is false, then update all devices in the device group that have configuration older than the specified device.BIG-IP_v11.2.0 https://clouddocs.f5.com/api/icontrol-soap/System__ConfigSync.html
- Thanks Greg. If I understand correctly, if the cluster is in a pre-existing non-sync'd state where one or more secondary nodes have newer configs than the primary, and force is false, then post iControl sync the cluster will remain in a non-sync'd state.
