Persistence Across pools via iRule

The persistence cookie contains an encoding of the member IP:port. If the VIP is using cookie insert persistence but requests are load balanced across pools, the persistence will fail whenever the last selected pool member IP:port doesn't exist in the currently selected pool.

You could try inserting a unique cookie per pool in an iRule using the persist command (Click here😞

 
 when HTTP_REQUEST { 
    switch -glob [string tolower [HTTP::path]] { 
       "/vmsxml/order.asp" - 
       "/vmsxml/status.asp" - 
       "/_xml/ors/status_mismo21.asp" - 
       "/_xml/ors/status.asp" - 
       "/_xml/ors/rels_status_mismo21.asp" { 
          persist cookie insert b2_cookie 
  pool uat.domain.com_B2B_HTTPS 
       } 
       "/batchprocessing*" { 
          persist cookie insert batch_cookie 
          pool uat.domain.com_BatchPro_HTTPS 
       } 
       default { 
          persist cookie insert https_cookie 
          pool uat.domain.com_HTTPS 
       } 
    } 
 } 
 

Also, if you check the path using HTTP::path instead of the URI, you can remove the wildcard from the end of the asp paths.

Aaron