<?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: AP doesn ́t connect to HWC in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41154#M2894</link>
    <description>I'd say something is wrong in the setup/configuration but the post doens't include even enough data to isolate the issue...&lt;BR /&gt;
&lt;BR /&gt;
- network diagram&lt;BR /&gt;
- only this AP or also others affected&lt;BR /&gt;
- are other APs on the same controller port working&lt;BR /&gt;
- screenshot of ping test, you'd ping from GUI, CLI, shell which could give different results as they are not the same (source IP which has an impact on the result)&lt;BR /&gt;
- how does the AP get's the controller IP if they are not in the same subnet&lt;BR /&gt;
.....&lt;BR /&gt;
&lt;BR /&gt;
I'd get on for hours but I think you get my point.&lt;BR /&gt;
&lt;BR /&gt;
VERY wild guess...&lt;BR /&gt;
- controller port has AP registration disabled&lt;BR /&gt;
- AP doens't know the controller IP (no static entry or learned via DHCP option 78)&lt;BR /&gt;
- routing issue&lt;BR /&gt;
&lt;BR /&gt;
BR,&lt;BR /&gt;
Ron</description>
    <pubDate>Wed, 01 Jun 2016 22:08:00 GMT</pubDate>
    <dc:creator>Ronald_Dvorak</dc:creator>
    <dc:date>2016-06-01T22:08:00Z</dc:date>
    <item>
      <title>AP doesn ́t connect to HWC</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41153#M2893</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
I´m facing a problem with an AP.&lt;BR /&gt;
&lt;BR /&gt;
The AP wouldn´t like to connect to the controller from the remote site to the local site.&lt;BR /&gt;
&lt;BR /&gt;
Log shows following:&lt;BR /&gt;
&lt;BR /&gt;
Jan  1 00:03:45 cap:   SLPU: Finding AC managers for service='siemens'Jan  1 00:03:45 cap:   SLPU: Finding RU managers for service='siemens'&lt;BR /&gt;
Jan  1 00:03:45 cap:   SLPM: Finding AC managers for service='siemens'&lt;BR /&gt;
Jan  1 00:03:45 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 104&lt;BR /&gt;
Jan  1 00:03:45 cap:  Attempting connection 3 to RU_manager &lt;BR /&gt;
Jan  1 00:03:45 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########&lt;BR /&gt;
Jan  1 00:03:46 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 103&lt;BR /&gt;
Jan  1 00:03:47 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 102&lt;BR /&gt;
Jan  1 00:03:48 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 101&lt;BR /&gt;
Jan  1 00:03:49 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 100&lt;BR /&gt;
Jan  1 00:03:50 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 99&lt;BR /&gt;
Jan  1 00:03:50 cap:  Attempting connection 4 to RU_manager ##########&lt;BR /&gt;
Jan  1 00:03:50 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########&lt;BR /&gt;
Jan  1 00:03:51 cap:   SLPM: Finding RU managers for service='siemens'&lt;BR /&gt;
Jan  1 00:03:51 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 98&lt;BR /&gt;
Jan  1 00:03:51 cap: 00660:ru_discov.c:472-ru_discov_check_timeout()-delta_s 200&lt;BR /&gt;
Jan  1 00:03:52 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 97&lt;BR /&gt;
Jan  1 00:03:53 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 96&lt;BR /&gt;
Jan  1 00:03:54 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 95&lt;BR /&gt;
Jan  1 00:03:55 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 94&lt;BR /&gt;
Jan  1 00:03:55 cap:  Attempting connection 5 to RU_manager ##########&lt;BR /&gt;
Jan  1 00:03:55 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########&lt;BR /&gt;
Jan  1 00:03:56 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 93&lt;BR /&gt;
Jan  1 00:03:57 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 92&lt;BR /&gt;
Jan  1 00:03:58 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 91&lt;BR /&gt;
Jan  1 00:03:59 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 90&lt;BR /&gt;
Jan  1 00:04:00 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 89&lt;BR /&gt;
Jan  1 00:04:00 cap:  Delete node 0x537a58, IP ##########&lt;BR /&gt;
Jan  1 00:04:01 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 88&lt;BR /&gt;
Jan  1 00:04:01 cap: 00660:ru_discov.c:472-ru_discov_check_timeout()-delta_s 210&lt;BR /&gt;
Jan  1 00:04:02 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 87&lt;BR /&gt;
Jan  1 00:04:03 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 86&lt;BR /&gt;
Jan  1 00:04:04 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 85&lt;BR /&gt;
&lt;BR /&gt;
It seem´s that he can see the controller but no connection establish between this.&lt;BR /&gt;
I can ping the controller from AP, also from the HWC the AP.&lt;BR /&gt;
&lt;BR /&gt;
The firewall between is completly open.&lt;BR /&gt;
&lt;BR /&gt;
What is the problem and why?&lt;BR /&gt;
&lt;BR /&gt;
Many thanks for your help.&lt;BR /&gt;
&lt;BR /&gt;
BR,&lt;BR /&gt;
&lt;BR /&gt;
Mario</description>
      <pubDate>Wed, 01 Jun 2016 19:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41153#M2893</guid>
      <dc:creator>Mario_Netuschil</dc:creator>
      <dc:date>2016-06-01T19:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP doesn ́t connect to HWC</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41154#M2894</link>
      <description>I'd say something is wrong in the setup/configuration but the post doens't include even enough data to isolate the issue...&lt;BR /&gt;
