Controllerless Networks

Hello,

I have an OMNIACCESS 4650 controller, version 6.5.2.1, working with around 400 IAP205 as CAMPUS AP (CAP).
I can provision any IAP205 in the controller successfully but when I try to provision any IAP-305, as campus AP, with the same provisioning procedure, the controller does not recognize it. I´ve tried to do it with several APs but with no success.
However I can provision IAP305 as remote AP (RAP) without any problem.

The initial image version of the IAPs before the provisioning is :
IAP-205-RW : 6.4.2.5-4.1.1.6
IAP-305-RW : 6.5.1.0-4.3.1.0

Can you help me on finding the reason because Controller does not recognize IAP-305-RW as CAP?

Thanks in advance.

I don't think you can mix Aruba APs with OMNIACCESS 4650 controllers.

check your logs. Some models Support. AP-515 also support for OAW controllers.

While not officially supported, Aruba APs are expected to work on OAW controllers, and OAW APs are expected to work on Aruba controllers.

I'm with Dinusha: The first step is probably to check the 'show log all 200' on the controller when you try to connect the APs.

Do you have the APs whitelisted and enough licenses? The show log all will tell you if any of these are wrong as well.

Thank you Dinusha and Herman,

I have AOW-4650 running with near 400 Alcatel-Lucent OAW-AP205 (labeled on their backside as Aruba APIN0205 IAP-305-RW) APs with no problem .

Now I´m trying to provisioning Alcatel-Lucent OAW-305 (labeled on their back side as Aruba APIN0305 IAP-305-RW) .with no successs.

I´m sorry for the confusion  generated .

Regards,

Juan.

Do you have enough licenses available?

Are the APs allowed authorized, or Cert Autoprovisioning enabled?

Did you check the controller logs (show log all 200, from the CLI) after you try to connect those APs? That will probably indicate what's going on.

What is your Firmware version on the Controller? It should be greater than 6.5.1 to provision AP305

Firmware version on the Controller is 6.5.2.1

What is Firmware Version Mentioned in Your IAP-305 Box? And attached your log files

Firmware version on 305 is 6.5.1.0-4.3.1.0 .

I can not attach logs today because I`m homeworking and not able to provision APs today . I´ll do it at the end of the week and will attach logs ..

Thanks for your help

Which screeshot you mean? 

Attached all the AP 305 CAP converting proccess thru console cale.

I whitlisted in controller but it never detects AP.

Afater conversion AP keeps continuosly rebooting 

Attachment(s)

IAP305 CAP CONVERTING PROCCESS.txt   18 KB 1 version

So, to confirm your Controller is at 172.16.255.10 ?

convert-aos-ap cap 172.16.255.10 
Converting to Controller based AP. Will automatically reboot when done.
34:fc:b9:cb:61:9c# 

However it appears to find a Master at 161.111.84.4?

172.16.255.152 255.255.0.0 172.16.255.3
Running ADP...Done. Master is 161.111.84.4
AP rebooted Thu Jan 1 08:03:13 UTC 1970; Image Upgrade Successful
shutting down watchdog process (nanny will restart it)...

I've seen this when the AP is looking for the aruba-master DNS record and is assigned public DNS servers. Do you have ADP enabled on the Controller if both the AP and Controller are in the same broadcast domain?

https://www.arubanetworks.com/techdocs/ArubaOS_85_Web_Help/Content/arubaos-solutions/access-points/enab-ctrl-disc.htm?Highlight=controller%20discovery

Hello,

I  have ADP enabled  if both the AP and Controller and are in the same broadcast domain.

Take into account that I do the same procedure for the 205 model with no problems.

Is this the below an IP of yours? This is where the AP is attempting to locate its master. Have you tried a factory reset of the AP?

161.111.84.4

These are the steps I follow:

in apboot mode:

purgeenv

clear os

save

factory_reset

boot

Then after booting:

admin

enable

convert-aos-ap cap 172.16.255.10 (private contoller address) 

Do you have enough licenses available? YES 

Are the APs allowed authorized, or Cert Autoprovisioning enabled? YES