Last Modified: Dec 20, 2018
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4
Opened: Apr 12, 2017
Related AskF5 Article: K00652162
TMM core while adding logging action to APM SWG.
TMM core. Traffic disrupted while tmm restarts.
-- Use of an application lookup perflow variable (perflow.application_lookup.result.*) in an SWG per-request Logging Agent. -- No Application Lookup Agent found prior in the chain. For example - The following example will crash: start : logging : allow - The following will succeed: start : application lookup : logging : allow
There are two possible workarounds: -- Remove the applicable perflow variables from the logging agent. -- Add an application lookup before trying to log application lookup perflow variables.