OPERATIONAL DEFECT DATABASE
...
...
After performing a ConfigSync, mcpd restarts and the following error is seen in /var/log/ltm: 01070734:3: Configuration error: Invalid mcpd context, folder not found <foldername>
Secondary blades do not process traffic as they restart
- Chassis cluster with at least two blades - sync-failover device group set to full-sync and auto-sync disabled - Changing a named pool-member in non-default partition without syncing between delete and create
To prevent blade restart, follow the workaround in K16592: ConfigSync may fail when deleting and recreating a pool member with a node name set (https://support.f5.com/csp/article/K16592). To work around this issue, you can synchronize the configuration just after deleting the pool member and node, before re-creating the pool member. To do so, perform the following procedure: Impact of workaround: Performing the following procedure may impact client connectivity to the node. You should perform this procedure only during a maintenance window. 1. Log in to the BIG-IP system Configuration utility. 2. Navigate to Local Traffic :: Pools, and select the Pool with the member you want to delete. 3. From the top of the menu, click Members. 4. Select the checkbox next to the pool member you want to delete, and click Remove. 5. Navigate to Local Traffic :: Nodes. 6. Select the checkbox next to the node with the same name, and click Delete. 7. Navigate to Device Management :: Overview. 8. Select the local device by hostname (self). 9. Click the Sync option. 10. If the ConfigSync was successful, you may now re-create the pool member.
Config sync after changing named pool members no longer causes mcpd on secondary blades to restart.
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.
