Forum Discussion
jake_macabuag_4
Nimbostratus
NimbostratusPersistence across pool members
**Subject should be: Connection Mirroring across Pool Members******
Hi,
I just wanted to ask if there is a way to do connection mirroring across pool members?
So for example, if the user logs in to the VS with cookie or source address persistence, and while navigating the page, the pool member suddenly went down. It should be directed to another pool member without logging in again to the virtual server. So it will be seamless to users. Im checking jsession using irule, but is there a way to copy that to another pool member via irule?
Ive read also that connection mirroring is not an irule feature. Just checking if there is another way to accomplish that.
thanks
hoolioCirrostratus
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- jake_macabuag_4Thank you for the information. Would this mean the active user doesn't need to re-login to the site?
I'll check that settings and will give you feedback.
thanks - hoolioIf the user's session exists in some kind of shared memory, database, etc that all pool members have access to, then the client would not need to log in again.
If the session only exists on the single pool member, and a new pool member is selected, the client would need to log in again. There isn't a way to for LTM to create a session on each pool member or sync any data to all pool members. This is something that would need to be implemented in the application.
Aaron