Persistence across pool members

Hi Jake,

 

 

I think the option that would help isn't persistence, but reselection of a pool member when the current member is marked down by a monitor. You can set this option on the pool. The option name is "Action on service down". You can set it to 'reselect' to have LTM select a new pool member. Here is the section from the online help in 10.1:

 

 

 

Specifies how the system should respond when the target pool member becomes unavailable. The default is None.

 

 

* None: Specifies that the system does not select a different node. Selecting None causes the system to send traffic to the node even if it is down, until the next health check is done.

 

* Reject: Specifies that the system sends an RST or ICMP message.

 

* Drop: Specifies that the system simply cleans up the connection.

 

* Reselect: Specifies that the system selects a different node. Selecting Reselect causes the system to send traffic to a different node after receiving the message that the original node is down.

 

 

 

 

Aaron