Bug ID 976669: FIPS Integrity check fails for other secondary blades after rebooting/replacing secondary blade

Last Modified: Oct 07, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5, 16.0.0,, 16.0.1,,

Fixed In:
17.0.0,, 16.1.0,,

Opened: Dec 24, 2020

Severity: 2-Critical


After rebooting or replacing a secondary blade, the FIPS integrity check fails for other secondary blades and they fail to fully boot.


When the FIPS integrity checks fail the blades won't fully boot.


This can occur after rebooting or replacing a secondary blade.


On the secondary blade reboot, the following critical files are deleted from other secondary blades which leads to FIPS integrity check failure: /root/.ssh/authorized_keys /root/.ssh/known_hosts To mitigate, copy the missing files from the primary blade to the secondary blade. From the primary blade, issue the following command towards the secondary blade(s). rsync -avz -e ssh /root/.ssh/* root@<Secondary Blade>:/root/.ssh/

Fix Information

Critical files are not deleted during secondary blade reboot.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips