Automate Wake on Lan

[Anon Anon]

Is there a way to automate a WOL in DSM 12.5? I have a weekly virus scan job that runs (another product) and right now I am manully right clicking on the object group and selecting "power up computers" prior to this weekly job running so that all the machines are on a ready for this other task to run which is automated. I am sure I could probably do this by creating a new software job and creating a script but wanted to see if there was a simplier way to do this and scheulde it to run weekly.

Thanks

[Shocko]

You can configure ITCM to auto send WOL when I job is triggered :)

[Anon Anon]

Its WOL enabled in your network(switches)?

[Richard Little]

By Default a WOL is sent with every Software Job

Ther is no way to specifically schedule a WOL from Client Automation and also no way to schedule a repeat software job.

If you have a job scheduling tool you could define a software job via CLI. I would suggest you use a configure or activate procedure so that it could be run multiple times without causing issues with install records.

regards
Rich

[Richard Little]

richard_little wrote:

By Default a WOL is sent with every Software Job

Ther is no way to specifically schedule a WOL from Client Automation and also no way to schedule a repeat software job.

If you have a job scheduling tool you could define a software job via CLI. I would suggest you use a configure or activate procedure so that it could be run multiple times without causing issues with install records.

regards
Rich

Did this answer your query?

If so could you mark as answer please

regards
rich

[Legacy User]

Still impossible to automate wake on lan even in the newer versions of Client Automation?

[lecri01]

If your network card or bios offers a command line option to configure it then client auto can do it.

 

Richard Lechner

Principal Engineering Services Architect

 

CA Technologies

Mobile: [phone] | [e-mail]

 

<mailto:[e-mail]>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>

[mccst05]

You can use the ‘caf sendwol’ command to have CAF send wake-on-lan instructions to devices.

 

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

[e-mail]

<mailto:[e-mail]>

[Legacy User]

Hi Stephen, thank you on quickly reply!

 

But caf sendwol cannot send the magic packet to a network address eg. caf sendwol 192.168.0.0 255.255.255.0, is that true? so, to use caf sendwol i have to create a script reading a list of targets.

 

Thanks in advance!

[Steve Parker]

Carlos,

 

The WOL standard from INTEL only supports a WOL packet sent to a MAC address. The IP address and subnet mask are specified in order that Routers etc. can send the magic packet to the correct subnet.

 

What are you trying to achieve by sending a WOL to clients using the command line?

 

Rgds,

Steve.

[mccst05]

Exactly,

 

This is one of the shortcomings of the wake-on-lan protocol. As Steve P. says, without the IP address and subnet mask, (or host name and subnet mask) the network would be unable to locate the MAC address provided since MAC addresses are only stored in router caches for a short time after a system is turned off, and by definition a system which is off does not actually have an IP address. In the WOL standard the WOL packet has to come from the same subnet and is broadcast with the MAC address specified as the intended recipient.

 

Client Auto tries to work around this by providing the capability to use the last known IP Address to route the packet to the correct subnet. The subnet address is not actually a required parameter but is recommended to help find the correct subnet. If there are other machines active in that subnet, the routers should be able to find the correct subnet using their caches without the subnet mask. However if there are no active machines in the subnet, the routers may require the subnet mask in order to route the packet correctly.

 

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

[e-mail]

<mailto:[e-mail]>

[Legacy User]

Hi Guys, many thanks!

 

I was thinking in a way to use data from ITCM groups to achive this task, but searching at knowledge base i found the TEC1276226 wich confirm the impossibility to send magic packets to machine groups so by using the caf "sendwold" could be an alternative and again as well explainned, the MAC address is a necessary parameter to use "caf sendwol" being impossible to "broadcast" the magic packets to a specific network range.

 

Now i would like to share an alternative to send the magic packets to a group of machines using "caf sendwol"

1st -  create a report to export mac addres, ip address and netmask to a csv file

2nd - create an asset job to run the attached script wich sends the magic packet one by one.

 

I hope it can be helpful.

 

Best Regards,

Carlos Carbonari

Attachment(s)

WOL_Targets.bat.zip   3 KB 1 version

Run_WOL.bat.zip   267 B 1 version

WOL_Targets.txt.zip   4 KB 1 version

[mccst05]

You could script this, using cadsmcmd to list the members (cadsmcmd compgroup action=listmembership group=groupname) of groups then ‘cadsmcmd targetcomputer action=list name=computername’ to get the last known IP Address, then finally use caf sendwol to wake the machines. Look at using cadsmcmd in batch mode to get the output for multiple computers with a single call, which would give hugely improved performance over a call to cadsmcmd (each of which has to make a connection to the API) for every computer in the list.

 

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

[e-mail]

<mailto:[e-mail]>