srsns's Posts

Switch configurations are extremely simple.  The interface is trunked with VLAN 363 tagged on the interface and included in spanning-tree on both ports. Again, the guest VMs can communicated with every other IP on the same VLAN except guests that reside on the other host.  This is true for both hosts. Regarding promiscuous mode, this would allow the NIC to receive and process packets destined to IP addresses that don't reside on the local host.  How does that apply here?  When the ARP entry is manually configured on each guest VM, then communication between the VMs functions as expected.

@a_p_  Thanks for the reply.  To clarify, guest VM's can communicate with other guest VMs on the same host.  They can also communicate with any other IP on the 363 VLAN except guest VM's on the second ESXi host in question.

To add some additional clarification to bwg1234's comments: Guest VMs on both hosts can communicate to everything else on VLAN 363, including guest VMs on the third, unrelated ESXi host. ARP entries for guest VMs on the other host are NOT populated in the ARP table for the local guest VM. If you configure static ARP entries on the guest VM on each host pointing to the guest VM on the other host, then the VMs start communicating with each other. This implies several things: The trunking configuration, VLAN configuration, and IP addressing are all configured properly. The problem appears to be directly related to broadcast traffic, but not all broadcast traffic. ONLY broadcast traffic between guest VM's on these two hosts seems to be impacted. Is there any type of identifier or configuration that could be causing a conflict for broadcast traffic between VMs on these two independent hosts? Note: I'm the network guy.  Any VMware specific information will come from bwg1234 Thanks, Blake