Forum Discussion

4 Replies

  • Possibly no members exist in the pool or they all failed health check.

     

  • yes and the question is?

     

    it means all the pool members are down, the cause isn't possible to give without more information. but in general you can assume something isn't fine with the server or servers in that pool or the network between the big-ip and those servers.

     

  • This is a very generic error, possibly the pool members are down or not listening on the service port or there is some connectivity issue b/w the F5 and the pool members.

     

  • This is a common error that you will find in your logs. The pool 'iENABLE-SSRS-PROD-443' doesn't have any available pool members. The most likely cause is the health monitor check has failed.

     

    If you go to that pool in the GUI and click on it you can drill down to the actual pool members and it will tell you which monitor has failed which should give you further insight into why that pool is down.

     

    If you are still unclear as to why the pool members are down you can also enable monitor logging but the simplest thing is to do a manual monitor check from the CLI. If you have a TCP monitor for instance you can try telneting to the pool member (node IP plus service port) and see what happens. If you are using an advance health monitor (you should) then you would use CURL to perform an HTTP GET to that pool member (assuming it is an HTTP service).

     

    Hope that helps!