<?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: Not mesh connection Mesh between AP 8432 and AP7632 in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63496#M5676</link>
    <description>Hello Alan,&lt;BR /&gt;
&lt;BR /&gt;
It all depends on your deployment, if you are setting up these 2 APs to only bridge 2 sites wirelessly then you don't really need a virtual controller; however, if you have multiple APs you'd like the AP8432 to adopt, then you can turn it into a virtual controller. Make sure you configure the AnyAP profile for heterogeneous AP adoption. &lt;BR /&gt;
&lt;BR /&gt;
In other words, a VC is not a must for meshconnex to work, but you can configure this setting should you like all APs adopted by VC. &lt;BR /&gt;
&lt;BR /&gt;
https://gtacknowledge.extremenetworks.com/articles/Q_A/Unable-to-adopt-heterogeneous-different-APs-by-my-WiNG-virtual-controller&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Chris</description>
    <pubDate>Mon, 25 Mar 2019 23:18:41 GMT</pubDate>
    <dc:creator>Christoph_S</dc:creator>
    <dc:date>2019-03-25T23:18:41Z</dc:date>
    <item>
      <title>Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63493#M5673</link>
      <description>Dear Team,&lt;BR /&gt;
&lt;BR /&gt;
Please help me resolve this issue:&lt;BR /&gt;
I try to setup Mesh between two APs. One is connected with Ethernet (AP 8432)and one not(AP 7632).&lt;BR /&gt;
. Would you please give me some idea can fix it.&lt;BR /&gt;
&lt;BR /&gt;
many thanks,&lt;BR /&gt;
Alan</description>
      <pubDate>Mon, 25 Mar 2019 17:39:50 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63493#M5673</guid>
      <dc:creator>Alan_Phan</dc:creator>
      <dc:date>2019-03-25T17:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63494#M5674</link>
      <description>Hello Alan,&lt;BR /&gt;
&lt;BR /&gt;
I've attached the meshconnex setup instructions. If testing in lab/office make sure you follow these guidelines:&lt;BR /&gt;
&lt;BR /&gt;
1 - The APs both be running on the latest recommended firmware. In your case this would be 5.9.2.6&lt;BR /&gt;
2 - Make sure that the APs are a few feet apart &lt;BR /&gt;
3 - Reduce the radio power to 1. Once tests done and connection established, reconfigure the power to whatever you need it to be prior to deployment&lt;BR /&gt;
&lt;BR /&gt;
I hope this helps,&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Chris</description>
      <pubDate>Mon, 25 Mar 2019 22:20:44 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63494#M5674</guid>
      <dc:creator>Christoph_S</dc:creator>
      <dc:date>2019-03-25T22:20:44Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63495#M5675</link>
      <description>Hello Chris,&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your information. In this case, I can set AP8432 do controller and mesh connection with AP7632 or not?&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Alan</description>
      <pubDate>Mon, 25 Mar 2019 23:07:10 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63495#M5675</guid>
      <dc:creator>Alan_Phan</dc:creator>
      <dc:date>2019-03-25T23:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63496#M5676</link>
      <description>Hello Alan,&lt;BR /&gt;
&lt;BR /&gt;
It all depends on your deployment, if you are setting up these 2 APs to only bridge 2 sites wirelessly then you don't really need a virtual controller; however, if you have multiple APs you'd like the AP8432 to adopt, then you can turn it into a virtual controller. Make sure you configure the AnyAP profile for heterogeneous AP adoption. &lt;BR /&gt;
&lt;BR /&gt;
In other words, a VC is not a must for meshconnex to work, but you can configure this setting should you like all APs adopted by VC. &lt;BR /&gt;
&lt;BR /&gt;
https://gtacknowledge.extremenetworks.com/articles/Q_A/Unable-to-adopt-heterogeneous-different-APs-by-my-WiNG-virtual-controller&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Chris</description>
      <pubDate>Mon, 25 Mar 2019 23:18:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63496#M5676</guid>
      <dc:creator>Christoph_S</dc:creator>
      <dc:date>2019-03-25T23:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63497#M5677</link>
      <description>&lt;BR /&gt;
Hello Chris,&lt;BR /&gt;
&lt;BR /&gt;
I followed as your document but it not ok. I do not know why, could you reference log the attack file below&lt;BR /&gt;
https://1drv.ms/f/s!AjaVi4rajm-PiDAqM7XROYnDV9TR&lt;BR /&gt;
&lt;BR /&gt;
Kindly help to check&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Alan</description>
      <pubDate>Tue, 26 Mar 2019 13:57:35 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63497#M5677</guid>
      <dc:creator>Alan_Phan</dc:creator>
      <dc:date>2019-03-26T13:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63498#M5678</link>
      <description>Hello Alan,&lt;BR /&gt;
&lt;BR /&gt;
Recommended changes:&lt;BR /&gt;
&lt;BR /&gt;
Change control vlan in meshpoint on both so something like vlan 99&lt;BR /&gt;
Change antenna mode from 1x1 to 2x2 again on both as an override&lt;BR /&gt;
&lt;BR /&gt;
Critical change:&lt;BR /&gt;
&lt;BR /&gt;
Add country code to your rf-domain or else the radios will not broadcast:&lt;BR /&gt;
&lt;BR /&gt;
rf-domain default&lt;BR /&gt;
&lt;B&gt;&lt;U&gt; no country-code&lt;/U&gt;&lt;/B&gt;&lt;BR /&gt;
 use nsight-policy default&lt;BR /&gt;
&lt;BR /&gt;
If issue is not resolved at this point I would recommend you contact GTAC to open a case.&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Chris</description>
      <pubDate>Tue, 26 Mar 2019 20:28:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63498#M5678</guid>
      <dc:creator>Christoph_S</dc:creator>
      <dc:date>2019-03-26T20:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: Not mesh connection Mesh between AP 8432 and AP7632</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63499#M5679</link>
      <description>&lt;BR /&gt;
Great.... Done&lt;BR /&gt;
Thanks for support, Chris</description>
      <pubDate>Wed, 27 Mar 2019 11:39:24 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/not-mesh-connection-mesh-between-ap-8432-and-ap7632/m-p/63499#M5679</guid>
      <dc:creator>Alan_Phan</dc:creator>
      <dc:date>2019-03-27T11:39:24Z</dc:date>
    </item>
  </channel>
</rss>

