http://www.intel.co.uk/content/dam/...sheets/i210-ethernet-controller-datasheet.pdf
Key info copied below, but the formatting is mangled so best read from the PDF.
I've used WOL in the past to start individual computers remotely, but for servers I always used the IPMI (or equivalent). The magic packet was generated from a router and sent to a specific MAC address if I recall. It would work or not-work regardless of Operating System, entirely dependant on hardware support and correct setting in the BIOS. A quick read of the PDF I found suggests that support may not depend just upon the i210, but also whether the motherboard is setup to support WOL too. Note in 5.6.1 it says "..a feature that existed in earlier 10/100 Mb/s NICs"... and ..."now uses (if configured) an in-band PM_PME message.."
So, next I googled for your motherboard and found ftp://ftp.supermicro.com/CDR-X10-UP_1.13_for_Intel_X10_UP_platform/MANUALS/X10SL7-F.pdf . Searching that I found no reference to Wake on Lan, but did find one mention of APM power management as a BIOS setting, but no further detail as to if/how that works.
At this point, proto's suggestion of
ipmitool seems worth investigating, at least if you need to script startup/shutdown.
Hope that helps
5.6.1 Advanced Power Management Wake Up Advanced Power Management Wake Up or APM Wakeup (also known as Wake on LAN) is a feature that existed in earlier 10/100 Mb/s NICs. This functionality was designed to receive a broadcast or unicast packet with an explicit data pattern, and then assert a subsequent signal to wake up the system. This was accomplished by using a special signal that ran across a cable to a defined connector on the motherboard. The NIC would assert the signal for approximately 50 ms to signal a wake up. The I210 now uses (if configured) an in-band PM_PME message for this functionality. On power up, the I210 reads the APM Enable bits from the Flash Initialization Control Word 3 into the APM Enable (APME) bits of the Wakeup Control (WUC) register. These bits control enabling of APM wake up. When APM wake up is enabled, the I210 checks all incoming packets for Magic packets. See Section 5.6.3.1.4 for a definition of Magic packets. Once the I210 receives a matching Magic packet, and if the WUC.APMPME bit or the PMCSR.PME_En bits are set to 1b and the WUC.APME bit is set to 1b it: • Sets the PME_Status bit in the PMCSR register and issues a PM_PME message (in some cases, this might require asserting the PE_WAKE_N signal first to resume power and clock to the PCIe interface). • Stores the first 128 bytes of the packet in the Wake Up Packet Memory (WUPM) register. • Sets the Magic Packet Received bit in the Wake Up Status (WUS) register. • Sets the packet length in the Wake Up Packet Length (WUPL) register. The I210 maintains the first Magic packet received in the Wake Up Packet Memory (WUPM) register until the software device driver writes a 1b to the WUS.MAG bit. If the WUC.EN_APM_D0 bit is set to 1b, APM wake up is supported in all power states and only disabled if a subsequent Flash read results in the WUC.APME bit being cleared or software explicitly writes a 0b to the WUC.APME bit. If the WUC.EN_APM_D0 bit is cleared APM wake-up is supported only in the D3 or Dr power states. Notes: 1. When the WUC.APMPME bit is set a wake event is issued (PE_WAKE_N pin is asserted and a PM_PME PCIe message is issued) even if the PMCSR.PME_En bit in configuration space is cleared. To enable disabling of system Wake-up when PMCSR.PME_En is cleared, the software device driver should clear the WUC.APMPME bit after power-up or PCIe reset. 2. If APM is enabled and the I210 is programmed to issue a wake event on the PCIe, each time a Magic packet is received, a wake event is generated on the PCIe interface even if the WUS.MAG bit was set as a result of reception of a previous Magic packet. Consecutive magic packets generate consecutive Wake events.
