Forum Discussion
Disabling a Pool Member for maintenance from the Server Side
Monitor disable mean your pool member will not take new request from VIP and slowly all existing session will be terminated/closed but system is remain in network. So, you will able to ping from your system/BigIP.
In-order to block ping, You will have to enable setting in window/unix server.
Thank you so much for question..
When the server team changes the file to "Status: enabled" the monitor should display the node is online again I believe, correct?
defaults-from http
destination *:webcache
interval 5
recv "Status: enabled" --> Server Team is changing the page contains based on that LB monitor. LB takes decision to enable & disable pool member
send "GET / HTTP/1.1\\r\\nHost:controlfile-test.corp.mdsdata.com"
time-until-up 0
timeout 16
recv "Status: enabled" --> Server Team is changing the page contains(enable/disable) based on that LB monitor. LB takes decision to enable & disable pool member
Client is states he see the server still receiving requests and I think he is incorrect.
Due to LB persistence method, current session is going to Pool member, Its default behavior of LB. You can make persistence
none
in LB VIP to solve issue and make sure other persistence profile should not attached.
Im trying to understand the logic from the server side of things. Where does the client place the server.txt file which contains the "Status: enabled/disabled" text?
Client placed file on server side & changing parameters via DB/Web to enable/disable pool member.
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