Wireless Access

Reply
Occasional Contributor II

AP status Is Down, With No network Issue

Happy New Year Everyone,

 

RIght now our Aruba facing another anomaly that never happen before. All of sudden all AP under the same subnet is down while all Network connectivity in l2 and l3 is Ok. We can ping the AP from controller. But the AP status and Ipsec is down. I dunno what happen, spending time asking our local partner just receive some unsatisfied answer. Anyone in here have experience with this kind of problem and How to fix this.

 

=============================================================

Re: AP status Is Down, With No network Issue

 

Has anything changed recently on your wired network or wireless network?

 

Please check the following under the master controller :

 

- show log errorlog all | include <one of the APs mac address>

- show log system all

 

See if you can console into one of the APs and see the booting process

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor II

Re: AP status Is Down, With No network Issue

show log errorlog all | include <one of the APs mac address> , no result for the spesific mac address.

 

Here is the show log system all for the specific AP Name

 

(Master-BIT-aruba) #show log system all | include JKTS
Dec 10 13:46:53 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.12 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:47:06 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-01@1.1.1.16 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:47:12 :326085:  <WARN> |AP JKTS-MegaKung-FoodCourt-ODR-02@1.1.1.17 sap                                                                                        d|  AM: Setting collection of statistics to : enabled
Dec 10 13:47:15 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-01@1.1.1.15 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:47:20 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-01@1.1.1.18 sapd                                                                                        |  AM: Setting collection of statistics to : enabled
Dec 10 13:47:39 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.19 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:47:48 :326085:  <WARN> |AP JKTS-MegaKung-FoodCourt-ODR-01@1.1.1.22 sap                                                                                        d|  AM: Setting collection of statistics to : enabled
Dec 10 13:48:21 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-03@1.1.1.26 sapd                                                                                        |  AM: Setting collection of statistics to : enabled
Dec 10 13:49:00 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-02@1.1.1.38 sapd                                                                                        |  AM: Setting collection of statistics to : enabled
Dec 10 13:50:23 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-02@1.1.1.55 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:50:31 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-03@1.1.1.62 sapd|                                                                                          AM: Setting collection of statistics to : enabled
Dec 10 13:50:35 :326085:  <WARN> |AP JKTS-MegaKung-FoodCourt-ODR-03@1.1.1.61 sapd|  AM: Setting collection of statistics to : enabled
Dec 12 12:31:44 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.224 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:08:43 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-01@1.1.1.252 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:08:43 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.253 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:27 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-01@1.1.1.2 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:28 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-03@1.1.1.254 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:28 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-03@1.1.1.4 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:29 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-02@1.1.1.1 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:29 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-02@1.1.1.5 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:31 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.3 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:09:34 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-01@1.1.1.7 sapd|  AM: Setting collection of statistics to : enabled
Dec 14 23:15:13 :311005:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.253 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 15 01:30:00 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.8 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:37:54 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.96 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:03 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-03@1.1.1.97 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:06 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-02@1.1.1.98 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:12 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-03@1.1.1.100 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:14 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-01@1.1.1.107 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:18 :326085:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-01@1.1.1.99 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:23 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.111 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:28 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-01@1.1.1.112 sapd|  AM: Setting collection of statistics to : enabled
Dec 15 22:38:32 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-02@1.1.1.110 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 10:13:05 :311005:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.96 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 10:15:53 :311005:  <WARN> |AP JKTS-MegaKung-FoodCourt-ODR-02@1.1.1.87 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 10:15:54 :311005:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.74 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 10:16:12 :311005:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-02@1.1.1.89 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 10:16:24 :311005:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-01@1.1.1.100 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 10:52:47 :311005:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-03@1.1.1.90 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Dec 23 12:49:00 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-01@1.1.1.17 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 12:49:01 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.18 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 12:49:11 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-02@1.1.1.24 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 12:49:47 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-03@1.1.1.19 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 12:49:48 :326085:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-01@1.1.1.22 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 12:52:52 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.25 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 14:48:18 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-02@1.1.1.29 sapd|  AM: Setting collection of statistics to : enabled
Dec 23 14:49:03 :326085:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.30 sapd|  AM: Setting collection of statistics to : enabled
Jan 4 06:18:09 :311005:  <WARN> |AP JKTS-MegaKung-TheEast-ODR-03@1.1.1.20 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Jan 4 06:19:03 :311005:  <WARN> |AP JKTS-MegaKung-Oakwood-ODR-03@1.1.1.17 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
Jan 4 14:34:39 :311005:  <WARN> |AP JKTS-MegaKung-Bellagio-ODR-01@1.1.1.75 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping

(Master-BIT-aruba) #

=============================================================

Occasional Contributor II

Re: AP status Is Down, With No network Issue

Finally I found  a way to solve this problem, while desperately waiting for help from this forum and local partner.

Here is the step I've done :

 

- deleted the vlan that used by down AP .

- re add the vlan

- re add the IP address

- last, this is when I realize what the problem truly are. Check in the Configuration Advanced Services > Redundancy, your controller operational state in every subnet and vlan use for AP management. In my current environment. We have 3 subnet for 3 different region. Turns out one from three subnet in our master controller operational state as BACKUP. And cause all the RAP under the subnet down. maybe because the secondary contoller didn't accept the AP, because the master is UP.

After knowing the vlan redundancy operational state is BACKUP, I deleted it from virtual routing table. And suddenly it's reappear and stated as MASTER. No need to re add the vlan in the redundancy virtual router table.

 

That's it, and problem solved.

 

 

Cheers.

=============================================================

New Contributor

Re: AP status Is Down, With No network Issue

I have a similar problem, except in my case only one single AP is down in a particular subnet.

This was working fine until today, and no changes have been made to any configuration.

 

I cannot delete this subnet as it has multiple AP's connected to it that is workinfg fine, and it is in use all the time.

 

I tried changing the fault AP with a new one that was not priorly configured, but this AP did not show up in the Management Central, and the Fault message related to the prior AP is still present.

 

How can I go about solving this issue?

 

 

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