Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
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.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 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.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Opened: Jul 29, 2015 Severity: 3-Major
Syncing a device group can overwrite the folder settings of another device group.
The parent folder may lose configuration. In particular, it may no longer be associated with the device group (i.e. /PARENT will no longer be associated with DG1 on BIG-IP2).
* There are multiple device groups configured (e.g. DG1, DG2, etc.). * A subfolder is assigned to a different device group than the parent folder (e.g., /PARENT is assigned to DG1 and /PARENT/CHILD is assigned DG2). * A device is a member of the device group assigned to the subfolder, but not the device group of parent folder (e.g., BIG-IP1 is a member of DG2 but not DG1). * There is a second device that is in both device groups (e.g., BIG-IP2 in both DG1 and DG2). * The device syncs configuration in the subfolders device group (e.g., BIG-IP1 makes a change to an object in /PARENT/CHILD and syncs it to peers).
The recommendation is create separate partitions for the different device groups and make sure subfolders always inherit the device group and traffic group settings of the parent/partition folder.
None