Forum Discussion
Wolfgang_Blau_7
Nimbostratus
NimbostratusPool selection based on initial connection request
Hi there,
some mobile network operators use legacy clients installed on their customers PC’s. These clients initially check if they’re talking to the right server by connecting to IP address 1.1.1.1:4321 and doing a hand shake.
In order to continue support for these clients we would have to
1. Spot connections to 1.1.1.1:4321 and route them to the legacy server.
2. Route all further requests from the same client (IP address) to the legacy server.
Req1 could be done with an iRule where we select the pool. I can’t see how to solve req2 if the persistence timeout kicks in:
- there can be any nmber of subsequent connections
- there may be different protocols involved
- Ip addresses are assigned temporarily to client devices hence the need to limit persistence
- client devices may be idle for longer than the persistence time
- we've to support 100000 clients in parallel
Thanks.
- Is there only one legacy server, or a pool of them? If there's a pool of legacy servers, is it important that once a client routes to one (the very first time) they ALWAYS persist to that SAME server, even if the next request is 60 days later or next year or something?
If all you need is for all requests for a given session to go to a single server, or if there's only one legacy server, then this shouldn't be a problem at all using normal persistence settings.
Colin 
Wolfgang_Blau_7There's a pool of legacy server and only request for the same session need to go to the same server. During the next session the client device will have a different IP address.
I agree as long as the idle time of the session isn't longer than the persistence timeout it'll work. I don't want to set the persistence timeout too high as this might introduce other problems.- I suppose my point is that this is a very standard configuration, and doesn't really involve iRules at all, as far as I can tell from the description. Basically you need to figure out a persistance timeout that will work for you and your users, based on the session idle timeout settings you're seeing.
Or...you could try to enforce a particular timeout setting for the session.
Colin
