Forum Discussion
Monitor Disables Node, persistent connections
Ok thanks for you help, neither reject or reset were effecting the behaviour. After a webex session with tristan from F5, we realised it was the "Receive Disable String".
According to this page: http://support.f5.com/kb/en-us/solutions/public/12000/800/sol12818.html?sr=38128338
The behaviour if the Receive String is not received, but the Receive Disable String is (in our case this was a string from an error page warning the back-end node was down) then the Node is marked UP(disabled) or "draining mode" as some people call it. The solution was to simply remove the Receive Disabled String and have the node marked as Down when the Receive String was not received.
Receive String Receive Disable String State
Yes No Up (Enabled)
No Yes Up (Disabled)
No No Down
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
