Forum Discussion
Incorrect load balancing when disabling Oneconnect
- Jan 13, 2016
Is the app-pool configured as Default Pool in your Virtual Server settings? If you conditionally select another pool, ie. the server-report1 pool in an iRule, you will need to include a 'Default or Else' clause in the iRule to 'Re-Confirm' your Default Pool. Just having the app-pool as your Default Pool setting in Virtual Server properties will not be enough.
You may see a similar problem occuring in your environment:
- Your first request to app-pool is routed correctly - Your second request to app-pool is routed correctly - .. All requests destined to app-pool are routed correctly, until the first occurence where a request is routed to server-report1 pool - .. All the requests that should go to app-pool (default) thereafter are now incorrectly routed to server-report1 pool.
For a solution, if you're using the
conditional statement, append anif
statement to specify the app-pool as your default selection in iRule. If you're usingelse
conditional statement, append aswitch
statement.default
Give it a try, if the conditions described match your configuration. This would be a generic iRule problem, not related to OneConnect by any means.
Hi,
In irule changing the pool based on URI, don't forget to change back to default pool URI which does not match specific URI.
Pool decision is done for the entire tcp connection when one connect is not enabled.
when CLIENT_ACCEPTED {
set default_pool [LB::server pool]
}
when HTTP_REQUEST {
if {[HTTP::uri] starts_with "/reports"} {
pool report
} else {
pool $default_pool
}
}
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