Bug ID 638091: Config sync after changing named pool members can cause mcpd on secondary blades to restart

Last Modified: Mar 12, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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.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.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 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.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, 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.1

Fixed In:
14.0.0, 13.1.1.2, 12.1.4

Opened: Jan 10, 2017
Severity: 3-Major

Symptoms

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>

Impact

Secondary blades do not process traffic as they restart

Conditions

- 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

Workaround

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.

Fix Information

Config sync after changing named pool members no longer causes mcpd on secondary blades to restart.

Behavior Change