Intel R2208GZ4GC: Management Features And Serviceability
Intel's server management solution is also based on the MegaRAC product, so many of these features will look fairly familiar from the previous two machines. Intel does give the interface some attention, though.
One great feature is a check box to boot to the firmware. If you've used MegaRAC in the past, then you know that the Java-based KVM does have a bit of latency associated with it. If you need to get into a remote motherboard's BIOS, checking that box makes that operation a lot easier than trying to time an F2 or Del keystroke.
Intel also gives you access to power statistics, shedding some light on minimum, current, maximum, and average consumption. What you see in the shot above only reflects our power use during setup, not during the benchmarks. We'll give you those numbers shortly.
Another feature called Node Manager that facilitates management of each machine in the context of a complete rack. You can set a power budget that limits consumption, allowing a number of systems to operate concurrently without exceeding a data center's limits.
One notable feature that the Intel Management WebGUI does not include is the ability to reset the baseboard management controller (BMC) from the Web interface. Though this doesn't sound like a show-stopper to anyone without experience using MegaRAC products, it's a problem if you get a Video Socket Error, where the Java KVM cannot open and refresh video. In a remote data center, if the BMC errors out, you could end up needing hands on-site to perform a cold reboot. Intel should be able to address this, and it is something that every MegaRAC-based solution needs. I encountered this exact situation during a reboot for a BIOS setting change with the Intel platform, and I see this error from time to time during my normal work on ServeTheHome with boards from various vendors using the MegaRAC solution. And, if you search online, you'll see the problem isn't uncommon. The easiest way to fix it is rebooting the BMC.
Intel also offers a neat feature called the Virtual Front Panel, which shows the enclosure's front LEDs. It is an interesting feature that comes in useful if you want simple diagnostic information from a remote location.
With that said, Intel does provide much more complete sensor information in the IPMI interface.
Intel's KVM-over-IP feature, seen in the shot above, is similar to the implementations from Tyan and Supermicro.
I agree. Just reduce it a little bit but don't make it too hard to see
As an AMD fan, I wish we could. But while Magny-Cours was competitive with the last gen Xeons, AMD doesn't really have anything that stacks up against the E5. In pretty much every workload, E5 dominates the 62xx or the 61xx series by 30-50%. The E5 is even price competitive at this point.
We'll just have to see how Piledriver does.
Having said that I would suggest you include expected PPD for the given TPF since that is what folders look at when deciding on hardware. Or you could just devote 48 hours from each machine to generate actual results for F@H and donate those points to your F@H team (yes Tom's has a team and visibility is our biggest problem).