Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5
Fixed In:
15.0.0, 14.1.0.6, 14.0.1.1, 13.1.3, 12.1.5, 11.6.5.2
Opened: Nov 09, 2018 Severity: 3-Major
Modifying nodes/pool-member can lose monitor_instance and monitor_rule_instances for unrelated objects.
-- The system might delete monitor rule instances for unrelated nodes/pool-members. -- Pool members are incorrectly marked down.
-- BIG-IP system is configured with nodes, pool-members, and pools with monitors. -- Modify one of the nodes that is in a pool. -- Run the following command: tmsh load /sys config -- Loading UCS/SCF file can trigger the issue also. -- Nodes share the same monitor instance. -- default-node-monitor is not configured.
You can use either of the following: -- Failover or failback traffic to the affected device. -- Run the following command: tmsh load sys config.
None