Aggresive reaper logs

A watchdog ensures the unit in the good states, if the watchdog expires then the watchdog will try to reboot the unit. So this problem might be caused by ranging the hardware problem or software problem or even combination of both. You may consider creating the Qkview and upload it to iHealth and see what the result from iHealth and open the case to F5 support if you can.

the adaptive db key values are not changed, are they?

[root@ve11a:Standby:Changes Pending] config  tmsh list sys db one-line |grep connection.adaptivereaper
sys db connection.adaptivereaper.hiwater { value "95" }
sys db connection.adaptivereaper.lowater { value "85" }

yes I changed it to high water mark to 85% and low water mark to 75%. I used iRule to increase memory gradually, when memory reached to almost 90%, tmm restarted. But aggresive reaper logs were not marked...

do you know if adaptive reaping is activated (e.g. some connection is reset)? just wondering if log is not shown or adaptive reaping is not activated.

if it is about the log, have you checked tmm log level?

sol5532: Configuring the level of information logged for TMM-specific events

Adaptive reaping should be activated as I'm hitting the high watermark set. I couldn't see reset connections as our lab F5 doesn't have active traffic going through. But ltm logged only below tmm restart logs.

Sep 5 02:06:47 bigipF5 notice sod[5792]: 01140045:5: HA reports tmm NOT ready. Sep 5 02:06:49 bigipF5 notice sod[5792]: 01140029:5: HA proc_running tmm fails action is go offline and down links. Sep 5 02:07:23 bigipF5 notice sod[5792]: 01140044:5: HA reports tmm ready. Sep 5 02:07:25 bigipF5 notice sod[5792]: 01140030:5: HA proc_running tmm is now responding. Sep 5 02:07:29 bigipF5 notice sod[5792]: 01140029:5: HA proc_running bd fails action is go offline and down links. Sep 5 02:07:59 bigipF5 notice sod[5792]: 01140030:5: HA proc_running bd is now responding.