Setting up AWCM persistence rules using F5

Setting up AWCM persistence rules using F5

The following guide shows an example of an F5 LTM configuration of persistence settings for an AWCM deployment, but it could be very similar to other load-balancing appliances.

The persistence settings are only necessary for AWCM servers that are load-balanced in an active-active manner.  The persistence settings will ensure that established connections are not dropped when the F5 switches from one AWCM server to the other to balance the load.

On-premises customers will need to configure their F5 to persist the HTTP requests to AWCM based on the value of a awcmsessionid cookie. The iRule might vary based on a client’s existing configuration or best-practices, but the basics are straight forward:

  • Parse the HTTP request for the awcmsessionid cookie's value
  • Set persistence with this value via the “persist carp” command.

For more background on this methodology, see the following F5 solution page for Overview of the CARP hash algorithm.


Steps for adding a persistence profile for AWCM

1. Create an iRule to inspect the HTTP request for the value of the “awcmsessionid” cookie.




    if { [HTTP::cookie exists "awcmsessionid"] }{

        set awcm_session_id [string tolower [HTTP::cookie "awcmsessionid"]]

        persist carp $awcm_session_id




2. Create a persistence profile based on the default “hash” profile.  All items should be default except the following:

    • Algorithm: “CARP”
    • iRule: created in Step 1.



3. Configure the Virtual server with the following settings:

    • Select an HTTP profile from the “HTTP Profile” drop-down.


    • Select OneConnect profile (for HTTP request balancing, not just connection).


    • Apply the persistence profile under the Resources tab.


Have more questions? Submit a request


Article is closed for comments.