Last Modified: Oct 21, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.1.3.6, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 21.0.0, 21.0.0.1, 21.0.0.2, 21.0.0.3, 21.1.0, 21.1.0.1, 21.1.0.2, 21.1.0.3
Opened: Oct 09, 2026 Severity: 3-Major
A secondary blade repeatedly fails to validate configuration received from the primary blade, causing MCPD to restart and retry the configuration load. Each attempt retains additional filestore backups under `/config/filestore/.trash_bin_d/.backup_*_d`. These backups accumulate and can eventually consume all available space on `/config`. config load failure on the secondary blade slot2 mcpd[31999]: 01070734:3: Configuration error: Configuration from primary failed validation: 01020036:3: The requested monitor instance (/Common/bigip 10.82.189.13 0 gtm-vs) was not found.... failed validation with error 16908342.
The affected secondary remains INOPERATIVE, reducing available cluster capacity and redundancy. Accumulating backups can exhaust `/config`, potentially preventing configuration writes and subsequent recovery operations. Disk exhaustion was reported in as little as 10 hours.
- BIG-IP is deployed across multiple blades. - A secondary blade fails to load configuration received from the primary and repeatedly retries. - The load/reset sequence retains filestore backup generations without sufficient cleanup. - An orphaned GTM monitor instance triggers the reported reproduction.
NA
None