Forum Discussion
iRule to direct specific IPs to specific members, not working as expected.
Agree with JPV - if you use cookie and source IP you are asking for trouble - the first request of an HTTP 'session' never has a cookie, so source IP will always be used!!
The problem is that your pool selection is being done in CLIENT_ACCEPTED, but oneconnect means that the pool is reset to the default each time HTTP_REQUEST is triggered, in addition, I think there is a slightly better way than your pool ISIS-Web_SSL member statements. I would use another pool for the webmethods traffic;
pool ISIS-Web_SSL_webmethod {
lb method member observed
snat disable
monitor all https1.0
members {
10.10.10.108:5004 {priority 3}
10.10.10.110:5004 {priority 1}
}
}
and then your iRule would become;
when HTTP_REQUEST {
if { [class match [IP::client_addr] equals "TXHUB_IP"] } {
persist none
pool ISIS-Web_SSL_webmethod
}
}
- IheartF5_45022Jan 17, 2014
Nacreous
The separate pool is purely a "I would do it this way" thing - your rule is fine - it's only the event that is causing you an issue
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com