Happy new year everybody,
Got a problem with BigIP ESXi 14.1.0.6. So far all I did was download the .ova file ,install it via Vmware player ,the free edition, and run 'config' command to set the management ip. As you can see in the images below its on bridge connection using my on board nic. My problem is that although I can ping from the bigip vm to both my host windows,and other vms using same connective in same network, machine and to the outside world, tried google.com for example, while obviously being able to ping back from my host machine I seem unable to connect to the web interface in order to activate product and configure it further. The error I get on browser is 'connection refused'. Tried telnet with putty and still cant connect. Both vm and host are on same subnet /24. Host machine ip is 192.168.1.139,bigip management ip is 192.168.1.177 and default getaway is 192.168.1.254. Tried setting a static arp route following this https://support.f5.com/csp/article/K16221, so my command was create net arp myarp ip-address 192.168.1.139 mac-adress '',which mac adress I found from running ipconfig/all on my windows host. Error was that 'neighbor entry 192.168.1.139 cant be resolved'. Last thing I did was restarting Vm after I closed down skype because I recall it causing issues with port 80 and apache when both were running so I thought maybe it interferes with Vms as well. But it didn't fix the problem. Is there something else I can do ? Am I wrong about asymmetric routing ? My end goal is to build a lab with the bigip and a another ubuntu server vm I already built with some docker images inside and test it.
Thanks in advance for your help
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.
