Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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.10, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0, 11.6.2
Opened: Mar 18, 2016 Severity: 2-Critical Related Article:
K42832526
When the system is configured to use network HSM for FIPS crypto services, all FIPS-related traffic will cease to function after the tmm daemon gets restarted, and does not recover until a restart of both pkcs11d and tmm, or a reboot of the unit.
Traffic that relies on the network HSM for crypto services fails and does not recover.
-- System is configured for network HSM for FIPS crypto services. -- tmm gets restarted.
Restart both pkcs11d and tmm by issuing the following command: On a standard BIG-IP appliance: bigstart restart pkcs11d tmm On a VIPRION system: clsh bigstart restart pkcs11d tmm
Traffic that relies on the network HSM for FIPS crypto services now recovers as expected when tmm is restarted.
