ProLiant Servers - Netservers
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant N36L microserver, WOL (wake-on-lan) not working?

 
Highlighted
Occasional Visitor

Proliant N36L microserver, WOL (wake-on-lan) not working?

 

Has anyone been able to wake up the server with WOL message? 

I've checked it's enabled in the BIOS, and i can see the network card LED blinking for traffic. 

When i send multiple WOL messages the LED activity clearly increases, so the motherboard should see the message, but nothing happens. 

 

It may be due the fact i'm running OpenSolaris Nexenta and it doesn't support the motherboard's ACPI completely, so it might send it down to wrong power level at powerdown (S2 i guess) . Is there a workaround? 

 

 

 

12 REPLIES 12
Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Yes, I have tested this using a Windows-based WOL tool and it worked first time.

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Oh, yeah,  The WOL message has been sent from windows7 and also debian linux - neither wake up the N36L.

 

I do have another server with asus motherboard which does start up with the WOL message.

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Hi,

 

Did you get this working? I have one of these servers running FreeBSD (well FreeNAS) and i can't get it to power on even though the BIOS is set correctly. I have a Windows PC that i can happily power up when i want even from work, so i don't think i have done something wrong in terms of actaul WOL setup.

 

FreeBSD 7.3 seems to not have WOL support for the NIC card, but i thought that just for powering on the hardware via WOL that this would be ok.

 

Drew

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

No, I did not find a WOL-based solution for this. My understanding is that the operating system network driver is responsible for turning the WOL listening on at shutdown. openSolaris driver for N36L NIC lacks the ability, and so i guess, many other *nix family OSs. 

 

In this case, i fiddled a bit with electronics - bought a USB controlled electronic relay, which is connected directly to the power button of N36L. A second computer (which is always on) can now turn on the power via USB command.. :smileyhappy:

 

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Ahh ok i did suspect that. Nice solution, but i don't have another PC that is on lol.  I will see if i can find some better drivers for the inbuilt card.

 

Out of interest where did you get the USB relay?

 

Cheers

Drew

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

 

The relay is this one:

 

http://www.sigma-shop.com/product/7/usb-relay-controller-one-channel.html

 

simple and easy. 

 

Highlighted
Occasional Visitor

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Thanks :)
Highlighted
New Member

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

I've struggled and failed to get WOL working on Ubuntu (10.04.* LTS + Natty). Upgrading the BIOS made no odds.

 

FYI A fresh install of CentOS 6.0 and it works out of the box for me. (running etherwake, not that it should matter).

 

Very happy.

Highlighted
New Member

Re: Proliant N36L microserver, WOL (wake-on-lan) not working?

Guys, not for nothin' here but WOL is kind of dead now these days.

It's always been a pain and there are two formats and two types of magic packets.

Plus it seems with this poster there is now an OS dependency revealed...

 

I do this:

Buy this item

http://www.apc.com/products/family/?id=70

 

If that's too robust for your needs they have smaller versions for less money.

 

Then plug all of your systems into it.

 

Configure all of your server's BIOS and Desktop BIOS for "ALWAYS ON" for the "after power failure" setting.

This is something that is BIOS only and not dependant on any NIC state after shutdown.

 

Then put the APC on an outward facing port. (SSH if you are paranoid)

and web into it remotely and turn on and off each individual outlet as needed.