Deadline’s Power Management not waking slaves properly

loocas | deadline,miscellaneous,software,technical | Sunday, May 29th, 2011

I recently had a problem with Deadline 5 and its (awesome) Power Management setup. The issue was that the server that was running the Pulse on wasn’t waking my machines up from their shutdown states (WOL).

The weirdest thing was that I was able to wake those machines up from any of my workstations via the Deadline Monitor app, but Pulse wasn’t able to. So, after speaking to the Thinkbox Software support (which is also top-notch and very helpful, by the way), they recommended me a few network traffic sniffing apps to monitor what is going on on the NICs.

The problem was that the NIC connected to the network was not actually sending the magic packet, so, no machines were, obviously, able to receive it. After a bit of further investigation, I found out that the WOL packet was actually being sent through the secondary NIC on the server, which wasn’t physically connected to the switch (mainly because the server also acts as a DC). So, the simplest solution seemed to disable the secondary NIC in Windows and have the primary NIC take care of the whole business.

This, however, presented a lot of trouble. By disabling the secondary adapter, you completely disable the NIC (in Windows, that is), so, with that you also disable any licenses that are bound to that particular adapter’s MAC! After that I wasn’t able to start Nuke, Mari, or even Deadline Slaves!

So, I had to dig deeper. The answer was Interface Metrics. In the Advanced tab under the IP properties, you can manually override Interface Matrics. See the link for more details, but basically, any lower value has higher priority. In my case, the secondary NIC (not physically connected to the switch), got automatically assigned a higher priority matric (a lower value), than the primary NIC. I manually overrode those and voila!, all traffic was being directed through the primary NIC.

To check what settings you’re at, use this command in the command prompt:

netsh interface ip show address

Hope this helps… :)

1 Comment »

  1. Hey, good experience, thanks for sharing ;)

    Comment by Deko — May 30, 2011 @ 12:52

RSS feed for comments on this post. TrackBack URI

Leave a comment

Powered by WordPress | Theme by Roy Tanck