<?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 AP3805i-ROW won't register with V2110 anymore (same VLAN) in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44997#M3865</link>
    <description>AP's in the same subnet as the physical topology (esa0, PHY, AP Registration checked).&lt;BR /&gt;
APs were already registered with EWC (initially deployed with .ova 10.11), but after upgrade to 10.31.x APs won't register anymore.&lt;BR /&gt;
APs have regular IPs, respond to ping and can be accessed via ssh;&lt;BR /&gt;
# &lt;B&gt;cget config global&lt;/B&gt; shows correct lastAcIp &lt;ESA0-IP-ADDRESS&gt;&lt;BR /&gt;
esa0 responds to ping from AP.&lt;BR /&gt;
&lt;BR /&gt;
Please advise.&lt;/ESA0-IP-ADDRESS&gt;</description>
    <pubDate>Tue, 07 Nov 2017 16:56:00 GMT</pubDate>
    <dc:creator>Dusan_K_</dc:creator>
    <dc:date>2017-11-07T16:56:00Z</dc:date>
    <item>
      <title>AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44997#M3865</link>
      <description>AP's in the same subnet as the physical topology (esa0, PHY, AP Registration checked).&lt;BR /&gt;
APs were already registered with EWC (initially deployed with .ova 10.11), but after upgrade to 10.31.x APs won't register anymore.&lt;BR /&gt;
APs have regular IPs, respond to ping and can be accessed via ssh;&lt;BR /&gt;
# &lt;B&gt;cget config global&lt;/B&gt; shows correct lastAcIp &lt;ESA0-IP-ADDRESS&gt;&lt;BR /&gt;
esa0 responds to ping from AP.&lt;BR /&gt;
&lt;BR /&gt;
Please advise.&lt;/ESA0-IP-ADDRESS&gt;</description>
      <pubDate>Tue, 07 Nov 2017 16:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44997#M3865</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T16:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44998#M3866</link>
      <description>I have not set any DHCP Option nor DNS entry.&lt;BR /&gt;
Is DHCP Option also mandatory with APs in the same subnet as the physical topology?&lt;BR /&gt;
We have DHCP relay.</description>
      <pubDate>Tue, 07 Nov 2017 17:20:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44998#M3866</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T17:20:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44999#M3867</link>
      <description>Here the information from the Wireless Getting Started Guide.....&lt;BR /&gt;
&lt;BR /&gt;
Determine the method of AP controller discovery used by the APs to find the controller(s) to which the AP registers to provide network service. The AP supports:&lt;BR /&gt;
&lt;BR /&gt;
• SLP-DA Discovery: Configure the segment settings for the DHCP server that provides IP assignment to the APs to include a reference to the SLP-DA to which WLAN controllers are registered. This allows the AP to obtain a list of eligible controllers.&lt;BR /&gt;
&lt;BR /&gt;
• DNS: Configure the controller.&lt;NETWORK domain=""&gt; entry to resolve to the IP address of a&lt;BR /&gt;
specific controller.&lt;BR /&gt;
&lt;BR /&gt;
• Multicast: Verify that the switching gear and interconnecting VLANs are provisioned so as to allow&lt;BR /&gt;
multicast traffic, and IGMP snooping allows for the establishment of multicast trees, allowing the&lt;BR /&gt;
APs to subscribe to SLP-DA server advertisements. The SLP-DA server sends queries to determine&lt;BR /&gt;
the list of registered controllers.&lt;BR /&gt;
&lt;BR /&gt;
So it should work via multicast if that is allowed on the infrastructure BUT I'd use DHCP#78 anyway - it's just one entry.&lt;BR /&gt;
&lt;BR /&gt;
-Ron&lt;/NETWORK&gt;</description>
      <pubDate>Tue, 07 Nov 2017 17:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/44999#M3867</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-11-07T17:29:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45000#M3868</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
log in to the (SSH) AP and set it to factroy default.&lt;BR /&gt;
login:admin&lt;BR /&gt;
password:new2day&lt;BR /&gt;
#cset f&lt;BR /&gt;
&lt;BR /&gt;
Clear the AP in the EWC to be sure and it should be abel again to connect to the EWC.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Umut Aydin&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Nov 2017 17:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45000#M3868</guid>
      <dc:creator>Umut_Aydin</dc:creator>
      <dc:date>2017-11-07T17:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45001#M3869</link>
      <description>Hi Umut,&lt;BR /&gt;
