Forum Discussion
how do I detect the rst returned by the server?
- Oct 24, 2023
小白 As jaikumar_f5 recommended you should be able to use LB_FAILED in conjunction with HTTP::redirect in this event and send the user to a URL stating the reset was caused by the pool member being down. Other than that I believe your only other option is to increase logging and log resets from pool members. The issue here is the F5 automatically forwards the reset received from the server to the client if configured this way. Any action take will not be based on the reset the pool member sends but the action that occurs the next time the client attempts to connect to the pool member that it has a persisted connection to. This seems like a whole lot of work just to know where you are receiving a reset from if you aren't experiencing an issue related to this.
TCP RST (Reset) from a server is typically caused by an invalid or unexpected packet received from a client. It is most commonly seen when a client attempts to communicate on a port that the server has no application listening on, or when a client attempts to initiate a TCP connection with a server while one is already established.
I know, but instead of analyzing the cause of rst, I need to listen to the rst returned by the server through irules and then return the page I defined to the client。
Recent Discussions
Related Content
* 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