Forum Discussion
Nimbostratusbest way to push new IIS sites with zero downtime?
We are going to be moving some of our API servers behind the F5 LTM.
What is the best way to drain connections from the current active server to the new IIS server with the newer code? Should I have each server in a different pool and just change the default pool in the virtual server or do I disable the member on the active server and enable the server with the new version of code? This API will be using 2 different TCP ports
I appreciate any thoughts?
3 Replies
- nitass
Employee
what about forcing node offline (i.e. adding new nodes to existing pool and then forcing existing nodes to be offline)?
sol13310: Disabling nodes or pool members for maintenance (11.x)
http://support.f5.com/kb/en-us/solutions/public/13000/300/sol13310.html 
Kevin_Bozman_15Yes that looks to be the way to go. I was told from others to setup two pools and just switch the default pool. I haven't found any docs recommending that though. One problem with that is you'll have to go into each virtual server and change the default pool. For application that have multiple servers, this could created problems for obvious reasons.
Being that we'll have a virtual server for http, one for https and virtual server another for two other TCP ports, I assume I can just have all of these virtual servers use the same pool. Once I deploy new code to my passive server, I'll enable it in the pool and force offline the server I want to bring down. The server with the new code will receive all the new connections and it should be pretty seamless for the end user.
Sound good?
- nitass
Sound good?
yes, it sounds okay to me.
