Help writing iRule based on user login id.

Thanks, Aaron, This will use TCP and we intend to look at the ID using TCP::collect as you mentioned.

 

Users do not share the connection. Each user will have their own connection to a specific pool, which answers the other question in that yes, we need to point to a pool.

 

We're already going down the general path of creating an iRule in the method you're describing, but the sheer potential size of the rule is what's concerning.

 

 

If we end up with 1000 IDs that we need to look for, that's 1000 if/else statements and it seems pretty cumbersome not only from a management perspective but we're more interested in what kind of load this will put on the F5.

 

 

If a new user comes in, that ID will be at the end of the rule. If many users come in that live at the end of the rule, it would seem that there would be some performance hit. For a rule this large, is there a more efficient method of looking up IDs and matching them to their own pool?