Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
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.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
12.0.0, 11.6.0 HF6, 11.5.3 HF2
Opened: Jul 01, 2015
Due to a related change in AFM ACL handling, global and route domain rule's were being logged (incorrectly) by the virtual server's AFM log profile (if it exists). This is incorrect since the behavior has always been that Global and Route Domain AFM rule logging is controlled by global-network log profile only.
This causes a regression (and inadvertent change in behavior) for Global and Route Domain AFM rule logging.
Global or Route Domain AFM ACL rule matches and logging is enabled. Also, the matched virtual server has a logging profile attached to it.
With the fix, global and route domain AFM rule logging is controlled by global-network log profile (as has been the case since inception).