Forum Discussion
sathish_126179
Jun 13, 2014Nimbostratus
Pool member reselection - not working
Hi,
We are using BIG IP LTM 11.3.0. We have a requirement that in case a pool member fails immediately after a health checkup and LB doesn't know the until the next checkup. During this interval...
dragonflymr
Mar 05, 2015Cirrostratus
Hi,
What do you mean here "failed pool member" - if you mean member not replying to http traffic then I am pretty sure both Reselect Tries and Inband monitor will not be a solution. I mean situation when only http service is down but node is not. Inband is working only for L4 so it's monitoring problems with connection at the TCP level not application level, the same is true for Reselect Tries.
Of course if http is not respoding at all it will work, but if it's responding even with wrong content or error code both inband and Reselect Tries will not be triggered (as well as iRule). So your http monitor can mark member down because it is not returning correct response as defined in Receive String, but member is still replying to http requests in some way. That is first think to verify when node monitor is green but member monitor is red.
Piotr
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects