Wireless Access

Hello, 

 

I'm experiencing some strange behaviour. i've got some clients which result some disconnection...

 

I'm trying to understand... but i cannot that why i'm writing you..

 

Could you give some tips to start a client troubleshooting ?

 

The behaviour is : the client is connected... disconnected during 10/20s sometimes more... and the client is back.

 

the strange things is : sometimes, during the outages i wasn't unable to ping to client but i stayed connected over a teamveiwer..

 

I can get the disconnection even if the client doesn't move...

Most of the issues are on Android clients.

I'm trying some RF Optimization ( founded here) 

 

but i'm continue to get this disconnection...

 

i saw on the "process logs " a lot of  :

 

Dec 17 16:24:22	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21250 Sequence Num is 61962
Dec 17 16:24:22	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21249 Sequence Num is 61963
Dec 17 16:24:23	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21250 Sequence Num is 61962
Dec 17 16:24:23	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21249 Sequence Num is 61963
Dec 17 16:24:24	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21250 Sequence Num is 61962
Dec 17 16:24:24	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21249 Sequence Num is 61963
Dec 17 16:24:24	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21250 Sequence Num is 61962
Dec 17 16:24:24	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21249 Sequence Num is 61963
Dec 17 16:24:25	syslog: PAPI_Send: sendto SAPM Client failed: Connection refused Message Code 21250 Sequence Num is 61962

 

I'm starting to loose my latin..

 

Please help me.

 

Mika

What version of software?

Model:	Aruba7210
Version:	6.4.2.13
Compiled:	2015-10-26 at 17:33:42 PDT (build 52246) by p4build

Please see the article here:  http://community.arubanetworks.com/t5/Technology-Blog/Removing-the-Bottleneck-in-Wireless/ba-p/77978

i read this before, and the only things not thicks on my settings that i've question is :

 

- Enable Drop Broadcast and Multicast on all of your Virtual APs - Broadcast and multicast traffic punish wireless and are very rarely used for current applications today.  In addition, Airgroup (on by default) can forward and proxy mDNS and DLNA discovery packets with "drop broadcast and multicast" on to maintain performance.  This is the main reason users say that their wireless works one day and without any changes, it gets worse and worse.  In Aruba Instant it is setting the "Broadcast Filtering" parameter to ALL, under Advanced.  Dropping broadcast and multicast results in a huge improvement in performance and reduces phantom performance issues generated by devices that send out random broadcasts.

 

--> is it possble to get some disconnection for the clients with these options not enables ?

the strange things is :

 

The phone is connected by i'm not able to ping it... after a 10/20s i can be the phone again....

Yes, it is possible

Hello,

The situation after enable the options is better but I've still get some strange issues :

The phone is connected ( full Wi-Fi) but I'm not able to ping the device.. After a reboot of the phone I can ping again.

Any idea?

What changes have you made?

Hello, 

 

The situation seems to be better after enable the options.

 

However, i still get an issue... something the phone is connected to the wifi ( connection internet OK - check browser ok ) bui the phone are not able to reach the local ressources... and after a few minutes the phone is back to reach out the server...

 

I don't understand why...

 

Any idea ?

How many access points do you have?
What band does the phone operate on?
What is the transmit power of your access points on that band? (Give is the output of "show AP active").

Hello, 

 

Thanks for the answers :

 

How many access points do you have?

-> 129 AP 
What band does the phone operate on?

