It's an HP switch, not Cisco. Kurt
On Thu, Apr 3, 2014 at 4:40 PM, David McSpadden <[email protected]> wrote: > Ok. > What IOS do you have on your switch? > I am on a Cisco 3580 with the latest IOS build as of June last year. > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Thursday, April 03, 2014 7:34 PM > To: [email protected] > Subject: Re: [NTSysADM] No communication between VMs on an ESXi host > > au-sw-03(config)# no gratuitous arp > Invalid input: gratuitous > > Kurt > > On Thu, Apr 3, 2014 at 4:08 PM, David McSpadden <[email protected]> wrote: >> It's a command. >> No gratuitous arp from config t. >> It is on by default. >> It helped a couple server but I still have issues. >> ESXi's knowledgebase is full of these intermittent IPstack issues that they >> are blaming on the OS and Physical switches. Kind of curious that the same >> physical switch was used in my realtime lab and never had these issues but >> now that it is backbone to the ESXi servers it is the problem.... >> Lol >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Thursday, April 03, 2014 6:58 PM >> To: [email protected] >> Subject: Re: [NTSysADM] No communication between VMs on an ESXi host >> >> I'm not finding any settings on the switch to manipulate gratuitous arp. >> >> Kurt >> >> On Thu, Apr 3, 2014 at 2:29 PM, David McSpadden <[email protected]> wrote: >>> On your switch configs did you set gratuitous arps to no? >>> Suggested by ESX support and knowledgebase. >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of John Cook >>> Sent: Thursday, April 03, 2014 5:17 PM >>> To: [email protected] >>> Subject: RE: [NTSysADM] No communication between VMs on an ESXi host >>> >>> Well we do it for our SAN traffic, no reason it wouldn't work on guests. >>> >>> John W. Cook >>> Director of Network Operations >>> Partnership For Strong Families >>> 5950 NW 1st Place >>> Gainesville, Fl 32607 >>> Office (352) 244-1610 >>> Cell (352) 215-6944 >>> >>> MCSE, MCP+I, MCTS, >>> CompTIA A+, N+, Security + >>> VSP4, VTSP4 >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Thursday, April 3, 2014 4:59 PM >>> To: [email protected] >>> Subject: Re: [NTSysADM] No communication between VMs on an ESXi host >>> >>> Which would mean multihoming the VMs, correct? I don't think that's the >>> right approach here... >>> >>> Kurt >>> >>> On Thu, Apr 3, 2014 at 1:50 PM, John Cook <[email protected]> wrote: >>>> Add another virtual switch with a private range for communication between >>>> servers? >>>> >>>> John W. Cook >>>> Director of Network Operations >>>> Partnership For Strong Families >>>> 5950 NW 1st Place >>>> Gainesville, Fl 32607 >>>> Office (352) 244-1610 >>>> Cell (352) 215-6944 >>>> >>>> MCSE, MCP+I, MCTS, >>>> CompTIA A+, N+, Security + >>>> VSP4, VTSP4 >>>> >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Kurt Buff >>>> Sent: Thursday, April 3, 2014 4:44 PM >>>> To: [email protected] >>>> Subject: Re: [NTSysADM] No communication between VMs on an ESXi host >>>> >>>> Sorry, forgot to add - only one VLAN on this switch, and the physical >>>> switch ports are tagged to this VLAN, and of course all of the VMs are on >>>> this VLAN, and are using the VMX NET 3 NIC. >>>> >>>> Kurt >>>> >>>> On Thu, Apr 3, 2014 at 1: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 >>>>> >>>>> >>>> >>>> >>>> >>>> ________________________________ >>>> >>>> CONFIDENTIALITY STATEMENT: The information transmitted, or contained or >>>> attached to or with this Notice is intended only for the person or entity >>>> to which it is addressed and may contain Protected Health Information >>>> (PHI), confidential and/or privileged material. Any review, transmission, >>>> dissemination, or other use of, and taking any action in reliance upon >>>> this information by persons or entities other than the intended recipient >>>> without the express written consent of the sender are prohibited. This >>>> information may be protected by the Health Insurance Portability and >>>> Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. >>>> Improper or unauthorized use or disclosure of this information could >>>> result in civil and/or criminal penalties. >>>> Consider the environment. Please don't print this e-mail unless you really >>>> need to. >>> >>> >>> >>> ________________________________ >>> >>> CONFIDENTIALITY STATEMENT: The information transmitted, or contained or >>> attached to or with this Notice is intended only for the person or entity >>> to which it is addressed and may contain Protected Health Information >>> (PHI), confidential and/or privileged material. Any review, transmission, >>> dissemination, or other use of, and taking any action in reliance upon this >>> information by persons or entities other than the intended recipient >>> without the express written consent of the sender are prohibited. This >>> information may be protected by the Health Insurance Portability and >>> Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. >>> Improper or unauthorized use or disclosure of this information could result >>> in civil and/or criminal penalties. >>> Consider the environment. Please don't print this e-mail unless you really >>> need to. >>> This e-mail and any files transmitted with it are property of Indiana >>> Members Credit Union, are confidential, and are intended solely for the use >>> of the individual or entity to whom this e-mail is addressed. If you are >>> not one of the named recipient(s) or otherwise have reason to believe that >>> you have received this message in error, please notify the sender and >>> delete this message immediately from your computer. Any other use, >>> retention, dissemination, forwarding, printing, or copying of this email is >>> strictly prohibited. >>> >>> Please consider the environment before printing this email. >> >> >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are not >> one of the named recipient(s) or otherwise have reason to believe that you >> have received this message in error, please notify the sender and delete >> this message immediately from your computer. Any other use, retention, >> dissemination, forwarding, printing, or copying of this email is strictly >> prohibited. >> >> Please consider the environment before printing this email. > > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited. > > Please consider the environment before printing this email.
