Forum Discussion
tomma
Nimbostratus
NimbostratusInquiry on F5's Maintenance Mode Feature for Pool Members
Hello F5 Community, I'm looking for a way to smoothly transition specific pool members into maintenance mode without disrupting service. Can anyone share insights or best practices on how to impleme...
Both "disable" and "force offline" actions may answer the requirement as they both provide some level of smoothness
- When set to Disabled, a node or pool member continues to process persistent and active connections. It can accept new connections only if the connections belong to an existing persistence session.
- When set to Forced Offline, a node or pool member allows existing connections to time out, but no new connections are allowed
So, for the first you need to disable the node then wait for a sufficient time to make sure there is no active nor persistent connection related to that node. Typically, you will disable a node 30 minutes to a few hours before the maintenance schedule.
For the second, you set the node to forced offline and wait a few minutes until there is no active connection to this node. Note that persistence here is immediately lost and any client who is in the persistence table but who is not actively connected will load blance to the next member.
tommaNimbostratus
NimbostratusI'm trying to find a way to move current established connections from one pool member to another, so I can perform maintenance on the first pool member.
P_Kueppers
MVP
MVPThan please explain whats wrong with disabling a pool member? You can either disable it (no new connections - established one will timeout/expire but persistent will be allowed furthermore) or you force offline so all connections to this poolmember will be timeout/expire
EDIT: Sorry I made a mistake - ForceOffline a BIGIP will close all connections immediately - On Poolmember this does not work