Auto switchover when other pool is unavailable

Hi Albert,

I dudo if the "match across pools" option if the right choice for your environment. The match across options is just required for scenarios where you need a "teamed" persistance across different service ports, virtual servers or even across pools having odd members. For further reading on this topic see sol5837.

If I understand your question right, then you don't have any problems with your the failover in general. Its just that the login session to the backend applications will break in the event of failover, right? If this is the case then you should elaborate addtional information on the application and especially the login mechanism used by your application (e.g. HTTP-based, Cookie-based, Forms, SAML, etc.)?

Cheers, Kai

Hi Kai,

Thank you for your quick reply. The issue is login session to the backend applications will break in the event of failover. I assumed that enabling match across option will handle the failover in the event of one of the pool member is down and client will not be affected. User should not notice it but user have to login again via http with source address (match across enable). There should be a tweak in iRule or Http class profile as we are still using 10.2.1 version.

Thanks,

Hi Albert,

as I said, the "match across pools" option is not needed for failovers to a different pool member of the same pool.

Also keep in mind that the failover capabilities of a LTM is just HTTP-based and does only work seemlessly, if your web application could handle non-sticky sessions. If your web application can't handle the load shift from the failed node to its standby system, then you have to implement a Single-Sign-On mechanism either on your web application itself or by using some sort of pre-authentication and single-sign-on functionalities by using APM or plain iRules.

Cheers, Kai