Yes, for this controller, the drivers are inbox only. There is no full support or PROset ANS features.
The connection issue could be related to some sort of power management either on the server port or the switch port. As a recommendation, please look at the power savings features related to the ports on both ends of the link and disable them. Some ports share IPMI management data. These disconnects may be happening during management role activities. Check if the board has IPMI, and if so, please see if it can be disabled. Hope this information is helpful, and help clear up the frequent disconnects.
Hi G. Thomas,
Thanks for the reply.
The boards in question do not support IPMI.
I did check into other power management options, and found that "CPU C3 report to OS" and "CPU C6 report to OS" were enabled.
(Just an aside: in the past, with this same board series we had encountered a case in Windows 7 where "CPU C6 report" enabled was greatly reducing the network throughput when using 9000 byte jumbo frames. Disabling "CPU C6 report" resulted in much higher data rates with jumbo frames.)
Anyway: sorry to say, disabling "CPU C3 report" and "CPU C6 report" had no effect on this problem in Windows 8.1; it still fails very frequently. I also tried disabling EIST & Turbo mode - again, no effect, it still fails.
In my effort to simplify my initial problem description, I neglected to mention some additional details:
1. These boards all have two 82574L chips.
2. Oddly, only one 82574L on each board we test fails like this in Win8.1; the other port does not fail, at least in several-hour tests.
3. And even more odd, it is not always the same 82574L among the tested boards: on some boards it is port #1, on others it is port #2. (and it is not possible the ports are physically swapped: the 8P8C jacks are soldered to the board)
4. But on a specific board, it is consistent: it is always the same port that fails in Win8.1.
I know this may sound like a hardware issue, but considering the fact that we have never reproduced a single failure in Win7 leads me back to suspecting the Win8.1 "in-box" 184.108.40.206 driver.
When enabling jumbo frames, you need to make sure everything from the beginning to the end support that larger size frame. This includes any other switch the data travels through. If anything along the path isn’t configured correctly, it may end up getting fragmented and or packet loss. This can result in poorer than expected performance and momentary disconnects. One thing to try is reduce the frame size from 9K to 4K and test. Chances are this will reduce the potential for fragmentation and may reduce disconnect episodes.
I hope this information is useful for you, Please let us know if you have more questions.
Thanks, but we don't have a problem with jumbo frames. As I said above: "Just an aside... " - which I mentioned regarding the "CPU C6 report to OS" setting. We are not using jumbo frames in the current tests of Windows 8.1.
Do you have any other suggestions for our problem with Windows 8.1?