Hewlett Packard Enterprise (HPE). And meet SLAs more affordably with high-performance all-flash and. Manage every stage of your server's lifecycle with easy. ASUS Broadcom NetXtreme Gigabit Ethernet Driver for Windows Server 2003 64bit. HP Gigabit Server Adapter. HP Integrated Module with Bluetooth 2.0 Wireless Technology. The drivers for HP ProLiant DL380 G5 with an OS of Windows Server 2008 R2 currently has two similarly named broadcom drivers listed: • HP Broadcom 1Gb Driver for Windows Server 2008 x64 Editions (American, International) Current Version: 17.0.0.3 (15 Jun 2015) • HP Broadcom 1Gb Multifunction Driver for Windows Server 2008 x64 Editions (American, International) Current Version: 7.8.50.0 (E) (9 Sep 2014) Are these two drivers related - is the first intended as a replacement for the second? Or are they two completely unrelated drivers that should both be installed simultaneously? Norton antivirus 2005 product key keygens and cracks in walls. The DL380 G5 uses the 'multifunction' Broadcom, so use that driver. That is the latest version (7.8.50.0 E) so you should be okay. In the future you could also look for newer drivers by going to the DL380 G6 or DL380 G7 pages. The DL380 G5 isn't being updated and won't have Server 2008 R2 or 2012 drivers at all, but in the case of the NIC, those G6/G7 servers use the same Broadcom multifunction NIC and you can find the driver there if needed. I only have one remaining G5 server in use and it comes in handy to look at newer server models as long as they use the same device I need to keep up to date (ILO 2, Broadcom multifunction, etc). The 2013.09 SPP that came out the other day has updated NIC drivers for the NC382i on my DL360 G7 servers (and many other models. It's the 'HP Broadcom 1Gb Multifunction Driver) for Win64. It's version 7.8.6.0 and it does something very strange. We're running Server 2012 with Hyper-V, and after installing this NIC driver, our virtual machines running on this box (2 different servers in fact, have the same issue) are having problems. The network connection between the virtuals and any other system are sporadic. I haven't taken the time to track it specifically to see if it's just dropping packets or what. ![]() For instance, we have a virtualized Ubuntu 13.04 server running Couchbase. Attempts to connect to the default port 8091 that Couchbase uses are useless, it just times out. But if I connect from another virtual machine on the same physical host, it's okay. It's only when it goes on the actual network that it freaks out. It may be all communications on the server, even to the host OS, but a lot of things like RDP sessions are pretty tolerant of network issues. The solution for me was rolling back to the previous drivers, version 7.4.14.0. That's all it took, and all of a sudden, all the software running on those virtual machines like Couchbase, MSSQL, IIS, etc. Started working just fine. I'm glad this was on our test environment. If I hadn't caught that before deploying to our production servers, it would have been a very bad day. Trust media center keyboard driver. It was bad enough as it is, dealing with developers and QA who couldn't do their work for most of a morning. Whew, I'm glad it's not just me then. Hopefully HP will find this thread and fix it, and other people who may run into issues might stumble on this thread. For me, since rolling back to the old driver fixed it, and nothing in the new version was important to me, I didn't think it was worth opening a ticket with HP. Also, just to cover my bases, I rolled back the NIC driver for my other Hyper-V hosts that have different network cards besides that 382i. Just in case. Also rolled back the driver for my systems that aren't running Hyper-V. I hadn't seen any issues with them in particular, but why take a chance? ![]() I don't know for sure that the issue ONLY affects virtuals. Maybe it's just easier to spot. I had installed the new driver on 2 or 3 of my production IIS servers when I noticed the Hyper-V problem, so I didn't really check back to see if those servers had been having any communications issues, but I'll just wait until HP addresses the issue before installing it on ANY systems. Glad to see its not just me. I perform an annual update of all my systems to the latest SPP, in this case to 2013.09 as the rest of you. I'm running Windows 2008 R2 with Hyper-V and also immediately noticed major problems after the update affecting network traffic on my guest VM systems (all running Windows 2008 R2). My issues were massive packet loss, particularly to/from anything outside of the Hyper-V virtual switch but most noticably affecting HTTP/HTTPS traffic. I ended up rolling back the NIC Firmware and drivers to resolve my issues (before I found this thread). I definately recommend avoiding the 7.8.6.0 broadcom drivers if you run Hyper-V though there are likely additional issues that I didn't see [yet] so I'm removing it from everything. I am having the same exact problems with a new Hyper-V Cluster on 2-DL360e gen8 servers running Server 2012 r2. They have the 4-port 331 FLR network adapters and I am using drivers from the 9-30-13 SPP.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. АрхивыКатегории |