Knowledge Article
Client Management - Increase Wake On Lan success rate by using good parameters.
Wake On Lan packets are stopped by some network equipments but this issue can be solved by using BCM architecture and some parameters
BMC Client Management
Client Management
Any version of BCM
Some devices can't be woken up. This type of message can be found in the logs of a wakener : 2017/10/11 09:38:53 WakeOnLan I [2360] [172.25.11.52] None of the Wakeup mechanisms worked
Looking closer, the fallback mechanism is not enabled: 2017/10/11 09:38:53 WakeOnLan I [2360] [172.25.11.52] Entering fallback mechanism
2017/10/11 09:38:53 WakeOnLan I [2360] [172.25.11.52] Fallback mechanism is disabled |
By default broadcast packets are sent and these can be filtered by network equipments
1- Configure the WOL module: These are the recommended parameters for the Wake On Lan module of devices: This will allow local devices to perform a Wake-up attempt, if the master fails to wake up the target then it will try to locate another device which is located in the same subnet as the target, and delegate wake-up to it. If it fails, other known devices are tried to be used on this subnet as wakeners. If this attempt also fails then a DirectBrodcast (or unicast if "unicast" is selected instead of "Direct Broadcast") packet is sent on the target subnet, which should succeed. Wake-up devices can also be added if these are always online, but this is not mandatory. 2- Deploy the new WOL module configuration: Here is the operational rule step you can use to set parameters on Wake On Lan module : |
Attachment(s):