WhereisAnt
Contributor
Contributor

Cannot WOL (Wake-On-LAN) with Intel NUC8 after Shutting Down ESXi 6.7U1

Hi,

I am aware Intel NUC isn't supported by VMware as a hardware to run on, but it does appear to be used a lot on home labs. I've come across an issue that appears to relate to e1000 network driver (according to Intel), and it involves the inability to wake the NUC machine via WOL (Wake-on-LAN) packet after it has been shutdown (via ESXi console or GUI). It works fine if you wake the machine up just after you switch the power on at the socket. But the minute you use a manual shutdown in ESXi, it will no longer wake up via WOL packet.

It has been raised here with Intel NUC:
https://forums.intel.com/s/question/0D70P000006GX2K/cannot-wol-with-intel-nuc8i7bek-after-shutting-d...

But the conclusion by Intel is that it is caused by NE1000 driver VIB used in VMWare.

Anyone else have this issue, or have any ideas how I could potentially solve this?

0 Kudos
17 Replies
fuckerlovetoomu
Contributor
Contributor

I have same problem with NUC8i3BEH. Please advice.

0 Kudos
MarcFinns
Contributor
Contributor

Today i bought a NUC8i7BEH an i have the same. So disappointing. Any news, anyone?

0 Kudos
daphnissov
Immortal
Immortal

If it's a problem with the ne1000 VIB that ships with 6.7 U1, you may try to get the ESXi650-201805217-UG patch and extract an older version of the same VIB from there and downgrade. Not sure that would work, but it's the next step to try (assuming you've already updated your BIOS to the latest published by Intel).

0 Kudos
MarcFinns
Contributor
Contributor

Thanks. I tried, but no luck. Based on your experience, is there any hope that it will be resolved at some point or shall i return the NUC..?

0 Kudos
daphnissov
Immortal
Immortal

It's unsupported hardware to begin with, so I couldn't speak to any futures (especially because it is unsupported). It would seem a shame to return it because this one piece of functionality isn't present, but I suppose that's really up to you.

0 Kudos
MarcFinns
Contributor
Contributor

Indeed, it is a nice machine. I was asking because it appears a similar issue happened with a previous generation NUC but i could not find much, so i was wondering whether it was ever resolved...

0 Kudos
daphnissov
Immortal
Immortal

Not sure. Also not sure about your use case, but consider that since they draw so little energy to begin with, one possible workaround is to just keep the thing running rather than shutting it down and attempting to wake it again.

0 Kudos
MarcFinns
Contributor
Contributor

In fact i forgot to mention the use-case. The nuc runs a number of VMs including my home firewall, so it is indeed always on.

The use-case is related to managing the UPS. The nuc shuts down when battery is low. However, if power returns before the UPS dies, the nuc (and other devices) might stay off. Therefore I have a small raspberry PI that checks. If power is available AND nuc is down, wakes it up. It has been working perfectly for years with an older nuc, and stopped when i upgraded the machine.

0 Kudos
daphnissov
Immortal
Immortal

But you say that WoL doesn't work only when a shutdown is initiated from within ESXi? If the device is hard down, does WoL from your Pi work in that case?

0 Kudos
MarcFinns
Contributor
Contributor

Sure it does work if the device is power cycled. The ESXi driver however puts the ethernet port in a state that does not respond to WOL anymore so when i shut it down nicely on UPS battery low, it is doomed. It is a recognised bug of the NE1000 driver, mentioned also on the intel web site.

0 Kudos
daphnissov
Immortal
Immortal

What you may want to do is have your automation, upon low battery, perform a graceful shutdown of your VMs, and then just let it [the ESXi host] die to avoid that state. ESXi runs entirely from memory, and as long as the VMs are down gracefully there's really not a data consistency problem. It should be fairly trivial to add that.

0 Kudos
MarcFinns
Contributor
Contributor

i see your point but you dont see mine. If power returns before the UPS dies, nothing will restarts the VM and a manual action is required. As i run my home automation and many other things on that nuc, if this happens when i am not at home i lose all that.

0 Kudos
daphnissov
Immortal
Immortal

Yes, I see your point, but I'm willing to bet there are workarounds. For example, setting a loop to check for UPS mains status, or eval on the mains status. Don't know what model of UPS you have but many of them have an ability to check for mains power. So it becomes and if/then situation. Just trying to think of other ways to help you out to bypass this WoL issue.

0 Kudos
MarcFinns
Contributor
Contributor

...and I thank you for taking the time! I am just saying that once the shutdown has started there is nothing I can do other than wake it up again, I guess (or am I missing something In your line of reasoning?)

0 Kudos
daphnissov
Immortal
Immortal

It would really depend on how you're doing the shutdown. If the USB cable from the UPS is plugged into your NUC (ESXi host), then that obviously wouldn't work. But if it's plugged into your Pi (which is your automation station), then you could run all the logic there and call out to the ESXi host to gracefully shutdown all VMs. From there, two branches of logic would apply:

  1. Power dies:  If power dies, VMs will already be down and your Pi will die. Since Pi has an open power circuit (there's no momentary power switch unless you use a 3rd-party accessory), when mains is restored the Pi comes on-line. You then run your scripts to begin checking the ESXi host. ESXi host should power up automatically (which you should be able to configure in the NUC).
  2. Power does not die: VMs will be down, but you can enter a watch loop on your Pi. After a timer expires if it's still up, begin powering up the VMs on the ESXi host.

Either of these ensures that regardless of what happens after the UPS triggers an outage, your automation functions and keeps your VMs online. This is just how I would approach it myself in case it isn't what you're doing.

0 Kudos
m_lp
Contributor
Contributor

Hello.

I have the same problem with a NUC8i7BEH model. Did anyone find a workaround on this problem?

Thank you.

0 Kudos
MarcFinns
Contributor
Contributor

No. Very, very disappointed.

0 Kudos