Forum Discussion
tai-ce_92453
Nimbostratus
NimbostratusNode Maintenance Steps Clarification
I have done some searching, but I have yet to find a clear step by step answer to what the correct process is for node maintenance.
Please clarify the iControl and equivalent WebGUI steps to perform maintenance on 1 node.
Here is what I gather are the correct steps:
1. Disable New Sessions
2. Monitor until current connections are zero
3. Mark Down
4. Perform Maintenance
5. Mark Active
What are the correct commands for steps 1 and 3 in iControl and the Web GUI?
Thanks!
3 Replies
- Hey tivers,
You've got the steps - though remember that persistent connections will not go away (at least not in a reasonable amount of time). If you have some, you should account for them in your code.
I think that this thread should help: http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&forumid=1&postid=4019 in the second post Loc lists both 1 and 3 for you.
Don. 
tai-ce_92453Don,
Thanks for the reply. That article hits on what I needed.
Another question:
If I do not need persistent connections, can I force all connections to be moved to other nodes/pools?
I currently have no persistence profile and use an iRule with "persist none" on HTTP_REQUEST.
How is connection persistence determined?
-Tom- Hey Tom,
Glad it helped!
My understanding - which may not be perfect, but I'm pretty confident in - is that connections can't be force moved, you have to wait for them to close or kill them outright (in which case they will be "moved" by reconnecting to another server in the pool, but the user will notice the dropped connection).
If you've got persist none set, then unless you have machines accessing the server persistently around the BIG-IP (people do it, more than you'd think because the BIG-IP is used for visitors, not always for admin), you should be good.
Don.
