Controllerless Networks

Reply
Highlighted
Occasional Contributor II

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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

Highlighted
Occasional Contributor II

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

Which screeshot you mean? 

Highlighted
Occasional Contributor II

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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 

Highlighted
MVP Guru

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Highlighted
Occasional Contributor II

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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.

Highlighted
MVP Guru

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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

 


ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)
Highlighted
Occasional Contributor II

Re: Problem when provisioning IAP-305-RW, as CAP, in OAW-4650 controller

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) 

 

 

 

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: