Forum Discussion

JS54_315899's avatar
JS54_315899
Icon for Nimbostratus rankNimbostratus
Mar 31, 2017

How can I change the idle timeout of the active connections on the member disabled?

Hi Expert,

 

 

I need your help to goal the following condition;

 

Environment:

 

LTM just is balancing the UDP traffic among 3 pool members. The connection idle timeout is 1 hours. I disable the poom member to maintain the real servers once a month.

 

 

 

Conditions:

 

When I disable specific pool member (e.g. the pool member1), LTM wait till the pool member1 proceed the active connection on it. but it means I sometimes wait more than 1 hour as this LTM LB mechanism. I also don't want that all of active connection on the pool member1.

 

So, I am looking for the way change the idle timeout of active connections on pool member1 from 1 hour to 5 minutes, if I disable the pool member1.

 

 

 

Does anyone give some advice to me?

 

I would appreciate your any input.

 

Thank you

 

J.Soon.

 

4 Replies

  • Please remove the connection from the connection table with delete sys connection command.

     

    delete /sys connection ss-server-addr 1.1.1.10 ss-server-port 80

     

  • Hi Arora,

     

    Thank you for your reply. My customer does not want to delete active connections on the member disabled, because that impact to their service. So, I am looking for the way to change idle timeout of active connections on the member disabled.

     

  • I think you can achieve this by creating a rule for server side connected

     

    Please modify this as per your understanding when HTTP_REQUEST {

     

    if { (([HTTP::host] == "abc.com") or ([HTTP::host] == "cdf.com")) and ([HTTP::uri] ==

     

    "/poodle") } {

     

    IP::idle_timeout 86400

     

    set serverside_idle_timeout 1

     

    } }

     

    when SERVER_CONNECTED {

     

    if {$serverside_idle_timeout} {

     

    IP::idle_timeout 86400

     

    }

     

    }

     

  • You can't change a timeout for just specific member because that is inherited by the profile settings (persistence, service, protocol, etc).