wake on lan with dynamic vlan assignment

[Heinz Kern]

Hallo,

i´m wondering if there is any solution for this problem: we plan to use dynamic vlan assignment and have wake on lan already in place. if using dynamic vlan assignment the port falls back to the default vlan, and than the magic packet doesn´t work any more.

does anybody have a solution for that beside the possibility to send the magic packet also into the default-vlan??

somebody told me thta the "energywise feature" would help but i couldn´t find a possibility.

from a theoreticl point of view i´m searching something like that: the switch recognizes during the day which domain-clients are connected on which ports (based on the domain-name known through 802.1x). if a mgaic packet comes to the switch with a speical domain, ip-subnet or whatever it is broadcasted out all these ports where such clients have been seen....

thanks

heinz

[Richard Burts]

heinz

I do not know of any way to have the swtich remember previous assignments and forward WoL based on the previous assignment. But I do not see why it would not work if you forward the WoL packet to the default vlan.

HTH

Rick

[Heinz Kern]

hi rick,

thanks for the answer. but it´s not a technical problem, it´s an organisational one: first we have to change a lot in the currently used wake on lan server which have been developed by our windows-department themselves. moreover we have about 2000 branches which are separated by Layer-3. every laptop can be everywhere and that means that we have to send every magic packet nto 2000 L3-subnets...

br

heinz

[Richard Burts]

heinz

Thanks for the additional explanation. Yes that does make it challenging when there is that much distributed network. From a technical perspective the WoL could be sent to all layer 3 subnets but that would impose quite a burden. So now the answer needs to be organizational and not technical.

HTH

Rick

[Heinz Kern]

and that brings me again to my first question: is there any intelligent WoL solution available whoch can deal with this challenge beside the "default-vlan"-story.