Selecting a monitor down the virtual server & pool

When I select any Monitor like TCP or HTTP, suddenly the pool and virtual server become down. As I unselect it the pool and virtual server become online.

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.

Can you share your configuration for the VS, Pool and Health Monitor?

Also, please share the output of curl -vvvk http://<pool-member-ip> or curl -vvvk https://<pool-member-ip> (depending on the port the pool members are listening on.

Have you tried to capture traffic on the destination?

when I telnet or ping from external to F5, then the F5 tcpdump shows nothing (below snapshot is for reference)

but

When I ping from F5 to the behind Server, I received the result on tcpdump (below snapshot is for reference)

I see other question you raised similar to this one. Lets stick to this one for all troubleshooting and resolution ..

So, I need from you to provide a topology, which will show how the devices should be connected. Moreover, I need the ESXi interfaces details along with the BIG-IP Config as to be able to deeply analyze the issue.

Do you have iptables running on the webserver? This looks very much like the result of a “REJECT --reject-with icmp-*” rule on port 80. Maybe default rules that came with the OS.

If you do a tcpdump on the webserver, while doing the curl from your F5 to the webserver, you should be able to see if there is some kind of reject response.