Bug ID 541126: Safenet connection may fail on restarting pkcs11d or HSM reboot or if the connection to HSM is lost and then resumed

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 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, 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.1 HF2, 11.5.4 HF2

Opened: Aug 20, 2015
Severity: 3-Major
Related AskF5 Article:
K16414704

Symptoms

netHSM usage may fail for Safenet users with error message in the ltm log similar to the following: warning tmm1[11930]: 01260009:4: Connection error: ssl_hs_vfy_sign_srvkeyxchg:9678: sign_srvkeyxchg (80). info tmm1[11930]: 01260013:6: SSL Handshake failed for TCP 10.10.0.1:59513 -> 10.10.1.150:20001. warning pkcs11d[12005]: 01680022:4: Crypto operation [2] failed. crit tmm1[11930]: 01260010:2: FIPS acceleration device failure: fips_poll_completed_reqs: req: 56 status: 0x1 : Cancel.

Impact

SSL handshake failure with a message similar to the following: SSL Handshake failed for TCP 10.10.0.1:59513 -> 10.10.1.150:20001.

Conditions

This may happen for any of the following conditions: -- Restart pkcs11d without starting tmm immediately after. -- Network connection between the BIG-IP and HSM is interrupted and then restored. -- HSM is rebooted without being followed by a restart to pkcs11d and tmm.

Workaround

For Safenet, always restart tmm after restarting pkcs11d. To do so, run the following commands: bigstart restart pkcs11d bigstart restart tmm When the networking to HSM is restored or after a HSM reboot, always run the following commands: bigstart restart pkcs11d bigstart restart tmm

Fix Information

After restarting pkcs11d, Safenet connections no longer fails with the message 'cannot locate key'.

Behavior Change