10-11-2011 02:13 AM
Hi,
Please look over the attached files.
I need the teardown the session manually ( clear conn )
In spite of RST packet, the session is still reaminig ESTABLISHED state to client. The other way is closed before of FIN.
Where is the problem? wrong RST, ACE bug ?
Regards,
10-12-2011 06:32 AM
Hi Karoly,
As I told you on the other thread for the same question (https://supportforums.cisco.com/message/3462070#3462070), please, open a TAC service request to have this investigated further.
Daniel
10-12-2011 07:10 AM
Karoly,
By any chance have you disabled normalization on your interfaces? The reason I ask is when I follow the tcp stream I see the 3way handshake, data, and the fin from the server and reset from client. This normally should close out the connection but after the reset I see an Ack From the .2 device. If you have disabled normalization this new Ack would build a new flow built from 100.1.1.2 to 100.1.1.7 and since the two endpoints think the connection is closed they will not try to close it out. This new connection will take 1 hour to idle out since from the ACE perspective it is just the server initiating a new connection to the server. With normalization enabled the ACE would just drop the last ack and no new connection would be built.
Hope this helps some.
Regards
Jim
10-13-2011 12:34 AM
Hi,
The ACK after RST was sent by ACE.
The normalization is enabled.
-------------------------------------------------------------------
I discussed it some CISCO guys.
it seems the main issue the RST. After zero window from client the client sent the RST with seq number ( +1 )
Is this standard or not???
Regards,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide