So you’re in the process of setting up a sweet Metal as a Service cluster and you’re taking all the second-hand hardware you can get your hands on. Lucky for you, a relatively beefy unmarked PSSC Labs server (4U) happens to make its way over to your rack.
*Or AMD Equivalent
With no wake on LAN capability obvious in the BIOS there is no way to enlist in MaaS. The BIOS refers to a Supermicro H8SGL(-F), which I took to mean H8SGL-F. Quick research shows that the -F supports Intelligent Platform Management Interface (IMPI). Flashing updated firmware for the IMPI failed with a “Send command” error. At this point it was time to open up the server and check out the motherboard. Inside is the Supermicro H8SGL. Don’t be confused by the naming convention like I was. The BIOS refers to this motherboard as the H8SGL(-F) because both models utilize the same BIOS. To be certain what motherboard you have you’ll want to examine the I/O and look for a dedicated IMPI LAN or look for the System Management Bus Header (IPMB) to the left of the internal USB (shown on page 1-4 here (PDF)). Both models have the Baseboard Management Controller necessary for IMPI.
Now that we (finally) know our target motherboard, download the most recent BIOS (.zip) from the above link and make a bootable freeDOS drive and extract the contents of the .zip on the drive. Boot into freeDOS and execute the flash.bat command.
After flashing, manually reboot the computer. When it comes back up it should greet you with a checksum error, so strike F1 to edit settings, strike F9 to load the defaults, and finally F10 to save and exit. The server never restarted and became unresponsive. Wow. The solution was to remove the graphics card and plug into the onboard VGA. After another reboot enter the settings to customize. Plugging the graphics card back in after customization did not cause any issues. Quick note: The BIOS version did not change after the update, but the look & feel is clearly different.
Once you’re back into the settings you quickly realize nothing has changed and there is still no wake on LAN option. Do not fret! Simply plug into the NIC and send some magic packets its way and the server should roar to life!
We also found out that wake on LAN does not respond after a loss of power. The recommendation is to enable resume on power failure to mitigate this.
This research was done after we had tried throwing wake on lan packets from MaaS at the onboard Intel network interface controller to no avail. Which is strange, because the documentation says the motherboard supports wake on LAN. It seems like a BIOS update was necessary to activate the feature. Wake from PCI 2.2 did not seem to work in a plug-and-play manner. We scavenged an old 10/100Mbps NIC with wake on LAN and sent it wakeup packets before and after the BIOS update. If all else fails there is a wake on LAN 3-pin header for legacy support that can be wired to a NIC with the same 3-pin header.
Obviously I _
have had some frustrations with _hate this motherboard, but in the end we have another enlisted node!