Last Modified: Sep 02, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.1.3.4, 17.5.1.8, 21.0.0.3, 21.1.0.1
Fixed In:
21.1.0.2, 17.5.1.9, 17.1.3.5
Opened: Jul 29, 2026 Severity: 1-Blocking
- In a FIPS-enabled device, upgrading or installing the defective ISO image causes BIGIP to stay in the "INOPERATIVE" state forever due to image integrity failure. - Image integrity failure is caused by the missing or incorrect HMAC for a few modules
BIG-IP is unusable due to the "INOPERATIVE" state
BIG-IP stays in the "INOPERATIVE" state forever in FIPS enabled device
Disabling FIPS is an workaround
N the build sequence, assume first i686 prefetched. Due to perforce mismatch RemoveOutfiles gets called and HMAC CSV file for this module is removed. i686 rebuild completes with newly generated HMAC CSV file for i686 binaries. Then x86_64 prefetched. Due to perforce mismatch RemoveOutfiles gets called and HMAC CSV file for this module is removed. This is leading to the loss of i686 contents from HMAC CSV file which was causing the FIPS integrity to fail in FIPS enabled device. As the fix for the issue, instead of blindly removing the file removed only the arch specific entries from the HMAC CSV file. This fix is preventing the complete loss of HMAC CSV content for one arch when compiling for another arch.