Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AFM
Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0
Opened: Jun 16, 2015 Severity: 3-Major
Configuration load fails when setting a DOS profile using the iRule "DOSL7::enable <profile>" due to the order of object loading in the configuration file.
Config fails to load due to expected object (DoS L7 profile) not being initialized first.
Using an iRule to call a DoS L7 profile
Manually editing the config and moving the iRule block after the DoS L7 profile block will allow the config to load. However, any configuration save will revert the order. Additionally, F5 does not recommend manually editing config files unless the need is urgent.
An issue has been fixed that prevented the configuration from successfully loading when setting a DOS profile using the iRule "DOSL7::enable <profile>".