You may call it play, but this PC and its twin were members of two nodes Win2K3 cluster (shared storage was connected through iSCSI) for more than 2 years. Though, it’s hard to tell now, was BCM...
See more...
You may call it play, but this PC and its twin were members of two nodes Win2K3 cluster (shared storage was connected through iSCSI) for more than 2 years. Though, it’s hard to tell now, was BCM5703 really stressed or not. I guess you are implying this setup used JFs for all this time... Weird. Then cluster was replaced with never nodes and I got old ones to play with ESX. Anyway, short answer is "forget about it!", right? Basically, yes: we're just following Broadcom's recommendations here (they're the chipmaker after all), but I don't really know about the specificities of the problems that may arise when using JFs. BCM5703 are old chipsets, it is unlikely we'll ever change anything about them now. Another question, would it be a problem to use another dual NIC "Intel Corporation 8254NXX Gigabit Ethernet Controller (rev 03)" as vSwitch to provide iSCSI for few guests OS (Win2K3) with Jumbo Frames enabled? For both "play" and "not-heavy loaded production"? Thank you! Maybe Joke aside, I don't know every nic's supported features, so the best thing to do here would be to try it by yourself and see how it goes: if "esxcfg-vswitch -m XXXX" succeeds then you will be good to go.