Fault Tolerant long-lived TCP connections

Thanks. I did setup a typical VIP, with a typical pool, but this isn't a typical scenario, asfaik. I need to make the whole thing fault-tolerant. I've confirmed that client connections round-robin between the two rvd servers, as I knew they would. However, if I kill one of the rvd servers, the clients attached to that rvd immediately terminate as well. What I want to accomplish is to detect, or intercept, the SERVER-side failure before the CLIENT-side TCP connection is closed and somehow get the client connected on another SERVER-side connection. I'm not sure if this is possible. If not, i'd like to know what, if any, of my options are for high availability of long standing TCP sessions. I'm hoping there are options.

 

 

The VIP is setup with SNAT and OneConnect is set to use the standard oneconnect profile. I'm using the round-robin algo. I implemented an iRule with stubs and log0. entries in each stub just to see what gets called when. When I kill the server, I see the client terminate before I see any LTM messages. And the first message I see is the health check message telling me my server died, but by then it's too late. The client has already terminated.