Forum Discussion
er_sandy_27437
Nimbostratus
NimbostratusTCP connection resets on LTM
Hello All, I am facing a issue with F5, here's the case: We created a VIP 192.168.16.68:443 for ssl handshake on F5. there are 2 pool members. 192.168.16.100:80 & 192.168.16.25:80. The setup from F5 ...
smp_86112
Cirrostratus
CirrostratusOK, now that makes sense. So the LTM is sending a RST to the client because the Pool Member is sending a RST to the LTM. Think of what happens on both sides of the LTM.
1) Client initiates a TCP connection with the LTM on port 443 on the external side.
2) LTM makes a TCP connection with the Pool Member on port 80 on the internal side.
3) Pool Member sends a TCP RST to the LTM on the internal side.
4) LTM sends a TCP RST to the client on the external side, because the Pool Member refused a connection.
If you take a trace of both sides simultaneously and compare the timestamps closely, this is exactly what you should find.
Again, I advise you to try and make a TCP connection with your Pool Member from the LTM with telnet (telnet 80). I bet you get a TCP RST.