AP doesn ́t connect to HWC

[Mario_Netuschil]

Hello,

I´m facing a problem with an AP.

The AP wouldn´t like to connect to the controller from the remote site to the local site.

Log shows following:

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'
Jan 1 00:03:45 cap: SLPM: Finding AC managers for service='siemens'
Jan 1 00:03:45 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 104
Jan 1 00:03:45 cap: Attempting connection 3 to RU_manager
Jan 1 00:03:45 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########
Jan 1 00:03:46 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 103
Jan 1 00:03:47 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 102
Jan 1 00:03:48 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 101
Jan 1 00:03:49 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 100
Jan 1 00:03:50 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 99
Jan 1 00:03:50 cap: Attempting connection 4 to RU_manager ##########
Jan 1 00:03:50 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########
Jan 1 00:03:51 cap: SLPM: Finding RU managers for service='siemens'
Jan 1 00:03:51 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 98
Jan 1 00:03:51 cap: 00660:ru_discov.c:472-ru_discov_check_timeout()-delta_s 200
Jan 1 00:03:52 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 97
Jan 1 00:03:53 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 96
Jan 1 00:03:54 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 95
Jan 1 00:03:55 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 94
Jan 1 00:03:55 cap: Attempting connection 5 to RU_manager ##########
Jan 1 00:03:55 cap: 00660:ru_connect_to_ma.c:560-ru_discov_send_connec_req()-my sn=##########
Jan 1 00:03:56 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 93
Jan 1 00:03:57 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 92
Jan 1 00:03:58 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 91
Jan 1 00:03:59 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 90
Jan 1 00:04:00 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 89
Jan 1 00:04:00 cap: Delete node 0x537a58, IP ##########
Jan 1 00:04:01 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 88
Jan 1 00:04:01 cap: 00660:ru_discov.c:472-ru_discov_check_timeout()-delta_s 210
Jan 1 00:04:02 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 87
Jan 1 00:04:03 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 86
Jan 1 00:04:04 cap: 00204:ru_mgmt.c:2149-whsl_trans()-S_EDISC 85

It seem´s that he can see the controller but no connection establish between this.
I can ping the controller from AP, also from the HWC the AP.

The firewall between is completly open.

What is the problem and why?

Many thanks for your help.

BR,

Mario

[M_Nees]

Hi Mario,

today i have an AP issue where the ap.log like very similar to yours!

The Problem was that AP has static IP and another system using the same IP (=duplicate IP)!
Change AP IP to next free one - all working well now.

Regards

[Mario_Netuschil]

Hi,

many thanks for the answers.

I will check all this things and update you asap.

BR,

Mario

[Steve_Ballantyn]

connect to the controller from the remote site to the local site

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 not supported by Extreme Networks. 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.

See this thread: https://community.extremenetworks.com/extreme/topics/bridged-ap-connected-client-cannot-obtain-dhcp-...

[Ronald_Dvorak]

I'd say something is wrong in the setup/configuration but the post doens't include even enough data to isolate the issue...

- network diagram
- only this AP or also others affected
- are other APs on the same controller port working
- 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)
- how does the AP get's the controller IP if they are not in the same subnet
.....

I'd get on for hours but I think you get my point.

VERY wild guess...
- controller port has AP registration disabled
- AP doens't know the controller IP (no static entry or learned via DHCP option 78)
- routing issue

BR,
Ron