Forum Discussion
Hi,
Try to reset rst-cause stats -
tmsh reset-stats net rst-cause
.
The run
watch -n 1 tmsh show net rst-cause
Then try to connect and see which counter was increased - based on that it will be easier to find out why F5 is resetting connection.
For sure ARP is working for you as SYN is delivered to F5 and there is RST reply from F5.
I am suspecting that:
profiles { /Common/Fuel_Career { context clientside }
means that you have clientssl profile attached to VS, or I am wrong here? If so when you try to telnet, connection will be rejected as well but after 3WHS.
Seems like some Packet Filter or AFM rule is responsible.
If first then in rst-cause you will see increase in Packet filter (reject) counter.
This is likely because connection initiated from F5 cli is not rejected by Packet Filter.
Piotr