Hello. I have two Aruba IAP 215s who are failing to enable their radios or accept clients. I cannot determine if the issue is hardware, firmware on the APs, or the current VC/Master. Both APs had been in-use without issue since 2015 in the same cluster.
Summary: After being factory reset, these APs can detect there is an existing VC, correctly set their "Master IP Address" to the current Master, and appear visible in the VC web interface, but are never able to load the config from the Master and enable their radios.
Full details:
On boot, PWR light flashes green continuously and never turns solid. ENET light flashes green continuously. 5Ghz and 2.4Ghz radio lights never turn on.
In the VC web interface the APs appears in the AP list-view after booting and display the Mode, Spectrum, and Serial Number. Mode/Spectrum show as Monitor/Disabled at first, then change to Access/Enabled shortly after. Channel, Power, Utilization, and Noise for both radios is never displayed.
The AP radios never appear to turn on. Running "AP Tech Support Dump" from the VC web interface, I can see the following anomalies compared to the other APs:
- All other APs show the other 16 APs under "AP Whitelist" except these two (VC Allowed AP Table)
- All other APs show the Radius server except these two (AP Radius Status)
- One AP shows “AP checksum error” in log (however, in console output the firmware image appears to checksum fine)
- Both APs incorrectly show “Virtual Controller IP Address: 0.0.0.0" but do correctly show "Master IP Address: 10.4.1.X"
Viewing console, AP appears to boot but ends with this output:
<<<<< Welcome to the Access Point >>>>>
Completed SW FIPS KAT test
User: [ 127.307361] asap_send_elected_master: sent successfully
[ 128.222682] wait for stm to initialize over
[ 128.272733] asap_send_elected_master: sent successfully''
From apboot in console, I can type `factory_reset` to clear all AP settings, then 'dhcp' to obtain a DHCP lease, and then successfully `ping` the VC IP and Master AP IP.
I have factory-reset one of them. Attempting to re-add factory-reset AP to cluster produces identical results to AP which has existing settings prior to start of issue.
Any ideas would be appreciated, thank you,
Matt Crosby