Forum Discussion
Jeremy_18125
Nimbostratus
NimbostratusF5 ASM AWS backend sending connection reset.
I deployed a couple of F5 WAF in AWS in HA, the backend fails to load on the browser (reset), tcpdump shows we can get to the virtual server, and the curl can reach the web server from the LTM.
...
Yann_Desmarest_
Nacreous
NacreousHi,
Did you set the snat setting to automap on the VS ?
You can log tcp reset reason in the ltm log file. Here is the link to askf5: https://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html
The tmsh command to activate logging:
modify /sys db tm.rstcause.log value enable
Jeremy_18125Nimbostratus
NimbostratusThanks, Source Address Translation is set to automap, and all monitors are green. Software version is 12.0
This looks puzzling, also the LTM log shows
RST sent from virtual server IP to browser, [0x2019dac:3657] No route to host
-------------------------------
tmsh show /net rst-cause
---------------------------------
TCP/IP Reset Cause
RST Cause: Count
---------------------------------
Flow expired (sweeper) 202
HA disconnect 4
No local listener 465
No pool member available 14
No route to host 819
No server selected 39
TCP 3WHS rejected 34
TCP RST from remote system 4
------------------------
No route to host & No pool member available could have something to do with the pool subnet being different to the internal subnet, maybe.
