Forum Discussion
Some strange behavior on the F5 when one pool member is down
Hello All, I'm facing a some strange behavior on the F5. When one web server (of the 2) was offline, refreshing the website in a browser got the website 404 error
This indicates that the LB is not really balancing - it's switching traffic between the 2 web servers. The LB should constantly poll the back end web servers and know when one if offline, so it can redirect all traffic to the other web servers in the pool.
Can you any body help me to narrow down this issue?
health monitors in LB is configured for 15 seconds as probing interval and timeout as 46 seconds.
Regards, Thiyagu
7 Replies
- gsharri
Altostratus
I assume your question is regarding LTM, correct? Which version? What is the status shape and color of the offline pool member?
- PeteWhite
Employee
What did you expect to happen?
When you connect to the virtual server it will send you to a server and possibly use persistence to keep you on that server. If that server goes down then it will send you to a different server. Obviously, health monitors take a period of time to detect issues but these can be modified depending on your required reaction time.
- Josiah_39459Historic F5 Account
Can you post the config of your health monitor? I would guess the problem is the monitor is incorrectly configured. You should have a receive string configured in the monitor (something like 200 OK) if you want to mark the pool member down based on a 404 response. If the receive string is blank, any server response will result in the pool member being marked up, essentially the same as a tcp monitor.
- Thiyagu_163984
Nimbostratus
Thanks guys for your reply. Here is the health monitor configuration: ltm monitor tcp /Common/TCP { defaults-from /Common/tcp destination : interval 15 ip-dscp 0 time-until-up 30 timeout 46 }
11.5.1 Build 5.0.147 - LTM version Please correct me if anything is wrong with the configuration. Thanks, Thiyagu- Josiah_39459Historic F5 AccountYes, there is nothing wrong with pool at the TCP level. 404 is a layer 7 HTTP protocol specific error. According to the TCP layer, everything is just fine here. Use an HTTP monitor with properly configured SEND and RECV (200 OK) strings.
- Josiah_39459Historic F5 Accounthttps://support.f5.com/kb/en-us/solutions/public/2000/100/sol2167.html
- Thiyagu_163984
Nimbostratus
Thanks a lot Guys for your reply.
Regards, Thiyagu
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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