Forum Discussion
Unable to access server Pool via Virtual Server IP
I was also suspecting asymmetric routing issue here. This happens when Web server gateway is not set to F5 and SNAT is disabled.
So was asking you to enable SNAT. I also missed to add one line in my earlier response that either enable SNAT or set gateway of webserver to F5.
In your earlier configuration, VS was sending traffic to backend webserver. But while sending response to that request, webserver was sending it to it's gateway which was not F5. So this was causing asymmetric routing issue and you were not able to browse webpage.
As said, normally such issues can be fixed by enabling SNAT or setting web server gateway to F5. And u already fixed your issue using 2nd option.
With SNAT enabled state, while sending client's request to backend pool members, F5 translates client IP address with its self IP address (for auto map). So webserver will receive request coming from F5 IP itself. So response coming from webserver comes through F5 and request gets completed.
This is how SNAT works.
I hope, you get some clarity about SNAT now.
Stay Safe, Stay Healthy!
Mayur
Yes, now i get more clarity on the SNAT concept. To be very honest I was also expecting that this could be related to gateway but as I was able to ping and telnet so I did not change it and prefer to ask this question from community members. Anyway thanks alot bro for such a useful explanation.
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