Hi,
My esxi 6.0 is running inside a vagrant vmware virtual machine and I can't ping the ip of the vcenter server applicance virtual machine from the host machine or access the web client from the host machine. I assume I am supposed to be able the appliance mui on https://172.16.139.135:5480/ after I get pass the network connection issue.
The VCSA was already installed on the vagrant esxi VM with a static ip of 172.16.139.135 so I setup vagrant to create the a private network with the interface:
vagrant created private network with the interface:
vmnet3 Link encap:Ethernet HWaddr 00:50:56:c0:00:03
inet addr:172.16.139.1 Bcast:172.16.139.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:322076 errors:0 dropped:12 overruns:0 frame:0
TX packets:172374 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
The IP address of vcenter server 6 VM is static
172.16.139.135
Gate set to
172.16.139.1
The VM Network details:
VLAN ID: 0
Virtual Machines (1)
vCenter Server 6
MAC Address 00:0c:29:3e:1c:c6
The Management Network details
VLAN ID: 0
VMkernel ports (1)
vmk0: 172.16.139.2
I can ping 172.16.139.2 from my host and ping the vcsa ip 172.16.139.135 from the esxi guest ( 172.16.139.2), but I can't ping the vsca VM from the host. I done the following checks and am out of ideas:
- Check promiscuous mode vmware workstation that is running the esxi vm. All /dev/vmnet* interfaces have g+x added and group owner set to my user. Though I'm not sure besides that.
- Have Allow promiscuous mode set to Yes for the VM Network port group that VCSA is running on.
- Using tcpdump I can see that no traffic except ARP requests are getting from the host to the esxi guess. Using esxcli network firewall I've set it to:
Default Action: PASS
Enabled: false
Loaded: false
Being a noob I'm stumped after a day and am out of ideas. Any pointers would be appreciated.
Please review KB Troubleshooting virtual machine network connection issues (1003893) that may shed more light on this issue. https://kb.vmware.com/s/article/1003893