Forum Discussion
NimbostratusHow to make server pool decision based on incoming IP
Suggestion on best way to handle:
Converting from Ace to F5
Have configuration on Ace that has a loadbalance policy that has the criteria that if a specific source IP is matched, request is sent to one server farm. All other source IPs are sent to a different server farm.
Is this a situation for an iRule, and if so, could an example of how to construct be provided?
Thanks!
Eric
- Kevin_Stewart
Employee
Definitely a simple iRule.
-
Create an address-type data group and enter your matching IPs (or IP subnets).
-
Create both pools.
-
Optionally attach the "default" pool to the VIP if you want monitor stats to be reflected in the VIP.
-
Add an iRule like the following to the VIP:
when CLIENT_ACCEPTED { if { [class match [IP::client_addr] equals my_ip_datagroup] } { pool secondary_pool } else { pool primary_pool } }
You can also do this with a CPM policy, or a single static IP and the [IP::addr ] command instead of using a data group match. However the data group match is arguably more flexible. Also, if you add the default pool to the VIP, you don't technically have to add the 'else' condition, but it's generally good practice to account for all conditions.
And you may also want to add a OneConnect profile to the VIP if client traffic switches between the pools mid-session, but it doesn't sound like that's the case here.
-
