Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.3.0, 11.5.0, 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.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
12.0.0, 11.6.1, 11.5.2
Opened: Feb 19, 2014
Related AskF5 Article: K17368
Loading the default configuration may cause the mcpd process to restart and produce a core file.
The BIG-IP system may temporarily fail to process traffic and fail over if configured as part of a high-availability system.
This issue occurs when the following condition is met: After you successfully load a UCS file that was created on a different system, you attempt to restore the system to factory defaults by loading the default configuration. When you load the default configuration, if the mcpd process is unable to decrypt the master-key, or attributes exist that were encrypted with a key other than the current master-key, the mcpd process restarts and produces a core file. These situations may occur if an RMA has occurred and you install a UCS from one device to another device of the same type, if the device unit key becomes corrupted, or if the master key file (/config/bigip/kstore/master) becomes corrupted.
Fixed crashes in mcpd and other daemons when the master-key cannot be decrypted, or when attributes exist that were encrypted with a key other than the current master-key. These situations may occur when a RMA occurs, when moving a UCS from one device to another device of the same type, if the device unit key becomes corrupted, or if the master key file (/config/bigip/kstore/master) becomes corrupted.