Last Modified: Sep 06, 2019
See more info
BIG-IP ASM, FPS
Known Affected Versions:
13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.3, 14.0.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.0.1
Opened: Oct 14, 2016
When adding a third device to the trust, the sync state might be show 'Awaiting Initial Sync' on the new device, while the other devices show 'In Sync'. Note: The sync status 'Awaiting Initial Sync' is related to a hidden device group (datasync-device-<devicename>-dg), which the system automatically creates and syncs. This device group does not appear in the GUI.
When this occurs, the sync status will show 'Awaiting Initial Sync'. There is no functional impact.
-- ASM or FPS is provisioned. -- The link status of the third device is offline while adding it to the trust. (This is a rarely occurring condition.)
1. Identify the device group that is out of sync using the following command: tmsh show cm sync-status The out-of-sync device group returns a status similar to the following: datasync-device-bip2-dg (Awaiting Initial Sync): One or more devices awaiting initial config sync. 2. Find the device that owns the device-group that needs to be synced by looking at the status. For example, the device group in the previous example is 'datasync-device-bip2-dg', so the device is 'bip2'. 3. From that device, run a command similar to the following, replacing 'datasync-device-bip2-dg' with the device group that is out of sync: tmsh run cm config-sync force-full-load-push to-group datasync-device-bip2-dg Note: The GUI cannot be used because this is a hidden device group that does not appear in the GUI.
The system now handles this condition, so there are no longer sync problems when adding a third device to the device trust when ASM or FPS are provisioned while the link is down.