<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: wake on lan - WOL in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46460#M11760</link>
    <description>Thank you for the response.  Is it REQUIRED to have this AND the ip directed broadcast to have WOL successfully work?&lt;BR /&gt;
&lt;BR /&gt;
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?&lt;BR /&gt;
&lt;BR /&gt;
Will having the profile defined make it work better? &lt;BR /&gt;
&lt;BR /&gt;
Or is it simply a requirement for WOL to operate, to have this UDP profile defined on our gear?   &lt;BR /&gt;
&lt;BR /&gt;
(Additionally We don't use netlogin so the second post doesn't' apply here.)&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Tue, 29 Aug 2017 05:40:00 GMT</pubDate>
    <dc:creator>Sarah_Seidl</dc:creator>
    <dc:date>2017-08-29T05:40:00Z</dc:date>
    <item>
      <title>wake on lan - WOL</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46458#M11758</link>
      <description>&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;Other than confirming that the ip directed broadcast settings are on all appropriate vlans on the core, what else can I check?&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;&lt;BR /&gt;Sarah&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000087175" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000087175&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2017 20:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46458#M11758</guid>
      <dc:creator>Sarah_Seidl</dc:creator>
      <dc:date>2017-08-28T20:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: wake on lan - WOL</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46459#M11759</link>
      <description>Hi Sarah,&lt;BR /&gt;
&lt;BR /&gt;
Create a policy file to be applied as a UDP profile. The format for this policy is below​.&lt;BR /&gt;
&lt;BR /&gt;
entry one {&lt;BR /&gt;
     if match all {&lt;BR /&gt;
           destination-port 9;&lt;BR /&gt;
     } then {&lt;BR /&gt;
           vlan &lt;VLAN_NAME&gt;;&lt;BR /&gt;
     }&lt;BR /&gt;
}&lt;BR /&gt;
 &lt;BR /&gt;
entry two {&lt;BR /&gt;
     if match all {&lt;BR /&gt;
           destination-port 9;&lt;BR /&gt;
     } then {&lt;BR /&gt;
           vlan &lt;VLAN_NAME&gt;;&lt;BR /&gt;
     }&lt;BR /&gt;
}&lt;BR /&gt;
&lt;BR /&gt;
Apply this policy to the VLAN that the WoL server is in, with the command configure vlan &lt;VLAN_NAME&gt; udp-profile &lt;BR /&gt;
&lt;BR /&gt;
Note:&lt;BR /&gt;
&lt;BR /&gt;
-We can have 1 UDP broadcast packet to 8 destination (vlan)&lt;BR /&gt;
-It is not recommended to have more than 8 entries in a UDP profile.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Karthikeyan&lt;BR /&gt;
&lt;BR /&gt;&lt;/VLAN_NAME&gt;&lt;/VLAN_NAME&gt;&lt;/VLAN_NAME&gt;</description>
      <pubDate>Tue, 29 Aug 2017 05:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46459#M11759</guid>
      <dc:creator>Narayanan__Kart</dc:creator>
      <dc:date>2017-08-29T05:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: wake on lan - WOL</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46460#M11760</link>
      <description>Thank you for the response.  Is it REQUIRED to have this AND the ip directed broadcast to have WOL successfully work?&lt;BR /&gt;
&lt;BR /&gt;
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?&lt;BR /&gt;
&lt;BR /&gt;
Will having the profile defined make it work better? &lt;BR /&gt;
&lt;BR /&gt;
Or is it simply a requirement for WOL to operate, to have this UDP profile defined on our gear?   &lt;BR /&gt;
&lt;BR /&gt;
(Additionally We don't use netlogin so the second post doesn't' apply here.)&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Aug 2017 05:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46460#M11760</guid>
      <dc:creator>Sarah_Seidl</dc:creator>
      <dc:date>2017-08-29T05:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: wake on lan - WOL</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46461#M11761</link>
      <description>&lt;P&gt;Hi Sarah,&lt;BR /&gt;&lt;BR /&gt;Please find the below useful article for WOL:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000082951" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000082951&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000066272" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?an=000066272&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthikeyan&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 05:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/wake-on-lan-wol/m-p/46461#M11761</guid>
      <dc:creator>Narayanan__Kart</dc:creator>
      <dc:date>2017-08-29T05:42:00Z</dc:date>
    </item>
  </channel>
</rss>

