Bug ID 465348: APM Policy Sync Folder remains after access profile is deleted

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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,,,

Fixed In:

Opened: Jun 02, 2014
Severity: 3-Major
Related Article:


When Access Policy Manager (APM) Policy Sync is used to exchange configuration for an Access Profile, a system folder is created and is later not deleted even when the associated access profile is deleted. More importantly files related to the status of the policy sync operation remain within the folder for each device within the device group.


Following a policy sync operation, each device within the device group will have a system folder that takes the name /POLICYSYNC_<profile-name>. Within that folder a policy sync status object will exist for each device within the device group.


When an APM Policy Sync is used to exchange configuration with devices within the device group.


To remove the system folders and related objects that are left behind, an administrator needs to log in and use tmsh to manually delete any objects within the folder first, and then the folder itself. You must run the following tmsh commands on each of the devices within the device group. Within tmsh syntax: `cd POLICYSYNC_profile-name` `delete apm policy psync-status all` Once the above commands are ran on every device within the device group, you may now delete the folders if desired, using tmsh. `delete sys folder POLICYSYNC_profile-name`

Fix Information


Behavior Change