Source Address Persistence issue

Hey Ram

First off, is connection limits an option? If the servers are crashing, perhaps you should set a high water value of connections that the servers can handle. Even though there is a persistence record, if the servers reach their connection limit, they won't accept any more traffic. This is set by the Override Connection Limit setting in the persistence profile, which is per default, turned off.

If Connection Limit is not an option, some sort of separation needs to be done in order to use different persistence profiles. I'd say that you either investigate further to find the ports used and create a separate VIP for this traffic where you can assign a different persistence profile.

Or you use an iRule on the existing VIP but you filter on different values, such as Client IP.

Below are some example iRules:

Match on Client IP:

when CLIENT_ACCEPTED { 
    if { [class match [IP::client_addr] equals addressrange] } then { 
        persist source_addr [] []  
    }
}

Match on URI:

when HTTP_REQUEST {
    if { [string tolower [HTTP::uri]] contains "myuri" }  {
            persist source_addr [] []  
       }
}

Let me know if you have any further questions. 🙂

Are your clients behind a proxy? If you have long-running sessions then you want to maintain persistence but it could be that all of your clients are only matching a single persistence record. You can check by looking at your persistence records. Do you have Match Across Services set in your persistence profile? I would expect that new connections will be loadbalanced across the servers, even if those sessions are long-running.

 

It could be that you would be better off assigning an HTTP and OneConnect profile and using cookie persistence instead. To improve your monitor, use the HTTP monitor and set the port to one on which you know the web server is running.