Hrmmm... Well we have a 4 port Broadcom NC382i Gigabit adapter, but this is VMware land so as far as windows is concerned they are intel e1000s, however we have tried the vmxnet3 adapter type as well.
-Robb -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: Thursday, June 11, 2015 10:31 AM To: [email protected] Subject: Re: [NTSysADM] VMware and networking issues In the HyperV world, we have this thing called evil Broadcom nics. In order to use them and HyperV we have to sacrifice interns to the gods, and then disable rss/toe and the new thing with 2012 and later - disable VMQ. And you have to do this not in the gui but in command line to make it stick. What brand is your nic card and is there anything similar in the vmware world where certain nic cards are just horrific when it comes to behaving? MS wants feedback on patching: http://tinyurl.com/patchingsurvey On 6/11/2015 10:19 AM, Robb Whiting wrote: > > Seems like a common problem… anyone have a definitive fix? Is it a > virtual hardware thing you think then? > > I’ve never seen it happen in Linux. Except maybe CentOS but that’s > more of a picky ARP cache thing. > > -Robb > > *From:*[email protected] > [mailto:[email protected]] *On Behalf Of *David McSpadden > *Sent:* Thursday, June 11, 2015 10:16 AM > *To:* [email protected] > *Subject:* RE: [NTSysADM] > > It happens on all OS’s for me and it is random. > > I can reboot a box 6 times and it comes up. > > Then at 3:00 am in the morning it reboots and the nic shows the > 169.x.x.x address. > > Disable and enable the nic and everything comes right back up. > > We are using the VMX or E1000 drivers and still get the same random > results. > > *From:*[email protected] > <mailto:[email protected]> > [mailto:[email protected]] *On Behalf Of *Todd Lemmiksoo > *Sent:* Thursday, June 11, 2015 1:13 PM > *To:* [email protected] > <mailto:[email protected]> > *Subject:* Re: [NTSysADM] > > We the same problem with our 2008 servers. There is a MS fix/patch > that sometimes fixes the nic. Else we just disable and reable the nic. > We use the vmx3net nic and vmtools are not always up-to-date. It is > very hard for us to get down time just to update vmtools. > > Todd Lemmiksoo > > On Jun 11, 2015 1:00 PM, "Jack Kramer" <[email protected] > <mailto:[email protected]>> wrote: > > What vNICs are you using? (E10000 or vmxnet3?) Tools up to date? > vSwitch settings? (Disabling MAC changes, promiscuous mode, etc?) > > On Jun 11, 2015, at 12:51 PM, Robb Whiting <[email protected] > <mailto:[email protected]>> wrote: > > Hello Everyone, > > I have an annoying problem that’s been vexing us for months now. > > All our servers are virtualized with static IPs running on VMware > hypervisors. > > The servers that have connections to more than 1 ip sometimes > drop their connection. > > Other machines connected to the same network don’t lose their > connection so I don’t think it’s the link between the hypervisor > and the switch. It appears to be a windows problem. > > Anyone else have servers running Windows 2k12 R2 that are > connected to multiple networks that somehow lose connection > randomly from time to time. > > If we disable and reenable the NIC then they come back up but > they really shouldn’t go down at all. > > Ideas? > > -Robb > > 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. >
