Disabling a Pool Member for maintenance from the Server Side

Hi f5_rock -

Thank you for clarifying the monitor disable state and from what I can see the node is currently disabled. Whats confusing is the steps taken from the server teams. When the server team changes the file to "Status: enabled" the monitor should display the node is online again I believe, correct?

Right now when I perfom a GET I am seeing "Status: disabled", so the node is marked down. Therefore the pool member will not take new request from VIP and slowly all existing session will be terminated/closed but system is remain in network. I guess I am seeing the correct result, but client is states he see the server still receiving requests and I think he is incorrect.

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? A specific directory under webpage? I perform a GET to http://controlfile-test.corp.mdsdata.com/server.txt and then I get the reply back with either a disabled or enabled. Would the server team have to create a file for every FQDN's theyd like to disable for maintenance?

[xxxxxxxxx:Active:In Sync] ~ curl http://controlfile-test.corp.mdsdata.com/server.txt

Status: disabled[xxxxxxxxx:Active:In Sync] ~

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

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.

i.e http://controlfile-test.corp.mdsdata.com/server.txt