<?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 NX5500E Express Manager - Sites in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24743#M2262</link>
    <description>Hi All&lt;BR /&gt;
&lt;BR /&gt;
I am in the process of deploying my first Express Manager solution. NX5500E and AP7522E.&lt;BR /&gt;
&lt;BR /&gt;
Upgraded to latest 5.9 firmware.&lt;BR /&gt;
&lt;BR /&gt;
Ques:&lt;BR /&gt;
&lt;BR /&gt;
Site based NX5500E Express Manager controller does not deploy WLANs to adopted APs unless I create a 'site'. Why? The APs receive Smart RF settings and other configuration parameters but not WLANs for some reason.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Mon, 25 Sep 2017 15:04:00 GMT</pubDate>
    <dc:creator>steve_kemball</dc:creator>
    <dc:date>2017-09-25T15:04:00Z</dc:date>
    <item>
      <title>NX5500E Express Manager - Sites</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24743#M2262</link>
      <description>Hi All&lt;BR /&gt;
&lt;BR /&gt;
I am in the process of deploying my first Express Manager solution. NX5500E and AP7522E.&lt;BR /&gt;
&lt;BR /&gt;
Upgraded to latest 5.9 firmware.&lt;BR /&gt;
&lt;BR /&gt;
Ques:&lt;BR /&gt;
&lt;BR /&gt;
Site based NX5500E Express Manager controller does not deploy WLANs to adopted APs unless I create a 'site'. Why? The APs receive Smart RF settings and other configuration parameters but not WLANs for some reason.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Sep 2017 15:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24743#M2262</guid>
      <dc:creator>steve_kemball</dc:creator>
      <dc:date>2017-09-25T15:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500E Express Manager - Sites</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24744#M2263</link>
      <description>Hi Steve,&lt;BR /&gt;
&lt;BR /&gt;
the Express deployment is meant to use Level2 adoption model to simplify configuration.&lt;BR /&gt;
In other words - you shall create specific sites for APs to be placed and configured apart of logical domain meant for controller.&lt;BR /&gt;
&lt;BR /&gt;
This brings better overview of particular groups of APs and will give you easier topology to work with.&lt;BR /&gt;
Another thing is that every site / domain must be set with country code in order to set correct regulations on AP's radio. This would be little more difficult using a single domain and multiple locations.&lt;BR /&gt;
&lt;BR /&gt;
In a nuthsell - WiNG Express uses some advanced features of WiNG which automatically create the deployment robust and structured. &lt;BR /&gt;
&lt;BR /&gt;
Let me know if you have further questions or issues.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Ondrej</description>
      <pubDate>Mon, 25 Sep 2017 15:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24744#M2263</guid>
      <dc:creator>Ondrej_Lepa</dc:creator>
      <dc:date>2017-09-25T15:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500E Express Manager - Sites</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24745#M2264</link>
      <description>Thank you Ondrej&lt;BR /&gt;
&lt;BR /&gt;
Just to be clear even for a single site deployment I still need to create at least one site with an auto provisioning policy in order for WLAN settings to be deployed. Thanks&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Sep 2017 18:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24745#M2264</guid>
      <dc:creator>steve_kemball</dc:creator>
      <dc:date>2017-09-25T18:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500E Express Manager - Sites</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24746#M2265</link>
      <description>Hello Steve,&lt;BR /&gt;
&lt;BR /&gt;
it might sound strange but the answer is yes.&lt;BR /&gt;
&lt;BR /&gt;
To ensure system will be stable with minimal configuration we rather force all adopted APs in separate groups (sites), ready for remote adoption.&lt;BR /&gt;
&lt;BR /&gt;
This makes the system performing on distributed basis having less to worry about.&lt;BR /&gt;
Might look unnecessary for couple of APs, but helps a lot in case of future expansion.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Ondrej</description>
      <pubDate>Mon, 25 Sep 2017 18:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24746#M2265</guid>
      <dc:creator>Ondrej_Lepa</dc:creator>
      <dc:date>2017-09-25T18:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: NX5500E Express Manager - Sites</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24747#M2266</link>
      <description>O.K. That works for me. I can see the logic and the site will be using two Internal and External antenna variants for office and factory use. This way I can create two sites if needed to deploy different WLANs to the office APs..</description>
      <pubDate>Mon, 25 Sep 2017 19:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500e-express-manager-sites/m-p/24747#M2266</guid>
      <dc:creator>steve_kemball</dc:creator>
      <dc:date>2017-09-25T19:55:00Z</dc:date>
    </item>
  </channel>
</rss>

