Bug ID 667788: System offline after deleting the datasync-global-dg device-group and manually re-creating it

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, FPS(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Fixed In:

Opened: Jun 03, 2017
Severity: 3-Major


If the datasync-global-dg device-group is accidentally deleted and then manually re-created, other devices in the trust-domain might lose the datasync configuration, and go Offline until a workaround is applied or system is rebooted.


The devices might go offline.


This might happen if the datasync-global-dg device-group is accidentally deleted and then manually re-created. Note: This device-group should never be deleted.


Perform this procedure from the device in the Offline state: 1. Run the following command: tmsh save sys config 2. Run the following command: tmsh load sys config 3. If system is Offline, wait approximately 3 minutes until the system is ACTIVE. Otherwise, wait a few seconds. 4. Run the following command again: tmsh save sys config 5. Perform a force sync of datasync-global-dg. To do so: a. From the GUI of the same device (the device that was previously Offline). b. Select 'Sync Device to Group'. c. Make sure 'Overwrite Configuration' is checked. d. Click 'Sync'. 6. Wait until the devices are ACTIVE and 'In Sync'.

Fix Information

The system no longer allows deleting the datasync-global-dg device-group: a configuration exception is thrown in this case.

Behavior Change