Session Replication

Hi!

 

You could setup connection mirroring and persistence mirroring, but it would not work for full proxy ssl connections and it's not recommended by F5 to do that for HTTP connections.

 

More information can be found here:

 

https://support.f5.com/kb/en-us/solutions/public/13000/400/sol13478.html

 

Hope that was what you were looking for. :)

 

/Patrik

 

I wonder if jaz is referring to pool members failing. Connection and persistent mirroring applies to a bigip failing and a peer bigip taking over the connections.

 

You've got a Pool setting called "action on service down" which might help, in certain circumstances. Apart from Reselect all the others result in a new session. Reselect is best for UDP or fastl4 virtual servers.

 

N

 

hi, yes, I am talking about pool members, not bigIP (HA peers).

 

in my case, is that I have two pools, and I have an iRule for directs all the calls to pool-1 but only one call to pool-2, all calls are from within the same app after the user logs in. what happens is when the user fire a call which goes to pool-2 , I start to see session exceptions.

 

what is happening in my case, is when the user first logs in, and do some browsing...ect....all those calls go to pool-1 ( and to the same member which is expected by the persistence -cook profile). but then once the user decide to fire that one job which goes to pool-2, we see exceptions.

 

so the session was never shared with other members.

 

There is a known issue where if you mix iRule pool decisions with configured default pools (via the GUI) you can get unexpected behaviour. Are you using a default pool via the GUI or via the iRule?

 

Have you considered doing some loggin in your iRule (or check the web server logs) to make sure that the exceptions come from the right source?

 

/Patrik

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.

 

GM, in fact I found the answer, session replication has to be done at the server side (backend, pool members).

 

thank you all.