Forum Discussion
Offline (Enabled) - The children pool member(s) are down
- Nov 22, 2023
In that case, it means the F5 can not ping your VM. So something is wrong with your config or ESXi.
Do you have 2 F5 in HA?
have you tried this:
https://my.f5.com/manage/s/article/K31552842
" I am able to ping the virtual server IP successfully from the F5 cli as well as a windows virtual machine on my ESXI that is connected to the same network. "
You should not have the VMs and the Virtual servers on the same network. This can work if you use SNAT (snat pool from a different range).
Usually, you have a network for Virtual servers (front end) and one for VMs (back end).
I have this on my ESXi host, and it is working for me:
I see that your pool members use port 80 and the monitor you are using is TCP.
So the question is are your members listening on port 80? Have you some sort of webserver installed?
You could change the monitor to ICMP and test if your pool becomes available.
Members are listening on port 80. I changed the monitor to ICMP and still nothing.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com