Wireless Access

Reply
Aruba Employee

Re: AP-375 won't join Wireless Manager


sistemi.informativi@speedline.it wrote:

Hi Charlie,

that's exactly our issue. AP won't come as mes point.

What drives me crazy is that I have this issue ONLY with AP-375 (I have 5 of them and no one joins the controller). The behavior is the same: connect to WLC, get latest firmware, reboot and try to connect, then reboot in factory mode. I have already joined several 304 and 305 models with no issues.

 


The license info looks good. I don't see a problem there.

 

To make sure I understand completely, the AP-375s ARE intended to be mesh points ... meaning they will not have a wired connection to the infrastructure where the mobility controller exists, but will instead talk over wireless back to a mesh point that does have wired access. Understanding that none of your AP-375s are operational, is it an existing AP-304/305 that is configured to operate as the mesh portal?


Charlie Clemmer
Aruba Customer Engineering
Occasional Contributor II

Re: AP-375 won't join Wireless Manager


@cclemmer

 

To make sure I understand completely, the AP-375s ARE intended to be mesh points ... meaning they will not have a wired connection to the infrastructure where the mobility controller exists, but will instead talk over wireless back to a mesh point that does have wired access. Understanding that none of your AP-375s are operational, is it an existing AP-304/305 that is configured to operate as the mesh portal?


No, all AP are wired to the network within the same subnet/vlan of Wireless controller. They act as Campus AP and none of AP-375 joins WLC. All AP-304/305 are configured as Campus AP wired to the network and are joined to our WLC.

 

Davide

Occasional Contributor II

Re: AP-375 won't join Wireless Manager

Hmm...I have tried once again to join AP as CAP to Wireless controller and I was able to catch some interestin info from datapath table:

 

Spoiler
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags CPU ID
--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- --------- --------- --------------- -------
10.11.48.21 10.11.48.253 17 8211 8211 0/0 0 0 0 pc0 b 3 3167 FCI 14

10.11.48.253 10.11.48.21 17 8222 8211 0/0 0 0 1 pc0 b 0 0 FYI 14
10.11.48.253 10.11.48.21 17 514 58175 0/0 0 0 0 pc0 6 0 0 FY 11
10.11.48.253 10.11.48.21 17 8211 8211 0/0 0 0 1 pc0 b 0 0 FYI 14
10.11.48.250 10.11.48.21 17 8222 8211 0/0 0 0 1 local b 1 139 FCI 11
10.11.48.21 10.11.48.253 17 8211 8222 0/0 0 0 1 pc0 b 0 0 FYCI 14

10.11.48.21 10.11.48.253 17 58175 514 1/15785 0 0 0 pc0 6 3 301 FC 11
10.11.48.21 10.11.48.250 17 8211 8222 0/0 0 0 1 local b 0 0 FYI 11

It seems that AP and WLC tries to setup the PAPI channel but for some reason AP doesn't go further and give up after some seconds.

 

Could be this info useful?

 

Davide

Aruba Employee

Re: AP-375 won't join Wireless Manager

Okay, so we do see PAPI traffic from the AP hit the controller's datapath.

 

Now if you view the logs on the controller, do you see anything related to the AP's join attempt?


Charlie Clemmer
Aruba Customer Engineering
Occasional Contributor II

Re: AP-375 won't join Wireless Manager

Nope :(

I've also increased the log level of system log to debug and attacched an external syslog server but no logs referred to AP. Only syslog messages sento by AP to WLC.

 

I tried also to install IAP (the same version as I have inside WLC) and it boots properly in IAP mode. Then I converted it to CAP via web interface.

 

Same issue. It downloads and install firmware package from WLC, reboots, discover master via ADP and then get stuck at # prompt.

After that nanny process reboot AP since it hasn't join WLC.

 

Then I did a third attemp by downgrading WLC to 8.2.1.0 but got exactly the same behavior.

 

Thank you

 

Davide

Aruba Employee

Re: AP-375 won't join Wireless Manager


sistemi.informativi@speedline.it wrote:

Then I did a third attemp by downgrading WLC to 8.2.1.0 but got exactly the same behavior.

 

Thank you

 

Davide


Downgrading to 8.2.1.0 is not an option that should work, since the AP-375s require 8.3.0.0 as a minimum release level.

 

The lack of logs showing the AP connection attempts is concerning. It may be best to open a TAC case for live debugging to see what's going on when the AP tries to connect.


Charlie Clemmer
Aruba Customer Engineering
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: