Trying to troubleshoot persistance in our environment and would like some assistance on how to do this on the F5 LTM running 11.4.1

An example of a tmsh command would be

tmsh show ltm persistence persist-records node-addr 10.40.90.40

There are also other switches like:

• key Specifies the key to look up in the persist table. It is based on the persist mode.
• mode Specifies the type of persistence.
• node-addr Specifies the address of the node with which the client session remains persistent.
• node-port Specifies the port of the node with which the client session remains persistent.
• pool Specifies the name of the pool with which the client session remains persistent.
• virtual Specifies the name of the virtual with which the client session remains persistent.

Hope that helps.

Worked on resolving a persistence issue to a few Citrix gateways that are load balanced by a BIG-IP® 6400.  I discovered that it is possible to use both a default persistence profile and to specify persistence in an iRule, all on the same Virtual Server.

Bearing in mind that I have the “Default Persistence Profile” set to use a profile other than cookie, here is the iRule that I wrote:

when HTTP_REQUEST { 
set header_uri [string tolower [HTTP::uri]] 
if { [matchclass $header_uri starts_with $::aaa_uri] } { 
       pool aaa_Pool 
} elseif { [matchclass $header_uri starts_with $::bbb_uri] } { 
       HTTP::redirect "https://bbb.companyname.com/bbb/main/Main.jsp" 
} elseif { [matchclass $header_uri starts_with $::CITRIX_uri] } { 
       persist cookie insert "CITRIX_Cookie" "0d 03:00:00" 
       pool CITRIX_Pool 
} else { 
       pool ccc_Pool
 } 
}

The command persist cookie insert “CITRIX_Cookie” “0d 03:00:00″, tells the BIG-IP® to create a cookie named CITRIX_Cookie, give it a duration of 3 hours and insert it into the header of traffic going to the CITRIX_Pool.  If traffic going to that pool already has the CITRIX_Cookie in its header then persist the connection to the same pool member that it used last time.

Traffic going to the rest of the pools will use whatever persistence method is set in the “Default Persistence Profile”.  It is also possible to disable persistence to pools by using the persist nonecommand.