Bug ID 1609273: Secondly attached Protocol Inspection log profile to virtual server is not effective

Last Modified: May 19, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
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, 17.1.2.2

Opened: Jul 09, 2024

Severity: 3-Major

Symptoms

Protocol inspection in the security log profile was not activated/enabled when another profile is already attached to the virtual server.

Impact

Inconsistency in configuration behavior.

Conditions

1. Create a Protocol Inspection log profile (for example, local db) and attach to virtual server (VS). 2. Create a second Protocol Inspection log profile (for example, remote) and attach to VS. 3. Event logs will only show on local db and do not show on remote. Therefore, the protocol inspection log profile attached later to the virtual server is not effective.

Workaround

Do not have a work-around. Only one log profile will work at a time. Run the below command to detach the profiles from virtual server (VS) and attach the required one. tmsh modify ltm virtual <VS Name> security-log-profiles none

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips