I start the server and ports are working, port 4 is not. Have a nice day! This series is designed as a compromise between high performance devices Crucial m4 and slow by today’s range hard drives. OK, finally we had to swap out the 10 core processors for the 8 core variants, and this solved this issue. The driver and firmware versions are exactly the same as the server that currently works.
|Date Added:||16 May 2016|
|File Size:||8.32 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
OTN – HCL: Hewlett-Packard HP Ethernet 1Gb 4-port i-SPI Adapter
We have shown them numerous tests, which point to it being a problem with their driver. Any other third-party products, brands or trademarks listed above are the sole property of their respective owner. Andrew France – http: Silent, Gaming and OC. I can even determine which NIC will fail.
Hi, Thanks for sharing your experience! Thanks for your contribution to Windows Server Forum! Tuesday, April 16, 1: However for testing I have now patched in the problematic server directly into the same ports the working server was using.
By continuing to browse this site, you adaptef to this use.
These servers are to take ethernett our current Hyper-V production cluster, and will bridge two sites, so it’s vital that these NICs are stable. The HP Hardware team could not repro the issue in their labs, however they were using the 8 core processors as these are the only ones that are certified for Server HP software and our Microsoft support team are concerned that this is looking like it will be passed to them, without fully being tested, and they’ll end having to sift through adapterr of log files only to determine that is indeed a driver issue, in which case it will be passed back to HP Hardware Looking through the event log we’ve discovered some errors possibly relating to the NIC drivers.
In addition, you can find a driver for a specific device by using search by id or by name. However, they are unwilling to do a lab test to try and repro the problem.
Please also 33i1 the NIC not 44 has mysteriously switched to NIC 4, after simply disabling and enabling ports to test.
Crucial officially introduced a series of SSD-drives v4. Then I’d finish the patching. We can now see both servers clearly display the gp, and is easily replicated. After some further testing this morning the NICs are once again losing connectivity, so back to the drawing board I guess. CPU power supply subsystem involves 8 phases; this is quite enough for a full-scale overclocking. Wednesday, April 17, 8: I disable portsbeing mindful not to disable the port I’m currently RDPing on got tired of sitting in a cold server room!
So in the end once I’d got everything patched in and added my virtual switches, there probably wouldn’t been a problem anyway. This behavior is also not restricted to just the on-board NICs, I have tested across the on-board NICs and the 4-port cards, and every time the fourth fails.
Enabled Ethernet adapter Port 3: But all in good time.
We know that when adding the Hyper-V the hyper ethwrnet has to bind to at least one adapter to lay down the virtual switch adapter. No affiliation or endorsement is intended or implied.
Wednesday, April 17, 1: I’m going to describe the issue as best as I can, but it’s extremely odd to say the least To add to the strangeness, if I create a virtual switch using the NIC that doesn’t work I can then zdapter out of that.
Currently HP Hardware are looking at this extremely slowly, and erring towards it being an OS issue not hardware.
HP Ethernet 1Gb 4-port 331i Adapter, list of drivers
One thing the on-board NICs and cards share is they use the same driver. Drivers may also be available for free directly from manufacturers’ websites.
Not for any vm access that’s what the other 8 ports are for.