query regarding connection issues to a particular node in a pool

Hello,

From what you have said in the below underline part, is that "if the member is not ready yet", you don't want F5 to forward requests to that member until the member is completely ready.

Your post:

"Traffic is being round robbined for all so what ive observed is when it hits the working member the webpage loads but when it hits the non working member the webpage keeps spinning and finally throws an error (as expected as this server is not yet ready)."

You can accomplish this by using a custom HTTP/HTTPs monitor, you can specify the URL and the expected receive string when the service on that node is working fine, here is an example:

Navigate to LTM > Monitor > create > HTTP/HTTPs.

For example, in the send string, for the below red URL, you can add the specific URL for the service, and for the Host, you can add the exact FQDN of the service:

GET /autodiscover/healthcheck.html HTTP/1.1\r\nHost: www.abc.com\r\nConnection: Close\r\n\r\n

Receive string:

200 OK

(it depends on your service, you can check it by using the developer tool or ask the service owner about the correct send and receive strings)

If the F5 device didn't receive a response (because the nod is not ready for example) on the above send string for the configured timeout in the custom monitor which has a default value of 16 seconds, the F5 will consider this pool member (node or server) as offline and will not forward any more requests to this node until the node respond successfully to the F5.

Hello,

Let's take the below screenshot as an example:

the red part that was mentioned in my last reply, is the below based on the screenshot:

/search.php

(the part after the "/" and before the "?")

Then the FQDN is: www.auction.com   (without https:// part)

so the send string will be as follow for example:

GET /search.php HTTP/1.1\r\nHost: www.auction.com\r\nConnection: Close\r\n\r\n

and the receive string is:

200 OK

I hope I clarified the procedure.

BR,

Mohamed Salah