Forum Discussion

6 Replies

  • As per my understanding F5 validate the VIP setting as per defined configuration (Top to Bottom). In that iRule comes prior then policies. So, I will go with iRule first.

     

    But both has unique feature...

     

    • Local Traffic Policies are faster if performance is an issue
    • iRules are more flexible and you can get help from DC people
    • Jhaunu_Gupta's avatar
      Jhaunu_Gupta
      Icon for Nimbostratus rankNimbostratus

      As per our setup LTM policy is getting executed first than irule getting executed

       

    • Samir_Jha_52506's avatar
      Samir_Jha_52506
      Icon for Noctilucent rankNoctilucent

      In your setup could be traffic match per policy condition.

       

      For support events such as HTTP_REQUEST & HTTP_RESPONSE; LTM policy evaluation occour before iRule. This means that's possible to write iRule to override an LTM policy decisions.

       

      Cheers...

       

  • Policies and profiles always execute before iRules for the same network layer.

    For example we have policy to ensure iRules events are enabled as we have several iRules that do an

    event disable all
    during select errors, to ensure we re-enable all the iRule event for the next HTTP request (multiplexed clientside connections) we use policies to run the TCL commend to
    event enable all
    . We can only do this as the Policies execute before our iRules.

    However, your

    CLIENT_ACCEPTED
    iRule event will execute before your HTTP profile or any Policy looking at the HTTP request as this is simply the order of events based on the F5 processing through the network layers.