For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

ghost-rider_124's avatar
ghost-rider_124
Icon for Nimbostratus rankNimbostratus
Apr 12, 2014

Disable Pool Member and Persistence session should die??

Hello Experts

 

If I manually disable pool member then the persistence session would remain on that pool member? If I want, clients in persistence table should move to other available pool member then what I need to do?

 

Regards,

 

GR

 

3 Replies

  • I guess one simple way would be to kill the service on the member, ie stopping the site for a second.

    Or try to delete the persistence records for the node via tmsh:

    tmsh delete persist-records node-addr 10.0.0.15

    To kill the connections to a specific member you can try this one:

    tmsh delete /sys connection ss-server-addr 10.0.0.15 ss-server-port 80

    /Patrik

  • This is untested, both in practice and in syntax. but you can give it a try. 🙂

    when HTTP_request {
    
        set pool "MyPool"
    
        Check if a server has been chosen and if the pool is the right one.
        if { [LB::server addr] and [LB::server pool] -eq $pool } {
            Check the status of the selected member and reject the connection if it's disabled
            if { [LB::status pool $pool member [LB::server addr] [LB::server port]] eq "session_disabled" } {
                reject
            }
        }
    }
    

    If you want the rule to also cover when the pool is down you can add an "or" to the "if" statement.

    /Patrik

  • It's actually as easy as choosing force offline rather than disable, you can't do it under the member list in the pool though, you have to click on the member to see that option. That will still leave some active connections on the member though. If you also want to kill active connections, look under advanced options in the pool for a parameter called action on service down and set that to reject.

     

    It won't remove the entries in the persistence table though, but it will force the clients to other members in the pool.

     

    On a completely unrelated note - hi Patrik! :)