Last Modified: Apr 10, 2019
Opened: Jul 19, 2013
Related AskF5 Article: K14995
Crash in tmm when attaching a CPM policy to a virtual server.
When this occurs, TMM restarts.
This occurs when the CPM policy has a rule that uses PEM to classify action using only a category.
Do not create custom CPM rules that use PEM to classify action using only a category. To recover when the TMM is restarting, remove the affected policy from the affected virtual server, and reload the configuration.
Tmm no longer cores in certain instances when a CPM policy is attached to a virtual server.