Wireless Access

Hi, 

i am trying to migrate/provision a 303H from our 6.5 cluster to our new 8.5 cluster. I can see the 303H connecting to the 8.5 but getting this error.

An internal system error has occurred at file sapm_ap_mgmt.c function sapm_proc_hello_req line 18034 error AP: Test-AP image version mismatch. bootfile is ipq40xx.ari, build string is ArubaOS version 6.5.4.6 for 30x (p4build@pr-hpn-build07) (gcc version 4.6.3) #63925 SMP Tue Mar 6 17:52:57 UTC 2018.

Then after some time, the AP will come back up on our 6.5 cluster.

Thanks in advance!

Daniel

Have you tried to reset the 303H to factory default?
What kind of controller are you using with 8.x?

Do you see any log entries on the AOS8.x controller?

How do you provision the 303H to the Controller?

Hi, 

thanks for the reply:

- I can´t reset it, because it is in one of our remote locations.

- 7010

- 

Mar  4 08:43:52  stm[3749]: <399803> <3749> <ERRS> |stm|  An internal system error has occurred at file sapm_ap_mgmt.c function sapm_proc_hello_req line 18034 error AP: Test-AP image version mismatch. bootfile is ipq40xx.ari, build string is ArubaOS version 6.5.4.6 for 30x (p4build@pr-hpn-build07) (gcc version 4.6.3) #63925 SMP Tue Mar 6 17:52:57 UTC 2018.
Mar  4 08:45:07  sapd[1391]: <311002> <WARN> |AP Test-AP@169.254.1.118 sapd|  Rebooting: Reboot after successful image upgrade
Mar  4 08:49:19  sapd[4356]: <311002> <WARN> |AP Test-AP@169.254.1.119 sapd|  Rebooting: Rebooting after provisioning

 - Over the 6.5 Gui, AP Installation -> Provision -> Under Master Controller IP Address/DNS name i suplly the IP of the new controller

What makes me wonder is the self signed IP Address.

169.254.x.x addresses are self-assigned by the clients when they fail to receive an IP address after a DHCP request. 

Do you use Activate or DHCP Option 43 for Provisioning?

Have you followed this instruction on AOS9 Controller - https://www.flomain.de/2019/05/basic-rap-setup-with-arubaos-8/

?

Does the Controller have licenses installed?

Have you set the Whitelist for that AP?

We are using those 169er adresses as our internal RAP pool. 

Normally we use Activate. There i can see, that the RAP is in the correct group and should get the new cluster IP. 

Licenses are plenty available and i have already checked the whitelist. 

I can see the AP for our short time in the new cluster, then after the image upgrade it jumps back to the old cluster. New devices can be connected to the new cluster without problems.

For me it looks like the RAP has still configurations in his AP System Environment.

I would suggest to do a Factory Reset on that AP by the Reset button.

Anybody near that AP who can do this?

Additionally what is in Activate configured? 

Convert to RAP and new Controller IP?

Some feedback to your questions:

- I tried the provisioning with a RAP fresh out of the box and it worked like a charm with Activate.

- We resetted the old RAP, got some Provision Request Notifications from Activate and then it reverted back to the old controller. 

- Yes, we do a IAP-to-RAP with the new cluster IP. 

Did you ever resolve this without factory defaulting the RAP(s)?