Last Modified: Mar 12, 2025
Affected Product(s):
BIG-IP AFM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1
Opened: Aug 23, 2024 Severity: 3-Major
MCPd validation does not occur when a second log profile is added to an existing virtual server.
Inconsistency in configuration behavior. The protocol inspection log profile attached later to the virtual server is not enabled.
1. Create an Empty Protocol Inspection log profile and attach to virtual server (VS). 2. Create a second Protocol Inspection log profile (for example, local db) and attach to VS. 3. Event logs will not show on local db. Therefore, the protocol inspection log profile attached later to the virtual server is not enabled.
Set the attached log profiles to 'none' and then add the logging profile. Example: tmsh modify ltm virtual <vs name> security-log-profiles none tmsh modify ltm virtual <vs name> security-log-profiles add { log profile name }
None