-> 2.4 ghz ( we are not able to use the 5ghz because we've got big big wall.. and only the 2.4ghz works)

 

below the result of the command : 

 

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
9c:1c:12:ca:b2:91 elone 172.18.10.143 0 AP:HT:1/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:47m:16s N/A
9c:1c:12:ca:ae:c3 elone 172.18.10.147 1 AP:HT:1/15/19 0 AP:HT:44+/21/22 105 daKr 161d:4h:22m:25s N/A
9c:1c:12:ca:ae:48 elone 172.18.10.163 0 AP:HT:1/15/19 0 AP:HT:100+/21/24 105 daKr 35d:11h:58m:25s N/A
9c:1c:12:ca:b5:d1 elone 172.18.10.52 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 5d:23h:35m:40s N/A
9c:1c:12:ca:be:12 elone 172.18.10.175 0 AP:HT:11/15/19 1 AP:HT:124+/21/24 105 daKr 43d:3h:57m:50s N/A
9c:1c:12:ca:ac:ee elone 172.18.10.56 0 AP:HT:1/15/19 1 AP:HT:132+/21/24 105 daKr 162d:6h:9m:26s N/A
AP-Refectoire:ce:95:0a elone 172.18.10.191 0 AP:HT:11/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:49m:37s N/A
9c:1c:12:ca:b1:4a elone 172.18.10.92 0 AP:HT:11/15/19 0 AP:HT:124+/24/24 105 daKr 173d:1h:46m:27s N/A
9c:1c:12:ca:b5:ed elone 172.18.10.80 1 AP:HT:6/15/19 0 AP:HT:60+/22/22 105 daKr 1h:8m:56s N/A
9c:1c:12:ca:ac:90 elone 172.18.10.76 1 AP:HT:6/15/19 0 AP:HT:116+/24/24 105 daKr 173d:1h:48m:57s N/A
9c:1c:12:ca:ad:05 elone 172.18.10.64 1 AP:HT:6/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:48m:40s N/A
9c:1c:12:ca:ac:a7 elone 172.18.10.124 1 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:51m:57s N/A
9c:1c:12:ca:ac:80 elone 172.18.10.112 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:50m:46s N/A
9c:1c:12:ca:ab:f4 elone 172.18.10.108 0 AP:HT:11/18/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:52m:10s N/A
9c:1c:12:ca:aa:5a elone 172.18.10.96 0 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 3h:54m:41s N/A
9c:1c:12:ca:bd:66 elone 172.18.10.132 0 AP:HT:1/15/19 0 AP:HT:124+/21/24 105 daKr 57m:56s N/A
9c:1c:12:ca:aa:09 elone 172.18.10.136 0 AP:HT:11/15/19 0 AP:HT:116+/24/24 105 daKr 173d:1h:46m:57s N/A
9c:1c:12:ca:b0:55 elone 172.18.10.148 1 AP:HT:1/15/19 0 AP:HT:108+/21/24 105 daKr 173d:1h:50m:31s N/A
9c:1c:12:ca:b2:a8 elone 172.18.10.152 0 AP:HT:11/15/19 0 AP:HT:108+/21/24 105 daKr 10d:0h:9m:53s N/A
9c:1c:12:ca:ac:65 elone 172.18.10.164 2 AP:HT:6/15/19 0 AP:HT:116+/24/24 105 daKr 173d:1h:45m:51s N/A
9c:1c:12:ca:af:ab elone 172.18.10.51 1 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 139d:21h:41m:49s N/A
9c:1c:12:ca:ac:4d elone 172.18.10.63 2 AP:HT:11/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:48m:10s N/A
9c:1c:12:ca:ab:d5 elone 172.18.10.168 0 AP:HT:6/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:49m:15s N/A
9c:1c:12:ca:ae:55 elone 172.18.10.180 0 AP:HT:6/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:52m:4s N/A
9c:1c:12:ca:ab:b4 elone 172.18.10.184 0 AP:HT:1/15/19 0 AP:HT:108+/21/24 105 daKr 173d:1h:49m:52s N/A
9c:1c:12:ca:be:28 elone 172.18.10.91 0 AP:HT:1/15/19 0 AP:HT:44+/21/22 105 daKr 173d:1h:54m:26s N/A
9c:1c:12:ca:b5:e3 elone 172.18.10.87 2 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 145d:22h:52m:49s N/A
9c:1c:12:ca:ab:68 elone 172.18.10.75 0 AP:HT:1/15/19 0 AP:HT:36+/21/22 105 daKr 173d:1h:49m:11s N/A
9c:1c:12:ca:bd:e1 elone 172.18.10.71 0 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:48m:57s N/A
9c:1c:12:ca:b5:56 elone 172.18.10.123 2 AP:HT:6/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:48m:36s N/A
9c:1c:12:ca:af:21 elone 172.18.10.119 0 AP:HT:6/15/19 0 AP:HT:100+/21/24 105 daKr 15d:7h:39m:36s N/A
9c:1c:12:ca:ab:92 elone 172.18.10.107 1 AP:HT:11/15/19 0 AP:HT:44+/21/22 105 daKr 173d:1h:51m:9s N/A
9c:1c:12:ca:b0:a3 elone 172.18.10.103 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:52m:22s N/A
9c:1c:12:ca:bd:7a elone 172.18.10.133 1 AP:HT:6/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:52m:26s N/A
9c:1c:12:ca:aa:75 elone 172.18.10.137 0 AP:HT:11/15/19 0 AP:HT:36+/21/22 105 daKr 173d:1h:52m:31s N/A
9c:1c:12:ca:ac:b9 elone 172.18.10.149 0 AP:HT:6/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:46m:57s N/A
9c:1c:12:ca:b6:8c elone 172.18.10.153 0 AP:HT:6/15/19 0 AP:HT:52+/21/22 105 daKr 15d:14h:30m:27s N/A
9c:1c:12:ca:b6:2a elone 172.18.10.165 0 AP:HT:11/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:49m:54s N/A
EXT-06:40:e8 Outdoor 172.18.10.50 0 AP:HT:11/15/19 0 275 AdaKr 173d:1h:52m:23s N/A
9c:1c:12:ca:bd:86 elone 172.18.10.62 0 AP:HT:1/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:48m:4s N/A
EXT-01:7b:24 Outdoor 172.18.10.181 0 AP:HT:1/15/19 0 114 odaKr 80d:10h:37m:27s N/A
9c:1c:12:ca:ac:8e elone 172.18.10.185 0 AP:HT:11/15/19 0 AP:HT:124+/21/24 105 daKr 139d:20h:6m:15s N/A
9c:1c:12:ca:ab:d7 elone 172.18.10.90 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 8d:3h:53m:6s N/A
9c:1c:12:ca:b6:51 elone 172.18.10.86 1 AP:HT:11/15/19 0 AP:HT:60+/21/22 105 daKr 159d:23h:31m:27s N/A
9c:1c:12:ca:aa:c6 elone 172.18.10.74 1 AP:HT:6/15/19 0 AP:HT:60+/21/22 105 daKr 38d:8h:30m:43s N/A
9c:1c:12:ca:b0:08 elone 172.18.10.209 0 AP:HT:6/15/19 0 AP:HT:36+/21/22 105 daKr 1d:1h:8m:58s N/A
9c:1c:12:ca:b1:3d elone 172.18.10.70 0 AP:HT:11/15/19 0 AP:HT:124+/24/24 105 daKr 173d:1h:46m:46s N/A
9c:1c:12:ca:ab:ce elone 172.18.10.122 0 AP:HT:1/15/19 1 AP:HT:100+/21/24 105 daKr 173d:1h:50m:32s N/A
9c:1c:12:ca:be:b8 elone 172.18.10.118 0 AP:HT:11/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:51m:12s N/A
9c:1c:12:ca:aa:b6 elone 172.18.10.106 0 AP:HT:6/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:52m:9s N/A
9c:1c:12:ca:c0:44 elone 172.18.10.102 0 AP:HT:1/15/19 0 AP:HT:44+/21/22 105 daKr 76d:22h:19m:8s N/A
9c:1c:12:ca:ac:d2 elone 172.18.10.130 0 AP:HT:1/15/19 0 AP:HT:44+/21/22 105 daKr 173d:1h:46m:20s N/A
9c:1c:12:ca:b7:0c elone 172.18.10.158 0 AP:HT:6/15/19 0 AP:HT:60+/21/22 105 daKr 24d:17h:8m:0s N/A
9c:1c:12:ca:ac:37 elone 172.18.10.53 1 AP:HT:1/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:52m:20s N/A
9c:1c:12:ca:ac:ea elone 172.18.10.162 0 AP:HT:11/15/19 0 AP:HT:60+/21/22 105 daKr 19d:22h:25m:42s N/A
9c:1c:12:ca:b6:05 elone 172.18.10.174 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:49m:56s N/A
EXT-13:7a:fc Outdoor 172.18.10.57 0 AP:HT:1/15/19 0 114 odaKr 173d:1h:52m:11s N/A
EXT-08:65:a4 Outdoor 172.18.10.178 0 AP:HT:11/15/19 0 114 odaKr 60d:22h:14m:38s N/A
EXT-07:40:52 Outdoor 172.18.10.190 0 AP:HT:11/15/19 0 275 AdaKr 173d:1h:52m:23s N/A
9c:1c:12:ca:af:a0 elone 172.18.10.93 1 AP:HT:6/15/19 0 AP:HT:52+/21/22 105 daKr 12d:14h:59m:49s N/A
9c:1c:12:ca:b2:50 elone 172.18.10.81 0 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 4d:0h:0m:26s N/A
9c:1c:12:ca:ab:63 elone 172.18.10.77 1 AP:HT:11/15/19 0 AP:HT:116+/21/24 105 daKr 173d:1h:53m:44s N/A
9c:1c:12:ca:b7:83 elone 172.18.10.65 0 AP:HT:6/15/19 0 AP:HT:36+/21/22 105 daKr 152d:20h:58m:36s N/A

Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
A = Enet1 in active/standby mode; B = Battery Boost On; C = Cellular;
D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x authentication;
H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M = Mesh;
N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
S = AP connected as standby; X = Maintenance Mode;
a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Cert RAP;
i = Provisioned as Indoor; o = Provisioned as Outdoor;
r = 802.11r Enabled

Channel followed by "*" indicates channel selected due to unsupported configured channel.
"Spectrum" followed by "^" indicates Local Spectrum Override in effect.

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
9c:1c:12:ca:b4:e5 elone 172.18.10.125 0 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:53m:14s N/A
9c:1c:12:ca:bd:ed elone 172.18.10.113 0 AP:HT:1/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:51m:56s N/A
EXT-10:65:b8 Outdoor 172.18.10.109 0 AP:HT:1/15/19 0 114 odaKr 173d:1h:51m:15s N/A
9c:1c:12:ca:aa:06 elone 172.18.10.97 0 AP:HT:6/15/19 0 AP:HT:36+/21/22 105 daKr 173d:1h:50m:17s N/A
9c:1c:12:ca:aa:cb elone 172.18.10.135 1 AP:HT:1/15/19 0 AP:HT:36+/21/22 105 daKr 173d:1h:49m:6s N/A
9c:1c:12:ca:ac:8f elone 172.18.10.139 2 AP:HT:6/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:52m:34s N/A
9c:1c:12:ca:bd:9b elone 172.18.10.151 0 AP:HT:6/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:50m:8s N/A
9c:1c:12:ca:b5:3d elone 172.18.10.155 8 AP:HT:6/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:46m:53s N/A
9c:1c:12:ca:ac:4b elone 172.18.10.167 1 AP:HT:6/15/19 1 AP:HT:36+/21/22 105 daKr 173d:1h:52m:31s N/A
9c:1c:12:ca:b1:0c elone 172.18.10.60 0 AP:HT:1/15/19 0 AP:HT:52+/21/22 105 daKr 161d:4h:57m:15s N/A
9c:1c:12:ca:c1:bc elone 172.18.10.171 0 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 163d:1h:43m:41s N/A
9c:1c:12:ca:ab:fe elone 172.18.10.183 0 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:46m:31s N/A
9c:1c:12:ca:ad:06 elone 172.18.10.88 3 AP:HT:11/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:53m:47s N/A
9c:1c:12:ca:aa:3e elone 172.18.10.72 0 AP:HT:6/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:48m:6s N/A
9c:1c:12:ca:b6:18 elone 172.18.10.68 0 AP:HT:1/15/19 0 AP:HT:108+/21/24 105 daKr 173d:1h:48m:44s N/A
9c:1c:12:ca:b6:0b elone 172.18.10.120 0 AP:HT:11/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:47m:56s N/A
9c:1c:12:ca:ab:5e elone 172.18.10.104 0 AP:HT:11/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:51m:52s N/A
9c:1c:12:ca:ab:dc elone 172.18.10.100 0 AP:HT:11/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:52m:32s N/A
9c:1c:12:ca:b6:64 elone 172.18.10.128 0 AP:HT:11/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:48m:10s N/A
9c:1c:12:ca:ac:10 elone 172.18.10.140 0 AP:HT:1/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:50m:17s N/A
9c:1c:12:ca:b6:02 elone 172.18.10.144 1 AP:HT:6/15/19 0 AP:HT:116+/21/24 105 daKr 8d:18h:25m:24s N/A
9c:1c:12:ca:ab:cd elone 172.18.10.156 1 AP:HT:11/15/19 0 AP:HT:124+/24/24 105 daKr 173d:1h:46m:49s N/A
9c:1c:12:ca:b5:cf elone 172.18.10.55 0 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 161d:5h:33m:40s N/A
EXT-03:7b:42 Outdoor 172.18.10.160 0 AP:HT:1/15/19 0 114 odaKr 9d:2h:1m:32s N/A
9c:1c:12:ca:ab:77 elone 172.18.10.59 0 AP:HT:11/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:53m:31s N/A
9c:1c:12:ca:ad:7d elone 172.18.10.172 1 AP:HT:1/15/19 0 AP:HT:108+/21/24 105 daKr 173d:1h:52m:30s N/A
9c:1c:12:ca:b1:57 elone 172.18.10.176 1 AP:HT:1/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:51m:10s N/A
9c:1c:12:ca:ac:74 elone 172.18.10.95 0 AP:HT:1/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:49m:18s N/A
9c:1c:12:ca:b1:2e elone 172.18.10.83 0 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 159d:22h:34m:43s N/A
9c:1c:12:ca:ab:a1 elone 172.18.10.115 3 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 50d:0h:7m:7s N/A
9c:1c:12:ca:ad:37 elone 172.18.10.111 0 AP:HT:1/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:50m:12s N/A
9c:1c:12:ca:b6:b7 elone 172.18.10.99 1 AP:HT:1/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:54m:16s N/A
9c:1c:12:ca:ab:2b elone 172.18.10.129 1 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:55m:16s N/A
9c:1c:12:ca:c0:6b elone 172.18.10.141 1 AP:HT:6/15/19 0 AP:HT:60+/21/22 105 daKr 173d:1h:48m:55s N/A
9c:1c:12:ca:aa:9a elone 172.18.10.145 0 AP:HT:1/15/19 1 AP:HT:60+/22/22 105 daKr 173d:1h:48m:42s N/A
EXT-05:7b:40 Outdoor 172.18.10.161 0 AP:HT:1/15/19 0 114 odaKr 173d:1h:51m:1s N/A
9c:1c:12:ca:bd:e8 elone 172.18.10.54 0 AP:HT:11/15/19 0 AP:HT:36+/21/22 105 daKr 173d:1h:52m:30s N/A
9c:1c:12:ca:b6:e1 elone 172.18.10.173 0 AP:HT:1/15/19 0 AP:HT:36+/22/22 105 daKr 39m:2s N/A
EXT-12:7b:2a Outdoor 172.18.10.58 0 AP:HT:11/15/19 0 114 odaKr 173d:1h:52m:31s N/A
EXT-15:7a:c8 Outdoor 172.18.10.177 1 AP:HT:1/15/19 0 114 odaKr 173d:1h:42m:19s N/A
EXT-09:7a:c2 Outdoor 172.18.10.189 0 AP:HT:6/15/19 0 114 daKr 173d:1h:50m:44s N/A
9c:1c:12:ca:b0:47 elone 172.18.10.94 0 AP:HT:1/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:51m:51s N/A
9c:1c:12:ca:aa:6c elone 172.18.10.82 0 AP:HT:6/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:53m:33s N/A
9c:1c:12:ca:b4:67 elone 172.18.10.78 0 AP:HT:1/15/19 0 AP:HT:60+/21/22 105 daKr 53d:16h:3m:35s N/A
9c:1c:12:ca:ab:b2 elone 172.18.10.66 1 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 14d:21h:54m:8s N/A
9c:1c:12:ca:be:ac elone 172.18.10.126 2 AP:HT:11/15/19 0 AP:HT:108+/21/24 105 daKr 173d:1h:47m:58s N/A
9c:1c:12:ca:b1:31 elone 172.18.10.114 0 AP:HT:11/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:52m:30s N/A
EXT-11:7b:3c Outdoor 172.18.10.110 0 AP:HT:1/15/19 0 114 odaKr 173d:1h:49m:22s N/A
EXT-14:40:5e Outdoor 172.18.10.98 0 AP:HT:11/15/19 0 275 AdaKr 173d:1h:52m:43s N/A
9c:1c:12:ca:b5:08 elone 172.18.10.134 2 AP:HT:1/15/19 1 AP:HT:36+/21/22 105 daKr 8d:19h:36m:22s N/A
9c:1c:12:ca:b6:a4 elone 172.18.10.138 0 AP:HT:1/15/19 0 AP:HT:132+/21/24 105 daKr 14d:22h:10m:38s N/A
9c:1c:12:ca:b5:62 elone 172.18.10.154 2 AP:HT:11/15/19 0 AP:HT:108+/21/24 105 daKr 161d:4h:39m:17s N/A
9c:1c:12:ca:b5:e7 elone 172.18.10.166 0 AP:HT:6/15/19 0 AP:HT:100+/21/24 105 daKr 32d:21h:57m:51s N/A
9c:1c:12:ca:a9:83 elone 172.18.10.61 1 AP:HT:6/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:50m:7s N/A
9c:1c:12:ca:b9:16 elone 172.18.10.170 0 AP:HT:1/15/19 0 AP:HT:100+/21/24 105 daKr 173d:1h:52m:29s N/A
EXT-04:7b:2c Outdoor 172.18.10.182 0 AP:HT:6/15/19 0 114 odaKr 173d:1h:43m:59s N/A
EXT-02:d9:58 Outdoor 172.18.10.186 1 AP:HT:11/15/19 0 275 AdaKr 173d:1h:52m:26s N/A
9c:1c:12:ca:ab:ca elone 172.18.10.89 0 AP:HT:6/15/19 0 AP:HT:124+/21/24 105 daKr 173d:1h:51m:42s N/A
9c:1c:12:ca:ab:88 elone 172.18.10.85 0 AP:HT:11/15/19 0 AP:HT:44+/21/22 105 daKr 8d:4h:7m:41s N/A
9c:1c:12:ca:b2:63 elone 172.18.10.73 1 AP:HT:1/15/19 0 AP:HT:124+/21/24 105 daKr 24d:22h:35m:27s N/A
9c:1c:12:ca:b6:69 elone 172.18.10.69 9 AP:HT:11/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:54m:7s N/A
9c:1c:12:ca:ab:90 elone 172.18.10.121 0 AP:HT:11/15/19 0 AP:HT:132+/21/24 105 daKr 173d:1h:52m:14s N/A
9c:1c:12:ca:b7:c0 elone 172.18.10.117 1 AP:HT:1/15/19 0 AP:HT:52+/21/22 105 daKr 173d:1h:52m:1s N/A

Flags: 1 = 802.1x authenticated AP; 2 = Using IKE version 2;
A = Enet1 in active/standby mode; B = Battery Boost On; C = Cellular;
D = Disconn. Extra Calls On; E = Wired AP enabled; F = AP failed 802.1x authentication;
H = Hotspot Enabled; K = 802.11K Enabled; L = Client Balancing Enabled; M = Mesh;
N = 802.11b protection disabled; P = PPPOE; R = Remote AP;
S = AP connected as standby; X = Maintenance Mode;
a = Reduce ARP packets in the air; d = Drop Mcast/Bcast On; u = Custom-Cert RAP;
i = Provisioned as Indoor; o = Provisioned as Outdoor;
r = 802.11r Enabled

Channel followed by "*" indicates channel selected due to unsupported configured channel.
"Spectrum" followed by "^" indicates Local Spectrum Override in effect.

Active AP Table
---------------
Name Group IP Address 11g Clients 11g Ch/EIRP/MaxEIRP 11a Clients 11a Ch/EIRP/MaxEIRP AP Type Flags Uptime Outer IP
---- ----- ---------- ----------- ------------------- ----------- ------------------- ------- ----- ------ --------
9c:1c:12:ca:ab:29 elone 172.18.10.105 1 AP:HT:6/15/19 0 AP:HT:44+/21/22 105 daKr 29d:13h:0m:37s N/A
9c:1c:12:ca:ab:12 elone 172.18.10.101 1 AP:HT:6/15/19 0 AP:HT:40-/21/22 105 daKr 173d:1h:47m:53s N/A

 

 

Your AP power on the 2.4ghz band looks like 15, which is not bad.  Choose an AP that you are having problems with and give me the output of "show ap arm state ap-name <name of ap>"

 

 

it's not related to one AP... it could work on this AP and few times not..

 

I'll give you the outpout of many aps :

 

show ap arm state ap-name 9c:1c:12:ca:aa:9a

AP:9c:1c:12:ca:aa:9a MAC:9c:1c:12:2a:a9:a8 Channel:60 EIRP:22 Max EIRP:22 Edge:enable
Client Density:0 Valid neighbors: 14 Relevant neighbors: 1 Rx Probe Reports: 189
Moves(T/S):0/0 Sticky(T/S):0/0 Bandsteer(T/S):0/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:b4:67 172.18.10.78 9 112 60/21 0 1/22
9c:1c:12:ca:ac:8f 172.18.10.139 34 99 116/21 0 1/28
9c:1c:12:ca:ac:10 172.18.10.140 39 79 60/21 0 0/16 Yes
9c:1c:12:ca:ad:37 172.18.10.111 23 100 52/21 0 0/10
9c:1c:12:ca:b9:03 172.18.10.127 15 103 100/21 0 2/24
9c:1c:12:ca:ab:90 172.18.10.121 27 91 132/21 0 1/25
9c:1c:12:ca:ab:88 172.18.10.85 7 113 44/21 0 2/26
9c:1c:12:ca:b2:a8 172.18.10.152 15 108 108/21 0 0/15
9c:1c:12:ca:be:ac 172.18.10.126 16 102 108/21 0 1/9
9c:1c:12:ca:be:b8 172.18.10.118 13 109 40/21 0 3/19
9c:1c:12:ca:b5:56 172.18.10.123 16 98 124/21 0 2/21
9c:1c:12:ca:b2:63 172.18.10.73 4 112 124/21 0 1/8
9c:1c:12:ca:b5:62 172.18.10.154 5 110 108/21 0 2/26
9c:1c:12:ca:b6:0b 172.18.10.120 0 111 52/21 0 1/19
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

AP:9c:1c:12:ca:aa:9a MAC:9c:1c:12:2a:a9:a0 Channel:1 EIRP:15 Max EIRP:19 Edge:enable
Client Density:0 Valid neighbors: 46 Relevant neighbors: 0 Rx Probe Reports: 189
Moves(T/S):0/0 Sticky(T/S):0/0 Bandsteer(T/S):0/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:b4:67 172.18.10.78 12 98 1/15 0 4/36
9c:1c:12:ca:ad:37 172.18.10.111 28 100 1/15 0 2/28
9c:1c:12:ca:b2:63 172.18.10.73 12 106 1/15 0 3/36
9c:1c:12:ca:b6:a4 172.18.10.138 6 102 1/15 0 4/40
9c:1c:12:ca:ab:ce 172.18.10.122 18 95 1/15 0 1/38
9c:1c:12:ca:b5:56 172.18.10.123 21 101 6/15 0 5/34
9c:1c:12:ca:ae:c3 172.18.10.147 4 107 1/15 0 3/36
EXT-10:65:b8 172.18.10.109 6 103 1/15 0 10/40
9c:1c:12:ca:ac:d2 172.18.10.130 15 102 1/15 0 5/54
9c:1c:12:ca:b5:08 172.18.10.134 4 105 1/15 0 3/27
9c:1c:12:ca:ab:90 172.18.10.121 35 105 11/15 0 3/47
9c:1c:12:ca:bd:e8 172.18.10.54 19 100 11/15 0 2/32
9c:1c:12:ca:ac:8f 172.18.10.139 30 92 6/15 0 6/44
EXT-08:65:a4 172.18.10.178 20 93 11/15 0 5/43
EXT-07:40:52 172.18.10.190 13 100 11/15 0 8/34
9c:1c:12:ca:b7:c0 172.18.10.117 6 105 1/15 0 4/33
9c:1c:12:ca:aa:cb 172.18.10.135 7 104 1/15 0 5/46
EXT-11:7b:3c 172.18.10.110 6 104 1/15 0 6/29
9c:1c:12:ca:b5:62 172.18.10.154 20 99 11/15 0 5/45
9c:1c:12:ca:ac:10 172.18.10.140 29 91 1/15 0 5/38
9c:1c:12:ca:b2:91 172.18.10.143 3 105 1/15 0 4/47
EXT-04:7b:2c 172.18.10.182 8 107 6/15 0 8/37
9c:1c:12:ca:ab:88 172.18.10.85 10 108 11/15 0 5/47
9c:1c:12:ca:b2:a8 172.18.10.152 22 98 11/15 0 2/40
9c:1c:12:ca:aa:b6 172.18.10.106 7 106 6/15 0 3/18
9c:1c:12:ca:be:12 172.18.10.175 11 103 11/15 0 4/27
9c:1c:12:ca:be:b8 172.18.10.118 10 100 11/15 0 3/31
9c:1c:12:ca:ac:90 172.18.10.76 11 98 6/15 0 5/41
9c:1c:12:ca:be:ac 172.18.10.126 18 91 11/15 0 5/27
EXT-09:7a:c2 172.18.10.189 13 97 6/15 0 5/38

#show ap arm state ap-name 9c:1c:12:ca:ab:5e

AP:9c:1c:12:ca:ab:5e MAC:9c:1c:12:2a:b5:e0 Channel:11 EIRP:15 Max EIRP:19 Edge:disable
Client Density:0 Valid neighbors: 32 Relevant neighbors: 3 Rx Probe Reports: 45742
Moves(T/S):10/1 Sticky(T/S):3/1 Bandsteer(T/S):7/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
AP-Refectoire:ce:95:0a 172.18.10.191 43 76 11/15 0 3/40 Yes
9c:1c:12:ca:ac:ee 172.18.10.56 35 101 1/15 0 3/49
EXT-14:40:5e 172.18.10.98 27 84 11/15 0 18/54 Yes
9c:1c:12:ca:ab:a1 172.18.10.115 25 97 11/15 0 3/36
9c:1c:12:ca:ac:65 172.18.10.164 38 84 6/15 0 4/33 Yes
EXT-01:7b:24 172.18.10.181 19 92 1/15 0 6/48
9c:1c:12:ca:af:ab 172.18.10.51 12 103 11/15 0 1/16
EXT-02:d9:58 172.18.10.186 10 102 11/15 0 2/32
9c:1c:12:ca:b6:0b 172.18.10.120 10 103 11/15 0 5/51
9c:1c:12:ca:ab:92 172.18.10.107 18 103 11/15 0 2/35
EXT-15:7a:c8 172.18.10.177 14 98 1/15 0 12/48
9c:1c:12:ca:b1:3d 172.18.10.70 8 107 11/15 0 4/42
9c:1c:12:ca:b1:31 172.18.10.114 9 105 11/15 0 5/28
9c:1c:12:ca:ac:37 172.18.10.53 20 105 1/15 0 3/33
9c:1c:12:ca:b6:2a 172.18.10.165 6 104 11/15 0 3/30
9c:1c:12:ca:ac:4b 172.18.10.167 16 102 6/15 0 6/26
9c:1c:12:ca:ae:48 172.18.10.163 9 102 1/15 0 7/48
9c:1c:12:ca:b6:02 172.18.10.144 11 103 6/15 0 5/33
9c:1c:12:ca:ab:d5 172.18.10.168 7 101 6/15 0 4/35
9c:1c:12:ca:af:21 172.18.10.119 9 101 6/15 0 0/52
9c:1c:12:ca:b5:62 172.18.10.154 4 106 11/15 0 5/45
9c:1c:12:ca:ac:b9 172.18.10.149 10 99 6/15 0 7/43
9c:1c:12:ca:ad:7d 172.18.10.172 7 102 1/15 0 1/34
9c:1c:12:ca:b5:e7 172.18.10.166 6 104 6/15 0 3/26
9c:1c:12:ca:b6:05 172.18.10.174 6 104 11/15 0 3/34
9c:1c:12:ca:b6:e1 172.18.10.173 25 93 1/15 0 5/40
9c:1c:12:ca:bd:66 172.18.10.132 11 102 1/15 0 3/36
9c:1c:12:ca:bd:e1 172.18.10.71 8 101 1/15 0 7/42
9c:1c:12:ca:be:12 172.18.10.175 4 106 11/15 0 4/27
9c:1c:12:ca:b4:e5 172.18.10.125 5 105 11/15 0 4/49
9c:1c:12:ca:b1:4a 172.18.10.92 5 104 11/15 0 3/40
9c:1c:12:ca:ac:ea 172.18.10.162 5 105 11/15 0 3/42
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

AP:9c:1c:12:ca:ab:5e MAC:9c:1c:12:2a:b5:e8 Channel:52 EIRP:21 Max EIRP:22 Edge:enable
Client Density:0 Valid neighbors: 9 Relevant neighbors: 1 Rx Probe Reports: 29625
Moves(T/S):1/1 Sticky(T/S):1/1 Bandsteer(T/S):0/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:ac:ee 172.18.10.56 21 87 132/21 0 0/15 Yes
9c:1c:12:ca:af:ab 172.18.10.51 4 111 116/21 0 0/10
9c:1c:12:ca:ac:65 172.18.10.164 29 95 116/24 0 0/11
9c:1c:12:ca:ab:a1 172.18.10.115 14 110 100/21 0 1/8
AP-Refectoire:ce:95:0a 172.18.10.191 30 92 40/21 0 1/21
9c:1c:12:ca:ac:4b 172.18.10.167 13 111 36/21 0 0/14
9c:1c:12:ca:ad:7d 172.18.10.172 5 112 108/21 0 0/12
9c:1c:12:ca:ab:92 172.18.10.107 10 110 44/21 0 1/24
9c:1c:12:ca:b6:e1 172.18.10.173 14 111 36/21 0 1/13
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

show ap arm state ap-name 9c:1c:12:ca:ac:4d

AP:9c:1c:12:ca:ac:4d MAC:9c:1c:12:2a:c4:d0 Channel:11 EIRP:15 Max EIRP:19 Edge:disable
Client Density:0 Valid neighbors: 33 Relevant neighbors: 4 Rx Probe Reports: 191
Moves(T/S):0/0 Sticky(T/S):0/0 Bandsteer(T/S):0/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:b1:3d 172.18.10.70 30 93 11/15 0 4/42
9c:1c:12:ca:b5:d1 172.18.10.52 17 101 11/15 0 1/24
9c:1c:12:ca:ac:80 172.18.10.112 21 101 11/15 0 2/29
9c:1c:12:ca:aa:75 172.18.10.137 10 99 11/15 0 5/43
9c:1c:12:ca:b1:4a 172.18.10.92 10 99 11/15 0 2/40
9c:1c:12:2a:e3:00 - - - - - - -
9c:1c:12:ca:b2:50 172.18.10.81 15 95 11/15 0 3/31
9c:1c:12:2b:81:00 - - - - - - -
9c:1c:12:ca:ac:8e 172.18.10.185 14 99 11/15 0 3/24
9c:1c:12:ca:b0:d5 172.18.10.142 11 107 11/15 0 5/34
9c:1c:12:ca:bd:9b 172.18.10.151 41 81 6/15 0 4/36 Yes
9c:1c:12:ca:aa:06 172.18.10.97 23 98 6/15 0 6/33
9c:1c:12:ca:bd:86 172.18.10.62 33 97 1/15 0 5/33
9c:1c:12:ca:b5:cf 172.18.10.55 29 88 11/15 0 4/45 Yes
9c:1c:12:ca:ac:ea 172.18.10.162 11 106 11/15 0 1/41
9c:1c:12:ca:ad:05 172.18.10.64 36 93 6/15 0 3/37
9c:1c:12:ca:ac:74 172.18.10.95 38 87 1/15 0 3/30 Yes
9c:1c:12:ca:ab:88 172.18.10.85 12 105 11/15 0 5/47
9c:1c:12:ca:ac:b9 172.18.10.149 18 98 6/15 0 7/43
9c:1c:12:ca:b0:55 172.18.10.148 19 102 1/15 0 7/30
9c:1c:12:ca:c0:6b 172.18.10.141 34 89 6/15 0 7/35 Yes
9c:1c:12:ca:b6:18 172.18.10.68 21 101 1/15 0 3/48
9c:1c:12:ca:a9:83 172.18.10.61 24 98 6/15 0 5/39
9c:1c:12:ca:b5:e3 172.18.10.87 23 93 1/15 0 4/32
9c:1c:12:ca:b1:0c 172.18.10.60 0 99 1/15 0 4/51
9c:1c:12:ca:bd:ed 172.18.10.113 19 103 1/15 0 3/35
9c:1c:12:ca:ab:cd 172.18.10.156 5 103 11/15 0 3/51
9c:1c:12:ca:b6:8c 172.18.10.153 12 108 6/15 0 4/43
9c:1c:12:ca:ab:fe 172.18.10.183 8 101 1/15 0 5/45
9c:1c:12:ca:ae:48 172.18.10.163 23 102 1/15 0 7/47
9c:1c:12:ca:b6:69 172.18.10.69 4 106 11/15 0 3/41
9c:1c:12:ca:bd:e1 172.18.10.71 13 97 1/15 0 6/42
EXT-11:7b:3c 172.18.10.110 0 105 1/15 0 5/29
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

AP:9c:1c:12:ca:ac:4d MAC:9c:1c:12:2a:c4:d8 Channel:40 EIRP:21 Max EIRP:22 Edge:enable
Client Density:0 Valid neighbors: 18 Relevant neighbors: 1 Rx Probe Reports: 47
Moves(T/S):5/0 Sticky(T/S):2/0 Bandsteer(T/S):3/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:b6:18 172.18.10.68 22 109 108/21 0 0/20
9c:1c:12:ca:c0:6b 172.18.10.141 32 98 60/21 0 2/19
9c:1c:12:ca:bd:9b 172.18.10.151 31 92 132/21 0 1/17
9c:1c:12:ca:b5:e3 172.18.10.87 10 107 132/21 0 2/15
9c:1c:12:ca:bd:86 172.18.10.62 28 101 60/21 0 1/14
9c:1c:12:ca:ad:05 172.18.10.64 28 93 124/21 0 1/13
9c:1c:12:ca:b5:cf 172.18.10.55 24 103 108/21 0 1/27
9c:1c:12:ca:b1:3d 172.18.10.70 28 98 124/24 0 0/18
9c:1c:12:ca:ac:8e 172.18.10.185 7 110 124/21 0 0/10
9c:1c:12:ca:aa:06 172.18.10.97 19 101 36/21 0 2/17
9c:1c:12:ca:b6:8c 172.18.10.153 4 110 52/21 0 3/18
9c:1c:12:ca:ac:74 172.18.10.95 42 87 36/21 0 1/15 Yes
9c:1c:12:ca:b1:0c 172.18.10.60 18 108 52/21 0 1/23
9c:1c:12:ca:ac:b9 172.18.10.149 9 106 116/21 0 3/21
9c:1c:12:ca:b1:4a 172.18.10.92 4 116 124/24 0 1/18
9c:1c:12:ca:ac:ea 172.18.10.162 4 112 60/21 0 2/19
9c:1c:12:ca:bd:e1 172.18.10.71 0 109 100/21 0 2/23
9c:1c:12:ca:ac:80 172.18.10.112 7 109 116/21 0 0/9
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

show ap arm state ap-name 9c:1c:12:ca:b5:08

AP:9c:1c:12:ca:b5:08 MAC:9c:1c:12:2b:50:88 Channel:36 EIRP:21 Max EIRP:22 Edge:enable
Client Density:0 Valid neighbors: 11 Relevant neighbors: 0 Rx Probe Reports: 552
Moves(T/S):1/1 Sticky(T/S):0/0 Bandsteer(T/S):1/1 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:ab:29 172.18.10.105 15 109 44/21 0 1/14
9c:1c:12:ca:b2:91 172.18.10.143 14 106 124/21 0 1/14
9c:1c:12:ca:be:12 172.18.10.175 23 99 124/21 0 0/7
9c:1c:12:ca:b6:2a 172.18.10.165 16 110 60/21 0 0/14
9c:1c:12:ca:b6:a4 172.18.10.138 20 92 132/21 0 0/11
9c:1c:12:ca:ab:92 172.18.10.107 8 107 44/21 0 1/25
9c:1c:12:ca:b6:0b 172.18.10.120 12 101 52/21 0 0/19
9c:1c:12:ca:bd:66 172.18.10.132 0 103 124/21 0 2/17
9c:1c:12:ca:af:21 172.18.10.119 11 109 100/21 0 0/23
9c:1c:12:2b:81:08 - - - - - - -
9c:1c:12:ca:b4:67 172.18.10.78 5 112 60/21 0 1/22
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

AP:9c:1c:12:ca:b5:08 MAC:9c:1c:12:2b:50:80 Channel:1 EIRP:15 Max EIRP:19 Edge:enable
Client Density:0 Valid neighbors: 28 Relevant neighbors: 2 Rx Probe Reports: 552
Moves(T/S):1/0 Sticky(T/S):1/0 Bandsteer(T/S):0/0 Loadbal(T/S):0/0
Neighbor Data
-------------
Name IP Address SNR (dB) Path Loss (dB) Channel/Pwr Neighbor Density Neighbors (R/T) Relevant
---- ---------- -------- -------------- ----------- ---------------- --------------- --------
9c:1c:12:ca:ad:37 172.18.10.111 8 102 1/15 0 2/28
9c:1c:12:ca:b2:91 172.18.10.143 27 93 1/15 0 3/47
9c:1c:12:ca:ac:10 172.18.10.140 16 100 1/15 0 4/38
9c:1c:12:ca:b6:a4 172.18.10.138 29 90 1/15 0 5/41
9c:1c:12:ca:b1:57 172.18.10.176 10 105 1/15 0 3/27
EXT-10:65:b8 172.18.10.109 20 95 1/15 0 9/40
9c:1c:12:ca:b4:67 172.18.10.78 13 105 1/15 0 4/35
9c:1c:12:ca:ab:29 172.18.10.105 28 97 6/15 0 3/32
9c:1c:12:ca:af:21 172.18.10.119 25 95 6/15 0 2/52
9c:1c:12:ca:b6:2a 172.18.10.165 19 96 11/15 0 2/30
9c:1c:12:ca:aa:9a 172.18.10.145 6 103 1/15 0 0/46
EXT-09:7a:c2 172.18.10.189 27 87 6/15 0 6/38 Yes
EXT-11:7b:3c 172.18.10.110 8 97 1/15 0 5/29
9c:1c:12:ca:be:12 172.18.10.175 26 89 11/15 0 4/27 Yes
9c:1c:12:ca:b6:b7 172.18.10.99 4 106 1/15 0 1/26
9c:1c:12:ca:ab:d5 172.18.10.168 13 105 6/15 0 4/35
EXT-13:7a:fc 172.18.10.57 5 106 1/15 0 6/21
9c:1c:12:ca:b5:e7 172.18.10.166 20 100 6/15 0 3/26
9c:1c:12:2b:81:03 - - - - - - -
9c:1c:12:ca:b6:0b 172.18.10.120 16 98 11/15 0 5/51
9c:1c:12:ca:bd:66 172.18.10.132 18 103 1/15 0 3/36
9c:1c:12:ca:b4:e5 172.18.10.125 12 97 11/15 0 4/50
9c:1c:12:ca:ab:88 172.18.10.85 10 107 11/15 0 5/47
9c:1c:12:ca:ac:8f 172.18.10.139 13 98 6/15 0 6/44
9c:1c:12:ca:b5:3d 172.18.10.155 6 104 6/15 0 5/42
EXT-08:65:a4 172.18.10.178 15 95 11/15 0 6/43
9c:1c:12:ca:c1:bc 172.18.10.171 7 102 1/15 0 2/30
9c:1c:12:ca:ab:92 172.18.10.107 0 106 11/15 0 2/35
Legend: R = Relevant, T = Total, Neighbor Density = (Overlap/Neighbor's Density/ Overlap to local density ratio/ Overlap to neighbor's density ratio)

 

Okay.  Your Density is too high, so the power needs to be lower on your access points.  In addition, I would consider removing the lower rates.  Before you do that, on the controller GUI, go to Dashboard> Performance.  There are two sides to the page.  Take a screenshot of the "AP" side of the page and post it here...  That will show us your RF utilization at this time.

To be clear, in a network with the best performance, an access point should not be able to see another access point on the same channel, because it would cause contention and a reduction in performance.  In the 2.4ghz band, since there are only 3 channels, frequently access points will see each other on the same channel.  The only thing you can do is (1) lower the transmit power (2) remove some transmit rates in your SSID profiles.

 

I am asking for the screenshot because the channel utilization chart will tell us how your entire network is doing..

your advice which power ?

 

the issues if we lower the power that we are not able to get wifi over the big walls..

The strange things is that the client could works 2 or 3 hours during the time without any issues... and lost few minutes of network and go back to the network without any issues..

 

I removed the lower rates 

Is the fairtimes airness be able to improve the situation ?

The "show ap arm state" command shows how many APs an individual AP can see.  Every AP that it can see on the same channel degrades its performance.  If an AP can see 10 APs, a client can see at least 5 and you can drop the transmit power by 3 db to 12.  Your Channel utilization is between 50 and 60 for 17 access points, which is too high, especially with the small amount of clients you have on your network.  You can afford to drop the maximum transmit power to 12.

 

With regards to removing the lower rates, you need to do that for all of your SSIDs, not just one...

Lastly, run the "show ap arm state ap-name" command for those 3 APs again after you change the maximum transmit power to 12 to compare the difference.

it's means that on the ARM profile i need to lower the MAX power from 21 to 12 ? and the min from 15 to 9 ?

 

If we do that, we are going to decrease the coverage of the network ?

 

And why we need to remove the lower rates to all the SSID ? we could get some side effect if not ?

 

(sorry with my stupid question, i'm trying to inderstand)

21 for the max is too high, period.  You could just lower the min to 12 and the access points will take time to lower to 12. If you make the min and max 12, all the APs will be on 12 and you will get an immediate result that you can test right now.

 

Lowering the power will make fewer APs see each other and reduce your contention and co-channel interference.  Removing the lower rates allows the APs that must see each other communicate at a higher rate, and lowers contention as well. 

 

After you make the change, get another screenshot of that Dashboard page to see how the RF utilization has changed.  If you do not have any coverage issues, now, you should not have any coverge issues just by lowering all of the APs 3 db to 12.  All the APs are at 15 right now, which means they would go lower if they could...

Thanks for the very clear information :)

 

However, couples of days ago the min power value was 9 and we experiencing the same behavior. ( drop connection for a few minutes)...

 

 

 

 

Start with 12 as the min/max.  Measure how many access points an android device can see by running the Aruba Utilities App here:  https://play.google.com/store/apps/details?id=com.arubanetworks.arubautilities

 

5 minutes after you make the change, take another snapshot of the Dashboard > APs page to see if your utilization has dropped.

ok i'll do it tonight.

 

Is it the cause for the client dropped ( connected to the wifi but not able to past data on the network) ?

 

Because with the last min setting ( 9 ) same behaviour

It could definitely contribute to it.  You also did not have "drop broadcast and multicast" enabled at the time.  You also did not remove the lower rates.  With your density, you have to do multiple things besides lower the power to make improvements.  You need to use the Dashboard> RF Utilization as your guide to see how you are dealing with contention.  You also need to run "show ap arm state" for those same 3 access points after you change the power to see how that changes...

thanks for the information

 

And what about the Airtime fairness ? it can play a role on this issue ?

 

On internet i founded yes... or not..

what's your opinion ?

Remove airtime fairness if you have it configured.  It will distort actual performance when you are trying to fix an issue.

To be clear, Airtime fairness does not create capacity; it just shifts capacity from one type of client to another.  If you do not have capacity because of contention, you need to increase capacity by lowering contention, otherwise things like Airtime Fairness will not help.

oh ok thanks.

i didn't enable it it's just question and i founded it on RF best practices guide of aruba 

 

https://community.arubanetworks.com/aruba/attachments/aruba/Aruba-VRDs/28/1/RF%20and%20Roaming%20Optimization%20for%20Aruba%20802.11ac%20Networks.pdf

 

are there any good things to do regarding my issue?

I already told you the things you can do and how to measure the changes you made.  Those are probably the only changes we should make right now based on your current situation.  Lets do those first and then consider others later based on how things improve.

i've put the lower to 12 just now.

(on just 2min some AP moved to 12)

 

i'll let you know in a moment...

If you only changed the lower, it will take some time for the APs to move to 12 from 15, so the effect will be much more gradual.  It could take a great deal of time for all APs to even consider moving lower.

sure, but some critical apps are running on the network... i would like to go steps by steps... it could takes a couples of hours, my big test is going to be during the night 

 

Now 22 AP's moved to 12

 

I just get the same issues... the phone get disconnected during 20s and back to the network...

 

is it cause the interference that the TTL can be from 10ms to 150ms ?

 

 

20 packets lost... and back to the network...

Is that device a phone or a laptop?

What band is it on?

 

 

Also, if only a few APs are on 12, the changes will only be felt in those areas.

 

it's on some phone, no issues with laptop

 

How i can get the band ?

55ap's now see the screenshot

when i've got the issue, the show datapath session table is empty..

 

but the phone is connected to the wifi ...

- Are you using encryption on that SSID?

- How many SSIDs are you broadcasting?

- Did you enable Drop Broadcast ad Multicast on all of your SSIDs?

- What kind of phone is that?

 

the RF utilization is moving in the right direction..

 

Below the answers :

 

- Are you using encryption on that SSID?

-> WPA2-PSK/AES

- How many SSIDs are you broadcasting?

->4

- Did you enable Drop Broadcast ad Multicast on all of your SSIDs?

-> yes on all SSID

- What kind of phone is that?

-> Android based

If all the APs in the area of that phone did not drop their power to 12 already, we cannot rule out congestion being the issue...  Having more SSIDs increases the RF contention, even without clients because it consumes airtime to broadcast SSID availability.  To find out which SSID is the least used, I would type "show ap essid".

100AP's move to 12

 

show ap essid

ESSID Summary
-------------
ESSID APs Clients VLAN(s) Encryption
----- --- ------- ------- ----------
employe 130 11 40 WPA2 PSK AES
rtls 130 1 20 WPA2 PSK AES
VoIP 130 56 30 WPA2 PSK AES
guest 115 10 50 WPA2 PSK AES
Num ESSID:4

It looks like all of your APs are used equally.  You still have almost 100 APs to go, right

 

Reducing the power is probably the only thing that you can do to make things better.  We need to let that take effect. If that specific client is the only thing with the problem, we should look at figuring out if that client is the problem.  If multiple devices are still having a problem, it is the wifi or the network and we need to figure it out.

 

Make sure you don't have a simple issue like that client being assigned an ip address that a statically addressed client like a server or router has.  Make sure the role that your clients have are completely open (allowall), or that they are not blocking DHCP in any way.

 

ok, i'll reduce the power to 9 and see what's happened

 

i'm also remove the lower rates to all SSID ( now just one )

 

the roles looks clean... the client only gets IP over the DHCP not overlap with some server

 

 

So, you can leave the minimum tx power at 12, but remove all of the lower rates.  We should only change one thing at a time, really.

i'm in it :)

 

And if on 2h i've got 50/60 AP's to 9 ? i need to lower to 6 ?

Okay.  We changed the Min TX power to 12.  We should leave it there and see if all the APs end up at 12.  Anything below 9 could cause issues with clients.  You can remove the lower rates on all the SSIDs, wait a couple minutes and then get a screen print of the dashboard with RF utilization.

min at 9 

 

and attached the lower rates settings did on all SSID

29 AP's moved on power 9

here the all and the 2.4ghz

 

the situation looks better, isn't it ?

Much better.  Below is the first screenshot and the last screenshot:

 

yes ! much better!

 

The final test is tonight... i'll let the ARM process to work by itself to ajust to power of the AP's.

 

i hope that the situation regarding my connectivity issue will be better

 

i'll you know :)

 

However, many many thanks for your time and your well advices !

 

now 50 AP's move to 9, and it's right that below 9 we could get issues with the clients ?

i've observed a better TTL on the clients... not the whole but it's on the right ways...

hello, 

 

Feedback after the night, the communication looked better during the night !

 

However, after all the changes yesterday two devices were not able to communicated on the network ( connected to the wifi but no ping or data...) after a reboot of the devices everythings were ok...

 

And i can explain this...any idea ?

Which two devices?  Are they communicating now?

after a reboot yes...

 

i'm scrare do get this issues again ...

What operating system and wireless card did the two clients have?

Android 7.0...

 

What SSID were the clients connecting to?

 

101 AP's move to 9 for the power

VOIP SSID

The APs moved to 9 because you had alot of congestion.

 

What provides DHCP on the VOIP SSID?

your're right !

 

It's a Classic Windows server.

 

the users gets access over a :Voip-acess-role which allows the DHCP polices, see the capture

 

 

Delete all of your DHCP acls and replace it with :

 

 

If you use anything else, it will create problems on DHCP renewal.  That could be the cause of the intermittent problem you are having..

 

 

this document gives another information :

https://community.arubanetworks.com/t5/Controller-Based-WLANs/What-is-the-purpose-of-denying-UDP-68-traffic/ta-p/177728

 

!?

the lease of the DHCP is few days....

---

@Michael-dc wrote:

the lease of the DHCP is few days....

---

Yes, but according to the DHCP standard, clients should try to renew when the lease is halfway.

 

I'm not saying that all your clients are having this problem, but change the ACL to make sure they are not having the problem.

ok i've got it.

 

But my DHCP rule is smiliar to the any / any to be sure to get it correctly ( again sorry for the stupid question...but if i've never ask... i'll never learn :) )

