Loading...
Loading...
Config sync operation fails for APM policy when policy item of same name points to different agent on source and target The system posts errors similar to the following: Sync error on rfang-vemgmt.lab.labnet.com: Load failed from /Common/rfang-ve-3mgmt.lab.labnet.com 01070734:3: Configuration error: DB validation exception, unique constraint violation on table (access_policy_item_agent) object ID (/Common/resm_act_message_box_1 /Common/resm_act_message_box_ag_1). A duplicate value was received for a non-primary key unique index field. DB exception text (Cannot update_indexes/checkpoint DB object, class:access_policy_item_agent status:13)"
Unable to sync configuration in a failover device group.
This occurs in the following scenario: 1. Configure a failover device group containing two BIG-IP systems. 2. Create an APM access profile on one unit. + Launch VPE for the policy. + Add a macro. + In macro add an agent, e.g., Message box. + Add macro to the main policy. 3. Initiate config sync to another device. 4. On one BIG-IP system, add another Message box agent using the same macro. On the other BIG-IP system, make a copy of the access profile. 5. On either BIG-IP system, initiate another config sync operation.
You can work around this using the following procedure: 1. On the device receiving the config sync, delete the APM policies that contain the referenced APM policy items. 2. Perform an overwrite-config-sync operation from the sending device to this device.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.