Forum Discussion
robert_hodge_10
Nimbostratus
NimbostratusHealth Monitor not Satisfactory
The health monitoring with F5 BIGIP is not satisfactory and cannot quarantee a tcp connection. The health monitor has a frequency configured for connection attempts, but if a server fails between the health monitor connection attempt then a client could be sent to the server that is down.
We notice that V9.X can snoop the tcp connection, or http connection and we hope that we can configure the BIGIP to send the client to the good server within the pool before the client has been established at the tcp layer. Is there hope for us? Can anyone assist?
- hodge,
I'm not sure that this is something we can address here on the iControl SDK forum. This looks like a BIG-IP product related question and if so will have to be directed to F5 Product Technical Suport:
F5 Technical Support
Email: support@f5.com
Phone: 206-272-6888
Web: http://www.f5.com/support/
AskF5: http://tech.f5.com/
With that being said, in 9.x, you can use iRules to peek at the traffic and make load balancing decisions based on the content. I'm not sure how this would help you determine which server is the "good server" within the pool as there are no real-time outbound network calls from within iRules (due to obvious performance related issues). But you can "snoop" in both directions (request and response). So, if there is something in the response you can use to determine whether the server is in a "bad" state, then you can perform other routing decisions at that point. Maybe that is what you are looking for.
Feel free to post iRules related questions to the appropriate iRules forum if you feel that iRules can help you out.
As for the health monitors, that's a product related question and I'd suggest you use the Product Support link for that one.
-Joe
