Forum Discussion
NimbostratusApplication timeout.
Hello,
We have an application its using for bi. while generating huge report through the LB vip we are facing timeout. hence we increased timeout value but still facing the issue. When we pointing to the individual node we are able to generate report.
Please see the current profile.
profile persist src_ip_3600_zzzas-q { defaults from source_addr mode source addr mirror enable timeout 3600 mask 0.0.255.255 map proxies enable across services enable }
please have a look and let me know a solution for the same
4 Replies
Bhanu_9561Cirrus
This might be an issue at the TCP layer, where the long idle time wait (during the generation of the report) is causing the TCP session to be closed.
What is the Idle Timeout setting on the TCP profile. Did you try increasing the idle timeout and test?
sinu_121261:Active] config b virtual gtafasfafafvzvvz list virtual gtafasfafafvzvvz { pool gtafasfafafvzvvz destination 171.205.9.37:8090 ip protocol 6 rules SNAT2VIP persist src_ip_3600_ gtafasfafafvzvvz profiles { http-xff {} tcp-lan-optimized { serverside } tcp-wan-optimized { clientside } } }
profile tcp tcp { reset on timeout enable time wait recycle enable delayed acks enable proxy mss disable proxy options disable deferred accept disable selective acks enable ecn disable limited transmit enable rfc1323 enable slow start enable bandwidth delay enable nagle enable ack on push disable idle timeout 300 time wait 2000 fin wait 5 close wait 5 send buffer 32768 recv window 32768 keep alive interval 1800 max retrans syn 3 max retrans 8 congestion control highspeed zero window timeout 20000 }
profile tcp tcp-lan-optimized { slow start disable bandwidth delay disable nagle disable ack on push enable proxy buffer low 98304 proxy buffer high 131072 send buffer 65535 recv window 65535 }
profile tcp tcp-wan-optimized { defaults from tcp selective acks enable nagle enable proxy buffer low 131072 proxy buffer high 131072 send buffer 65535 recv window 65535 }
Hereby iam adding the complete profile details. please have a look and let me know the how to resolve the issue.
- Bhanu_9561
Create a new tcp profile and set the idle timeout to a value greater than 300. This depends on how long a report takes to be load. If the report takes 10 - 15 minutes to load, you can set the timeout to 900 seconds and see if that helps.
Also did you get a chance to capture traffic and see if the F5 is sending RST packets? This will confirm that the idle timeout has been reached and the connection is being torn by the BIG-IP.
- sinu_121261
thanks i am able to see RST packets after 300 sec. thanks your answer helped me a lot
