Forum Discussion
bugslayerx
Nimbostratus
NimbostratusOffline (Enabled) - The children pool member(s) are down
Hi, new to F5. I am going through the F5 101 course. Currently using Udemy. I have an ESXI setup. I have created my F5 virtual machine and have successfully connected to the Big-IP console. I have set up my VLANs and Self-IPs. The issue I am having is with the creation of pools and having members that are down. I created an http pool and connected it to a created http virtual server. As soon as I created this I saw the red diamond that says that "Offline (Enabled) - The children pool member(s) are down". 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. I am pretty sure the ESXI networking is configured correctly. Additionally, I am able to ping the Big-IP self-IPs successfully. I have attached several pictures. I have played around with a lot of the settings and for the life of me, I cannot figure out what is wrong. Any advice or help is appreciated.
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:
mihaicMVP
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:
- mihaic
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.
bugslayerxMembers are listening on port 80. I changed the monitor to ICMP and still nothing.
- bugslayerx
I changed my virtual switches to the settings shown above and this worked! Thank you!!!!