Last Modified: Nov 15, 2019
See more info
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.3, 220.127.116.11, 18.104.22.168, 14.0.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.0.1, 18.104.22.168
Opened: Jul 05, 2017
When installing a new netHSM client to a new BIG-IP volume, the pre-existing netHSM client installed to other BIG-IP volumes will be overwritten and could be unusable
The pre-existing BIG-IP volumes that work with the netHSM client installed earlier might not work after the new client overwrites the old one. If the newly installed netHSM is not compatible with the pre-existing BIG-IP volume, the pre-existing BIG-IP volume will not work when the user boots to the old BIG-IP volume.
netHSM (Thales/SafeNet) client existed in the old version and a new client version is installed on a new volume. The new client will overwrite the old client in /shared.
When booting to the old BIG-IP volume with the pre-existing older netHSM client, re-install the netHSM client version that is compatible to that volume. Note that once this is done, the new volume will be similarly affected and will need a reinstall of the newer (different) netHSM client too, once that is booted into.