Forum Discussion

Luiz_Guimaraes_'s avatar
Luiz_Guimaraes_
Icon for Nimbostratus rankNimbostratus
Apr 04, 2017

iRules and traffic policy does not take effect

Hi guys,

 

Let me explain the facts:

 

We're running with Microsoft Application Request Routing (ARR) and we're about to change to F5 4000S.

 

The original idea is migrate "as is", but some diferences between the Technologies don't let us to do a "smooth" job.

 

There are a lot of applications on our environment published under one DNS name. Example:

 

Oursapps.xpto.com is our HTTP_HOST and there are a lot applications under that, like:

 

Oursapps.xpto.com/app1 Oursapps.xpto.com/app2 Oursapps.xpto.com/app3 etc

 

So, we are very concerned with our Change Management, because is very commom to publish new applications in the morning and I realized that BigIp keeps some configurations to existing sessions and it's needed to reset all connections to send the new configurations to the client immediately.

 

Is there any diffence whether I using Irules or Traffic Policies(Local Policy)? I'm trying to find out one way to make it works without forcing clients to drop their sessions using "Delete Sys Conn".

 

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Well, I am having a hard time trying to understand what the problem is. :-) So, could this be re-phrased somehow?

     

  • @Jie hi buddy! It's all about the use of traffic policy or iRule to route the traffic to an specific pool based on the URI. The problem is: some department here should ask me to deploy a new application or make some change in a production application but this changes doesn't take effect even in iRule or Traffic policy. If I wait some minutes and try to access again I can see the changes. Why is it happen ?

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Perhaps an example would explain this better?

     

  • Example: I have an iRule that works with the URI /app1 in a VS called VS_HOME_APP so I will create another iRule to another application based in the HTTP_URI /app2 and apply it to the same VS. Note the iRule will redirect the traffic to a different pool.

     

    This kind of change doesn't take effect immediately, its take effect after some minutes when doesn't have traffic to the VS from my machine. Is it normal ? Will I need to perform anything else about this ?

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Will you show the output of:

     tmsh list /ltm virtual VS_HOME_APP

    ?

  • Hi,

     

    Pool assignment is connection based.

     

    If you change the default pool defined in the virtual server in an irule, the new pool will be assigned for next request within the same connection until a new pool is assigned by the irule or policy

     

    You can change this behavior with 2 solutions:

     

    • enable one connect profile
    • define a default rule in policy or a else statement in irule