[url=http://meincmagazine.com/civis/viewtopic.php?p=24353259#p24353259:35j17d90 said:
Matt Wallis[/url]":35j17d90]
[url=http://meincmagazine.com/civis/viewtopic.php?p=24352289#p24352289:35j17d90 said:
w00key[/url]":35j17d90]Realtek was always kinda horrible. Unexplainable problem somtimes just vanishes when you switch to an Intel card, or when you upgrade, downgrade drivers and fiddle with options until it goes away. Nowadays I just insist on either installing an Intel® 82574L based card (€25) or having it onboard (Supermicro seems to like them).
Yeah, I keep a couple of Intel cards and even an old 3COM card floating around for fixing issues with computers running Realtek cards. The cards are cheap enough. I remember having a lot of trouble with early Broadcom chips as well, although they seem to have cleaned up their act.
Yeah, the drivers were horrible also. Heck, even Marvell has more or less come around.
Realtek seems to finally have cleaned up its act.
I'm just waiting for them to drop a bomb on other network vendors by dishing out a $20 10gb NIC
----
In other news, want to slow down your Exchange 2010 DAG and have random failures of replication and even storage presentation within the VM?
Easy, instead of doublechecking the NIC MAC addresses, cleverly barge on ahead assuming that all 4 of the VMs are properly configured instead of say...2 of them

And those two misconfigured VMs (just wrong IPs) have similar but opposite failings.
I had a VERY hard time believing that MSCS was this crappy, so I knew it had to be a misconfiguration somewhere. Blam.
PEBCAK. I was in a rush to get it done (political pressure) and mistakes are the result.
Working good now.
In other words, when you're sure it's not PEBCAK, it's probably PEBCAK
EDIT: And, yup, that cleared up the performance issue I was seeing in the cluster too. Nice.