Forum Discussion
NimbostratusCluster reboots VMs but F5 was still routing traffic to the down nodes
Hi,
I have VM web servers running on a Dell PowerEdge M620 with VMware ESXi 5.5, the host was apparently running short on memory and decided to reboot servers. When the server were rebooted F5 did not detect that the nodes were down and kept routing traffic to these nodes, I had to manually take the nodes out of the pool. Any ideas why F5 did not re-route traffic? Is there an issue with ESXi rebooting the nodes unexpectedly?
Thank you!
5 Replies
JPV_131616Cirrus
what type of monitor is being used on the pool?
Also do you have the reselect option enabled on service down for the pool?
- basithr_150707
There are no health monitors set up for the pools but there are health monitors set up for the nodes. I relatively new to F5 so I am not sure where to check if the reselect option is enabled.
- basithr_150707
I found the setting for Action on service down, it is set to none
- nitass
Employee
There are no health monitors set up for the pools but there are health monitors set up for the nodes.
was the node marked down?
I found the setting for Action on service down, it is set to none
just in case you have not yet seen this.
sol15095: Overview of the Action On Service Down feature
http://support.f5.com/kb/en-us/solutions/public/15000/000/sol15095.html - basithr_150707
Thank you very much for your guidance, that really helped a lot!