What's is the difference ?

- The ligne : any to 255.255.255.255

- User instead of any

 

the both lines can makes the difference ?

---

@Michael-dc wrote:

ok i've got it.

 

But my DHCP rule is smiliar to the any / any to be sure to get it correctly ( again sorry for the stupid question...but if i've never ask... i'll never learn :) )

What's is the difference ?

- The ligne : any to 255.255.255.255

- User instead of any

 

the both lines can makes the difference ?

---

The initial DHCP request is a broadcast.  DHCP renewals are typicaly unicast to the DHCP server (the destination is not 255.255.255.255).  You can avoid any problems just by using the "allowall" ACL or "any any svc-dhcp permit"

The only two lines you would need are:

 

user any udp 68 deny
any any svc-dhcp permit

 

 

The first line blocks clients from acting as a DHCP server and is optional.

i've got the same rule for the logon and the Access roles

 

i need to ajust the both ?

---

@Michael-dc wrote:

i've got the same rule for the logon and the Access roles

 

i need to ajust the both ?

---

How many access roles do you have?  Do you need anything besides  an allowall rule?

 

What devices use the rtls SSID?  There was only a single device on there...

 

 

How many access roles do you have?  Do you need anything besides  an allowall rule?

 

-> for the login or access roles ?

 

 

 

