Last Modified: Apr 19, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5
Fixed In:
16.1.0, 16.0.1, 15.1.1, 14.1.2.8, 13.1.3.5
Opened: Apr 09, 2018 Severity: 3-Major Related Article:
K08689542
-- UCS archive restore fails -- The Traffic Management Shell (TMSH) and/or /var/log/ltm file show following error message: 01071769:3: Decryption of the field (privatekey) for object (9717) failed. Unexpected Error: Loading configuration process failed.
-- The UCS configuration is not applied. -- The BIG-IP is not in a fully operational state.
- Restoring configuration from UCS. - The UCS is being restored on a different BIG-IP system with a different master key.
If you encounter this error and dynad is not in use (dynamic debug) you can manually edit bigip_base.conf. 1. Locate the dynad config in /config/bigip_base.conf file: For example, the dynad config will look like: sys dynad key { key $M$jV$VX7HMp5q346nsTYDYFPnYdJLrBPyQSCrDTJYAz4je7KXJAC38fxtDJL35KtF66bq } 2. Modify the dynad configuration lines to: sys dynad key { key "test" } 3, Save the updated bigip_base.conf file 4. Load the configuration with command: tmsh load sys config
The log message is improved to provide the BIG-IP administrator with more specific detail that the dynad key failed to be decrypted.