I'm looking for a "least effort" method to allow developers to take pool members offline and add them back once maintenance is completed. We don't currently have anything setup via API to do this and I have recently taken this environment over. Can someone make some suggestions that I could implement fairly quick? They have a number of updates to make on members next week and I'm trying to set something up by then.
I thought about giving them limited access to the F5 allowing them to do so but as developers they would rather not log into the WEB UI if they can use REST or curl or.....?? Which I understand. Looks like most pools are doing generic health checks (https/http).
They did ask the following " If we hook the KeepAlive page up everywhere we have one, that would effectively be giving us access"
Does that make sense?
Any advice is much appreciated, I'm sure plenty run into this scenario.
Keep alive page is always best option to monitor application from LB with receive/disable string. Ask application to team to create simple page in server with OK string and configure http/https lb monitor accordingly.
Actually for the OP to not get confused. Dont just put OK as string. Because when the LTM monitor looks for a string, it looks for in the 1st 5120 bytes of data. So even a 200 OK will mark the pool members as UP. So be specific with your string to mark the server up and for draining with recv-disable. Cheers.