Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member


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

primarySorryServer sorryTHIS

protocol tcp

port 80

url "/*"

advanced-balance arrowpoint-cookie

flow-timeout-multiplier 120

no persistent

arrowpoint-cookie name XXX01


Cisco Employee

Re: Flow-timeout-multiplier

the CSS will not close the connections, even if you change the timeout multiplier.

Only the client or the server can close the connection.

Therefore, changing the timeout on the CSS will have no effect on the proxies.

However, it could break something on the CSS.

I would therefore not change the CSS timeout.

If you have control of the servers, reduce the timeout there.

This will force idle connection to be disconnected.