<?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 AP121 and AP330  Mesh distance greatly reduced  if configure using the HiveManager Connect in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85233#M10620</link>
    <description>&lt;P&gt;I have two APs: AP330 and AP121 configured in a mesh using the 5Ghz wifi1 as the backhaul. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that if I use the HiveManager Connect Web interface to create a policy and push it to the AP, then the  distance I can place these two AP apart  is greatly reduced.  With the policy pushed from the HiveManager Connect, these two AP would only form the mesh when they are close by, with no wall on between. (is the AP121 would not join AP330 via the Wifi backhaul link)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However if I configure these two AP using the CLI (Using the  Mesh CLI example from the deployment guide),  I can place these two AP further apart, even with a couple of walls in between, and they would still form a mesh.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The CLI configuration only has several lines of configuration when show run-config. The configuration using the HiveManager, however, would have many many lines of configuration. It seems that the HiveManager changed the default configuration a lot, causing the 5Ghz Wifi1 range to be greatly reduced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone has any thoughts on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2019 17:07:41 GMT</pubDate>
    <dc:creator>xelaus</dc:creator>
    <dc:date>2019-09-11T17:07:41Z</dc:date>
    <item>
      <title>AP121 and AP330  Mesh distance greatly reduced  if configure using the HiveManager Connect</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85233#M10620</link>
      <description>&lt;P&gt;I have two APs: AP330 and AP121 configured in a mesh using the 5Ghz wifi1 as the backhaul. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that if I use the HiveManager Connect Web interface to create a policy and push it to the AP, then the  distance I can place these two AP apart  is greatly reduced.  With the policy pushed from the HiveManager Connect, these two AP would only form the mesh when they are close by, with no wall on between. (is the AP121 would not join AP330 via the Wifi backhaul link)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However if I configure these two AP using the CLI (Using the  Mesh CLI example from the deployment guide),  I can place these two AP further apart, even with a couple of walls in between, and they would still form a mesh.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The CLI configuration only has several lines of configuration when show run-config. The configuration using the HiveManager, however, would have many many lines of configuration. It seems that the HiveManager changed the default configuration a lot, causing the 5Ghz Wifi1 range to be greatly reduced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone has any thoughts on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 17:07:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85233#M10620</guid>
      <dc:creator>xelaus</dc:creator>
      <dc:date>2019-09-11T17:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: AP121 and AP330  Mesh distance greatly reduced  if configure using the HiveManager Connect</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85234#M10621</link>
      <description>&lt;P&gt;We'll need to collect some data showing all of this to show to our engineers. Would you be able to file a case for this question?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2019 02:04:15 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85234#M10621</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-09-12T02:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: AP121 and AP330  Mesh distance greatly reduced  if configure using the HiveManager Connect</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85235#M10622</link>
      <description>&lt;P&gt;Let me do some more tests and see if I can narrow down the issue. Will report back.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 10:58:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/ap121-and-ap330-mesh-distance-greatly-reduced-if-configure-using/m-p/85235#M10622</guid>
      <dc:creator>xelaus</dc:creator>
      <dc:date>2019-09-13T10:58:41Z</dc:date>
    </item>
  </channel>
</rss>