&lt;BR /&gt;
- network diagram&lt;BR /&gt;
- only this AP or also others affected&lt;BR /&gt;
- are other APs on the same controller port working&lt;BR /&gt;
- screenshot of ping test, you'd ping from GUI, CLI, shell which could give different results as they are not the same (source IP which has an impact on the result)&lt;BR /&gt;
- how does the AP get's the controller IP if they are not in the same subnet&lt;BR /&gt;
.....&lt;BR /&gt;
&lt;BR /&gt;
I'd get on for hours but I think you get my point.&lt;BR /&gt;
&lt;BR /&gt;
VERY wild guess...&lt;BR /&gt;
- controller port has AP registration disabled&lt;BR /&gt;
- AP doens't know the controller IP (no static entry or learned via DHCP option 78)&lt;BR /&gt;
- routing issue&lt;BR /&gt;
&lt;BR /&gt;
BR,&lt;BR /&gt;
Ron</description>
      <pubDate>Wed, 01 Jun 2016 22:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41154#M2894</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2016-06-01T22:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP doesn ́t connect to HWC</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41155#M2895</link>
      <description>&lt;BLOCKQUOTE&gt;connect to the controller from the remote site to the local site&lt;/BLOCKQUOTE&gt;I am betting that you ran into the same issue that I had a while back. Is your remote site connected via a VPN tunnel? You may be running into an issue where the controller is behind NAT, and this is &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/Access-points-in-a-NAT-configuration" target="_blank" rel="nofollow noreferrer noopener"&gt;not supported by Extreme Networks&lt;/A&gt;. The solution for me was to configure an external IP address to port-forward into the internal IP of my controller. And then configured the access points with that external IP address for the controller.&lt;BR /&gt;
&lt;BR /&gt;
See this thread: &lt;A href="https://community.extremenetworks.com/extreme/topics/bridged-ap-connected-client-cannot-obtain-dhcp-address-from-the-local-cisco-asa-5505" target="_blank" rel="nofollow noreferrer noopener"&gt;https://community.extremenetworks.com/extreme/topics/bridged-ap-connected-client-cannot-obtain-dhcp-address-from-the-local-cisco-asa-5505&lt;/A&gt;</description>
      <pubDate>Wed, 01 Jun 2016 22:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41155#M2895</guid>
      <dc:creator>Steve_Ballantyn</dc:creator>
      <dc:date>2016-06-01T22:25:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP doesn ́t connect to HWC</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41156#M2896</link>
      <description>Hi, &lt;BR /&gt;
&lt;BR /&gt;
many thanks for the answers.&lt;BR /&gt;
&lt;BR /&gt;
I will check all this things and update you asap.&lt;BR /&gt;
&lt;BR /&gt;
BR,&lt;BR /&gt;
&lt;BR /&gt;
Mario</description>
      <pubDate>Thu, 09 Jun 2016 20:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41156#M2896</guid>
      <dc:creator>Mario_Netuschil</dc:creator>
      <dc:date>2016-06-09T20:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP doesn ́t connect to HWC</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41157#M2897</link>
      <description>Hi Mario,&lt;BR /&gt;
&lt;BR /&gt;
today i have an AP issue where the ap.log like very similar to yours!&lt;BR /&gt;
&lt;BR /&gt;
The Problem was that AP has static IP and another system using the same IP (=duplicate IP)!&lt;BR /&gt;
Change AP IP to next free one - all working well now.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;</description>
      <pubDate>Wed, 31 May 2017 12:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/ap-doesn-%CC%81t-connect-to-hwc/m-p/41157#M2897</guid>
      <dc:creator>M_Nees</dc:creator>
      <dc:date>2017-05-31T12:38:00Z</dc:date>
    </item>
  </channel>
</rss>