You have 4 SSIDS, correct?

Which SSIDs have you had the intermittent connection issues with?

 

the VOIP only on Android which roams alot...

only Android are on this SSID

 

One other SSID using the same DHCP with the same rules without any issues

screenshot on PM

Thank you for the screenshot.

 

On the controller, when you go to Monitoring> Controller> Clients, what role is in the "user role" column?

 

On the commandline, type "show rights <name of role>" and PM me that output.

Sent on PM

Thank you.

 

Your first 2 rules are system rules that allow everything.

Your 4th rule is "allowall", so nothing really matters after that.  You do not have to change anything.

 

Just monitor your network for any problems.

the true is not with the DHCP policies...

 

is it very odd behaviour...

 is it cause the device roams alot ?

client match behaviour ?

 

the controller put the device on "sleep mode" ?

 

 

Are you still having problems after we made the changes?

the changes with the power and the lower rates ?

 

-> Yes just on the tow devices

 

Since now

-> nobody tell me something... but it could happen now or in a couples of hours..

 

What's your opinion about this behavior ? config on the client ? a timeout on the controller ? a side effect following the changes made yesterday.?

tow?  Android devices?

 

How often has it been happening since the changes?

i've just the information of one time on the both devices ( after the changes) and i suppose one time during the night ( like 10min of backout ) and the devices go back to the network

 

