wake on lan - WOL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-28-2017 01:56 PM
Hello, We currently use IP directed broadcast to allow wake on LAN for our 460-48p (G1) switches running 16 code. On occasion we'll have a field tech tell us that WOL isn't working.
Other than confirming that the ip directed broadcast settings are on all appropriate vlans on the core, what else can I check?
Thank you,
Sarah
https://extremeportal.force.com/ExtrArticleDetail?an=000087175
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-28-2017 10:42 PM
Hi Sarah,
Please find the below useful article for WOL:
https://extremeportal.force.com/ExtrArticleDetail?an=000082951
https://extremeportal.force.com/ExtrArticleDetail?an=000066272
Regards,
Karthikeyan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-28-2017 10:40 PM
Create a policy file to be applied as a UDP profile. The format for this policy is below​.
entry one {
if match all {
destination-port 9;
} then {
vlan
}
}
entry two {
if match all {
destination-port 9;
} then {
vlan
}
}
Apply this policy to the VLAN that the WoL server is in, with the command configure vlan
Note:
-We can have 1 UDP broadcast packet to 8 destination (vlan)
-It is not recommended to have more than 8 entries in a UDP profile.
Regards,
Karthikeyan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-28-2017 10:40 PM
Guess I'm trying to nail down where the issue could be. Is it b/c I don't have the profile defined that it sometimes works sometimes doesn't?
Will having the profile defined make it work better?
Or is it simply a requirement for WOL to operate, to have this UDP profile defined on our gear?
(Additionally We don't use netlogin so the second post doesn't' apply here.)
