Did you try disabling port security on the switch?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kurt Buff Sent: Friday, April 4, 2014 9:11 AM To: [email protected] Subject: Re: [NTSysADM] No communication between VMs on an ESXi host Update: I've tried several configuration changes with no success: o- The trunk on the HP switch was tagged to the VLAN. I changed the port group configurations to reside in VLAN 0, and then set the trunk on the switched to untagged in the VLAN. This has made no difference - the VMs still cannot ping each other o- I destroyed the trunk, and then untagged the individual switch ports in the vlan. Also no go. In both cases, the VMs can talk to the rest of the environment (and vice versa) but not to each other. Kurt On Thu, Apr 3, 2014 at 5:20 PM, Dave Hardyman <[email protected]> wrote: > Remove the trunking on the switch ports that your uplinks are connected to. > > > ________________________________________ > From: [email protected] [[email protected]] > On Behalf Of Kurt Buff [[email protected]] > Sent: Thursday, April 03, 2014 6:44 PM > To: [email protected] > Subject: Re: [NTSysADM] No communication between VMs on an ESXi host > > They're trunked... > > Kurt > > On Thu, Apr 3, 2014 at 4:16 PM, Sean Martin <[email protected]> wrote: >> If you're uplinks aren't trunked, don't specify the VLAN ID within >> the port group settings. Try leaving the VLAN type set to none. >> >> >> On Thu, Apr 3, 2014 at 12:39 PM, Kurt Buff <[email protected]> wrote: >>> >>> All, >>> >>> My search-fu is failing, so I turn to you for help... >>> >>> I have a small ESXi 5.5 host, about to go into production. >>> >>> The three VMs (2008R2 for all of them, a DC, Exchange 2010 and a >>> PRTG >>> box) on it can communicate with machines not on the ESXi host - >>> ping, RDP, etc. - and vice versa. No problems. >>> >>> However, the three VMs on this host cannot talk with each other. No >>> ping, no RDP. When pinging from one of the VMs to another, I get a >>> mix of unreachables from the VMs own address and straight timeouts. >>> >>> There is only one vSwitch, which has two NICs bound to it, and the >>> vswitch is set up to route based on IP hash. The physical switch to >>> which they are connect (and this shouldn't matter, but...) is an HP >>> 2510G-48, and the ports for the host are in a simple trunk - no LACP. >>> >>> I've turned off the Domain profile of the firewall on one of the >>> machine, which seems to make no difference. >>> >>> I've examined the VMware host security settings to no avail. I've >>> turned off the Windows firewall. >>> >>> I've got 3 ESXi hosts in a vSphere Standard cluster that doesn't >>> have this problem. >>> >>> Kurt >>> >>> >> >
