Network Setup
Router
IP: 192.168.1.1
Subnet Mask: 255.255.255.0
Serves as DHCP server for range: 192.168.1.2 - 192.168.1.254
Hyper-V Host (Windows 2012R2)
Connected directly to the Router with a fixed IP address:
IP: 192.168.1.98
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
The below two VM's are connected using the same Hyper-V Virtual Switch (bridged)
Windows 2012R2 VM (running on Hyper-V Host)
Virtual NIC fixed IP
IP: 192.168.1.200
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
ESXi 5.5 VM (running on Hyper-V Host)
Legacy Virtual NIC with DHCP IP
IP: 192.168.1.249
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
Schematic View
// WINDOWS 2012R2 VM
ROUTER <===> HYPERV-HOST <===>
\\ ESXi 5.5 VM
Issue
The Hyper-V Host does ping the Router and the Windows 2012R2 VM
The Hyper-V host cannot ping the ESXi 5.5 VM
The Windows 2012R2 VM does ping the Router and the Hyper-V Host
The Windows 2012R2 VM cannot ping the ESXi 5.5 VM
The ESXi 5.5 VM does ping the Router
The ESXi 5.5 VM cannot ping the Hyper-V Host and the Windows 2012R2 VM.
It makes no sense to me why the 2012 VM can ping both the host and the router and the ESXi VM only the router.
Does anyone know a solution to this issue?, as I am clueless.
EDIT 01-dec-2014 13:50 I already tried the things described in https://communities.vmware.com/message/2441159#2441159 , but not the solution for my issue.
EDIT 01-dec-2014 22:00
HyperV Host has the firewall disabled for all interfaces (i know, not best practice, but its a lab environement )
There is no duplicate mac address.
Unloaded the firewall and enabled promiscuous mode using the ESXi Shell:
> esxcli network firewall unload
> esxcli network vswitch standard policy security set --allow-promiscuous y -v vSwitch0
Both commands executed succesfully, but did not solve the "not pinging" issue.
The HyperV does have an ARP cache entry for the MAC Address of the ESXi VM, so it does recognise it at that level
.98 is the HyperV Host, .249 is the ESXi VM.
========= BEGIN ARP RESULT ==========
PS C:\Users\Administrator> arp -a 192.168.1.249
Interface: 192.168.1.98 --- 0x11
Internet Address Physical Address Type
192.168.1.249 00-15-5d-01-64-f1 dynamic
========= END ARP RESULT ==========
========= BEGIN PING RESULT =========
PS C:\Users\Administrator> ping 192.168.1.249
Pinging 192.168.1.249 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.249:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
========= END PING RESULT =========
Just to make sure, I added the follwing line in the XML file of the ESXi VM (added line is in bold text)
<global_settings>
<allow_promiscuous_mode type="string">TRUE</allow_promiscuous_mode>
<devices>
Message was edited by: bakkerb
Seems like this is more related to Hyper-V than ESXi, but what if you enable MAC Spoofing for the ESXi VM ?
Just run: Set-VMNetworkAdapter –VMName MyVM –MacAddressSpoofing On
Hi Richardson,
Thanks for your kind reply to my post. As mentioned in my link to another post in my post (maybe you overlooked that), I have already tried enabling MAC Spoofing, but that did not solve the issue. Either with or without MAC Spoofing, the ARP entry for the ESXi VM is dynamically discovered by the Hyper-V host.
Not sure why you think it is related to the Hyper-V host, because the Hyper-V host is able to ping and access the Windows Server 2012 VM. Also the 2012 VM is able to ping and access the Hyper-V host and router.
In my opinion, when I look at this situation, the problem lies somewhere with the ESXi VM, although I am clueless what is causing this behavior. Maybe you are able to share your thoughts on why you think it is related to the Hyper-V host and/or have any other thoughts?
Kind regards,
Bastiaan Bakker
Hello,
i think i have the tip, that might solve issue. I also think that the problem lies on ESXi VM.
Maybe you need to set "port dubbling" (i don't now is that correct translation?). Simply put, this feature copy the input and output packets and sent to other VM. Try to set the source option.
You can also try to check the last feature: "allow this network interface to join the group of interfaces in guest OS."
Sorry for my translation (from polish to english), but do my best.
I attach the screen-shot of my settings. Unfortunately, the OS language is polish, but i have labeled and translated the key options.
I also cannot check correctness of my tip, because i have no longer use ESXI, but i have set the same network settings on another machine. So if i enable ESXI it may by result with IP conflicts. This is production environment. So i cannot afford that.
Best regards
obi
PS: bakkerb, i cannot send any PM to you, because i don't have min. 20 points. I hope you will read this. Please let me know, is the issue solved If you have any further questions please ask them by PM and i will answer here.