Controllerless Networks

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

Hey, to confirm this IAPs have previously been part of the cluster and working as expect? 

Can you confirm the IAPs are allowed to join the cluster?

show allowed-aps

Can you confirm if there is any regulatory domain issues when running the follow:

show ap allowed-channels

Can you also post the swarm state from the problematic AP please?

show swarm state
show swarm mode

Feel free to also attach the logs/tech-support from the problematic IAPs with any sensitive information remove :)

Cheers,
Craig

Thanks for the reply!

 

Confirming both APs had been in-use in this cluster since install in 2015 and were working normally until last week.

 

To note, when logging into one problematic AP I see the warning:

Warning: CLI module is running in a degraded state. Configuration, write memory, and support command are disabled; please debug with caution.

Running commands via console from problematic AP:

 

show allowed-aps:

Allow New APs :disable
AP Whitelist
------------
MAC Address
-----------

show ap allowed-channels:

Allowed Channels for AP Type 215 Country Code US
------------------------------------------------
PHY Type Allowed Channels
-------- ----------------
802.11g (indoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (indoor) 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
802.11g (outdoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (outdoor) 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
802.11g 40MHz (indoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (indoor) 36-40 44-48 52-56 60-64 100-104 108-112 116-120 124-128 132-136 140-144 149-153 157-161
802.11g 40MHz (outdoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (outdoor) 36-40 44-48 52-56 60-64 100-104 108-112 116-120 124-128 132-136 140-144 149-153 157-161
802.11a 80MHz (indoor) 36-48 52-64 100-112 116-128 132-144 149-161
802.11a 80MHz (outdoor) 36-48 52-64 100-112 116-128 132-144 149-161
802.11a 160MHz (indoor) None
802.11a 160MHz (outdoor) None
802.11a (DFS) 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144

show swarm state:

AP Swarm State :swarm_image_ok
mesh auto eth0 bridging :no
Config in flash :no
factory SSID in flash :no
extended-ssid configured :no
extended-ssid active :yes
Factory default stat :yes
Config load cnt :0
VC Channel index :0
IDS Client Gateway Detect :yes
Config Init success cnt for heartbeat :0
Config Init success cnt for register :0
Config Init skipping cnt for heartbeat :0
Config Init skipping cnt for register :0
Config Init last success reason :N/A
Config Init last success time :N/A

show swarm mode:

Swarm Mode :Cluster

Running same commands via SSH from a properly functioning AP in the cluster:

 

show allowed-aps:

Allow New APs :enable
AP Whitelist
------------
MAC Address
-----------
xxx:94 <- Problematic AP #1
xxx:84
xxx:5c
xxx:56
xxx:8e
xxx:5a
xxx:04
xxx:0c
xxx:00
xxx:6c
xxx:80
xxx:36
xxx:78
xxx:7e
xxx:2e
xxx:90 <- Problematic AP #2

show ap allowed-channels:

Allowed Channels for AP Type 215 Country Code US
------------------------------------------------
PHY Type Allowed Channels
-------- ----------------
802.11g (indoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (indoor) 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
802.11g (outdoor) 1 2 3 4 5 6 7 8 9 10 11
802.11a (outdoor) 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
802.11g 40MHz (indoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (indoor) 36-40 44-48 52-56 60-64 100-104 108-112 116-120 124-128 132-136 140-144 149-153 157-161
802.11g 40MHz (outdoor) 1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (outdoor) 36-40 44-48 52-56 60-64 100-104 108-112 116-120 124-128 132-136 140-144 149-153 157-161
802.11a 80MHz (indoor) 36-48 52-64 100-112 116-128 132-144 149-161
802.11a 80MHz (outdoor) 36-48 52-64 100-112 116-128 132-144 149-161
802.11a 160MHz (indoor) None
802.11a 160MHz (outdoor) None
802.11a (DFS) 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144

show swarm state:

AP Swarm State :swarm_config_sync_complete
mesh auto eth0 bridging :no
Config in flash :no
factory SSID in flash :no
extended-ssid configured :yes
extended-ssid active :yes
Factory default stat :no
Config load cnt :1
VC Channel index :13
IDS Client Gateway Detect :yes
Config Init success cnt for heartbeat :0
Config Init success cnt for register :1
Config Init skipping cnt for heartbeat :0
Config Init skipping cnt for register :6
Config Init last success reason :register
Config Init last success time :2018-09-16 17:32:06

show swarm mode:

Swarm Mode :Cluster

Any news on this issue.

We are experiencing the same issues.

Every time an access point boots it starts in degraded mode and will not turn on it's radio. Only solution now is to completely wipe the configuration and build it from scratch

Similar problem here, APs look fine in WebGUI but won't initilise radios...

------------------------------
Toby Setchfield
------------------------------

Original Message:
Sent: Feb 04, 2020 04:10 AM
From: Mark Driessen
Subject: Instant IAP 215 detects Master but won't enable radios/load VC config

Any news on this issue.

We are experiencing the same issues.

Every time an access point boots it starts in degraded mode and will not turn on it's radio. Only solution now is to completely wipe the configuration and build it from scratch