CirrusI've been looking at the Receive Disable String on some HTTP monitors, and we can confirm that when the monitor detects the string the pool members do in fact get disabled, but when the receive string is returned instead the member never gets returned to enabled. Is this normal? or is there a way to automatically re-enable the member once it's functioning again?
Thanks in advance.
CumulonimbusWhat are your "Receive String" and "Receive Disable String"?
CirrusRecv: Online Recv-Disable: Maintenance
CirrusIs there only one monitor for the pool ? Are there monitors at the node or pool member level ?
When the "Recv" string is returned, the pool member should be marked online. Where you able to confirm for sure that the "Recv" string is indeed sent by the pool member to the F5 by running CURL from F5 to the relevant pool member ?
If so, have you checked to make sure that the monitor doesn't have "Manual Resume" enabled. This could cause the down pool member to be down till it is manually enabled.
Also, check to make sure that the "Reverse" setting is not enabled.
CumulonimbusAccording to "sol12818: Using the Receive Disable String advanced configuration setting", you configuration should work. You might want to contact F5 Support to see if this is a known issue. And which version of BIG-IP are you running?
NimbostratusJust tried this and got the similar result, Receive-Disable String Online=false causes the node to be Disabled but when string is the set to Online=true node is still Disabled have to force it Online through the GUI of F5