F5 LTM is keep on rst packet to pool member.

Question

Hi,&nbsp;
This is little tricky for me as I have two pools and applied conditional rule in VS.
Like if condition match's then Pool1 else Pool2.
But as soon as connection towards Pool2 breaks (or Pool member in pool2 send RST packet) then client break both connections for Pool1 and Pool2.
Rather in any pool if pool member goes down then F5 never send RST packet to client rather and continue connection to another available pool member.
Please help me out to mitigate this issue" how can I prevent rst packet towards client.&nbsp;
/Regards
Amit Grover
8527000635 &nbsp;

kai_wilke · Answer

Hi Amit,
if the real server unexpectly resets the connection, but is not yet marked as down by the health monitor, then you could try to catch this event using the LB::failed event.
when CLIENT_ACCEPTED {
    set retries 0
}

when LB_FAILED {
    if { $retries &lt; [active_members [LB::server pool]] } {
        LB::mode rr
        LB::reselect
        incr retries
    }
}

For further information on this topic I'd like to recommend the following kb articles...
https://support.f5.com/kb/en-us/solutions/public/10000/600/sol10640.html
https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10386.html
Cheers, Kai

Forum Discussion

F5 LTM is keep on rst packet to pool member.

1 Reply

Recent Discussions

BIG-IP DNS: Check Status Of Multiple Monitors Against Pool Member

Open Redirection Mitigation

F5Access | MacOS Sonoma

enable tls1.2 on management interface on F5 ltm running version 10.x

[ASM] - what is "Browser Challenge file" ?

Related Content

Decrypting BIG-IP Packet Captures without iRules

Decrypting BIG-IP Packet Captures Automatically

Packet in/out not balancing between member in pool

Automating Packet Captures on BIG-IP

F5 packet buffer