curl command

So you made a custom monitor and assigned the same monitor to 3 pool members separately? What version of BIG-IP are you using? Check to see if a different monitor is assigned to the whole pool as well.

 

HERE, HERE, and HERE are some good articles to read up on.

 

Hope that helps! If it does please up-vote and select this answer, it'd be greatly appreciated!

 

-Dylan

 

Can you post the health monitor configuration?

tmsh list ltm monitor 

Cheers,

Kees

Hey GLM

As previous people have mentioned, it seems that there is something misconfigured with the monitor that marks the pool member offline. First of all, can you please share the configuration of the monitor? Like Kees van den Bos mentions, it is far easier to go into CLI and tmsh and write the command:

 tmsh list ltm monitor 

Another great way to troubleshoot a monitor is to turn on Monitor Logging specified in the following article: Enabling monitor logging for a pool member

When enabling this it will create a unique log file for the specific pool member located under /var/log/monitors/[pool_member_name].

In that log file you can see the following:

2016-07-26 14:43:09.951852: ID 122   :(_send_active_service_ping): writing [ addr=::ffff:1.1.1.1:80 srcaddr=::ffff:10.10.10.10%0:41219 ] send=GET /\x0d\x0a\x0d\x0a
2016-07-26 14:43:09.952893: ID 122   :(_recv_active_service_ping): rcvd 689 bytes: -->\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0aIIS7\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a<-- [ addr=::ffff:1.1.1.1:80 srcaddr=::ffff:10.10.10.10%0:41219 ]

So in the first request you see the send string being sent configured in the HTTP monitor. And the second entry is the response coming back. Then make sure that the response matches what you have configured in the receive string.

I hope this helps! 🙂