Odd Connection resets returned by

Question

Hello,&nbsp;
 &nbsp;
We have followed the design guide to deploy exchange behind our edge gateways and ltms.&nbsp;
Couple of facts about our environment&nbsp;
    LTMS 3600s running BIG-IP 11.1.0 Build 2027.0 Hotfix HF2&nbsp;
    Edge Gateways 1600s running BIG-IP 11.2.0 Build 2713.0 Hotfix HF3&nbsp;
    Nothing is Natted(CAS nodes see real ips)&nbsp;
It is deployed exactly as specified by the design guide.&nbsp;
 &nbsp;
Basically what is happening at random.  When a user logs in via the Edge gateway to owa, randomly the ltm will return a rst.  Upon refreshing the browser traffic flows as normal.&nbsp;
 &nbsp;
I have confirmed that the reset is being returned from the ltm, as I followed the traffic back doing packet captures.  Comparing the packet captures from a regular request and a request that recieves the reset, they appear to exactly the same request.&nbsp;
 &nbsp;
Is there anything else that I should look at?  I asked here, because I dont necessarily believe it is directly related to the Exchange iApp or Design guide,  just wondering what else could cause resets to be randomly returned.&nbsp;
 &nbsp;
I know this post lacks a lot of information, I just wasnt sure what information to provide, or the type of response I would get.&nbsp;
         &nbsp;
 &nbsp;
 &nbsp;

nitass · Answer

have you tried to log reset cause? 
&nbsp;  
&nbsp; sol13223: Configuring the BIG-IP system to log TCP RST packets 
&nbsp; http://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html

terrence · Answer

Thank you nitass, that solution was very helpful, however the messages that I recieved were less than insightful. 
&nbsp;  
&nbsp; The solution to log the packets unfortunately didnt work as it was quickly throttled by syslog. 
&nbsp;  
&nbsp; I added the reason to the pkt, and the reset cause for the traffic in question was  
&nbsp; "Reset cause: BIG-IP: Unknown reason" 
&nbsp;  
&nbsp; Is there known scenerios that I might reference as to why the ltm would return a reset with an unknown reason? 
&nbsp;  &nbsp;

nitass · Answer

are you using match across setting in persistence profile? if so, can you open a support case to verify? 
&nbsp;  
&nbsp; ID385333 - (377421-1) Match-across-* persistence across TMMs requests record, then fails to match

nitass · Answer

this is askf5 sol. 
&nbsp;  
&nbsp; sol14061: Persistence may fail when a persistence profile is configured with Match Across Virtual Servers/Pools/Services 
&nbsp; http://support.f5.com/kb/en-us/solutions/public/14000/000/sol14061.html

terrence · Answer

Thank you.  I think you might have hit the nail on the head with this one.   
&nbsp;  
&nbsp; We are using the aformentioned persistence, as it is extensively used in the Exchange iApp as mentioned. 
&nbsp;  
&nbsp; I am kind of thinking that I wont open a ticket, as they will just tell me to upgrade, which I am okay with doing anyways.  If the problem persists after an upgrade, I will then open a ticket. 
&nbsp;  &nbsp;

Forum Discussion

Odd Connection resets returned by

7 Replies

Recent Discussions

Client certificate Authentication - open multiple tabs

google autenticator broken barcode

Chrome V 124+ on MacOS - Virtual Server Access Issue

vulnerabilities (CVE-2020-36363), CVE-2016-0736,CVE-2019-6593-FOR VERSION BIGIP LTM-16.1.4

Port Group on F5OS network setting

Related Content

After applied ASM Policy to Virtual Server, connections will reset with Internal error in log

The return of DevCentral CodeShare.

BIGIP resets connecion

how do I detect the rst returned by the server?

F5 Connection Mirroring question