Forum Discussion
That would suggest that your bigip is unable to reach the pool members.
Note that in a cluster, while load balanced end user traffic goes through the floating IP, health checks are sent by the local-only IPs of each individual cluster member.
So if there's a firewall, make sure all bigip IPs are allowed.
If that's not it, you can use something like curl directly on the bigip CLI to see what kind of response you get from the pool members, if any.
But that's more interesting for failing http(s) checks. The basic TCP health check failing points towards a very fundamental connectivity issue, like routing, firewall, access list or the service not even running on the pool member.
For your informaation
1- Node created, Pool created, Virtual server created
2- F5 load balancer is able to ping both VLANS (Internal & External) machines and self IPs are assigned on both VLANS
3- External machine is able to ping Virtual Server
4- internal machine hosted a simple web and access/work locally
5 Firewall is disabled on internal and external VLANS machines and there is no firewall between clients & F5
6- I am even able to telnet VS
So no connectivity issue and http service on server. I followed below sample scenario.
https://f5-agility-labs-adc.readthedocs.io/en/latest/class3/module2/lab2.html