Last Modified: Jun 08, 2021
Opened: May 20, 2021
The following message may be logged to /var/log/tmm* Can't process event 16, err: ERR_NOT_FOUND
Since the PEM policy is already applied to the session, the failure message is essentially cosmetic, but it can cause the tmm logs to grow in size if this is happening frequently.
Applying a PEM policy to an existing session that already has that policy (eg, through an irule using 'PEM::subscriber config policy referential set xxxx'