Forum Discussion
HI
I have not seen your configuration but basically you mentioned that when you stop your App Pool the monitor stays green or in an avialble state.
With that said the F5 will still load balance to server where the app pool has stopped because your monitor is reporting the pool member is available. Please check your monitor configuration you have applied to the pool. Please post your configuration if you still have issues.
tmsh ltm list virtual "virtual server name"
tmsh ltm list pool "name of pool which is configured with the above virtual server"
load balancing behaviors will be based on your health monitor, in a very basic configuration the f5 will load balance a connection to pool member as long as the pool member has a green status/available, Do you mind posting your configuration, not 100% but I would assume the default settings in the tcp monitor will check the port if its up and running. You will need to more then a simple port monitor to check your application status on the web server.
Best to ask your web team to create a test page for you, that contains a simple sting such as SERVER_UP, then create a custom http monitor to request the page with a recv string. Below is an example
ltm monitor http custom-monitorhttp { adaptive disabled defaults-from http destination : interval 5 ip-dscp 0 recv SERVER_UP recv-disable none send "GET /HealthCheck.html\r\n" time-until-up 0 timeout 16
[root@bipipbrplab01:Active:Disconnected] config curl --get http://10.1.2.12/HealthCheck.html
F5 Test Page
SERVER_UP
The web server software is running.
[root@bipipb01:Active:Disconnected] config