Last Modified: Jul 12, 2023
Known Affected Versions:
13.0.0, 13.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.4, 22.214.171.124, 13.1.5, 126.96.36.199
Opened: Jan 12, 2017 Severity: 2-Critical
During a failover event, a newly active BIG-IP will generate its own Dynamic Signatures rather than use a copy of the previous Active unit's signatures.
During failover events, there will be a lag of a few seconds while the Dynamic Signatures are generated and collated.
HA configuration with Dynamic Signatures enabled.
1. Use the following command to verify that the device-group is set to none: list sys folder dos-common 2. If it is, you can associate dos-common to device group dos-global-dg using the following command: tmsh modify sys folder dos-common/ device-group dos-global-dg 3. Save the config using the following command: tmsh save sys config
The system now explicitly adds folder and device group association, so the issue no longer occurs.