Among my 10 slaves, I have 2 of them that won’t wake on lan. I tried everything: lan card setup and bios setup. Are there any other way to startup a machine when wake on lan does not work? I see in machine startup that we can enter a command instead of using WOL. Which command can we enter there?
One of the machine that won’t wake up is a mac with windows 7 installed with bootcamp. The other one is a regular Supermicro server board. All my other machines are almost all supermicro server and they work well with WOL.
For sure it make me do some exercice cause I have to walk to get them started for every render (it’s called walk on lan).
Hi,
WoL support is dependent on the motherboard supporting it, together with ‘flashing’ the latest BIOS version onto the motherboard, has been known to resolve the odd old motherboard/BIOS version. However as it’s hardware dependent, if the motherboard simply doesn’t have support for WoL, then it’s game over. If your using a separate NIC to the on-board NIC on the motherboard, it’s worth checking that it to has support, but it sounds like this is something you have already covered.
An alternative to our built-in WoL is to execute a command to ANY hardware device which could support some kind of remote ‘waking-up’ functionality. The more modern industry std of “IPMI” is provided on newer machines, such as ‘blades’ from DELL, HP, etc. A lot of SuperMicro motherboards support IPMI, but have dropped WoL as a way of saving power in their hardware design, so it’s worth going through your motherboard manual to see if IPMI is supported.
IPMI is more complicated to setup as there are various ways of doing it, so please refer to your hardware manufacturer for clarification on this one. However, here’s a snippet to at least get you going.
where {SLAVE_IP} is a variable you feed into the Python script as an argument. This is then effectively how you can make it work, by executing it via Power Management via Pulse for “Machine Startup”.
You might need to override the MAC address for your Mac computer as it might not be seeing the correct one that Deadline has on file. See here for more info: thinkboxsoftware.com/deadlin … ne_Startup
Also, make sure nothing is blocking transmission from source to destination such as firewalls, subnets/switches, etc. There are a few free WoL ‘tester’ applications available via a google search which you could use to confirm that the WoL packet is reaching your machines.
I finally updated the bios in my pc and it did the trick. Now only my mac pro with bootcamp is not waking up. I will take a look to see if the mac motherboard support IPMI.
We had to just buy a cheap Intel gigabit card to circumvent one particular motherboard that wouldn’t cooperate. Rather than spend hundreds of dollars worth of Man Hours I recommend just buying a new NIC.
Often times that is the easiest answer to a motherboard that won’t do WOL for you, but verifying with Apple on that machine supporting Wake On LAN shouldn’t take too long.
In fact my mac pro does support wake on lan. I was able just this week to make it work. I restarted inside of osx and I made sure the settings were correctly set in there too and not just in windows and I think there were already set up correctly (I thought I did it already in the past but it didn’t work) but now I don’t know why it started to work. So since a few days my mac pro just wake up like all the other computers in my farm as soon as a job is launched! No more crouching under the desk to open this mac every time!
So I can confirm mac pro with boot camp can wake on lan, but I don’t why it didn’t work in the past. Just reboot in osx and go in the network settings make sure wake on lan is enabled then restart in windows and try, if it does n’t work repeat until it does!
