Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP PEM
Known Affected Versions:
12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 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
Fixed In:
15.0.0, 14.1.0.5, 13.1.1.5, 12.1.5
Opened: Jan 31, 2019 Severity: 2-Critical
Webroot database mapping and unmapping takes a very long amount of time on TMM, so you might see clock advances occur. The long interval might result in a failover/state-transition in clustered environment.
TMM does not process traffic because of the long delay in mapping and unmapping, and failover might happen in a clustered environment.
-- Webroot database is downloaded. -- TMM needs to swap to the new instance.
You can avoid this issue by disabling BrightCloud updates, however, your environments will miss the latest updates as a result. #vi /etc/wr_urldbd/bcsdk.cfg DoBcap=true DoRtu=false DownloadDatabase=false
Mapping/Unmapping the database is done asynchronously and the delay is reduced so that the CDP failover does not happen.