BigIP ESXi 14.1.0.6 version routing problem. Probably asymmetric routing ?

And yes I can ping 8.8.8.8 . The Vm can ping outside my local network.

And what output does the command 'ip r' shows?

I read in other posts that maybe SNAT has to do something but I only downloaded, installed and set up a management address. https://devcentral.f5.com/s/question/0D51T00006i7fraSAA/cant-access-virtual-server-ip-from-browser-however-i-can-ping-and-telnet-on-port-80 I found a couple of days ago this post that kinda has the same problem as me but he can at least telnet to it, according to him, but he stopped replying after a while.

Everything seems to be okay. The curl is working and you only have one default route. And like you mentioned SNAT couldn't be an issue, since this is pure management (no TMM).

What output does the command 'tmsh sys service tomcat' shows? Also try reading /var/log/tomcat/catalina.out to see if errors occur? Try restarting tomcat: 'restart sys service tomcat'.

After the restart command it seems like its doing something because it takes some seconds but I dont know whats up with the unexpected argument error. This whole situation doesn't make a lot of sense. Also output with "WARNING" which to be honest I am searching now what it may mean but again it seems weird that something this basic has to go through so much troubleshooting. Could it be my version of windows ? I recall seeing an older,way older I think tho, post with a bug with certain windows versions. Could it be that on the VM network settings it uses my on board nic ? Does it have to use another one or a virtual one ? Is there a possibility that although installed it might still have incompatibility issues with the version of vmware ? In theory there are endless possible problems but as I said I find it extremely unlikely for such a basic setup.

Also no it doesn't seem to work even after restart. It still refuses to connect.

Is the httpd process running on port 443?

# lsof -i -n | grep https

httpd   4578   root  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   11089  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   11452  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   11472  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   11854  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   12345  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   12365  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   16134  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

httpd   16178  apache  5u IPv6  34593   0t0 TCP *:https (LISTEN)

#

What happens if you do a curl to the mgmt address?

# curl -k -v https://192.168.1.177

Is the configuration of the BIG-IP fully loaded?

# tmsh show sys mcp-state

--------------------------------------------------------

Sys::mcpd State:

--------------------------------------------------------

Running Phase          running

Last Configuration Load Status full-config-load-succeed

End Platform ID Received    true

#

If not, what part of the configuration gives problems?

# tmsh load sys config verify

Yeah everything is fine. I was using 192.168.1.177 instead of actually writing https://192.168.1.177. Sorry for wasting your time. At least I learned how to troubleshoot general connectivity thanks to this question. Again thank you very much.

Good to hear it's working now 🙂