&lt;BR /&gt;
have tried that as well, but it does not work.&lt;BR /&gt;
AP gets IP, is pingable from EWC and back, but won't register ...&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Nov 2017 18:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45001#M3869</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T18:06:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45002#M3870</link>
      <description>Try it with a static controller IP just so we know that the problem is the discovery...&lt;BR /&gt;
&lt;BR /&gt;
ssh to the AP&lt;BR /&gt;
cset authip 1 x.x.x.x&lt;BR /&gt;
capply&lt;BR /&gt;
csave&lt;BR /&gt;
&lt;BR /&gt;
x.x.x.x is the controller IP</description>
      <pubDate>Tue, 07 Nov 2017 18:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45002#M3870</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-11-07T18:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45003#M3871</link>
      <description>Hi Dusan,&lt;BR /&gt;
&lt;BR /&gt;
if this doesn't work please check if somehow the AP went to a older code ..e.g 9.xx maybe this cause that the AP can't get the EWC?&lt;BR /&gt;
&lt;BR /&gt;
# cat /etc/ap_version.txt&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Umut&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Nov 2017 20:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45003#M3871</guid>
      <dc:creator>Umut_Aydin</dc:creator>
      <dc:date>2017-11-07T20:15:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45004#M3872</link>
      <description>APs were successfully registered with 10.11 and currently still running this code:&lt;BR /&gt;
&lt;BR /&gt;
AP3805i-ROW 10.11.03.0004 interactive shell for service personnel only&lt;BR /&gt;
# cat /etc/ap_version.txt&lt;BR /&gt;
export AP_VERSION=10.11.03.0004&lt;BR /&gt;
...&lt;BR /&gt;
&lt;BR /&gt;
V2110 is currently running 10.31.07.0002 and all APs are online. (Option 78 was needed).</description>
      <pubDate>Tue, 07 Nov 2017 20:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45004#M3872</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T20:15:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45005#M3873</link>
      <description>Solved.&lt;BR /&gt;
&lt;BR /&gt;
Option 78 was needed.&lt;BR /&gt;
&lt;BR /&gt;
Any idea how to enter the second controller in Option 78?&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Nov 2017 20:37:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45005#M3873</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T20:37:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45006#M3874</link>
      <description>could you provide a screenshot of your 78 option settings - there is more then one way to do it and I don't want to provide a wrong answer</description>
      <pubDate>Tue, 07 Nov 2017 20:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45006#M3874</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-11-07T20:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45007#M3875</link>
      <description>Please advise for "Data Entry Byte: Decimal" scenario.&lt;BR /&gt;
We entered one controller by setting Values: "1" and then "10" Add + "1" Add + "11" Add + "4" Add being 10.1.11.4 an IP addr of EWC's PHY port. The PHY port of second EWC is 10.1.11.5.&lt;BR /&gt;
Each single number in its line, looks like this:&lt;BR /&gt;
1&lt;BR /&gt;
10&lt;BR /&gt;
1&lt;BR /&gt;
11&lt;BR /&gt;
4</description>
      <pubDate>Tue, 07 Nov 2017 21:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45007#M3875</guid>
      <dc:creator>Dusan_K_</dc:creator>
      <dc:date>2017-11-07T21:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45008#M3876</link>
      <description>You can set up the new address right under that one in the array (without another leading 1) so it would look like:&lt;BR /&gt;
&lt;BR /&gt;
1&lt;BR /&gt;
10&lt;BR /&gt;
1&lt;BR /&gt;
11&lt;BR /&gt;
4&lt;BR /&gt;
10&lt;BR /&gt;
1&lt;BR /&gt;
11&lt;BR /&gt;
5</description>
      <pubDate>Tue, 07 Nov 2017 22:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45008#M3876</guid>
      <dc:creator>Careno__Ryan</dc:creator>
      <dc:date>2017-11-07T22:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP3805i-ROW won't register with V2110 anymore (same VLAN)</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45009#M3877</link>
      <description>Hi Dusan,&lt;BR /&gt;
&lt;BR /&gt;
I think that the following article will help you.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;&lt;/B&gt;How To Configure an AP to Find the IdentiFi Wireless Controller with DHCP Option 78 on a Windows Server&lt;BR /&gt;
&lt;B&gt;&lt;/B&gt;&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-AP-to-Find-the-IdentiFi-Wireless-Controller" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-AP-to-Find-the-IdentiF...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;BR /&gt;
Bin &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2017 03:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap3805i-row-won-t-register-with-v2110-anymore-same-vlan/m-p/45009#M3877</guid>
      <dc:creator>Bin</dc:creator>
      <dc:date>2017-11-12T03:15:00Z</dc:date>
    </item>
  </channel>
</rss>

