I have 3 x86 NASs (running 4.2.17) each with LACP NIC Bonding and WOL enabled. All three NASs are connected to a HP Procurve V1810g-24 switch also with LACP configured for the required ports.Here is the deal. When teaming is enabled on both the switch and NAS, WOL never happens. When teaming is disabled on both and only one NIC is used WOL works fine. The problem is I'm not sure which to blame. The switch or the NAS.In the last pic, you can see in the MAC Table that the two NICs of the ReadyNASs have two MACs. But, in the ReadyNAS teaming settings they share one MAC (as I think it would if it was bonded). I did submit a case with HP and started working with them to see if it's on their side.Any thoughts?Here are my settings...Pro-6 Teaming ConfigCrashPlan Teaming ConfigPro-2 Teaming ConfigHP V1810g-24 Trunk StatusHP V1810g-24 Trunk ConfigHP V1810g-24 Pro-6 TrunkHP V1810g-24 CrashPlan TrunkHP V1810g-24 Pro-2 TrunkHP V1810g-24 MAC Table

Suspect this will not work because when readynas is off the bond on the switch will show down but still configured and ports active so the switch may not try to send the WOL packets out the now down lag interface / member ports. The LAg would not be up because when readynas is asleep the bonding driver is not active. Would need to test on Netgear switch but would suspect we would behave sameMake sense?

Thanks for the reply OptimusPrime. I tried the same setup on my Netgear GS724Tv3 (LACP enabled) and the WoL worked no problem. I have other issues with the GS724Tv3 so I won't use it as my main switch but I wanted to test this scenario on it. So it looks like an issue with the HP Procurve 1810. Will keep you posted though.

As I know a little about switch what is other problem with GS724Tv3

The web GUI becomes broken and inaccessible. Case numbers 15569849, 15602170 and 15690045.Netgear forum thread...http://forum1.netgear.com/showthread.php?t=65954

Sorry to revive and old thread, but I have the exact same switch and am getting ready to set up a trunk on it for teaming my Pro ports.Curious as to what solution you found (if any)?Also, which teaming option (on the Pro) did you find the best performance/reliability using?Thanks.

WOL with NIC Teaming | NETGEAR Communities

19 Replies

Replies have been turned off for this discussion

Jetlag1
Guide
Nov 10, 2011
I think I agree with the explanation of OptimusPrime above.
Since I run ReadyDLNA and SqueezeCenter my Pro is on 24/7.
Only shut it down for rack maintenance, etc.

I'll give it a try but not expecting much.
fbmachines
Guide
Nov 10, 2011
I agree, it makes sense but obviously there is/was a way around it for the Netgear switch to be able to handle the magic packet with a down bond.
Jetlag1
Guide
Nov 10, 2011
When my ReadyNAS was off the ReadyNAS Trunk on my HP switch displayed "down", and the ports showed black on the web GUI.
fbmachines
Guide
Nov 10, 2011
Do you have the "enable WoL service" checked in frontview->system->power?

I thought my NIC's showed as 100Mb when powered off.
Jetlag1
Guide
Nov 10, 2011
I have WoL enabled now (missed that one, sorry).
With the Pro shut down the trunk now shows as "Link Status = Down" but the ports show 100MbpsFullDuplex (green) just as you mentioned.

I tried sending magic packets via both UDP and TCP/IP to the ReadyNAS IP (host) with no response.

Were you successful with UDP or TCP/IP prior to ReadyNAS NIC bonding?
Which port did you designate with the one you were successful with?
Jetlag1
Guide
Nov 10, 2011
I tried a few more times to get my Pro to Wol, sending first TCP/IP and then UDP magic packets to it with no response.

Is someone from Netgear wants to suggest a specific port or anything else to try let me know.

You said you were successful with WoL prior to bonding the ReadyNAS NICs?

<Heading down to the basement to turn on my Pro>
fbmachines
Guide
Nov 10, 2011
Thanks for giving it a whirl.

I don't think ports come into play unless you try to wake from a WAN. On a LAN I think just the IP, subnet (broadcast in some cases) and MAC is needed.

I have used various WoL software and some just didn't work. So you might want to try another. Currently I use iNet on my iPhone.

I could never get remote WoL or WoW working reliably but I think it has to do with my UTM25 router.
benhaines
Aspirant
Jul 10, 2013
hi fbmachines,

Did this every get resolved by HP? I see from this post that you tried to get HP to sort it out. - http://h30499.www3.hp.com/t5/Web-and-Unmanaged/Wake-on-Lan-with-V1810G-24-and-teaming/td-p/2307007#.Ud1S1z6G2Zc

It also appears a few users on the QNAP forums are experiencing the same thing. In my mind this suggests it is a problem with the HP ProCurve 1810 switch and not NetGear or QNAP.
fbmachines
Guide
Aug 05, 2013
Hey Ben - No, HP never got it working. They basically just blew me off and said that's how it works.

They sent me a beta firmware but said it had nothing to so with the WoL w/ teaming issue I brought up. It of course didn't help the symptom. After that they said they'll look into it and closed the case. I never heard from them again. The beta firmware was never publicly released.

Forum Discussion

WOL with NIC Teaming

19 Replies

Related Content

WOL D6220

Wol R7000

Orbi RBE772 - Teams meetings and video streaming drops/reconnects

Orbi router RBR50v2 WOL through VPN

Nighthawk RAX54 WOL Setup?

NETGEAR Academy

ProSupport for Business