long story
During a cookie issues involving passing through 2 CSS units I opened a Tac Case.
During this case , I was advised to use the flow timout multiplier command as a possiblity in resolving the cookie issue.
Unique names on the cookie seemed to cure the issue. But, I did leave the flow timeout multiplier on the rule.
This has worked for well for many months.
above this CSS are a pair of proxies that take care of external access. These proxies are having problems under load. The logs from these proxies seem to indicate that sessions are staying open, TCP 3 way handsahake don't always close correctly etc.
My question is Do I really need the flow timeout multiplier set to 120 ( default 8 for http ) Is this contributing to the issue. Below is a cleaned up content rule
content appexternal
balance aca
add service appwwebprod01-appex
add service appwwebprod02-appex
add service appwwebprod03-appex
add service appwwebprod04-appex
vip address 1.1.1.1
primarySorryServer sorryTHIS
protocol tcp
port 80
url "/*"
advanced-balance arrowpoint-cookie
flow-timeout-multiplier 120
no persistent
arrowpoint-cookie name XXX01
active
