Forum Discussion
Brandon_High_10
Nimbostratus
Nimbostratusswitch matching incorrectly
We've seen a few errors that seem to come from a request being sent to the wrong pool.
We have an iRule similar to:
when HTTP_REQUEST {
switch -glob [HTTP::path] {
...
Ah hah! The fact that the problem only happens in subsequent requests within the same connection tells me that this is related to our OneConnect feature.
I'm assuming that you do not have a oneconnect profile on your virtual (otherwise this would not be happening). Without the oneconnect profile, the BigIP will only remake the load-balancing decision when the pool actually changes between requests (with OneConnect it remakes it every time). So, when you add the pool default_pool to the default case, it forces the repick because the pool is changed.
So, you have two options here: a) you can leave your configuration the same and simply add the default pool to the default case like you had done, or b) you can add oneconnect to your virtual.
We are actually going to be changing the http profile in an upcoming release to have OneConnect enabled by default.
Hope this helps.
