Forum Discussion
virtual-server with multiple irules : conditions of invocation
virtual-server-1
default pool-1
irule-1.conf
priority 100
for url A , conditional logic does to this line :
pool pool-2
irule-2.conf
priority 110
for url A , conditional logic goes to this li...
JPV_131616
Cirrus
Cirrusfrom my understanding, you cannot guarantee invocation order.
so if multiple conditions are met it could cause conflicts/errors.
default pool is hit if no other conditions are met via irule, etc. on the vip - but you cannot rely on order from my experience.
just my two cents
cheers
- My very limited experience ( this is first time I've created > 1 irule per virtual-server ) indicates ( via logs ) that indeed irule-1 ( priority 100 ) fires first , and once it is completed irule-2 ( priority 110 ) fires second ( always ). What I find non-intuitive is that if irule-1 routes the request to a pool , why does irule-2 fire at all ? In other words , why did f5 design it this way ? Also, another strange behavior I'm seeing is that after irule-2 routes to pool-3, irule-1 fires again, then irule-2 again. This repeated sequences occurs 7 times before ceasing. There are no site redirects in play here -- I've even performed a test where I stop the website and test and the f5 logs still show the same pattern of irule-1,irule-2,irule-1,irule-2,etc. What could be causing this behavior ?
