Forum Discussion
Nimbostratusremoved pool member - traffic continues to be sent to node
I have a node that is in multiple pools. We were having issues w/ a pool member, it was disabled (which I realize would continue w/ persistant connections if there were still entries in the persistance table). So the user then deleted the node from the pool.
It continued to sent traffic to the pool member for traffic pointing to the vip w/ that pool. It was not until the node was deleted from the other pool that it was in that is stopped sending traffic.
Is this normal behavior?
4 Replies
uniAltocumulus
Interesting behaviour. It is unexpected as far as I'm concerned. However, you would be better off forcind the member down. From the GUI, click on the pool member and force it down, rather than just disabling it.
Sukhjit_Singh_1I have seen the same behavior. Even when we removed the pool-member from pool (that is not being used in any other pool or irule or IP Forwarding). Node is Still serving the genuine traffic via LTM.
- Maneesh_72711
Cirrostratus
Forced Offline is what should be used if you want the connections to bleed off quickly.
When you disable a pool member, you allow it to continue to service already established connections and anything that's tied to it in the persistence table.
Force a pool member offline, you're only allowing it to service already established connections.
IainThomson85_1Cumulonimbus
This is an old question that's been dragged up....
But if you have quite "Active" connections using the same TCP Stream, you might be best off using Action on Service Down: Reset - Which will send a TCP RST if the pool member is marked offline by a monitor or by manually disabling.