but the user may restart the devices by itself...

 

odd behaviour that it's very hard to catch it....

Turn on user debugging:

 

config t

logging level debugging user

exit

 

When you have a problem, type:

 

show log user all

 

 

ok i'll let you know once i've can test and catch the issues..

 

However, no risks to enable to log on it ? how many time the log stay on the controller ?

( no issues get a full memory ?)

 

 

The logs will roll over.  You can point the logs to a syslog server so that it can retain more:

 

config t

logging (ip address of syslog server)

good idea about the syslog.

 

i'll install it if i'm not able to catch the issue..

 

However, did you get the PM message about the LED ? Could be related to the issue or not ?

That would be if you are running a WEP or WPA-TKIP SSID on one of the radios.

the main SSID is : WPA2-PSK/AES

 

It's somethng related to the "n" which my major clients are runinng on the "n"

It could also be a bug.  I would reboot that AP..

it could be on the major of the AP ?

I don't understand....  It could be just a bug...

After applying some best practices,  the issues was fixed by deactivated the CSD override option.

 

Many thanks Joseph for you precious help !

Running "show log wireless 10" repeatedly will tell you what APs changed power or channel..

Dec 21 17:21:42 :404074: <WARN> |AP 9c:1c:12:ca:c0:44@172.18.10.102 sapd| AM 9c:1c:12:2c:04:40: ARM - increasing power cov-index 4/0 tx-power 4 new_rra 1/5
Dec 21 17:23:40 :404075: <WARN> |AP 9c:1c:12:ca:aa:75@172.18.10.137 sapd| AM 9c:1c:12:2a:a7:50: ARM - decreasing power cov-index 25/1 tx-power 4 new_rra 11/3
Dec 21 17:24:51 :404085: <WARN> |AP 9c:1c:12:ca:b1:0c@172.18.10.60 sapd| AM 9c:1c:12:2b:10:c8: ARM HT Channel Interference Trigger new 132+/35 old 52+/76 new_rra 132+/7 TCI 6
Dec 21 17:24:52 :404075: <WARN> |AP 9c:1c:12:ca:ad:06@172.18.10.88 sapd| AM 9c:1c:12:2a:d0:60: ARM - decreasing power cov-index 15/0 tx-power 4 new_rra 11/3
Dec 21 17:25:42 :404075: <WARN> |AP 9c:1c:12:ca:af:a0@172.18.10.93 sapd| AM 9c:1c:12:2a:fa:00: ARM - decreasing power cov-index 12/1 tx-power 4 new_rra 6/3
Dec 21 17:26:00 :404075: <WARN> |AP 9c:1c:12:ca:ac:a7@172.18.10.124 sapd| AM 9c:1c:12:2a:ca:70: ARM - decreasing power cov-index 9/0 tx-power 4 new_rra 11/3
Dec 21 17:28:20 :404075: <WARN> |AP 9c:1c:12:ca:be:ac@172.18.10.126 sapd| AM 9c:1c:12:2b:ea:c0: ARM - decreasing power cov-index 11/1 tx-power 4 new_rra 11/3
Dec 21 17:28:55 :404075: <WARN> |AP 9c:1c:12:ca:b6:8c@172.18.10.153 sapd| AM 9c:1c:12:2b:68:c0: ARM - decreasing power cov-index 21/9 tx-power 4 new_rra 6/3
Dec 21 17:29:05 :404075: <WARN> |AP 9c:1c:12:ca:b6:e1@172.18.10.173 sapd| AM 9c:1c:12:2b:6e:10: ARM - decreasing power cov-index 21/11 tx-power 4 new_rra 1/3
Dec 21 17:29:13 :404075: <WARN> |AP 9c:1c:12:ca:b2:50@172.18.10.81 sapd| AM 9c:1c:12:2b:25:00: ARM - decreasing power cov-index 19/9 tx-power 4 new_rra 11/3

Rf utilization screenshot, please?