<?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: High density AP Deployment minimum data rate/single strength in ExtremeWireless (General)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30895#M615</link>
    <description>Really good idea. &lt;BR /&gt;
&lt;BR /&gt;
The client limit of the C5120 in mind, keep me asking the question how many controllers did Extreme use in there reference station high density deployment? Around 9 controllers for the approximately 70.000 users i think.   &lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 18 Feb 2015 01:43:00 GMT</pubDate>
    <dc:creator>hsachse</dc:creator>
    <dc:date>2015-02-18T01:43:00Z</dc:date>
    <item>
      <title>High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30892#M612</link>
      <description>We are in the process of deploying wifi in public areas across the city.&lt;BR /&gt;
At some public areas we get on average 200 to 300 people walking past a single AP. &lt;BR /&gt;
The users might not be using the wifi service but their client devices still automatically associates to the AP, resulting in each AP having +- a 100 associated clients at any one time = poor service.&lt;BR /&gt;
How do we prevent clients with a -75/-80 dbm signal strength from associating with the AP? &lt;BR /&gt;
Or do we restrict the number of users per AP?</description>
      <pubDate>Tue, 17 Feb 2015 23:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30892#M612</guid>
      <dc:creator>Andre_Brits_Kan</dc:creator>
      <dc:date>2015-02-17T23:29:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30893#M613</link>
      <description>Hello Andre,&lt;BR /&gt;
&lt;BR /&gt;
there are several features you can use to load balance the clients between access points in range of the clients: &lt;BR /&gt;
&lt;BR /&gt;
1. Band steering push clients with 802.11a/n(/ac) to this ap radio module instead of establishing a client connection at the 802.11b/g/n radio module&lt;BR /&gt;
&lt;BR /&gt;
2. Enable load sharing of clients between access points (possible at site configuration i think) for better density balance &lt;BR /&gt;
&lt;BR /&gt;
Other reasons for poor wireless performance resulting in sharing the available channels with other access point around the location. In the 2,4 GHz frequency space high channel contention (co-channel contention) is a big problem. 5 GHz is much better, because you have more channels available, but not every mobile support it. &lt;BR /&gt;
&lt;BR /&gt;
Another recommended practice is create smaller cell sizes and use more access points. In some cases is make sense to only use 20 MHz channels on the 802.11a/n radios.&lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Hartmut&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Feb 2015 01:31:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30893#M613</guid>
      <dc:creator>hsachse</dc:creator>
      <dc:date>2015-02-18T01:31:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30894#M614</link>
      <description>The only thing that you'd do is to increase the minimum basic rate so clients with a low RSSI couldn't connect to the AP.&lt;BR /&gt;
&lt;BR /&gt;
Also please keep in mind that the controller only supports a certain number of clients at any time i.e. C5210 supports 8192 clients.&lt;BR /&gt;
So in your example that would result in 4x WLAN Controller C5210.</description>
      <pubDate>Wed, 18 Feb 2015 01:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30894#M614</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2015-02-18T01:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30895#M615</link>
      <description>Really good idea. &lt;BR /&gt;
&lt;BR /&gt;
The client limit of the C5120 in mind, keep me asking the question how many controllers did Extreme use in there reference station high density deployment? Around 9 controllers for the approximately 70.000 users i think.   &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Feb 2015 01:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30895#M615</guid>
      <dc:creator>hsachse</dc:creator>
      <dc:date>2015-02-18T01:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30896#M616</link>
      <description>&lt;A href="https://community.extremenetworks.com/#" target="_blank" rel="nofollow noreferrer noopener"&gt;Andre&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
How do you know the numbers of associated clients is the cause of the poor performance?&lt;BR /&gt;
&lt;BR /&gt;
A number of attached clients should not degrade performance too much. Its the bandwidth and airtime they take up when they are sending or receiving data that would cause a problem.&lt;BR /&gt;
&lt;BR /&gt;
In certain conditions it would not be unreasonable for an AP to support 100 clients that are concurrently transmitting data and still provide the client/application with the throughput it needs to function, especially if that's just web traffic.</description>
      <pubDate>Fri, 12 Jun 2015 16:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30896#M616</guid>
      <dc:creator>Simon_Vosper</dc:creator>
      <dc:date>2015-06-12T16:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30897#M617</link>
      <description>Min basic rate a good idea, and perhaps lower client session times.&lt;BR /&gt;
&lt;BR /&gt;
Articles for load balancing and band steering:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-set-up-a-Band-Preference-Group-Band-Steering-on-IdentiFi-Wireless/?q=band+steering&amp;amp;#38;l=en_US&amp;amp;#38;fs=Search&amp;amp;#38;pn=1" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-set-up-a-Band-Preference-Group-Band...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-set-up-a-Client-Balancing-AP-load-group/?q=load+balancing&amp;amp;#38;l=en_US&amp;amp;#38;fs=Search&amp;amp;#38;pn=1" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-set-up-a-Client-Balancing-AP-load-g...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sat, 13 Jun 2015 08:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30897#M617</guid>
      <dc:creator>Raffi</dc:creator>
      <dc:date>2015-06-13T08:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30898#M618</link>
      <description>&lt;BR /&gt;
&lt;BR /&gt;
Hello Deborak.&lt;BR /&gt;
&lt;BR /&gt;
A query. I want to improve roaming in my WLAN&lt;BR /&gt;
&lt;BR /&gt;
If I set a minimum basic rate on a radio, it is mandatory to enable Probe Suppression ????</description>
      <pubDate>Thu, 14 Feb 2019 02:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30898#M618</guid>
      <dc:creator>Jorge_Cota</dc:creator>
      <dc:date>2019-02-14T02:14:00Z</dc:date>
    </item>
    <item>
      <title>RE: High density AP Deployment minimum data rate/single strength</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30899#M619</link>
      <description>Hi Jorge,&lt;BR /&gt;
&lt;BR /&gt;
no you don't need to enable probe suppression.&lt;BR /&gt;
&lt;BR /&gt;
-Ron</description>
      <pubDate>Thu, 14 Feb 2019 05:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/high-density-ap-deployment-minimum-data-rate-single-strength/m-p/30899#M619</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2019-02-14T05:57:00Z</dc:date>
    </item>
  </channel>
</rss>

