anyone get wakeonlan to work with SC1430

I did a packet trace on the Magic Packet that ether-wake is sending.  It seems to be properly formed, with a payload of six ones (hex FF FF FF FF FF FF) followed by sixteen reps of the servers' MAC.  I also tried a broadcast packet of the same information.  No luck.  So it looks to be a hardware issue at this point.

I'm going to run Dell Diagnostics 2.7 tonight to see if that will give me any answers.

'sodo

sudo ether-wake -DV 00:1a:a0:ae:24:c5

ether-wake.c: v1.09 11/12/2003 Donald Becker, http://www.scyld.com/
The target station address is 0:1a:a0:ae:24:c5.
Packet is  00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 08 42 ff ff ff ff ff ff 00 1a a0
ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5 00 1a a0 ae 24
c5 00 1a a0 ae 24 c5 00 1a a0 ae 24 c5.
Sendto worked ! 116.

tcpdump -i eth0 -s 0

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:00:24.256178 00:0c:29:03:e7:29 (oui Unknown) > 00:1a:a0:ae:24:c5 (oui Unknown), ethertype Unknown (0x0842), length 116:
       0x0000:  ffff ffff ffff 001a a0ae 24c5 001a a0ae  ..........$.....
       0x0010:  24c5 001a a0ae 24c5 001a a0ae 24c5 001a  $.....$.....$...
       0x0020:  a0ae 24c5 001a a0ae 24c5 001a a0ae 24c5  ..$.....$.....$.
       0x0030:  001a a0ae 24c5 001a a0ae 24c5 001a a0ae  ....$.....$.....
       0x0040:  24c5 001a a0ae 24c5 001a a0ae 24c5 001a  $.....$.....$...
       0x0050:  a0ae 24c5 001a a0ae 24c5 001a a0ae 24c5  ..$.....$.....$.
       0x0060:  001a a0ae 24c5                           ....$.
^C
1 packets captured
1 packets received by filter
0 packets dropped by kernel

I tried running the Dell Diagnostics program on the SC1430. 

http://support.euro.dell.com/support/downloads/download.aspx?fileid=178199

Complicating matters, I run Linux.  Even so, Diagnostics depends on your server being IPMI compatible (http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface).  The Dell site for Linux engineering (http://linux.dell.com/) shows the IPMI compatible systems

http://linux.dell.com/ipmi.shtml

Unfortunately, the SC1430 is not one of them.  Out of luck on using Diagnostics, I turned to the Broadcom utilities, which I should have probably used in the first place.  But I needed to know the exact model.  In Fedora, I ran:

dmidecode | grep -i road

to gather the information on any Broadcom gear.  DMIdecode showed that the SC1430 I have has the Broadcom 5751 NIC.  So, I downloaded the User Diagnostics (a bootable CD) for my chipset from here:

http://www.broadcom.com/support/ethernet_nic/netxtreme_desktop.php

After burning the ISO, I rebooted and ran b57udiag.exe.  The program did not find any problems after about a minute of testing registers and firmware.  On a lark, I decided to try ether-wake again.  Running a broadcast Magic Packet, I was shocked to hear my box startup!  So the diagnostics must have reset something with the card.

I then went about pulling network cables to see if that might trigger a reset of some sort on the card.  Pulling and then resetting network cables from the server side, then the router side and then both sides did not work.  When I sent the Magic Packet nothing happened.  However, after pulling the power cable on the box and putting it back in, the box started up when I sent the Magic Packet.

So, the NIC seems to be set correctly when the machine is first started, but after wake on lan is used once, something goes wrong in the NIC where it can't be started via wake on lan a second time.

A conundrum no doubt!  Anyone have any ideas at this point?

'sodo

A friend of mine sent me this link describing people who had trouble getting wake on lan to work in an earlier version of Fedora:

http://forums.fedoraforum.org/archive/index.php/t-63763.html

The key was to find out what the operating system was seeing.  In Fedora, this is done using ethtool to examine the features of your NIC:

sudo ethtool eth0
Settings for eth0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: g
    Wake-on: d
    Current message level: 0x000000ff (255)
    Link detected: yes

"Supports Wake-on" tells you if your card supports the feature.  G means good, d means disabled or not supported.  Also, there is the "Wake-on" feature, which means is wake on lan enabled in the operating system.  In my case, "Supports Wake-on" was set to "g", but "Wake-on" was set to "d" for disabled.  Therefore, I needed to enable Wake-on.  I did this for the current session and when the box rebooted by following instructions here:

http://www.mythtv.org/wiki/Wake-on-LAN

Once I set the Wake-on value, I shutdown the server.  Moment of truth came when I sent an etherwake broadcast packet.  Voila!  Box started up!  Sweet!

Finally, Sam Ruby had a nice short page about Wake On Lan that gave some further information:

http://intertwingly.net/blog/2009/05/22/Wake-on-LAN

So..PROBLEM SOLVED!  Of course, now I just need to lock down the wake feature with a secure password, as in the above MythTV Wiki.

thanks for listening.

'sodo