F5 not sending health check to all members in a pool

I'm having the same problem, I use the http monitor and some members get infinite status checking, with tcpdump the check attempt is not even done.

Doing test with ping, telnet and curl results is positive.

>> I already did the bigd restart;

>> I pushed forced offline and returned;

*** I believe a possible solution would be the touch / service / mcpd / forceload procedure; reboot, however, doing this I will not have the root cause of the problem

Note: As a palliative solution I enabled the tcp monitor and some members returned, however, some still have a problem.

update November 14, 2018

The "Logging Monitor" enabled on a Node was the trigger for Health Check failure, it is a known BUG as described in article K06263705.

After disabling the logging monitor and running the restart of the bigd process (clsh bigstart restart bigd) the environment has normalized.

Problem solved!