Forum Discussion
sosabsd_111766
Nimbostratus
May 18, 2010[RST, ACK] from F5
client jBOSS VIRTUAL Server IP F5
No. Time Source Destination Protocol Info
1 0.000000 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY TCP 60093 > 9181 [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
2 0.000006 YYY.YYY.YYY.YYY XXX.XXX.XXX.XXX TCP 9181 > 60093 [SYN, ACK] Seq=0 Ack=1 Win=4380 Len=0 MSS=1460 WS=0
3 0.000294 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY TCP 60093 > 9181 [ACK] Seq=1 Ack=1 Win=49640 Len=0
4 0.000734 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY TCP 60093 > 9181 [PSH, ACK] Seq=1 Ack=1 Win=49640 Len=1263
5 0.100609 YYY.YYY.YYY.YYY XXX.XXX.XXX.XXX TCP 9181 > 60093 [ACK] Seq=1 Ack=1264 Win=5643 Len=0
6 2.236408 YYY.YYY.YYY.YYY XXX.XXX.XXX.XXX TCP 9181 > 60093 [PSH, ACK] Seq=1 Ack=1264 Win=5643 Len=645
7 2.236637 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY TCP 60093 > 9181 [ACK] Seq=1264 Ack=646 Win=49640 Len=0
8 2.236842 YYY.YYY.YYY.YYY XXX.XXX.XXX.XXX TCP 9181 > 60093 [FIN, ACK] Seq=646 Ack=1264 Win=5643 Len=0
9 2.237078 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY TCP 60093 > 9181 [ACK] Seq=1264 Ack=647 Win=49640 Len=0
10 11.139761 YYY.YYY.YYY.YYY XXX.XXX.XXX.XXX TCP 9181 > 60093 [RST, ACK] Seq=647 Ack=1264 Win=5643 Len=0
on the client (XXX) we are getting connection rest in application logs, i need to know why there is RST ACK (packet10) , and who is the faulty Node YYY( F5) or XXX( client).
BR
sosa
- hoolio
Cirrostratus
It would help to see both the client to VIP and LTM to pool member communication. It looks like the VIP (or more likely the pool member) FINs the connection and the client ACKs the FIN, but does not send its own FIN as part of the four way close. As a result, LTM (or the pool member) RSTs the connection after the FIN WAIT timeout expires. - sosabsd_111766
Nimbostratus
i try to get all the flow of traffic or request start from Client (X) to LB VS (Y) then Y to Y-pool and from Y-Pool to Another VS (Z) and from VS-Z Snat to VS-Z pool - rm_77927
Nimbostratus
I'd blame the client here. The BIG-IP has long-since closed its connection to the server, and has initiated a 4-way close to the client. The client has not responded by closing back to the BIG-IP, so the connection will at this point be in FIN-WAIT-2 on the BIG-IP and CLOSE-WAIT on the client. BIG-IP waits almost 9 seconds before sending a RST to tear down the connection, which will release connection resources on both the BIG-IP as well as the client. - tell_316027
Altostratus
when f5 sends a FIN for closing socket , it jumps Fin_wait_1、Fin_wait_2 and Time_wait, directly enters into Closed.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects